gh-migration
This repo is used to manage the migration from bugs.python.org to GitHub.
Relevant Documents
PEPs
- PEP 581 -- Using GitHub Issues for CPython: outlines the rationale for the migration and
- PEP 588 -- GitHub Issues Migration Plan: outlines the initial migration plan
- PEP 595 -- Improving bugs.python.org: includes issues with PEP 581/588, migration considerations, and a list of advantages that Roundup has over GitHub Issues
PEP 581 has been accepted, PEP 588 is still a draft (thus subject to changes), and PEP 595 has been withdrawn (but still contains valuable information).
Discourse threads
- PEP 581 - Using GitHub Issues (Dec 2018, 37 msgs): early discussion about PEP 581
- Proposal: Create “Bug Triage” team on GitHub (Mar 2019, 59 msgs): discussion about the triage team, labels, CODEOWNER file, etc.
- What are next steps for PEP 581? (Feb 2019, 3 msgs): short discussion about triaging, components and priority labels
- Using CLA Assistant for Python (Mar 2019, 25 msgs): discussion about using CLA-assistant
- CLA-assistant is No-Go (Jul 2019, 32 msgs): discussion about using CLA-assistant
Mailing list threads
- PEP 581: Using GitHub Issues for CPython (Mar 2019, python-dev, 7 msgs)
- Steering Council Update for April 2019 (Apr 2019, python-committers, 12 msgs)
- PEP 581 (Using GitHub issues for CPython) is accepted (May 2019, python-dev, 24 msgs)
- PEP 595: Improving bugs.python.org (May 2019, python-dev, 13 msgs):
- PEP 581/588 RFC: Collecting feedback about GitHub Issues (Aug 2019, python-dev, 3 msgs)
- Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues (Sep 2019, python-committers, 11 msgs)
Mailing list threads (historical)
- PSF Infrastructure Committee's recommendation for a new issue tracker (Oct 2006, python-dev, 3 msgs)
- PSF Infrastructure has chosen Roundup as the issue tracker for Python development (Oct 2006, python-dev, 3 msgs)
GitHub repos, issues, and projects
-
PEP 581/588 RFC: Collecting feedback about GitHub Issues (core-workflow repo): a long list of features/issues with comments and votes (from Aug 19th)
-
Consider whether or not to migrate bugs.python.org source code to this repo (bugs.python.org repo): contains info about different repos related to our fork of Roundup, b.p.o, and the other instances
-
Backup GitHub information (core-workflow repo): discussion about backing up GitHub data
-
Adding triagers role into CPython GitHub project (core-workflow repo)
-
Migrating to CLA Assistant project (core-workflow repo)
Wiki links
- How to make the tracker read-only: https://wiki.roundup-tracker.org/ReadOnlyTracker
- The Desired Tracker Features page discusses features we wanted for Roundup, and different ways to handle labels
- The Tracker Development page contains (mostly outdated) info about setting up and maintaining Roundup and irker, and using roundup-admin
- The Tracker Development Planning page contains other discussions
Zulip streams
Twitter threads
- https://twitter.com/mariatta/status/1128531347914407936 : Tweet about PEP 581 being approved, with some comments/concerns/suggestions
- https://twitter.com/VictorStinner/status/1128476712084410373 : Tweet about PEP 581 being approved, with a comment about not being able to assign issues to non-coredevs
Blog posts
- Python Core Sprint 2018: Part Two / PEP 581 (Sep 2018, Mariatta's blog)
- Mariatta Wijaya: Let's Use GitHub Issues Already! (May 2019, PSF blog)
Other links
Other instances
In addition to bugs.python.org, we are also hosting two other instances:
Jython
- Jython is already using GitHub issues
- Still has a legacy instance of Roundup at https://bugs.jython.org/ (bjo)
- Thread on the Jython ML that suggests to switch to GitHub issues but keep bugs.jython.org around
- They are using the form on python.org to sign the CLA and bpo to check it.
- They would be fine with a mostly read-only bjo
Roundup
- The tracker for Roundup is at https://issues.roundup-tracker.org/
- They are not planning to migrate
- They depend on us for hosting, unless they find another place