I have read in the meeting notes of today’s weekly call that you have also talked about this topic there, so I link it here for easier reference: Weekly call about Karrot development - Date: 2021-01-18 12:00 (UTC+1)
- maybe have 3 trust carrots to get approval, and 5 to get editor (for example, would vary with group size)
While I think the flow
newcomer -> approved -> editor can work, I think this needs more thought.
First, I think it is important to make these thresholds configurable, or, alternatively, have a way for groups to accept or reject such an automatic upgrade. For instance, in our group, people need to do 3 test pickups - and more if they do not turn up.
Second, I imagine new projects emerging in groups, which would ideally be represented by activities. However, a new member would have to transition through the
approved role into the
editor role to be able to create such an activity. In other words, this flow reduces flexibility in the case of different activities’ needs. For example, in our groups, only pickups require trials, whereas you could directly set up and manage a new Foodsharing Point. One option could be to configure what you can do with both
editor roles, which I am not totally convinced of and just put here as I have not had a better idea yet.
Leading back to:
- in the proposal, it’s a bit weird that you could be editor, but not approved (you could then approve yourself…)
While this may seem a bit odd, I think that the group’s history would easily reveal such a misuse.