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.
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
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
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
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
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
