Change with FAS sysadmin-* accounts

[Tajidin Abd]

On Tue, Aug 31, 2010 at 3:08 PM, Matt Micene <matt.micene at dlt.com> wrote:

> > -----Original Message-----
> > From: infrastructure-bounces at lists.fedoraproject.org
> > [mailto:infrastructure-bounces at lists.fedoraproject.org] On Behalf Of
> > Jon Stanley
> > Sent: Tuesday, August 31, 2010 8:19 AM
> > To: Fedora Infrastructure
> > Subject: Re: Change with FAS sysadmin-* accounts
> >
> > > to be a mentor along with this new contributor to work closely with
> > him. For
> > > example doing some small tasks like documentation, wiki, content,
> for
> > the
> > > Infrastructure team that is some menial basic things. As they say
> you
> > have
> > > to learn how to follow before you can lead.
> >
> > Whenever I sponsor someone into Infrastructure groups, it's with a
> > clear task/project in mind. Once you've accomplished that task,
> > there's limitless other tasks to be accomplished, and you gradually
> > "move up the ranks". so to speak, in terms of responsibility.
> >
> > Does that make it more clear?
>
> That plus Mike's earlier feedback definitely set me straight.  I had
> come in (even after reading the docs) thinking that it was 'look around,
> find where you'd like to work, get to know those people, ask to work
> with them, pick up tasks, Profit!!!'.  Mike's got me started in the
> right order despite that misunderstanding.  :)
>
> In retrospect, it makes sense.  OSS projects I've worked on before I got
> started with b/c of a fix to a script or something that I brought to a
> list.  I asked questions, did the work, and then presented it up for
> review.
>
> -Matt
> _______________________________________________
> infrastructure mailing list
> infrastructure at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/infrastructure
>



yea clears it up fine for me now thanks alot keep up the good work what you
fellas do


tajidin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20100831/a1bd3ea3/attachment-0001.html