community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@apache.org>
Subject Re: GSoC & Temporary commit access accounts
Date Thu, 21 Jul 2011 09:21:33 GMT
On Thu, Jul 21, 2011 at 01:19:14AM -0700, Ted Dunning wrote:
> I completely agree with this.
> 
> Mahout has worked on just this basis quite well.

At Subversion we did this, too, during the last two years (we have
no gsoc student this year). It has been working extremely well.
In some cases gsoc students already had commit access because of
prior work they did on the project.

I personally think it is not a good idea to hand out commit access to
gsoc students just because they're gsoc students. This is not how open
source works in reality. gsoc is a training program for open source
developers and should mirror the real experience.

Submitting patches also forces students to build their work in pieces
which can be reviewed. It helps them with organising their commits
when they attain commit access later.

gsoc students can be expected to learn about git/mercurial if they really
need local commits (or wait until Greg finishes 'svn checkpoint' :)
I've recommended mercurial patch queues to students I've mentored:
http://hgbook.red-bean.com/read/managing-change-with-mercurial-queues.html

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

To prevent unnecessary overloading of this term, I'd like to point out
that in Subversion a "partial committer" is someone who is granted
access to a particular subdirectory or a branch.
http://subversion.apache.org/docs/community-guide/roles.html#partial-commit-access
This has nothing to do with gsoc. The access is usually never revoked.

Mime
View raw message