PyConDE 2019 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. #PEP581 #PEP581 #PyConDE 2019
 @mariatta PEP 581 and PEP 588 Migrating CPython’s Issue Tracker
2. #PEP581 #PyConDE 2019
 @mariatta Python Core Developer Backend Engineer CPython’s emoji and core-workflow expert @mariatta mariatta.ca #IceCreamSelfie #BotsForHumanity WHO AM I? Mariatta ! https://zapier.com/jobs/
3. #PEP581 #PyConDE 2019
 @mariatta WHAT IS Core-workflow?
4. #PEP581 #PyConDE 2019
 @mariatta Tools & infrastructure Contributors & maintainers’ experience
5. #PEP581 #PyConDE 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
6. #PEP581 #PyConDE 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
7. #PEP581 #PyConDE 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
8. #PEP581 #PEP581 #PyConDE 2019
 @mariatta PEP 581 Using GitHub Issues for CPython #MyFirstPEP https://www.python.org/dev/peps/pep-0581/
9. #PEP581 #PyConDE 2019
 @mariatta
10. #PEP581 #PyConDE 2019
 @mariatta
11. #PEP581 #PyConDE 2019
 @mariatta
12. #PEP581 #PyConDE 2019
 @mariatta
13. #PEP581 #PEP581 #PyConDE 2019
 @mariatta PEP 595 Improving bugs.python.org
14. #PEP581 #PyConDE 2019
 @mariatta Please improve UI/UX BUGS.PYTHON.ORG I have trouble signing up Can I have REST APIs? How can I contribute?
15. #PEP581 #PEP581 #PyConDE 2019
 @mariatta
16. #PEP581 #PEP581 #PyConDE 2019
 @mariatta PEP 588 GitHub Issues Migration Plan
17. #PEP581 #PyConDE 2019
 @mariatta Vendor lockdown risk
18. #PEP581 #PyConDE 2019
 @mariatta New CLA Host we need: https://github.com/python/core-workflow/ issues/360
19. #PEP581 #PyConDE 2019
 @mariatta Playground GitHub Issues copy over 100+ of issues from b.p.o we need:
20. #PEP581 #PyConDE 2019
 @mariatta Updates to Devguide we need:
21. #PEP581 #PyConDE 2019
 @mariatta Python Triage Team we need: https://devguide.python.org/triaging/ #python-triage-team
22. #PEP581 #PyConDE 2019
 @mariatta bots & tools we need: https://github.com/python/core-workflow/ issues/359
23. #PEP581 #PyConDE 2019
 @mariatta Donations https://www.python.org/psf/donations/ python-dev we need:
24. #PEP581 #PyConDE 2019
 @mariatta Discuss https://discuss.python.org/c/core- workflow
25. #PEP581 #PyConDE 2019
 @mariatta Contact mariatta@python.org
 Follow @mariatta Sponsor github.com/users/Mariatta/sponsorship Thank you