[python-committers] Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues
On 11Sep2019 1117, Steven D'Aprano wrote: On Wed, Sep 11, 2019 at 10:17:48AM +0100, Benjamin Peterson wrote: In other words, vanilla GitHub issue search does address Raymond's request? Given that github search is unlikely to be able to search "our voluminous history of already evaluated and decided feature requests" on b.p.o then it probably doesn't. Besides, I spent about two minutes playing with github's filter/search, not long enough to really test its capabilities and limitations. I've spent a couple of years playing with GitHub's filter/search on much smaller projects than CPython and I find its search woefully inadequate compared to bpo. But I know some people find it easier, so I'll probably rely on them to do the history searches for me after we switch. Cheers, Steve ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/ZQTBEO26FJPJNWXSYTJPIKHYPZBPHJFD/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Tooling built around historical record of core devs
A couple months ago I generated a canonical, historical record of people who have been core developers at https://github.com/python/voters/blob/master/python-core.toml. The goal was for that list to feed into the devguide for the public record of who has been a core dev as well has to help calculate who has been active for voting purposes. Both are now done. https://devguide.python.org/developers/ has been updated to use a CSV generated from the python-core.toml file using code found in that repository. This should make maintaining that page in the devguide much easier and make it complete. In the voters repo I have also written code for validating the data in python-core.toml (which I hope to make into a GitHub action at some point to act as a check against PRs), a command to calculate who has authored or committed a change to CPython in the past two years to be classified as active, and code to generate a voter roll from that active contributor data. I am also hoping to help automate the adding/revoking permissions to at least GitHub, if not also b.p.o and discuss.python.org (this is why it's important you fill that information in python-core.toml). And in case anyone is curious, as of today there are currently 76 out of 166 people who have contributed in the past two years and thus are currently considered active. ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/N4EORFP6AKWFW2AZXAJAANXH2FXFESOZ/ Code of Conduct: https://www.python.org/psf/codeofconduct/
