[vstinner]

List core developers who left the team in a separated Emeritus Core Developers table.

[read-the-docs-community]

Documentation build overview

📚 CPython devguide | 🛠️ Build #35871041 | 📁 Comparing 56c92c7 against latest (8c852bd)

  🔍 Preview build  

1 file changed

± core-team/team-log/index.html

[vstinner]

Currently, it's uneasy for me to distinguish Core Developers who are still in the team from the ones who left in https://devguide.python.org/core-team/team-log/ table. I propose moving Core Developers who left the team to a new Emeritus Core Developers table.

Having a separated table would help me to have an idea of how many core developers are currently active (and how many left) which an useful information to me.

See also the related Steering Council ticket which uses the "Emeritus committers" term: Remove commit bit from inactive core devs as part of SC elections.

This change depends on https://github.com/python/voters/pull/140 (in the private voters repository) to generate core-team/core-team.csv and core-team/emeritus-core-team.csv.

[encukou]

Having a separated table would help me to have an idea of how many core developers are currently active (and how many left) which an useful information to me.

Could we show two numbers for that, and keep the chronological log?

[hugovk]

No strong opinion on whether to split the tables, but some suggestions for if we do.

[hugovk]

The main list now drops the redundant Left column:

:header: "Name", "GitHub username", "Joined", "Notes"

An idea, shall we re-order this so it's easier to append the left date when shuffling CSV rows in a text editor?

Suggested change

	:header: "Name", "GitHub username", "Joined", "Left", "Notes"
	:header: "Name", "GitHub username", "Joined", "Notes", "Left"

It also makes the two CSVs easier to read programatically.

[vstinner]

Notes is longer than other fields. I prefer putting it at the end (as it is currently). Also, I like have the two dates written one after the other (joined,left).

[vstinner]

The Python Security Response Team (PSRT) already have a Members emeritus. The process is defined by PEP 811:

Once per year the Steering Council will receive a report of inactive members of the PSRT with the recommendation to remove the inactive users from the PSRT. “Inactive” is defined here as a member who hasn’t coordinated or commented on a vulnerability report in the past year since the last report was generated. The Steering Council may remove members of the PSRT with a simple vote.

[vstinner]

Could we show two numbers for that, and keep the chronological log?

That would be an option. But I would still prefer to have a separated table for Members emeritus 🙂

[vstinner]

I changed the title from "Emeritus Members" to "Members emeritus" to use the same title than the PSRT page.

[orsenthil]

If this were generated automatically based on say last commit or github activity date, this document will remain alive, otherwise it will meet the same fate as previous innumerable attempts.

[encukou]

Well, count me as -1. IMO, the log should stay a log.
Unlike PSRT, this list is now tied to two kinds of permissions (commit bit & voting) and we might be adding more. (Presumable, you can also lose both bits but stay on the list, at least temporarily.) So it's not clear to me what exactly “emeritus” (or “left” for that matter) should mean nowadays, and I don't want to emphasize this bit of information.

[StanFromIreland]

Victor, I usually use https://hugovk.dev/python-core-team/ to check membership, maybe that could work for you?