community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <>
Subject Re: GSoC & Temporary commit access accounts
Date Thu, 21 Jul 2011 08:19:14 GMT
I completely agree with this.

Mahout has worked on just this basis quite well.

Where it is deemed important for students to be allowed to commit changes,
we have used github as a temporary work area, but all changes committed to
the project code have been committed by actual committers with the
concurrence of the rest of the committers.  We watch to make sure that
temporary work areas do not involve inadvertent inclusion of code not
produced by the students.

I haven't observed a need for any "partial committer" status.  I certainly
don't see any need to issue email addresses to students.

On Wed, Jul 20, 2011 at 11:44 PM, Luciano Resende <>wrote:

> As the PMC overseeing the GSoC program at Apache, I'd like to see a
> set of recommendations, guidelines and if necessary processes on how
> to handle these cases. Having said that, I believe students are and
> should be treated as any other community contributor, that have design
> discussions on the project mailing list, and provides patch towards
> earning trust and committership status as a community recognition of
> his contributions.
> What are your thoughts on what should be the official recommendation,
> and based on that we can discuss required processes.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message