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 everything, right?
Mariatta
On Wed, Aug 1, 2018 at 2:54 PM Eric Snow <ericsnowcurrently@gmail.com> wrote:
On Wed, Aug 1, 2018 at 3:44 PM M.-A. Lemburg <mal@egenix.com> wrote:
On 01.08.2018 23:28, Mariatta Wijaya wrote:
See also an open issue to revamp the Developer log: https://github.com/python/devguide/issues/390
Someone has also said that they're working on tracking down the dormant core devs, but now I can't find that email.
I think the log is fine at it is, since it serves a different purpose.
The list should be in addition to the log, not replacing it.
Resources we already have:
https://bugs.python.org/user?%40action=search&iscommitter=1&%40pagesize=300&%40sort=username
- python-committers Subscribers List (but this is currently only for list admins to see - perhaps we could make that available to list members ?!)
- https://hg.python.org/committers.txt
- for the early days:
https://raw.githubusercontent.com/python/cpython/e42b705188271da108de42b55d9...
in combination with
https://github.com/python/cpython/blob/e42b705188271da108de42b55d9344642170a...
(in those times, there was no direct access to the repo and all patches had to go through the team around Guido)
There's also:
- the members of the github team
- folks marked as committers as BPO
I don't recall if these are exposed via public lists though.
-eric
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.