[python-committers] Changing commiter status (was: Missing In Action)

[M.-A. Lemburg]

Victor:

please make sure that you contact the developers whos status
you intend to modify prior to doing so. Being a core developer
of Python is a status and not something that should be changed
without consent by the developer in question.

Also note that the dev list log doesn't include all core developers.
Data from before the move to SVN in 2006 is essentially missing,
since AFAIK we never kept around a log of who received the core
bit before that.

And there were times when the core bit itself did not exist, since
all patches had to go through the small team around Guido
which had access to the CVS system at the time.

Overall, I think that removing repo or bpo permissions should be
kept separate from the status itself. It would probably be wise
to send around reminders to all core devs who have access and
have not used their permissions every few year. The keys of those
who don't respond could then be disabled, without affecting
anything else; and, of course, easily be reenabled if needed,
without much process either.

Thanks,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Jun 18 2018)
>>> 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/



On 16.06.2018 01:59, Victor Stinner wrote:
> Hi,
> 
> Last months, we debated about the number of *active* core developers.
> 
> The problem is that there are 3 lists and each has different numbers
> of core developers: 90 according to GitHub, 170 according to
> bugs.python.org.
> 
> * https://github.com/orgs/python/teams/python-core/members
> * https://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300
> * https://devguide.python.org/developers/
> 
> I propose to move inactive core developers to a new list (ex:
> "Inactive Core Developers") and remove their permission for security
> reasons. If the core developer shows up, they will just have to ask a
> GitHub administrator (like Brett Cannon) to be added again.
> 
> My intent is to enhance security and better track of the current
> number of active core developers.
> 
> In practice, it should only mean removing these inactive developers
> from the list of core developers on bugs.python.org. To make sure that
> a developer can become again a core developer, we should track that we
> dropped their priviledge. We can add new section in the devguide,
> near:
> https://devguide.python.org/developers/#permissions-dropped-on-request
> 
> There are already two lists of inactive core developers in the
> devguide: "Permissions Dropped on Request" and "Permissions Dropped
> after Loss of Contact".
> 
> I propose to start by removing all core developers who didn't migrate
> to GitHub yet, since it's a simple way to check if they are active
> since February 2017.
> 
> I can work on a concrete list of developers, but it seems like it will
> take me some time. Some developers are cores according to
> bugs.python.org but I cannot find them in the devguide list. Some
> developers are no longer core devs according to devguide, but still
> core in bugs.python.org. There are some inconsistencies.
> 
> Victor
> _______________________________________________
> 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/
>