RFC: Fedora Community Working Group charter (draft)

Rex Dieter rdieter at math.unl.edu
Tue Oct 19 18:31:58 UTC 2010


Kevin Fenzi wrote:

> So we have:
> 
> FAmSCo: ambassadors community issues.
> FESCo: package maintainer / SIGs community issues.
> irc-support-sig: IRC community issues (#fedora/#fedora-social only)
> Other irc admins: their particular #fedora* channels
> Hall monitors: mailing list issues
> Moderators of other mailing lists: their mailing list issues.
> Websites sig: planet
> 
> In some cases, handling issues close to the source works well, as that
> community understands it's communication channel and issues with it. In
> other cases it goes poorly, as the people are too close to the problem
> and can't see the issues.
> 
> I could see several ways a CWG _could_ help:
> 
> a) Be a layer above all the above groups. Just a way to escalate an
> issue up and get more people looking at it and seeing how we could make
> the community better or handle it in a better way. This could also
> cause some friction as the above groups may feel the CWG is usurping
> their authority. It could also be good for some groups as that would
> give them a place to tell people to escalate to. It could make users
> happier that their concerns were heard by a larger group, even if no
> action was taken.
> 
> b) We could replace all the mediation/escalation process of the above
> groups with a single CWG stop. The downsides here would be that it
> could be a lot of work, day to day stuff would still need to be handled
> by the particular group. On the plus side people would have one place
> to come with concerns or to be heard. Groups may not want a CWG to tell
> them how to mediate concerns directly however.
> 
> c) Help where needed. This could be mixed with a) above, but just have
> CWG available to help where above groups have concerns or lots of users
> are seeing issues, and where CWG thinks things could be improved. In
> some cases the CWG could see issues in community where above groups
> haven't yet and help smooth things out.

Excellent points.

C (plus a little A where appropriate) is definitely the way to go here.

I have added some language to the draft to consider this as one of the 
group's initial tasks.

-- Rex




More information about the advisory-board mailing list