> devguide now uses developers.rst which is generated from the following private file: https://github.com/python/voters/blob/master/python-core.toml
Ah good to know. I don't have access to the voters repo so I wasn't sure about the exact format or location of the file. > Guessing a GitHub identifier from a real name is not really easy. Yeah that's my main concern, particularly for new contributors trying to find or identify a specific core developer. For some people it's quite easy when it matches up with their real name (such as yourself and Brett for example). But for others it's definitely not obvious, especially when their real name isn't included in any part of their username. I admit that I'm guilty of this myself with using "aeros167" instead of "kstanley" or something along those lines (I had my GitHub account for a decent while before I started contributing to Python). This would be a non-issue with a public listing of core developer real names -> GitHub usernames that isn't dependent on bpo. On Wed, Sep 25, 2019 at 7:12 AM Victor Stinner <vstin...@python.org> wrote: > Le mer. 25 sept. 2019 à 08:24, Kyle Stanley <aeros...@gmail.com> a écrit : > > Recently, Brett updated the developer log in the devguide > > (https://devguide.python.org/developers/) to fetch the names of each > core > > developer and the date they were given commit privileges from the private > > python-committers repository. > > devguide now uses developers.rst which is generated from the following > private file: > https://github.com/python/voters/blob/master/python-core.toml > > The TOML file contains developer identifiers for: > > * GitHub > * bugs.python.org (Roundup) > * discuss.python.org (Discourse) > > > The motivation behind creating a a new topic for this issue was Brett's > > response to my comment in the PR that updated the devguide > > (https://github.com/python/devguide/pull/533#issuecomment-532405907). > > Essentially, if no core developers have an issue with having their GitHub > > username posted on the devguide, we can move forward with adding it. > > I'm in favor of making the GitHub identifiers public since it's part > of the trust relationship between core developers and contributors. > Some operations in our workflow *requires* a core developer on GitHub > pull requests. So it's good to be able to check who are core > developers on GitHub. > > Guessing a GitHub identifier from a real name is not really easy. > > The GitHub identifer can be *guessed* using the public bugs.python.org > data. For example, I'm user 2377 on bugs.python.org which shows that > my GitHub identifier is vstinner: > https://bugs.python.org/user2377 > > "Is Committer [hidden]" doesn't help to check if it's real or a fake > account :-/ Some core developers have multiple bugs.python.org > accounts. > > Note: I changed my bugs.python.org and GitHub identifiers one year ago > from "haypo" to "vstinner" :-) > > It seems like https://github.com/orgs/python/teams/python-core/members > is private. > > Victor > -- > Night gathers, and now my watch begins. It shall not end until my death. >
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/NKDS3ELJH3N3ARWJH2FAMBJ7KX4J3JKC/
