@mattcropp @Matt_Noyes I made another flowchart, to reflect the process described on the call - however, we didn't really talk about what happens at the end. I feel that if the Community Ops Team decides not to involve the Standing Jury in the decision, it shouldn't then have to make a report to the main group. Instead, it should report to the Jury, who will take it further if necessary?
Nice -- at the risk of making the flowchart too big, there is an emerging soft resolution flow, which includes the option of escalating to the "hard" process laid out here. https://pad.disroot.org/p/Social.Coop_Conflict_Resolution_Guidelines_v1
I started a pad https://pad.disroot.org/p/Reporting_Process_Notes#
What do you guys feel is next?
I think the pad content is great. I made one suggestion. For now, maybe we have to wait to see what shape the Reporting Guidelines and Conflict Resolution process end up taking??
@Matt_Noyes @mattcropp Ah, fair enough. Yes, it's waiting on the Guidelines and Conflict Resolution process, but the Report form itself, the rotating ops role, and the anonymous reporting are separate.
I thought we were trying to get a proposal done in the CWG by 08/16-08/21. But there's a ten day timeline in the taskforce agenda, but not in the same section as teams/actions. To be honest I was struggling to hear at the end of the call - is there a date set for the next big step/proposal?
social.coop is a cooperatively-run corner of the Fediverse. The instance is democratically governed by its members, who generally share an interest in the co-op model, but topics of discussion range widely.
Our instance is supported by sliding scale contributions of $1-10/mo made via Open Collective. You must have an active Open Collective account to apply for membership; you may set one up here