[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Blog syndication for GSoC - ers



On Tue, 2008-05-27 at 10:28 -0500, Mike McGrath wrote:
> On Tue, 27 May 2008, Karsten 'quaid' Wade wrote:
> 
> >
> > On Sat, 2008-05-24 at 23:27 -0500, Mike McGrath wrote:
> >
> > > Alternatively, perhaps we should just have an GSoC group?  These guys
> > > are
> > > technically contributors...
> >
> > I didn't realize this discussion was cross-posted, I already sent my
> > agreement to this idea to the other thread.  Having a group 'gsoc_2008'
> > or 'summercoders_2008' could help more than just this problem.  As was
> > said elsewhere, these _are_ Fedora contributors, but they don't all fit
> > directly in to an existing group, or their contributions are being
> > filtered outside of the group.
> >
> 
> Why not just gsoc?  I don't understand what we gain from the _2008?

Gain, not sure.  Lose, the ability to differentiate between groups.

A main purpose of GSoC is to get more coders into more projects.

For this reason, all students who stick around Fedora should be in other
groups.  Their continued presence in "last year's group" should *not* be
construed as an ongoing contributor effort.  By the end of this Summer,
the group is essentially defunct.  If that is the only group someone is
in, and six months later ... it's still the only group, then they aren't
contributing to any coding projects.  If they move on to Ambassadors,
then they are in another group, are contributing, etc.

Does that make sense?

For a similar reason, I recommend a generic name.  Maybe all interns and
summer coders could be in the group.  That way we can include the
Finnish Summer Code effort into this, and any RHT interns that aren't
part of another group (yet.)

- Karsten
-- 
Karsten Wade, Sr. Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]