On 10.12.2019 23:57, Nick Coghlan wrote: > On Wed, 11 Dec 2019 at 06:52, M.-A. Lemburg <m...@egenix.com> wrote: >> The conversion to an inactive dev is something that core devs need >> to be asked to agree to, and thus needs to be managed as a status >> flag, not depend on commits to the repo. > > All committers were asked to check the voter list in mid-November, > before the ballot period started: > https://mail.python.org/archives/list/python-committers@python.org/thread/EXT5XHEHPGJQS3LW5UG7SK63C2GJDJ2P/ > > The relevant section in PEP 13 is this one: > > ====================== > There's no time limit on core team membership. However, in order to > provide the general public with a reasonable idea of how many people > maintain Python, core team members who have stopped contributing are > encouraged to declare themselves as "inactive". Those who haven't made > any non-trivial contribution in two years may be asked to move > themselves to this category, and moved there if they don't respond. To > record and honor their contributions, inactive team members will > continue to be listed alongside active core team members; and, if they > later resume contributing, they can switch back to active status at > will. While someone is in inactive status, though, they lose their > active privileges like voting or nominating for the steering council, > and commit access. > ====================== > > So everyone *was* asked if they wanted to be kept as active for this > election, but it wasn't explicitly emphasised to the folks that were > otherwise going to being marked as inactive that this was happening > (as it had to be inferred from the absence of your name, rather than > being called out as a list of voters that had been flagged as > potentially inactive since the last voter roll was generated).
I'm sorry, but I had not expected to be delisted and thus did not check the voters list. The email also did not make it clear that there was a change which could result in such an action. I read it to mean to check the email address, which in my case, I knew was correct. I do believe that asking a person to have his or status changed to inactive requires a bit more personal approach than this. The PR mentions that the script removed 18 core devs from the list of active ones. It would certainly have been possible to contact these directly and asking them if they are ok with that plan of action: https://github.com/python/voters/pull/10 Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, Dec 11 2019) >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ >>> Python Database Interfaces ... http://products.egenix.com/ >>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ ________________________________________________________________________ ::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ http://www.malemburg.com/ _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/FFT3LOHZ6J73APXCP2Z4GQFGAZSVRLQK/ Code of Conduct: https://www.python.org/psf/codeofconduct/
