airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marlon Pierce <marpi...@iu.edu>
Subject Fwd: Re: [QUESTION] commit access to GSOC students?
Date Fri, 31 May 2013 16:42:15 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is Ulrich's suggestion appropriate for Airavata GSOC students?


Marlon



- -------- Original Message --------
Subject: Re: [QUESTION] commit access to GSOC students?
Date: Fri, 31 May 2013 09:47:17 +0200
From: Ulrich Stärk <uli@apache.org>
Reply-To: code-awards@apache.org
To: code-awards@apache.org

I personally would treat the student like any regular contributor.
Have them work with the issue
tracker, have them submit patches, have them participate in on-list
discussions. One thing they
should learn during GSoC is how open source software development
works, and especially how it works
at Apache.

Once they have earned enough merit (depends on the community, I
personally would be rather
inclusive) vote them in as committers.

Uli

On 31.05.2013 09:40, Dan Haywood wrote:
> Hi Lewis, Thanks for that.  Yeah, you are right that with github it
> is easier to submit patches. In this case the two students I have
> are each going to be writing a new module, and if there are any
> changes to existing code, then it'll be to a backend module that I
> was the sole author of.  So the risk of something nasty/unexpected
> happening is pretty low.  Even so, I don't want to ride roughshod
> over ASF principles. Dan
> 
> 
> On 31 May 2013 08:16, Lewis John Mcgibbney
> <lewis.mcgibbney@gmail.com>wrote:
> 
>> Hey Dan, Last year we branched the code, kept it in line with
>> trunk (concerning the porting of trunk development over to the
>> branch), the student submitted patches to me, I committed them to
>> branch and it seemed to work OK. In this case the student did not
>> get write access until we succeeded in VOTE'ing him in post GSoC
>> however I abstain from providing opinion on what works best. I
>> think the barrier is slightly lower now that the student can 
>> easily maintain his/her copy of the code on a public github repos
>> as the infra guys have done a sterling job getting every projects
>> that requested mirrors which can be mirrored as well. lewis
>> 
>> 
>> On Thursday, May 30, 2013, Dan Haywood
>> <dan@haywood-associates.co.uk> wrote:
>>> Some advice, please.
>>> 
>>> I was reading (more thoroughly) through Google's 76 page
>>> mentoring guide [1], and they recommend that students are
>>> granted commit access where possible, so that they are part of
>>> the community and not shoved off somewhere else.
>>> 
>>> This is, though, somewhat in conflict with ASF's general policy
>>> requiring that committers are first contributors.
>>> 
>>> As it happens, one of my two students was on GSOC last year.
>>> He tells me that he spent about a month last year submitting
>>> patches, after which he was allowed to commit directly.
>>> 
>>> That seems like a balanced approach; I'm thinking of starting
>>> this immediately during this "getting to know you phase", so
>>> that he can be given commit access sooner rather than later.
>>> 
>>> My question is: what have others done in the past on this?
>>> 
>>> Thx Dan
>>> 
>>> 
>>> [1] http://www.flossmanuals.net/gsocmentoring/#
>>> 
>> 
>> -- *Lewis*
>> 
> 


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRqNLnAAoJEOEgD2XReDo5GikH/2S+HsXHJKdqY7smf0BfPEa8
buEzni4biBqwKXPcG5M4klHzX77UOPfOLre0We5W6HMDLjKR4Kg2NxkT83Awsahx
udPZJ5TswEfu755xkdVY2jMkCq9x9srkB8yUiDp+zhp6i7MNi9cuwMtRzcawaRlG
RWedqBMiPi3qR58nAS3FUqVWNIzjxZCmkRX8p221uVTCqKEPaFrZEhajhRkEz90e
ixhA+JSiSZg9RLxiqYxhc0IybYqKoUzELKuFVz2sf7puJQKun/AIBl/N543YrqIg
QU6QD4NJpEEyutxRpfgcmBDH4aQgD6fkFvbtqWTPdRjTc8P9/kLs34hY4MKAtMA=
=Jak8
-----END PGP SIGNATURE-----

Mime
View raw message