[python-committers] Changing commiter status

Victor Stinner vstinner at redhat.com
Tue Jun 19 13:35:41 EDT 2018

2018-06-19 2:54 GMT+02:00 Guido van Rossum <guido at python.org>:
> 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 dev. Choices
> could include
>   a. Yes
>   b. Keep the logo and b.p.o. access but disable GitHub key
>   c. Drop everything
> 3. If someone doesn't respond despite repeated attempts (maybe using
> different email addresses or social media) then after 4 weeks assume they
> meant to answer (c). But if they write back later they can be restored
> according to their preference (a, b, c), no questions asked.
> 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.

Question about "emeritus".

My intent is to maintain a list of active core developers. If an
inactive core dev becomes active again, they should be able to
retrieve quickly the "active" status. Is "emeritus" still a good name
with such constraint?

Note: I like "emeritus" name to describe inactive core devs ;-)


More information about the python-committers mailing list