CommOps managing discussion.fp.o?

Thanks @mattdm … regarding the “technical contributors” category, I was referring to this:

Which is basically to create a catch all technical/devel category which functions in much the same way that the devel mailing list currently functions.

Ah, I see. Hmmm, I’m not sure that’s necessarily so useful, since it’s easy to cross-link and move topics between categories. But it’s worth trying. I guess under the “Project Conversations” main category to start?

Yeah, I agree “Project Conversations” would be the appropriate place. What was confusing for me was the only subcategories I see there are “CommOps” and “COPR” - so if you wanted to talk about an issue with fedpkg, dnf, bodhi, koji, etc. there isn’t an obvious place to start the topic.

You should have the power now. Go ahead and create it and we’ll see what happens. :slight_smile:

ok, I’ll give it a whirl… Thanks Matt…

I came back across this thread after a long time. We’ve come a long way since kicking off the Discourse site in June 2019. It could be a good idea to think about moderation guidelines in the context of the ongoing Code of Conduct work too.

No action needed, but I wonder if others have thoughts now that two-ish years passed since we last reviewed moderation guidelines.

1 Like

In the last two years, I’ve developed a strong opinion: there need to be moderation guidelines that are separate from the code of conduct. A lot of moderation should be just routine, and not raise to the level of “incidents”. This is better for the moderators, better for keeping the site running smoothly, and better for gently encouraging good behavior rather than escalating. The CoC needs to be there in the unfortunate event of escalation or ongoing problems, or of course for serious incidents, but most moderation shouldn’t need to invoke it.

1 Like