[python-committers] List of all core developers
Eric V. Smith
eric at trueblade.com
Thu Aug 2 08:43:31 EDT 2018
On 8/2/2018 7:53 AM, Stefan Richthofer wrote:
> Again, this was in the (poorly conveyed) context of getting email
> addresses for them, or at least being able to contact them.
> I always thought there were already at least three places containing the
> necessary email addresses.
> * python-committers should be exactly this mailing list.
> * according to https://devguide.python.org/coredev/#issue-tracker it is
> mandatory for core developers to subscribe to the issue tracker which
> AFAIK requires a confirmed email address.
> * Every committer clearly must have signed the contributor agreement
> https://www.python.org/psf/contrib/contrib-form/ wich also contains a
> mandatory email field
> So why is it still necessary to get email addresses at all?
I don't recall, exactly. It was at an early Language Summit, and we were
looking for ways to contact everyone and to associate people with email
addresses. It might have involved the mercurial migration. Maybe it's
not still required. My point is that it's hard to come up with a list of
core devs and match them with email addresses. If that's not the
requirement here, then great!
I know I've had several addresses over the years, some of which are
non-obviously associated with me, and some of which I no longer have
> 2018-08-02 10:59 GMT+02:00 Eric V. Smith <eric at trueblade.com
> <mailto:eric at trueblade.com>>:
> On 8/2/2018 3:32 AM, M.-A. Lemburg wrote:
> On 02.08.2018 03:24, Eric V. Smith wrote:
> On 8/1/2018 8:32 PM, Mariatta Wijaya wrote:
> I think it would also be a good idea to include
> core developers
> of other Python implementations in such a document, in
> separate sections, e.g. for Jython, IronPython, PyPy,
> Stackless, etc
> Hmm, I don't think it is should be our (CPython)
> responsibility to
> keep track and maintain the list of the core devs of
> alternate Python
> implementations. Don't they have their own community /
> website? They
> have their own repo, bug tracker, governance model, and
> Agreed. We have a hard enough time keeping track of our own core
> I don't really think we have a hard time doing this. The only
> problem is that we never sat down and actually properly recorded
> this in one place.
> I was specifically thinking of a way to stay in touch with core
> devs, or more specifically a way to send them email. In the past,
> before we moved to github, I took it upon myself to find email
> addresses (current or not) for all core devs, and I gave up without
> much success.
> I agree that we could probably come up with a list of names for
> people who have been given the "core dev" status.
> For our core devs, can't we just say that the CPython core
> devs are
> those with commit bits on the CPython repo? I realize that will
> eliminate some people who have been core developers and
> never moved to
> github, but if they bring it to our attention, we can add
> them easily
> As discussed before, being a core developer is a status you
> gain and never lose. There is a clear difference between have
> commit rights to the (current) repo and this status.
> Agreed. Again, this was in the (poorly conveyed) context of getting
> email addresses for them, or at least being able to contact them.
> python-committers mailing list
> python-committers at python.org <mailto:python-committers at python.org>
> Code of Conduct: https://www.python.org/psf/codeofconduct/
More information about the python-committers