On 27/07/2010 13:56, Antoine Pitrou wrote:
So long as Eric is prepared to commit to our standard procedures
(discussion and patches on issues before commit and general caution and
regard for backwards compatibility) I would like to see him given commit
rights under the watchful eye of Tarek and those who review checkins. We
could see this as an "experimental" commit access in line with the
lowered barrier proposed by Guido.
I'm fine with commit access for Éric (especially for documentation
issues where his contribution has been quite useful).
The issue at hand is the fate of distutils maintenance.
As indicated by my previous +1, I favour the approach suggested by
Marc-andre Lemburg.
Michael
Regards
Antoine.
_______________________________________________
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
--
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.
_______________________________________________
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
