On 09.01.2015 23:26, Ezio Melotti wrote: > Hi, > > On Fri, Jan 9, 2015 at 1:09 PM, M.-A. Lemburg <m...@egenix.com> wrote: >> >> BTW: How about having an "incubator" phase for new core devs ? >> The new candidate will get commit rights for say 3 months and >> after those 3 months, the mentor then suggests whether make >> the status permanent or not. >> > > Not sure this will work too well. I'm assuming that new candidates > are good developers and reasonable persons that will still be chosen > based on their merits (previous contributions, recommendations from > other core devs, etc.), so nearly all of them will probably get the > permanent status. > I can't imagine many reasons why we wouldn't eventually accept a > candidate. If they wreak havoc in the repo we will probably remove > their commit rights immediately, if they do something wrong we would > just tell them and they would hopefully fix the problem and keep it in > mind for the next time. If they really can't figure out/follow our > workflow or have similar problems they will probably gave up being > contributors on their own, even if they still have rights. > >> As long as this is stated clearly from the beginning, I don't >> think people will feel offended if they end up not receiving >> the permanent status, and this will reduce the barrier for >> entry a lot. Learning on the job is a rather common practice >> in the industry these days :-) >> > > If they do something clearly wrong they shouldn't be surprised if we > revoke their right, 3 months period or not. If they are just not good > enough they won't be offended but they will probably be disappointed. > Comparing Python with a paid job is also somewhat misleading, since > the only investment we have to do is following the new contributor for > a while and possibly intervene if something goes wrong (e.g. they made > a wrong commit and don't know how to fix it/revert it). IME this > doesn't happen often and it's not a particularly time-consuming task. > > TL;DR We can give access rights to whoever proves to be up to the task > and willing to contribute, the three month period is not necessary, if > they cause trouble we will just revoke the right (but that shouldn't > happen).
Perhaps I wasn't clear about the context. The discussion was focusing on requirements for a new developer to get commit rights. 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. The incubator phase is meant to check whether the new developer is up to the task he or she signs up for. The mentor keeps checking the code quality during this phase to avoid broken code or backwards incompatible changes which would need more discussion. In summary, we'd allow developers to start taking on responsibilities earlier than in the current process, while still maintaining the high quality standards we have. I may be misunderstanding your reply, but it appears you'd even want to go beyond that, so we're not really in disagreement it seems :-) -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jan 09 2015) >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ >>> mxODBC Plone/Zope Database Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
