Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Comments on Drafting the Codidact Arbitration & Review Panel
Parent
Drafting the Codidact Arbitration & Review Panel [duplicate]
Closed as outdated or superseded by ArtOfCode on Nov 21, 2020 at 21:10
This question has been superseded or is outdated. For more up-to-date information, see the linked post. See: Second Iteration of Drafting the Codidact Arbitration & Review Panel
This question was closed; new answers can no longer be added. Users with the reopen privilege may vote to reopen this question if it has been improved or closed incorrectly.
Since Codidact was founded, we have had one rule leading our path every step of the way. It's the rule that community comes first. That the Codidact "staff" shouldn’t overrule the community, but could be overruled by it.
In any community, acts of moderation should be rare. And even rarer is the need to review these decisions. However, there will inevitably be cases where certain situations need to be reviewed:
- Users think that an action (for example, a suspension) is wrong or even malicious.
- A moderator might misbehave and violate our light Code of Conduct or our Terms of Service.
I want to emphasize that there have been no such cases yet, and there will likely (and hopefully) not be for months, if not years. But we can be sure that there will be one at some point in the future. When this situation does arrive, it's better to have an existing process that can be followed to guarantee the best resolution of the conflict rather than coming up with a brand new process on the spot.
It should be clear that such a process shouldn't involve "us" (the Codidact team), but rather "you" (the community). Hence, at some point, it was decided on the old forum that we'd eventually have some kind of review panel, which would be responsible for these cases.
While there will probably be no "panel elections" for the time being, because the panel members would still be a large percentage of our community members (which wouldn't exactly make sense at this stage), we have made a start on the Panel review process. It is based on these three principles:
- The Panel decisions are binding to moderators and the Codidact team1.
- Every party should be heard before any decision is made.
- The Panel shall be independent and impartial.
This process is currently only a draft. We'd like your feedback, and welcome any suggestions for changes to it. Please leave them in answers to this question.
You can find our current draft here.
-
For obvious reasons, there are some legal limits. However, in these cases, we have tried to strike a balance between legal and community interests. For example, in such a case, the Panel may decide to publish our reasons (with private information redacted). ↩
Article 17.1 disallows successive warnings within two years. I don't think that's best. The second malfeasance may be of …
4y ago
Article 27 requires members to explicitly recuse themselves if they feel they can't be impartial. I suggest explicitly a …
4y ago
It might be worthwhile for this document to make it clear which of its provisions about moderators apply to moderators p …
4y ago
Article 30 discusses that substitutes are sworn in if and only if at least 1/3 of the panel is recused. What happens …
4y ago
I propose that we need a clause governing the criteria and process for removing a panel member in the very rare case tha …
4y ago
Some thoughts: - A clarification of the term "community" might be needed. My take is that this is meant to be a Codid …
4y ago
Article 22 says that all decisions are to be published, exclusive of summary judgments. I think it should specify that t …
4y ago
Note: The comments indented as list items have been added by luap42 as a reply. Articles 7, 13 and 20 could be rep …
4y ago
Article 1 discusses each appointee's vote scores. When trust levels are rolled out, will this clause be affected as well …
4y ago
Post
Article 17.1 disallows successive warnings within two years. I don't think that's best. The second malfeasance may be of a different type from the first or a lesser degree than the first, in either of which cases a warning may be warranted. While a second warning within two years may be inappropriate in most cases, we can probably leave it to the panel to decide.
1 comment thread