# Karrot newcomer ## Understand the need ### Understand the context: What is the trigger and the underyling issue - initial prompt about trial pick-ups - especially foodsharing groups require a number of trial pickups (e.g. 3) from applicants as part of the on-boarding process - one way to do the on-boarding is outside the actual karrot group (e.g. with a second group or spread sheet). Once the requirements are met (trial pick-ups are done), people are accepted to the group - makes on-boarding more complex - some pick-ups are more suitible for trial pickups than other (e.g. because the store is easy-going/ the people in the team are very welcoming). Currently there is no way to show which slots are good for applicants/ newbies - for some pick-ups it would be nice to be more specific what is needed: e.g. 1 person with big transport capacities, 2 with smaller capacities - other example: for cycling without age it's crucial to get a training on how to ride a rickshaw (and an introduction to the setup: where are keys, the garage etc.) before riding the rickshaw. - once a person entered the karrot group, this person can volunteer to any open slot, there is no way to control signing up based on requirements other than social control - requiremets my vary from activity to activity e.g. pick-up vs cleaning foodshare point - the step from applicant to accepted is quite big - applicant: can't see anything, only chat throught application - accepted applicant: can see everything/ write everywhere/ sign up for anything ### Explore needs: What do you think this is really about for everyone involved? - make on-boarding process less complex - have the software supporting on-boarding - make a coherent story with past ideas - not only think about newcomers but other positions within karrot - evaluate trust system (newcomer/ editors) - look for a approach which also works well from a code perspective ### Needs Statement: We synthesize what we know about the needs and consent **We want to support an on-boading process in the software. We want a more advanced way to configure activities. We want to build on excisting ideas and don't add massive changes on a code level.** ## Generating a proposal ### Understand the scope - picture forming: What questions will we have to answer? - At what point is an applicant accepted - How to go about the trust system - How are trial-pickups integrated - different permissions within a group - What effect does an implimetation has on excisting groups? - Participation in conflict resoluation - ... maybe more ### Explore ideas -- proposal shaping: Suggest proposal pieces Have something before applicants are accepted → doesn't seem to be worth exploring this more Accept applicants to group and having trial-pickups within group - enhance excisting trust system - how it is now: different levels of rights/ permissions - can join activties = newcomer - can join activties & can edit everything = editor - possibility to limit activities to newcomers - can join newcomer activities = newcomer - can join non-newcomer activity and edit everything = editor - introduce another in-between step - can join newcomer activities = newcomer - can join non-newcomer activity = approved - can join non-newcomer activity & can edit everything = editor - other names: - newcomer = newcomer - approved = member - editor = member with editing rights - other names part 2 - newcomer = newcomer - approved = member without editing rights - editor = member - other names part 3 - newcomer = newcomer - approved = member - editor = editor - level of permission depents on number of trust karrots - newcomer= 0 - approved= 3 - editor = 5 - other idea for number of karrots - newcomer = -2 - approved = 0 - editor = 3 - the number of newcomer karrots can be set as a group setting - if number of newcomer karrots is 0, the applicant enters as approved (=status quo) - what is displayed when giving trust - newcomer → approved: karrot seeds or little plant - approved → editor: karrots - prompt users to give trust in more places - integrate into feedback step after activity is done - change trust system that only approved or editors can give trust - show permission status in profile - terminology (what the number of karrots influences) - permission - trust level - group role - status - position - rights - permission level - badge - user level (as used in https://community.karrot.world/t/info-karrot-trust-system-and-user-levels/108) - not only have trial-pickups, but be more flexible in the design - different types of activity slots with custom description - have trial-pickup as activity type and count them in users profile. As soon as a certian number is reached something happens - second „currency" along trust system - manual override if person misses trial pickup - don't make change from newcomer to approved based on karrots - manual approvement from one editor needed - once a person is approved the karrot trust system comes to play - don't make change from newcomer to approved based on karrots - automatic approval after number of trial pick-ups is reached - don't introduce limits like „read-only" as another type of permission - only have different activity types but no software logic on who can sign in, display newcomers in another color so there is general awarnes a person is new - color goes away once editor level is reached (by trust) - change trust system into „trust for role" or „trust per right" - trust to join pick-ups - trust to be editor - more..? - changes to trust system - giving trust in the context of a role and a place - „I trust X to join pick-ups in place Y" - having some "badges" (custom-made defined on the group level) on the avatar and profile of a user, they would not be *necessarily* connected to any trust system - defined at the group level and self-assigned - don't let newcomers vote in a conflict resolution process - save the word „role" for group-oriented roles like coordinator, ambassador, social-media-person or whatever - these roles should come with a describtion, a term and a group process how they are filled (software-based or ofline) - group-oriented roles are a group agreement More ideas\... - in the group settings the newcomer-feature can be turned on or off - When turned **off** - there is still an advanced mode for activites to describe participant types - only 2 levels of permission are active - **user**: can join activity - editor: can join activities & edit places and the group - note: what was ‚newcomer' before is now ‚user' - therefore activities can not be limited to a certain level of permission - When turned **on** - the trust system features 3 levels of permission - everyone can read and write messages, private and on walls - **newcomer**: can join newcomer activities - **user**: can join non-newcomer activities - **editor**: can join non-newcomer activities & edit places and the group - the sign-up for activities can be limited based on the level of permission of the user - when not using the advanced mode for activities, anyone (meaning newcomer, user and editor level) can sign up - when using the advanced mode for activities it is possible - to set activity slots where only newcomer can sign up - to set activity slots where non-newcomer can sign up - note: there is no option for ‚editors only' - when switching from off → on: every existing member keeps their level of permission, every newly accepted applicant is now a newcomer - when switching from on → off: every newcomer ist set to user with 0 trust - how to become **editor**? Get trust karrots from members of the group. A user with 3 trust karrots becomes an editor - how to become **user**? Get trust karrot seeds from members of the group. A user with 3 trust karrot seeds becomes an user. You can not undo trust karrot seeds (se <https://en.wikipedia.org/wiki/The_Carrot_Seed>) . Once user you can get trust karrots (see above). Members who gave you trust karrot seeds are eligible to give you trust karrots too. ### Synthesize proposal ideas - There is the possibiliy to customize activities - you can enter an advanced mode - it is possible to define different participant types with a custom description - e.g. one person with cargo bike, 2 persons helping with sorting - the trust system features 3 levels of permission - everyone can read and write messages, private and on walls - **newcomer**: can join newcomer activities - **user**: can join non-newcomer activities - **editor**: can join non-newcomer activities & edit places and the group - the sign-up for activities can be limited based on the level of permission of the user - when not using the advanced mode for activities, anyone (meaning newcomer, user and editor level) can sign up - when using the advanced mode for activities it is possible - to set activity slots where only newcomer can sign up - to set activity slots where non-newcomer can sign up - note: there is no option for ‚editors only' - newcomer can not vote in a conflict resolution process - levels of permission based on group size (also see <https://community.karrot.world/t/info-karrot-trust-system-and-user-levels/108>) - 1 or 2 active group members - ~~ **newcomer**~~ - **user**: 0 trust needed - **editor**: 1 trust needed - 3 or 4 active group members - **newcomer** - **user**: 0 trust needed - **editor**: 2 trust needed - 6 or more active group members - **newcomer**: 0 trust - **user**: 1 trust needed - **editor**: 3 trust needed - note: the newcomer level becomes only relevant starting with a group size of 6 ## Future steps Making a decision: Preparing the decision Understand the proposal: claryfying questions Explore reactions (quick reactions) Synthesizing quick reactions: facilitator needs to assess whehe the proposal is ready Making a decision: Decision Re-state Proposal Conset Round Acknowledge consent/ objection Making a decision: Publish decision Plan publication Prepare materials Publish