[python-committers] Proposed core developer for contributing to multiprocessing
Guido van Rossum
guido at python.org
Fri Jan 9 23:54:12 CET 2015
More information about the python-committers mailing list
Fri Jan 9 23:54:12 CET 2015
- Previous message: [python-committers] Proposed core developer for contributing to multiprocessing
- Next message: [python-committers] Proposed core developer for contributing to multiprocessing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jan 9, 2015 at 2:52 PM, Antoine Pitrou <antoine at python.org> wrote: > > Le 09/01/2015 23:47, M.-A. Lemburg a écrit : > > > > Antoine and Victor argued that new developers should first > > show their skills by submitting patches to tickets, working > > with other core devs before getting the commit bit set. > > > > My suggestion was allowing new developers to start committing > > patches themselves before having worked on dozens of tickets > > using the usual patch approach. > > What would that bring? Reverting commits or asking people to make post > hoc changes is much more bothersome than making pre-commit code reviews. > > And I don't see how it's beneficial to ask developers to commit up front > while we're trying to promote a culture of code review, anyway. > I'm with Antoine here. -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20150109/63f02f33/attachment.html>
- Previous message: [python-committers] Proposed core developer for contributing to multiprocessing
- Next message: [python-committers] Proposed core developer for contributing to multiprocessing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list