Monday, September 12, 2016

Re: IRC SIG needs external oversight

> Some suggestions for #fedora:
>
> - My suggestion here would be that if any OP has had multiple complaints filed against
> them in the ticket system - there's probably been many other CoC violations the
> victims didn't bother to file - and they really should retire and recover from their
> burnout before trying again.
>
> - Op status is *not* a status symbol, it's a responsibility, and it seems like a lot
> of people wield IRC ops not due to any actual personal responsibility but rather because
> they were around when the Fedora project was in its early days and have held on to it
> since then - not really a good reason to keep them. It should be more like a relay race
> baton, not a certificate you hang on your wall forever.
>
> - A suggestion would be to offer ops to top-rated helpers on ask.fpo and make them
> rotating positions as any other parts of the project (fesco, council, famsco, etc.) are.
> This would also hopefully help combat burnout by giving overwhelmed ops a e asy way to
> gracefully bow out without drama or feeling like a quitter or leaving the other opers high
> and dry without a replacement - just don't run for re-election and let someone else
> step up.
>
> We do get very positive feedback about users' interactions on ask.fpo and use it as
> the main support channel we point people to on our websites. The system has built in
> moderation that allows to keep things more civil than IRC affords.
>
> ~m

+1 to all of this. I don't think that Ask and IRC are so different that it requires different kinds of people to moderate each of them.
_______________________________________________
council-discuss mailing list
council-discuss@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
https://lists.fedoraproject.org/admin/lists/council-discuss@lists.fedoraproject.org

The Fedora Project's mission is to lead the advancement of free and
open source software and content as a collaborative community.

No comments:

Post a Comment