On Mon, 30 Aug 2010, Matt Micene wrote:
> > -----Original Message-----
> > From: email@example.com
> > [mailto:firstname.lastname@example.org] On Behalf Of
> > Mike McGrath
> > Sent: Sunday, August 29, 2010 10:42 PM
> > To: Infrastructure
> > Subject: Change with FAS sysadmin-* accounts
> > FYI everyone, I've now changed all the sysadmin groups to be invite
> > only.
> > Lots of users would apply and kind of just sit there for months, and
> > that's not good. So by invite only, one of us has to add users to the
> > groups and sponsor them at that time.
> > -Mike
> Does this dovetail with the "promotion paths" we talked about for some
> of the more critical groups? Getting invited in, being mentored for a
> while and then a combination of the mentee wanting to move up and the
> mentor sponsoring them for a group like -main or -dba.
> So a new user has to show some interest and initiative in the list and
> IRC to get an invite to the main group. And the same to move up to some
> of the higher responsibility groups. It makes sense to judge skill and
> availability, IMHO.
> Course, we run the risk of sounding like Masons ... "The Supreme Council
> of the Infrastructures General of the Project Fedora of the
> Twenty-second degree of the Ancient and Accepted Linux Distributions"
It's certainly like that for -main or -dba. But even for the easier
groups to get into, application for those groups isn't the right way to go.
No one's going to sponsor someone they don't know and haven't worked with
in infrastructure. This just further forces a new user to get to know the
group, look at the tickets, etc while making sure new users don't just
apply and think they're now in the team, or then wait for someone to
I think the application -> then sponsor method would be idea but it
doesn't work in practice.
infrastructure mailing list