Machine-parsable developers list

We currently have several lists of developers, some manually maintained, some machine-generated, including:

• a machine-parsable list in the voters repo (private)
• a machine-generated (from the list above) developers.csv (in the devguide repo)
• a machine-generated (from the csv above) developer log (in the devguide)
• a separately-maintained list of experts (in the devguide repo)
• a machine-generated (from the list of experts above) nosy-list autocomplete on bpo (no longer used)
• a separately-maintained translators list (in the devguide)
• a separately-maintained CODEOWNERS file (in the cpython repo)
• possibly others (e.g. release managers), more or less related to list of core devs

I suggest to consolidate this into two lists:

• the one in the voters repo (private) can remain mostly unchanged
• a new list in this repo can be created to list experts

The new list could use a similar format: listing users and fields about:

• their GitHub username
  • and possibly the GitHub teams they belong to (to generate teams)
  • see python/core-workflow#350
• the modules they maintain (to generate the CODEOWNERS file)
• the modules, interest areas, platforms, translation languages they are interested in (to generate the expert index)
  • the translator table could be moved back into the expert list
    • see also #842
  • the release manager table in the main page could be generated from this too
• possibly flags like is_triager, is_core_dev, release_manager=<versions>, translator=<language>
  • these could be used to mark names in the expert index and to create RM and translator tables
  • we could also have an is_bot for bots

We should also move some info from the voters file to here, in particular the joined, left, notes info. This information is already public and by moving it here we will remove duplication and simplify the generation of developers.csv in this repo. The only remaining duplicated info between the two lists will be the GitHub username.

Some relevant links:

• PR that implemented a similar idea: #517
• Issue where the idea was proposed: #507
• Discourse message about listing maintainers
• Discourse message about notifying experts

Commencez par lire les fichiers existants developers.csv, experts.rst, la documentation de traduction, CODEOWNERS et le flux de génération de ce dépôt. Examinez les issues et PR associés #517, #507, #842 et python/core-workflow#350 avant de définir le format de la liste. C’est terminé lorsque le périmètre est convenu et que la liste consolidée peut générer les sorties documentées relatives aux développeurs et à l’ownership sans maintenance dupliquée.