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 everything, right?
Agreed. We have a hard enough time keeping track of our own core developers.
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 enough. 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.
Eric