On 18 June 2018 at 20:41, M.-A. Lemburg mal@egenix.com 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 good on a resume for sure). And I wouldn't want to make it any harder for a 3rd party to verify someone's claim to this status in their resume.
Marc-Andre, is that what you meant?
I guess I wasn't clear, sorry.
Perhaps the better term is "title" rather than "status". My understanding is that you become core developer and essentially keep this title forever.
Whether you actually have your keys in the repo to push a PR or not is a different story and not really related to the "title" you earned.
Listing the core developers somewhere on an official page would help with the verification you are referring to. At the moment, we don't seem to have this. It does make a difference on CVs and it's one of the few things we can give back to people when contributing code and time to Python.
Just to add my thoughts here. I agree that "being a Python core developer" is something people can be proud of (I know I am!), as well as being good to put on a CV. It would be a shame to devalue that pride by saying in effect that you're no longer a "real" core developer if you don't keep contributing.
So I'd very much like to distinguish the idea of "being a core developer" from the administrative management of commit privileges. The respect and gratitude of our peers is one of the few things it's possible to get as a reward for open source contributions - let's be generous with that (and with openly acknowledging it).
Paul