User story:
When I open a Karrot group, I implicitly decided to accept the ways the software works. As karrot is a software for organising, this directly interacts with my group e.g. how I can manage editors (trust system), remove users (membership review) and so on.
It might be nice to make this relationship between the group and the software more explicit. One idea could be to draft a default agreement which is already in the agreement section of the group. The group could modify the whole agreement/ certain aspects of it to their needs.
Additionally this agreement could contain information on server/ instance configuration, which are otherwise not accessible to group members easily (e.g. time period when users become inactive)
Complexity:
More on a social/ strategic level I’d say
Outcomes (or what needs to be done to move forward):
- continue conversation