On Mon, 6 Dec 2010 15:24:31 -0700 Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > On Mon, Dec 6, 2010 at 07:26, Matt Micene <matt.micene@xxxxxxx> wrote: > >> We also need to show the separation between groups, sysadmin, > >> sysadmin-noc, sysadmin-test, sysadmin-main etc. Some groups are > >> going to take a while for someone to get into (sysadmin-releng and > >> sysadmin-main) mainly because it is a matter of trust and work. > >> Other groups are 'easier' to get into but still require trust. > >> Anyway, I would like to get ideas on how e can do this better and > >> move forward. > > > > Speaking of AWOL, I was working with Mike on "job descriptions" for > > the FIGs (for lack of a better term) to help expand the publicly > > available information about the skills sets that were desired. I > > started this b/c I had some issues trying to figure out how and > > where to start contributing. We got about 1/4 of the way done > > before $DAYJOB ate my time and knocked me off IRC. > > > > I'd be glad to pick these back up and get into the hierarchy > > discussion as well. You can see the current state if you hit the > > FIGs page and follow on to any of the FIG names that have links. > > I'd also like to get some input from FIG sponsors on the content. > > > > https://fedoraproject.org/wiki/Infrastructure/FIGs > > https://fedoraproject.org/wiki/Infrastructure/FIGs/FIG_Build_job_description > > > > I have a template for these that I can send round to anyone else > > who is interested. > > > > Hi could you send this to Kevin Fenzi. I think he is hitting this > partially with ticket groups. If we could have a mapping of: componenet in trac == FIG that might be nice. Then we could have each FIG get CC'ed on tickets in their area. So, one way to join a FIG or see if it's something you want to work on would be to look at all the tickets in that group. It might be easier for people than looking at the big pile of all tickets. Thoughts? kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
