On Thu, Jul 4, 2019 at 5:00 AM Antoine Pitrou <anto...@python.org> wrote:

> > So, how do we pull together a clean-enough list of historical core
> > developers? Here is my idea of criteria of people to be on the list
> > (based on the developer log and the git log):
> >
> >   * Was not a GSoC student (clarification to follow for those who fall
> >     into this category and are actually active)
>
> I think you should replace "are actually active" with "have been
> actually active after their GSoC project" (without necessary being
> active *now*).  Example with Alexandre, who's been the pickle maintainer
> during several years but is inactive now:
>

Oh, I'm not inactive (at least not by the definition in PEP 13
<https://www.python.org/dev/peps/pep-0013/#id18>.) I was part of the
initial active core team members who were grandfathered in from the "Python
core" team on GitHub, and nobody asked me to declare myself as inactive
(yet!) But outside of the PEP 13 definition, yeah, it is true that I am not
actively contributing right now. (I still read the mailing lists and still
keep an eye on the pickle module though.) I would be sad to see my
membership invalidated because I became a committer through GSoC.

And BTW, PEP 13 defined the initial inactive members as anyone who has been
a committer in the past. PEP 13 didn't qualify the membership on what
process the person went through become a committer (e.g., by a vote, for
GSoC, or for sprints). Brett, are you planning to propose an amendment to
PEP 13 to change that?

-- Alexandre
_______________________________________________
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/4XHI4RYZ6IYLYCNFKGKLTKW2EFRMSVFK/
Code of Conduct: https://www.python.org/psf/codeofconduct/

Reply via email to