community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon" <edwardy...@apache.org>
Subject Re: GSoC & Temporary commit access accounts
Date Fri, 22 Jul 2011 08:30:55 GMT
Sorry this is other question but, one of my students asked about
"anyone can jump in and volunteer to be a committer."[1] ..........

What's the exact policy on this?

1. http://markmail.org/thread/jb63zsbenmanr3fs

Thanks,
Ed

On Fri, Jul 22, 2011 at 5:03 PM, ant elder <ant.elder@gmail.com> wrote:
> On Fri, Jul 22, 2011 at 1:34 AM, Greg Stein <gstein@gmail.com> wrote:
>> On Thu, Jul 21, 2011 at 16:55, Benson Margulies <bimargulies@gmail.com> wrote:
>>>...
>>>> Personally I feel that GSoC students should earn commit access just
>>>> like anyone else.
>>>
>>> I have a lot of sympathy for Greg's position. Treating 'committer' as
>>> a single monolithic category drives people away.
>>
>> Right. It is necessary to distinguish between "commit access [to a
>> branch]" and "commit access [to trunk]". I fully concur that access to
>> trunk follows the same pattern as regular committers. GSoC students
>> have no elevated rights.
>>
>> However, I think providing a GSoC student with commit to a branch is
>> an easy decision, and that it should be the default policy. (for the
>> reasons listed in my previous note)
>>
>> [ next part strays from the GSoC discussion ]
>>>...
>>> should have to. I'd be happy to see the foundation endorse the idea
>>> that a PMC can choose to grant commit karma to branches, in a trial
>>> basis, to people who have submitted a suitable cla. That would not
>>> given them nexus karma, web-site-editing karma, or dogma karma.
>>
>> The Subversion PMC has an operating rule that basic states, "any
>> individual PMC member may grant commit access to a non-trunk area, to
>> a developer with an ICLA on file". There is a subjective level to
>> this: does it clearly make sense (say, a branch), or might it be a
>> little controversial (say, the directory for the 'svn' command-line
>> tool). For the latter, we encourage the Member to float the idea on
>> private@ first. But we don't have a strict written policy here; good
>> judgement is always a great replacement for more rules :-)
>>
>> I would very much encourage other PMCs to adopt similar policies.
>> Again, with version control, the phrase "damage control" almost
>> doesn't apply.
>>
>> Cheers,
>> -g
>>
>
> I agree with Greg and the others in favour of keeping it easy to get
> write access, and i really like the Subversion PMC approach.
>
> I don't understand the mindset that commit access should be hard to
> get or something that must be worked hard to earn. Most project i
> watch don't find it that easy to attract new developers so when one
> does turn up i think its better to be open and welcoming and not be
> like "thanks but earn you place first" which is more likely to just
> discourage them.
>
>   ...ant
>



-- 
Best Regards, Edward J. Yoon
@eddieyoon

Mime
View raw message