[python-committers] Changing commiter status
Guido van Rossum
guido at python.org
Tue Jun 19 14:30:37 EDT 2018
I honestly have very little stake in this -- the minimum that I'd like to
see is that unused GitHub permissions be revoked to reduce the risk when a
dormant core dev is compromised. (Though if they contribute regularly to
*other* GitHub projects even that risk seems minimal.)
On Tue, Jun 19, 2018 at 11:23 AM Brett Cannon <brett at python.org> wrote:
> On Mon, 18 Jun 2018 at 17:56 Guido van Rossum <guido at python.org> wrote:
>> 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.
> One point I want to make about this pull approach versus a push one is
> this is going to be a lot of work. :) For the "no GitHub username"
> situation on bugs.python.org there are 80 people to reach out to. For
> people with commit rights who have not committed in the past year to
> CPython (because that's the best data point I have without writing custom
> code to find out who has commented on a PR recently), that would require
> reaching out to an additional 50 people. So we're looking at potentially up
> to 130 people to try and track down.
>> 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 can make a complete list as people seem to want that and have it be
> active versus emeritus and list the year people got their commit rights.
> Here's a counter-proposal so we can figure out what middle ground we are
> all happy with. The developer log gets rewritten to be simpler to just be
> two lists: a chronological one of active core devs sorted by when they got
> commit privileges, and an alphabetized list of core devs who are now
> emeritus (listing their years of service to the project).
> The lists start with everyone who has committed to CPython, the devguide,
> or the peps repo in the past year as active. Everyone else is listed as
> emeritus. People are then given some window -- a month? -- to update
> themselves in those lists from emeritus to active. At the end of that month
> whomever is still listed as emeritus we turn off their commit access and
> b.p.o extras. We announce this here, python-dev, social media, etc. IOW
> this becomes more opt-in/push than opt-out/pull.
>> On Mon, Jun 18, 2018 at 5:21 PM Chris Jerdonek <chris.jerdonek at gmail.com>
>>> 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.
>>> On Mon, Jun 18, 2018 at 1:52 PM Paul Moore <p.f.moore at gmail.com> wrote:
>>>> On 18 June 2018 at 20:41, M.-A. Lemburg <mal at 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
>>>> >> "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
>>>> >> 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).
>>>> python-committers mailing list
>>>> python-committers at python.org
>>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>> python-committers mailing list
>>> python-committers at python.org
>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>> --Guido van Rossum (python.org/~guido)
>> python-committers mailing list
>> python-committers at python.org
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the python-committers