Skip to content
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

GOVERNANCE.md: Do we need a process to appoint moderators for services other than the forum? #21150

Open
miri64 opened this issue Jan 21, 2025 · 4 comments
Labels
Area: doc Area: Documentation Area: governance Area: Community processes and governance Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation

Comments

@miri64
Copy link
Member

miri64 commented Jan 21, 2025

Currently the GOVERNANCE.md only describes the process to appoint forum moderators since they have special technical moderation powers (editing posts, splitting out discussions into separate topics, blocking users, filtering spam, …). Should we also have also a process for the following services? Should these moderation role also be expanded to the more social responsibilities of moderators?

  • Matrix: Here the moderation powers only go as far as blocking/kicking out users
  • Mailing lists: Here the moderation powers only go as far as filtering spam

Useful links

@miri64 miri64 added Area: doc Area: Documentation Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation labels Jan 21, 2025
@miri64 miri64 added the Area: governance Area: Community processes and governance label Jan 21, 2025
@chrysn
Copy link
Member

chrysn commented Jan 21, 2025

I don't think we need any added process there – there are lots of things that happen in the project that are not "merging a PR" that happen (changing GitHub settings, changing moderators, creating repos, hosting something on tattooine, creating a social media account somewhere) for which I'd rather not have an individual policy.

My impression of how we do all these things today is "when two maintainers agree that it is good and that it doesn't need a broader consensus, they do it" – but I'd not write this down individually, but only as a general policy. That creates the issue of distinguishing this from "how do we make statements as a project" (say, if someone suggested that we add to our readme that we support human rights, which I think is a given, but I predict it'd spawn so much discussion that it doesn't happen). But I trust that if we want to put this down, we'd find a phrasing that draws an arbitrary fuzzy line between everyday chores and making public statements on behalf of the project.

@maribu
Copy link
Member

maribu commented Jan 21, 2025

I think documenting the process has value. If that just is: "Maintainers decide whom to grant the following roles: Forum moderator, ..." that is little effort to write down. People seeking to gain that role then would know where to knock and ask.

How were those roles handed out so far? Let's just write that down with a sentence or two.

@miri64
Copy link
Member Author

miri64 commented Jan 21, 2025

If that just is: "Maintainers decide whom to grant the following roles: Forum moderator, ..." that is little effort to write down.

That's picking the worst example. Especially forum moderators (for which we already have a process described) should be granted by the community at large, not just the maintainers.

@miri64
Copy link
Member Author

miri64 commented Jan 21, 2025

How were those roles handed out so far?

See #21067 (comment). Also added that comment to the Useful links section above.

@miri64 miri64 assigned jkarinkl and unassigned kaspar030 Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: doc Area: Documentation Area: governance Area: Community processes and governance Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Projects
None yet
Development

No branches or pull requests