René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Machine-parsable developers list","articleBody":"We currently have several lists of developers, some manually maintained, some machine-generated, including:\r\n\r\n* a machine-parsable list in the voters repo (private)\r\n* a machine-generated (from the list above) [developers.csv](https://github.com/python/devguide/blob/main/core-developers/developers.csv) (in the devguide repo)\r\n* a machine-generated (from the csv above) [developer log](https://devguide.python.org/developers/) (in the devguide)\r\n* a separately-maintained [list of experts](https://github.com/python/devguide/blob/main/core-developers/experts.rst) (in the devguide repo)\r\n* a machine-generated (from the list of experts above) nosy-list autocomplete on bpo (no longer used)\r\n* a separately-maintained [translators list](https://devguide.python.org/documentation/translating/) (in the devguide)\r\n* a separately-maintained [CODEOWNERS file](https://github.com/python/cpython/blob/main/.github/CODEOWNERS) (in the cpython repo)\r\n* possibly others (e.g. release managers), more or less related to list of core devs\r\n\r\nI suggest to consolidate this into two lists:\r\n* the one in the `voters` repo (private) can remain mostly unchanged\r\n* a new list in this repo can be created to list experts\r\n\r\nThe new list could use a similar format: listing users and fields about:\r\n* their GitHub username\r\n  * and possibly the GitHub teams they belong to (to generate teams)\r\n  * see python/core-workflow#350\r\n* the modules they maintain (to generate the `CODEOWNERS` file)\r\n* the modules, interest areas, platforms, translation languages they are interested in (to generate the expert index)\r\n  * the translator table could be moved back into the expert list \r\n    * see also #842\r\n  * the release manager table in the main page could be generated from this too\r\n* possibly flags like `is_triager`, `is_core_dev`, `release_manager=\u003cversions\u003e`, `translator=\u003clanguage\u003e`\r\n  * these could be used to mark names in the expert index and to create RM and translator tables\r\n  * we could also have an `is_bot` for bots\r\n\r\nWe 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.\r\n\r\nSome relevant links:\r\n* PR that implemented a similar idea: #517 \r\n* Issue where the idea was proposed: #507 \r\n* [Discourse message about listing maintainers](https://discuss.python.org/t/gaps-in-maintenance-coverage-language-summit-follow-up/15369/8?u=ezio-melotti)\r\n* [Discourse message about notifying experts](https://discuss.python.org/t/github-issues-migration-is-coming-soon/13791/66?u=ezio-melotti)","author":{"url":"https://github.com/ezio-melotti","@type":"Person","name":"ezio-melotti"},"datePublished":"2022-04-30T19:17:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/848/devguide/issues/848"}