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.
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.
Community, Use Cases
Domain Expertise:some
Python Skill Level:basic
Abstract as a tweet:PEP 581 and PEP 588: Migrating CPython's Issue Tracker 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.