Re: [python-committers] Proposed core developer for contributing to multiprocessing

2015-01-09 Thread Ezio Melotti
Hi, On Fri, Jan 9, 2015 at 11:47 PM, M.-A. Lemburg wrote: > On 09.01.2015 23:26, Ezio Melotti wrote: >> Hi, >> >> On Fri, Jan 9, 2015 at 1:09 PM, M.-A. Lemburg wrote: >>> >>> BTW: How about having an "incubator" phase for new core devs ? >>> The new candidate will get commit rights for say 3 mon

Re: [python-committers] Proposed core developer for contributing to multiprocessing

2015-01-09 Thread M.-A. Lemburg
On 09.01.2015 23:52, Antoine Pitrou 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

Re: [python-committers] Proposed core developer for contributing to multiprocessing

2015-01-09 Thread Guido van Rossum
On Fri, Jan 9, 2015 at 2:52 PM, Antoine Pitrou 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. > >

Re: [python-committers] Proposed core developer for contributing to multiprocessing

2015-01-09 Thread Antoine Pitrou
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 >

Re: [python-committers] Proposed core developer for contributing to multiprocessing

2015-01-09 Thread M.-A. Lemburg
On 09.01.2015 23:26, Ezio Melotti wrote: > Hi, > > On Fri, Jan 9, 2015 at 1:09 PM, M.-A. Lemburg 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 m

Re: [python-committers] Proposed core developer for contributing to multiprocessing

2015-01-09 Thread Ezio Melotti
Hi, On Fri, Jan 9, 2015 at 1:09 PM, M.-A. Lemburg 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

Re: [python-committers] Proposed core developer for contributing to multiprocessing

2015-01-09 Thread Steve Dower
M.-A. Lemburg 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. > > As long as this is stated clearly from the beginning,

Re: [python-committers] Proposed core developer for contributing to multiprocessing

2015-01-09 Thread M.-A. Lemburg
On 09.01.2015 12:47, Nick Coghlan wrote: > On 7 January 2015 at 20:22, Victor Stinner wrote: >> If David didn't contribute before, I'm against giving him directly the >> developer access. Different people repeat that you don't need to have >> the developer access to contribute. Send patches, revie

Re: [python-committers] Proposed core developer for contributing to multiprocessing

2015-01-09 Thread Nick Coghlan
On 7 January 2015 at 20:22, Victor Stinner wrote: > If David didn't contribute before, I'm against giving him directly the > developer access. Different people repeat that you don't need to have > the developer access to contribute. Send patches, review patches, > comment issues, etc. > > We rejec