Issue #5: Fedora join FAS group membership kinks - Fedora-Join

fedora-join / Fedora-Join

#5 Fedora join FAS group membership kinks

Closed: Fixed Sep 26, 2018 Opened May 14, 2015 by ankursinha.

How does someone join the FAS group? Who is the group for?

The group is for existing fedora contributors who want to help out. They should be part of at least one (release contributing?) team to be eligible?
They need to have introduced themselves on the mailing list before group membership is approved (this ensures that the ML is aware of who the contributors are). Mailing list membership and introduction e-mail should be compulsory IMO.
Do we need an template for the introduction e-mail - a set way in which people can introduce themselves - telling the list what they're good at and how they can help?
It'll be nice if they can also hangout on the IRC channel, although I wouldn't make this compulsory.
Inactivity would result in removal from the FAS group in a period of time? Per release maybe? Two reasons for this:
To produce metrics - number of contributors helping + number of newbies that asked for help + number of newbies we helped
To prevent stagnation of the group - we need the contributors to be active - to approach newbies that come for help - not passive and wait for newbies to start the conversation (newbies are generally shy and often scared of asking questions)
Add more here!

immanetize commented May 14, 2015

Yes, I think SIG membership should require participation in at least one other group. fedora-join should be experienced contributors helping new ones, we want to avoid a blind-leading-the-blind situation. FAS doesn't feature a "cla_done +1" prereq as far as I know, but sponsors should be trusted and expected to use their judgment.
+1 for compulsory introductions. We should supply an [optional] SIG member introduction template for this, which would be useful across the project. Ticket inbound.
+1 for a general introduction template. Ticket Inbound.
Definitely advertise the IRC channel, but if there are alternative approaches, all the better. SIG-facing copy should say ie "If you're doing something not covered, share your methods!"
I'm in favor of removing inactives, but have no idea how to fairly implement that in an automated manner. A datagrepper query, followed by a real person sending a "Are you still there?" email, maybe? Ideally, SIG sponsors should be following the activity of those they sponsor, and offering guidance to those that might be struggling to participate.
More coming, probably.

ankursinha commented May 21, 2015

This is another thing we need to figure out before I send out the invitation e-mails.

ankursinha commented May 21, 2015

So, we're thinking:

Sponsorship guidelines:
- CLA +2
- Active in Fedora for at least one full release cycle (this ensures that they're aware of the workflows of the groups they're part of)
- ML subscription
- Clean up each release - we'll find a datagrepper way to do this like the ambassadors do - perhaps activity on fedora-join channels can also be taken into account - this isn't very important right now IMO - depending on how much activity we manage to generate, this can be decided later.

What say everyone?

Metadata Update from @dhanesh95:
- Issue tagged with: next-meeting

Aug 21, 2018

x3mboy commented Sep 25, 2018

+1 to the guidelines. CLA +2 is a must, just being, e.g. an Ambassador, doesn't mean that you are able to help anyone to join any other team. I think we, the core members, should be the contact point that Ambassadors use at events to guide people inside the community.

ankursinha commented Sep 25, 2018

Added a section on the wiki page here: https://fedoraproject.org/wiki/SIGs/Join#Membership Closing.