[python-committers] List of all core developers

[Stefan Richthofer]

> 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?
>

Core developers of Python implementations under PSF ownership were
traditionally listed in committers.txt and developer log.
This includes at least PyPy, Jython and IronPython. If you want to propose
to change this, that should be a distinct discussion
I suppose. I don't know the reason why it was originally decided to
maintain this together, but I guess that the named lists are
more a PSF thing than a CPython thing.
If you intend to change this suddenly, the communities should get at least
some transition time. I only know the situation of Jython,
where no committers list is available. Currently it relies on the lists
named above to identify committers.


Stefan


2018-08-02 2:32 GMT+02:00 Mariatta Wijaya <mariatta.wijaya at gmail.com>:

> 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 at gmail.com>
> wrote:
>
>> On Wed, Aug 1, 2018 at 3:44 PM M.-A. Lemburg <mal at 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://devguide.python.org/developers/
>> > *
>> > 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/
>> e42b705188271da108de42b55d9344642170aa2b/Misc/HISTORY
>> >   in combination with
>> >
>> > https://github.com/python/cpython/blob/e42b705188271da108de42b55d9344
>> 642170aa2b/Misc/ACKS
>> >   (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.
>>
>
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20180802/c1a34859/attachment.html>