<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, 2 Aug 2018 at 04:54 Stefan Richthofer <<a href="mailto:stefan.richthofer@gmail.com">stefan.richthofer@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Again, this was in the (poorly conveyed) context of getting email addresses for them, or at least being able to contact them.<br></blockquote><div><br></div></div><div dir="ltr"><div>I always thought there were already at least three places containing the necessary email addresses.</div><div><br></div><div>* python-committers should be exactly this mailing list.</div></div></blockquote><div><br></div><div>The list also has email archiving services as well as duplicate emails for people (e.g. I'm in it twice so that if I accidentally send an email from a personal email address it doesn't get held up in moderation).<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>* according to <a href="https://devguide.python.org/coredev/#issue-tracker" target="_blank">https://devguide.python.org/coredev/#issue-tracker</a> it is mandatory for core developers to subscribe to the issue tracker which AFAIK requires a confirmed email address.</div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>* Every committer clearly must have signed the contributor agreement <a href="https://www.python.org/psf/contrib/contrib-form/" target="_blank">https://www.python.org/psf/contrib/contrib-form/</a> which also contains a mandatory email field</div><div><br></div><div>So why is it still necessary to get email addresses at all?<br></div></div></blockquote><div><br></div><div>Because none of those necessarily have accurate email addresses at this point. E.g. even python-committers has had people dropped off due to too many email rejections. And if we hold a vote for a governance model we will need a place to send ballots.</div><div><br></div><div>Now if the vote is open to any core developer (using MAL's definition of it being a lifetime title), then the subscription list for this mailing list is probably good enough with some manual grooming as long we are okay with long-dormant folk who predate this list not voting (which I'm personally fine with). But if we wanted a way to reach just people with commit privileges then that's a separate challenge.</div><div><br></div><div>-Brett<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-08-02 10:59 GMT+02:00 Eric V. Smith <span dir="ltr"><<a href="mailto:eric@trueblade.com" target="_blank">eric@trueblade.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 8/2/2018 3:32 AM, M.-A. Lemburg wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 02.08.2018 03:24, Eric V. Smith wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 8/1/2018 8:32 PM, Mariatta Wijaya wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think it would also be a good idea to include core developers<br>
of other Python implementations in such a document, in<br>
separate sections, e.g. for Jython, IronPython, PyPy,<br>
Stackless, etc<br>
<br>
<br>
Hmm, I don't think it is should be our (CPython) responsibility to<br>
keep track and maintain the list of the core devs of alternate Python<br>
implementations. Don't they have their own community / website? They<br>
have their own repo, bug tracker, governance model, and everything,<br>
right?<br>
</blockquote>
<br>
Agreed. We have a hard enough time keeping track of our own core<br>
developers.<br>
</blockquote>
<br>
I don't really think we have a hard time doing this. The only<br>
problem is that we never sat down and actually properly recorded<br>
this in one place.<br>
</blockquote>
<br></span>
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.<br>
<br>
I agree that we could probably come up with a list of names for people who have been given the "core dev" status.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
For our core devs, can't we just say that the CPython core devs are<br>
those with commit bits on the CPython repo? I realize that will<br>
eliminate some people who have been core developers and never moved to<br>
github, but if they bring it to our attention, we can add them easily<br>
enough.<br>
</blockquote>
As discussed before, being a core developer is a status you<br>
gain and never lose. There is a clear difference between have<br>
commit rights to the (current) repo and this status.<br>
</blockquote>
<br></span>
Agreed. Again, this was in the (poorly conveyed) context of getting email addresses for them, or at least being able to contact them.<span class="m_3393588379333805150HOEnZb"><font color="#888888"><br>
<br>
Eric</font></span><div class="m_3393588379333805150HOEnZb"><div class="m_3393588379333805150h5"><br>
_______________________________________________<br>
python-committers mailing list<br>
<a href="mailto:python-committers@python.org" target="_blank">python-committers@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-committers" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-committers</a><br>
Code of Conduct: <a href="https://www.python.org/psf/codeofconduct/" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct/</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>
python-committers mailing list<br>
<a href="mailto:python-committers@python.org" target="_blank">python-committers@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-committers" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-committers</a><br>
Code of Conduct: <a href="https://www.python.org/psf/codeofconduct/" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct/</a><br>
</blockquote></div></div>