There are a few sets of people that we consider core developers:
- people with the check on bugs.python.org
- people on the python-committers@ mailing list
- people in https://hg.python.org/committers.txt
- people in https://devguide.python.org/developers/
- people on the Python core team on GitHub
We discussed this in some depth on python-committers in early August but in different context. Here I’m interested in something else.
We need a good definition of who a core developer is because we’re approaching a delicate time of discussing governance and eventually voting on a model. Since the question of governance and other current affairs affects those contributors the most who are currently active, it feels natural to me to call committers the people listed in the Python core team on GitHub.
In this context we can assume all inactive core developers as Emeritus committers. This acknowledges their past contributions but at the same time signals they are retired. For example, they would not vote on current affairs. Just like Professor Emeritus, they could resume their activity if interested. It’s as easy as getting the commit bit on GitHub and resuming contribution.
(I think it was @guido who first suggested the term.)
What about Discourse? I don’t want to exclude people who want to participate in the discussion but I feel like splitting hair between the rights to generally discuss and the right to vote is not productive.