<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, 18 Jun 2018 at 12:41 M.-A. Lemburg <<a href="mailto:mal@egenix.com">mal@egenix.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 18.06.2018 21:07, Guido van Rossum wrote:<br>
> Hm, unless I misunderstood, MAL's<br>
> <br>
>> Being a core developer of Python is a status<br>
> <br>
> suggests that core devs might want to keep this status since it confers<br>
> "status" on their person (it looks good on a resume for sure). And I<br>
> wouldn't want to make it any harder for a 3rd party to verify someone's<br>
> claim to this status in their resume.<br>
> <br>
> Marc-Andre, is that what you meant?<br>
<br>
I guess I wasn't clear, sorry.<br>
<br>
Perhaps the better term is "title" rather than "status". My<br>
understanding is that you become core developer and essentially<br>
keep this title forever.<br>
<br>
Whether you actually have your keys in the repo to push a PR<br>
or not is a different story and not really related to the "title"<br>
you earned.<br>
<br>
Listing the core developers somewhere on an official page<br>
would help with the verification you are referring to. At<br>
the moment, we don't seem to have this. It does make a difference<br>
on CVs and it's one of the few things we can give back to people<br>
when contributing code and time to Python.<br>
<br>
Hope that's a little clearer.<br></blockquote><div><br></div><div>Yep, and no one is suggesting you don't get listed as a core dev somewhere. Basically the idea is you would swap the Python logo next to your name on <a href="http://bugs.python.org">bugs.python.org</a> to being listed on a page on <a href="http://devguide.python.org">devguide.python.org</a> in terms of visibly being identified as a core dev.<br></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">
<br>
Thanks,<br>
-- <br>
Marc-Andre Lemburg<br>
eGenix.com<br>
<br>
Professional Python Services directly from the Experts<br>
>>> Python Projects, Coaching and Consulting ... <a href="http://www.egenix.com/" rel="noreferrer" target="_blank">http://www.egenix.com/</a><br>
>>> Python Database Interfaces ... <a href="http://products.egenix.com/" rel="noreferrer" target="_blank">http://products.egenix.com/</a><br>
>>> Plone/Zope Database Interfaces ... <a href="http://zope.egenix.com/" rel="noreferrer" target="_blank">http://zope.egenix.com/</a><br>
________________________________________________________________________<br>
<br>
::: We implement business ideas - efficiently in both time and costs :::<br>
<br>
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48<br>
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg<br>
Registered at Amtsgericht Duesseldorf: HRB 46611<br>
<a href="http://www.egenix.com/company/contact/" rel="noreferrer" target="_blank">http://www.egenix.com/company/contact/</a><br>
<a href="http://www.malemburg.com/" rel="noreferrer" target="_blank">http://www.malemburg.com/</a><br>
<br>
<br>
> On Mon, Jun 18, 2018 at 11:59 AM Brett Cannon <<a href="mailto:brett@python.org" target="_blank">brett@python.org</a>> wrote:<br>
> <br>
>><br>
>><br>
>> On Mon, 18 Jun 2018 at 06:43 Nick Coghlan <<a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a>> wrote:<br>
>><br>
>>> On 18 June 2018 at 18:07, M.-A. Lemburg <<a href="mailto:mal@egenix.com" target="_blank">mal@egenix.com</a>> wrote:<br>
>>>> Overall, I think that removing repo or bpo permissions should be<br>
>>>> kept separate from the status itself. It would probably be wise<br>
>>>> to send around reminders to all core devs who have access and<br>
>>>> have not used their permissions every few year. The keys of those<br>
>>>> who don't respond could then be disabled, without affecting<br>
>>>> anything else; and, of course, easily be reenabled if needed,<br>
>>>> without much process either.<br>
>>><br>
>>> Aye, that's the key concept behind adding an explicit "Dormant" status<br>
>>> for core developers - they're folks that are still trusted with core<br>
>>> commit privileges if they choose to exercise them, but while they're<br>
>>> not using their access, it's better to deactivate their credentials to<br>
>>> reduce the potential for compromise.<br>
>>><br>
>>> We'd add a note to the developer guide that gave instructions on how<br>
>>> to request reactivation (likely just "Check the developer guide to<br>
>>> ensure you're up to speed with any changes since you were last active,<br>
>>> then past to python-committers requesting that your credentials be<br>
>>> reactivated").<br>
>>><br>
>><br>
>> Right, no one's role of having been a core dev will be wiped from history,<br>
>> they just won't have the core dev logo next to their <a href="http://bugs.python.org" rel="noreferrer" target="_blank">bugs.python.org</a><br>
>> username in the issue tracker (which if they are so dormant to have not<br>
>> added their GitHub username then they probably don't care about that<br>
>> anyway ;) . And flipping everything back on is a radio button and a word in<br>
>> <a href="http://bugs.python.org" rel="noreferrer" target="_blank">bugs.python.org</a> if their triage rights are removed and clicking on a<br>
>> button on a web page on GitHub if we clean up for dev access on the<br>
>> repository.<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>
>><br>
> <br>
> <br>
<br>
</blockquote></div></div>