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

Le 11/01/2015 21:26, Raymond Hettinger a écrit : > > We should at least grant him developer privileges on the tracker > to it much easier for him to move the tracker items forward. I just gave him developer privileges (or at least I hope so - I added the role "Developer"). > As far as I can te

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

> On Jan 10, 2015, at 12:09 PM, Gregory P. Smith wrote: > > I agree with MAL, it is more beneficial to trust people and give out commit > access early. For comparison, I think that is the norm for paid work. At companies I've worked for, new programmers are given check-in rights on the first

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

I have not been active for past year or so. But here is are thoughts on this process. The important thing should be "contribution" and a developer's personal satisfaction comes from contribution. The commit access IMO is secondary, but is very important and as it helps contributor to move at a fa

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

Le 11/01/2015 03:01, Brett Cannon a écrit : > > On Sat, Jan 10, 2015, 18:01 Antoine Pitrou > wrote: > > > Le 10/01/2015 21:16, Brett Cannon a écrit : > > I'm +1 as well since Raymond has said he will mentor Davin the way > > through and I'm willing to exp

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

On Sat, Jan 10, 2015, 18:01 Antoine Pitrou wrote: Le 10/01/2015 21:16, Brett Cannon a écrit : > I'm +1 as well since Raymond has said he will mentor Davin the way > through and I'm willing to experiment with giving commit rights earlier > based on personal vouching of a core developer. We have

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

Le 10/01/2015 21:16, Brett Cannon a écrit : > I'm +1 as well since Raymond has said he will mentor Davin the way > through and I'm willing to experiment with giving commit rights earlier > based on personal vouching of a core developer. We have already experimented with that. People like Jean-Pau

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

I'm +1 as well since Raymond has said he will mentor Davin the way through and I'm willing to experiment with giving commit rights earlier based on personal vouching of a core developer. On Sat Jan 10 2015 at 3:09:43 PM Gregory P. Smith wrote: > +1 for commit access, Raymond volunteered as a men

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

On Jan 10, 2015, at 12:09, Gregory P. Smith wrote: > > +1 for commit access, Raymond volunteered as a mentor. > > I agree with MAL, it is more beneficial to trust people and give out commit > access early. +1, for all of those reasons. My only concern is trying to ensure that Richard (sbt) i

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

+1 for commit access, Raymond volunteered as a mentor. I agree with MAL, it is more beneficial to trust people and give out commit access early. -gregory.p.smith On Sat Jan 10 2015 at 9:16:26 AM Ethan Furman wrote: > On 01/06/2015 11:09 PM, Raymond Hettinger wrote: > > > > I would like to prop

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

On 01/06/2015 11:09 PM, Raymond Hettinger wrote: > > I would like to propose Davin Potts as core developer to take on the > responsibility for maintaining the multiprocessing > package. > > I've been working with him on and off for over a year and found him to be > highly skilled, thoughtful, a

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

Le 10/01/2015 14:53, M.-A. Lemburg a écrit : > > Anyway, I think I've made my point now :-) If other committers > feel that we don't need to have a more welcoming approach to > new developers, that's fine. I half-agree with Berker: the number one problem is enough people to review patches and gu

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

On 10.01.2015 13:38, Berker Peksağ wrote: > On Sat, Jan 10, 2015 at 12:33 PM, M.-A. Lemburg wrote: >> Hi Ezio, >> >> I think I'm not making myself clear enough :-) >> >> Technically, operations would stay the same (tickets, patches, reviews), >> but from a motivational point of view, you change th

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

On Sat, Jan 10, 2015 at 12:33 PM, M.-A. Lemburg wrote: > Hi Ezio, > > I think I'm not making myself clear enough :-) > > Technically, operations would stay the same (tickets, patches, reviews), > but from a motivational point of view, you change things a lot for the > better if you put trust into

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

Hi Ezio, I think I'm not making myself clear enough :-) Technically, operations would stay the same (tickets, patches, reviews), but from a motivational point of view, you change things a lot for the better if you put trust into people by giving them the commit bit early. The "incubation" period

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

On 01/10/2015 12:03 AM, M.-A. Lemburg wrote: >>> 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 committ

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

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

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

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

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

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

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

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

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

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

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

> Did he already contributed to CPython? > What is his nickname on the bug tracker? > Can we see his previous contributions? Davin has already devoted significant time to researching 180+ open issues for multiprocessing and getting up to speed to the history of multiprocessing work. His tracker

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

Hi, 2015-01-07 9:51 GMT+01:00 Antoine Pitrou : >> I would like to propose Davin Potts as core developer to take on the >> responsibility for maintaining the multiprocessing package. Did he already contributed to CPython? What is his nickname on the bug tracker? Can we see his previous contributio

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

Le 07/01/2015 08:09, Raymond Hettinger a écrit : > Hello all, > > I would like to propose Davin Potts as core developer to take on the > responsibility for maintaining the multiprocessing package. > > I've been working with him on and off for over a year and found him to > be highly skilled, tho

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

Hello all, I would like to propose Davin Potts as core developer to take on the responsibility for maintaining the multiprocessing package. I've been working with him on and off for over a year and found him to be highly skilled, thoughtful, and responsible. He is willing to devote time to a