-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Who controls the CoC? #7
Comments
👍 |
??? |
+1 |
This is my +2 It's been 22 days and no clear answer. |
That's because there is no answer yet. Please feel free to submit ideas. See #14, #15. The answer I personally seem to levitating towards involves a legislative branch (an elected board, whose job it is to take input from community and set policy) and executive branch (Facebook admin/mod team, whose role it is to enforce that policy). Notably, in my version, the legislative branch does not actually have admin powers (they're not on Hackbot/Facebook mod) enabling a clear separation of concerns and limiting the possibility for tyranny: as it is merely the Facebook/Hackbot mod team's responsibility is to enforce the policies set by the board, they can't simply decide to do something else or something that is contrary to policy because they will be held accountable. Also allows general members to raise concerns and a procedure for implementing new rules, without popular-vote factions dictating policy at the expense of minorities (it is the board's job to consider all parties when making a decision, since the majority aren't likely to support things that don't benefit them.) This would also be useful if we chose to incorporate, see #12, as that's the structure of most NPOs. (Board decides high level concerns/policies, employees + volunteers execute.) |
My understanding is that the elected moderators are essentially HackBot janitors and the
onetwo admins (including the one super-admin...) are the ones deciding on policy. Supposedly the super-admin is only there to make sure people are removed after serving their terms, so that leaves one person in control of the actual policy being enforced, which sounds plain awful.The text was updated successfully, but these errors were encountered: