[Python-Dev] Enhanced tracker privileges for dangerjim to do triage.

Michael Foord fuzzyman at voidspace.org.uk
Mon Apr 26 13:45:34 CEST 2010


On 26/04/2010 12:24, Antoine Pitrou wrote:
> Hello,
>
>    
>> I think it is very much in the interest of Python to evolve our
>> processes in order to encourage more core-developers. Evolving means
>> experimenting *and* being willing to change. It is certainly less
>> *effort* to accept the status quo, but with several more committed and
>> enthusiastic (and good) core developers there is an awful lot (more) we
>> could achieve.
>>      
> I certainly agree we should try to attract more good-willed and
> competent contributors.
>
> I also agree with Stephen that, in a project with a non-trivial amount
> of complexity such as CPython, not having (tracker or commit) privileges
> is not the real barrier to entry. You have to learn how the software
> works, how its development works, who are the people working on it, etc.
>
>    

So the question remains - for *tracker* privileges, should the 
recommendation and commitment to mentor from an established commiter be 
sufficient (and therefore a standard part of our process)?

I think this is a reasonable barrier for entry and should be acceptable. 
It should be stated as part of our standard procedure however rather 
than being an exception to our standard procedure.

All the best,

Michael

> Regards
>
> Antoine.
>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
>    


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.




More information about the Python-Dev mailing list