[Python-Dev] Re: Adding GitHub usernames to the developer log
Le mer. 25 sept. 2019 à 08:24, Kyle Stanley 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/64LN2DSTXHZH6QFXBE5WLMLPXW7Y7VY7/
[Python-Dev] Re: Adding GitHub usernames to the developer log
I'm personally fine listing GItHub usernames in the devguide's developer list, but I'm also not trying to be anonymous on GitHub. But I will say that listing our GitHub usernames with our real names is not required to tell who is a core developer. In GitHub's UI there are multiple places it will tell you if a person is a member of the repository/team (e.g. hover cards, each comment a teammate makes). ___ 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/KOKMLHX4RSCWPCUR3YEQBVRB6R3VJOVS/
[Python-Dev] Re: Adding GitHub usernames to the developer log
> But I will say that listing our GitHub usernames with our real names is not required to tell who is a core developer. In GitHub's UI there are multiple places it will tell you if a person is a member of the repository/team Within the GitHub UI if you're not a member of the organization, it tells you who's a member of the org, but it does _not_ tell you what specific team they're on. There are close to 100 people that are in the Python organization on various teams but not a member of python-core. This includes anyone on the more recently created python-triage team or any of the PSF teams. I only became aware of this more recently, I'm not sure as to whether or not it's a configurable setting that is modifiable by the organization admins. To verify this, simply log out of your GitHub account and go into a PR with multiple organization members. Hovering over their name will show "Member of Python" but not the actual name of the team(s) they're on. For a recent example, logout of your GitHub account, go to PR-16375 ( https://github.com/python/cpython/pull/16375), then compare the hover cards between myself and Yury. Many people have their role within the organization mentioned in their GitHub bio (which appears on the hover card), but this is not always the case. It's also very useful when trying to find a specific core developer, particularly when trying to locate the GitHub usernames for specific experts. Locating the GitHub usernames of the experts is a bit of a separate issue, but having the usernames listed on the developer log would at least make it easier to do so without relying on bpo. On Wed, Sep 25, 2019 at 12:48 PM Brett Cannon wrote: > I'm personally fine listing GItHub usernames in the devguide's developer > list, but I'm also not trying to be anonymous on GitHub. > > But I will say that listing our GitHub usernames with our real names is > not required to tell who is a core developer. In GitHub's UI there are > multiple places it will tell you if a person is a member of the > repository/team (e.g. hover cards, each comment a teammate makes). > ___ > 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/KOKMLHX4RSCWPCUR3YEQBVRB6R3VJOVS/ > ___ 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/SGKRKMWXOAUW26332QAK2456QLDWL3AP/
[Python-Dev] Re: Adding GitHub usernames to the developer log
> 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 wrote: > Le mer. 25 sept. 2019 à 08:24, Kyle Stanley 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/
[Python-Dev] Re: The Python 2 death march
On 24/09/2019 04:21:45, Benjamin Peterson wrote: On Fri, Sep 13, 2019, at 18:18, Sumana Harihareswara wrote: Hi. I've joined python-dev to participate in this thread (I don't have email delivery turned on; I'll be checking back via the web). sorry :) Benjamin, I am sorry that I didn't check in with you, and assumed that January 1, 2020 would be the the date of the final 2.7 point release. (My understanding was based on Guido's EOL announcement from March last year https://mail.python.org/pipermail/python-dev/2018-March/152348.html -- I should have also gotten a review from you and not just the Steering Council in https://github.com/python/steering-council/issues/14 .) I'm going to continue this discussion here so I can make sure I understand the policy decision properly, and then (if necessary) update the FAQ. Based on what I've read here and what I see in https://www.python.org/dev/peps/pep-0373/#maintenance-releases , it sounds like the timeline will go something like: * 2019-10-19: release of 2.7.17 October * October, November, and December 2019: developers continue to fix issues in 2.7 * 2020-01-01: code freeze for 2.7.18 release candidate * January and February 2020: flexibility to fix any issues introduced since the 2.7.17 release, but no other bugs or security issues, and no 3.x backports Security issues will probably be fixed. At least, I wouldn't in abstract find that objectionable assuming someone wants to write a patch. * ~2020-04-02: release candidate for 2.7.18 * 2020-04-17: final 2.7.18 release I don't know if these will be the exact dates but probably close. Is this right? (If so, I can submit an update to PEP 373.) This is a little more complicated than I had anticipated when communicating out about the sunsetting. But I can find a way either to concisely communicate this, or to point to a user-friendly explanation elsewhere. A succinct statement of the relevant information is: "After 10 years, the core developers of CPython are stopping development on the 2.7.x line. The last release will be in April 2020." If it's easier to communicate that the sunset of CPython 2 is April 2020, that seems fine with me. January 1 was a somewhat arbitrary date we put in the PEP when 2020 still seemed like a long way off but people wanted to know whether 2.7 would be released until 2021 or not. I was never going to make a 2.7 release literally on January 1. (Fighting with GPG would make short work of New Year's resolutions pertaining to temperance and strong language.) I failed to anticipate how strongly people would latch onto that exact moment in time as the end of Python 2. I additionally share the bemusement of some other commentators on this thread to the idea of Python 2 "support", which is not something ever promised to Python 2 (or 3) users by CPython core developers. Essentially, next year, we're changing our "support" policy of Python 2.7 from "none, but we're nice people" to "none". I understand, but I hope that if a clear bug (perhaps especially a security bug) is found in Python 2.7 (perhaps one that is also in Python 3.x) the core devs will not be in principle opposed to fixing it. At least if one of them (or someone else sufficiently qualified) is prepared to do the work. Especially as you're "essentially" (and you ARE :-) -:) ) "such nice people". Best wishes Rob Cliffe Thanks. -- Sumana Harihareswara Changeset Consulting https://changeset.nyc ___ 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/MXCGMTXDY7BX6JBBU36O5YFRWWBB3NQE/ ___ 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/ETOBPFVKKS5ZBIUAYLOBXFXPOZB7A357/ --- This email has been checked for viruses by AVG. https://www.avg.com ___ 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/KQU7AQ5FZSOX5Z2HMX7LELJYUZTKMFXO/
[Python-Dev] Re: The Python 2 death march
On Wed, Sep 25, 2019, at 17:25, Rob Cliffe via Python-Dev wrote: > > I additionally share the bemusement of some other commentators on this > > thread to the idea of Python 2 "support", which is not something ever > > promised to Python 2 (or 3) users by CPython core developers. Essentially, > > next year, we're changing our "support" policy of Python 2.7 from "none, > > but we're nice people" to "none". > I understand, but I hope that if a clear bug (perhaps especially a > security bug) is found in Python 2.7 (perhaps one that is also in Python > 3.x) the core devs will not be in principle opposed to fixing it. At > least if one of them (or someone else sufficiently qualified) is > prepared to do the work. Especially as you're "essentially" (and you > ARE :-) -:) ) "such nice people". Before 2.7.18, sure. After that, in principle and practice, we're opposed. ___ 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/OA45RAVTXWE35JE3QKY2IXHYE7MQU4KP/
