PyBay Keynote

PEP 581/PEP 588: Migrating CPython issue tracker

In 2017, CPython codebase was moved to GitHub from Mercurial, an effort that took more than three years of planning and lots of volunteer coordination. The move proved to be successful and well-appreciated. New contributors face less barriers when contributing to Python. Core developers are benefiting from personal assistants in the form of GitHub bots and automations. Can the workflow be even better? In this talk, we'll look into other problems in CPython's workflow: the issue tracker itself.

The acceptance of PEP 581, by Python steering council means that another big workflow change is impending. Let's hear about some of the proposed plans on improving CPython's workflow, and learn how you can help and take part in this process.

Transcript

1. PyBay 2019
 @mariatta PEP 581 and PEP 588 Migrating CPython’s Issue Tracker #PEP581
2. PyBay 2019
 @mariatta Python Core Developer Backend Engineer CPython’s emoji and core-workflow expert @mariatta mariatta.ca #IceCreamSelfie WHO AM I? Mariatta ! https://zapier.com/jobs/ #PEP581
3. PyBay 2019
 @mariatta WHAT IS Core-workflow? #PEP581
4. PyBay 2019
 @mariatta Tools & infrastructure Contributors & maintainers’ experience #PEP581
5. PyBay 2019
 @mariatta CPython’s workflow bugs.python.org github.com/ python/cpython Python-dev Python-ideas Core-mentorship Discourse Zulip Sprints Language summit Conferences Issue tracker Chat Etc. Pull request Mailing lists #PEP581
6. PyBay 2019
 @mariatta CPython’s workflow bugs.python.org github.com/ python/cpython Python-dev Python-ideas Core-mentorship Discourse Zulip Sprints Language summit Conferences Issue tracker Chat Etc. Pull request Mailing lists #PEP581
7. PyBay 2019
 @mariatta Codebase moved to GitHub core-workflow improvements PEP 512 March 2017 Feb 2017 Git Bootcamp in Devguide Cherry-picker.py Bedevere June 2017 Blurb September 2017 Miss-islington September 2018 Blurb-it #PEP581
8. PyBay 2019
 @mariatta PEP 581 Using GitHub Issues for CPython #MyFirstPEP #PEP581
9. PyBay 2019
 @mariatta #PEP581
10. PyBay 2019
 @mariatta #PEP581
11. PyBay 2019
 @mariatta #PEP581
12. PyBay 2019
 @mariatta #PEP581
13. PyBay 2019
 @mariatta PEP 595 Improving bugs.python.org #PEP581
14. PyBay 2019
 @mariatta Please improve UI/UX BUGS.PYTHON.ORG I have trouble signing up Can I have REST APIs? How can I contribute? #PEP581
15. PyBay 2019
 @mariatta #PEP581
16. PyBay 2019
 @mariatta PEP 588 GitHub Issues Migration Plan #PEP581
17. PyBay 2019
 @mariatta Vendor lockdown risk: #PEP581
18. PyBay 2019
 @mariatta New CLA Host we need: #PEP581
19. PyBay 2019
 @mariatta Playground GitHub Issues copy over 100+ of issues from b.p.o we need: #PEP581
20. PyBay 2019
 @mariatta Updates to Devguide we need: #PEP581
21. PyBay 2019
 @mariatta Python Triage Team we need: #PEP581
22. PyBay 2019
 @mariatta bots & tools we need: #PEP581
23. PyBay 2019
 @mariatta Donations https://www.python.org/psf/donations/python-dev we need: #PEP581
24. PyBay 2019
 @mariatta Discuss https://discuss.python.org/c/core-workflow #PEP581
25. PyBay 2019
 @mariatta Contact mariatta@python.org
 Follow @mariatta Sponsor github.com/users/Mariatta/sponsorship Thank you #PEP581