Re: [python-committers] Changing commiter status

On Tue, Jun 19, 2018 at 3:54 AM, Guido van Rossum wrote: > > If we currently have a list of core devs we should by default change people's > status to emeritus core dev when they choose (c). They may also choose to be > removed from such a list. But I don't know if we have a list. We have at le

Re: [python-committers] Changing commiter status

I'd do it as follows. This basically makes withdrawal voluntary unless they don't respond at all. 1. Make a list of people who've not shown any sign of activity (on the b.p.o. or GitHub, as reviewer or committer) for at least one year. 2. Email all of them, asking if they still want to be a core d

Re: [python-committers] Changing commiter status

What will be the threshold of activity? For example, if one hasn’t been committing due to time but occasionally comments on or opens b.p.o. issues or reviews pull requests, etc, would that mean the logo disappears? There is value in having the logo show up when commenting. —Chris On Mon, Jun 18,

Re: [python-committers] Changing commiter status

On 18 June 2018 at 20:41, M.-A. Lemburg wrote: > On 18.06.2018 21:07, Guido van Rossum wrote: >> Hm, unless I misunderstood, MAL's >> >>> Being a core developer of Python is a status >> >> suggests that core devs might want to keep this status since it confers >> "status" on their person (it looks

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

On 6/18/2018 2:37 PM, Brett Cannon wrote: On Mon, 18 Jun 2018 at 11:17 Antoine Pitrou > wrote: Le 14/06/2018 à 04:30, Terry Reedy a écrit : > On 6/13/2018 7:03 PM, Carol Willing wrote: >> +1 With Victor's mentoring (1 or 2 months), I believe that it i

Re: [python-committers] Changing commiter status

On 6/18/2018 3:24 PM, Jack Jansen wrote: I know that this is the case for me. I wouldn’t _dream_ of committing anything (after 10 years or so) without first consulting with current core developers, etc. We would, of course, help you get back up to speed with the current workflow, if you wish

Re: [python-committers] Changing commiter status

On 18.06.2018 21:07, Guido van Rossum wrote: > Hm, unless I misunderstood, MAL's > >> Being a core developer of Python is a status > > suggests that core devs might want to keep this status since it confers > "status" on their person (it looks good on a resume for sure). And I > wouldn't want to

Re: [python-committers] Changing commiter status (was: Missing In Action)

I propose "emeritus core dev". It's a word that conveys *extra* status. On Mon, Jun 18, 2018 at 12:24 PM Jack Jansen wrote: > I know that this is the case for me. > > I wouldn’t _dream_ of committing anything (after 10 years or so) without > first consulting with current core developers, etc. Bu

Re: [python-committers] Changing commiter status (was: Missing In Action)

I know that this is the case for me. I wouldn’t _dream_ of committing anything (after 10 years or so) without first consulting with current core developers, etc. But formally being a Python core dev does give me status with my colleagues, students, children (well, one only), nephews and nieces,

Re: [python-committers] Changing commiter status (was: Missing In Action)

Hm, unless I misunderstood, MAL's > Being a core developer of Python is a status suggests that core devs might want to keep this status since it confers "status" on their person (it looks good on a resume for sure). And I wouldn't want to make it any harder for a 3rd party to verify someone's cla

Re: [python-committers] Changing commiter status (was: Missing In Action)

On Mon, 18 Jun 2018 at 06:43 Nick Coghlan wrote: > On 18 June 2018 at 18:07, M.-A. Lemburg wrote: > > Overall, I think that removing repo or bpo permissions should be > > kept separate from the status itself. It would probably be wise > > to send around reminders to all core devs who have access

Re: [python-committers] Maintenance Tasks

Le 16/06/2018 à 02:43, Victor Stinner a écrit : > > I chose to start discussing maintenance tasks with core developers > only (python-committers mailing list) since many tasks are reserved to > (or at least currently done by) core developers. And I'm not sure that > the concept of "maintenance ta

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

Thanks for correcting me. (by the way I'm 8th in that list... Serhiy is 2nd, not me ;-)) Regards Antoine. Le 18/06/2018 à 20:37, Brett Cannon a écrit : > > > On Mon, 18 Jun 2018 at 11:17 Antoine Pitrou > wrote: > > > Le 14/06/2018 à 04:30, Terry Reedy a écri

Re: [python-committers] Maintenance Tasks

On Fri, 15 Jun 2018 at 17:44 Victor Stinner wrote: > Hi, > > At FOSDEM (last February), I saw an interesting talk by VM (Vicky) > Brasseur: > "Passing the Baton: Succession planning for FOSS leadership" > > She explains that the maintenance of a project should be splited into > small tasks, and t

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

On Mon, 18 Jun 2018 at 11:17 Antoine Pitrou wrote: > > Le 14/06/2018 à 04:30, Terry Reedy a écrit : > > On 6/13/2018 7:03 PM, Carol Willing wrote: > >> +1 With Victor's mentoring (1 or 2 months), I believe that it is > >> reasonable to promote Pablo to a core developer either now or after 3 > >>

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

Le 14/06/2018 à 19:25, Gregory P. Smith a écrit : > Quick response: > > +0.5 > > But Pablo shows drive and desire to do good things and an > ability to eventually do it even if there are learning bumps along the > way. This is my impression as well, having interacted with Pablo on a single PR o

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

Le 14/06/2018 à 04:30, Terry Reedy a écrit : > On 6/13/2018 7:03 PM, Carol Willing wrote: >> +1 With Victor's mentoring (1 or 2 months), I believe that it is >> reasonable to promote Pablo to a core developer either now or after 3 >> months of coaching. >> >> I would also like to see Cheryl Sabe

Re: [python-committers] Changing commiter status (was: Missing In Action)

On 18 June 2018 at 18:07, M.-A. Lemburg wrote: > Overall, I think that removing repo or bpo permissions should be > kept separate from the status itself. It would probably be wise > to send around reminders to all core devs who have access and > have not used their permissions every few year. The

Re: [python-committers] Changing commiter status (was: Missing In Action)

Victor: please make sure that you contact the developers whos status you intend to modify prior to doing so. Being a core developer of Python is a status and not something that should be changed without consent by the developer in question. Also note that the dev list log doesn't include all core