{"id":20286981,"url":"https://github.com/psf/gh-migration","last_synced_at":"2025-12-03T01:05:39.093Z","repository":{"id":41534373,"uuid":"298307636","full_name":"psf/gh-migration","owner":"psf","description":"This repo is used to manage the migration from bugs.python.org to GitHub.","archived":false,"fork":false,"pushed_at":"2022-09-11T00:29:06.000Z","size":7,"stargazers_count":42,"open_issues_count":9,"forks_count":8,"subscribers_count":19,"default_branch":"master","last_synced_at":"2025-03-02T03:05:10.914Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/psf.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2020-09-24T14:42:00.000Z","updated_at":"2024-09-12T09:52:27.000Z","dependencies_parsed_at":"2023-01-18T03:15:26.160Z","dependency_job_id":null,"html_url":"https://github.com/psf/gh-migration","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/psf%2Fgh-migration","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/psf%2Fgh-migration/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/psf%2Fgh-migration/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/psf%2Fgh-migration/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/psf","download_url":"https://codeload.github.com/psf/gh-migration/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":241780497,"owners_count":20019061,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-14T14:37:44.685Z","updated_at":"2025-12-03T01:05:34.029Z","avatar_url":"https://github.com/psf.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# gh-migration\nThis repo is used to manage the migration from bugs.python.org to GitHub.\n\n# Relevant Documents\n\n## PEPs\n\n* [PEP 581 -- Using GitHub Issues for CPython](https://www.python.org/dev/peps/pep-0581/): outlines the rationale for the migration and\n* [PEP 588 -- GitHub Issues Migration Plan](https://www.python.org/dev/peps/pep-0588/): outlines the initial migration plan\n* [PEP 595 -- Improving bugs.python.org](https://www.python.org/dev/peps/pep-0595/): includes issues with PEP 581/588, migration considerations, and a list of advantages that Roundup has over GitHub Issues\n\nPEP 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).\n\n## Discourse threads\n\n* [PEP 581 - Using GitHub Issues](https://discuss.python.org/t/pep-581-using-github-issues/535) (Dec 2018, 37 msgs): early discussion about PEP 581\n* [Proposal: Create “Bug Triage” team on GitHub](https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992) (Mar 2019, 59 msgs): discussion about the triage team, labels, CODEOWNER file, etc.\n* [What are next steps for PEP 581?](https://discuss.python.org/t/what-are-next-steps-for-pep-581/864) (Feb 2019, 3 msgs): short discussion about triaging, components and priority labels\n* [Using CLA Assistant for Python](https://discuss.python.org/t/using-cla-assistant-for-python/990) (Mar 2019, 25 msgs): discussion about using CLA-assistant\n* [CLA-assistant is No-Go](https://discuss.python.org/t/cla-assistant-is-no-go/2066) (Jul 2019, 32 msgs): discussion about using CLA-assistant\n\n## Mailing list threads\n\n* [PEP 581: Using GitHub Issues for CPython](https://mail.python.org/archives/list/python-dev@python.org/thread/W4W6YSJH7ZOG3N6Y6BFFGVT6CPDS7X2P/) (Mar 2019, python-dev, 7 msgs)\n* [Steering Council Update for April 2019](https://mail.python.org/archives/list/python-committers@python.org/thread/UEKNCJ36H6GZKDD7MENZYJKD3FB3TIYX/) (Apr 2019, python-committers, 12 msgs)\n* [PEP 581 (Using GitHub issues for CPython) is accepted](https://mail.python.org/archives/list/python-dev@python.org/thread/CQWQIM5Y6ELN3NRBT5RR6U5WY5WF7KXZ/#CQWQIM5Y6ELN3NRBT5RR6U5WY5WF7KXZ) (May 2019, python-dev, 24 msgs)\n* [PEP 595: Improving bugs.python.org](https://mail.python.org/archives/list/python-dev@python.org/thread/OFENXHCWVADJS7I4HLY4F5MHCDW6TJV6/#OFENXHCWVADJS7I4HLY4F5MHCDW6TJV6) (May 2019, python-dev, 13 msgs):\n* [PEP 581/588 RFC: Collecting feedback about GitHub Issues](https://mail.python.org/archives/list/python-dev@python.org/thread/S5L54M2HJ4DM46HLU45HVEYYAQYXHEQ2/#S5L54M2HJ4DM46HLU45HVEYYAQYXHEQ2) (Aug 2019, python-dev, 3 msgs)\n* [Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues](https://mail.python.org/archives/list/python-committers@python.org/thread/IFSHRRBKRP56NOVI4DDWNWKAUK53C5SK/#2HWYHURO7XETBZO7YR4V6JDWX3FA2OA5) (Sep 2019, python-committers, 11 msgs)\n\n## Mailing list threads (historical)\n\n* [PSF Infrastructure Committee's recommendation for a new issue tracker](https://mail.python.org/archives/list/python-dev@python.org/thread/KSJTYU4XC5VTLHJGV76ZCGTEQZY26D7X/#6MY6XXFRXFGSGQ3NJELX7HEJUISMHYIC) (Oct 2006, python-dev, 3 msgs)\n* [PSF Infrastructure has chosen Roundup as the issue tracker for Python development](https://mail.python.org/archives/list/python-dev@python.org/thread/VK3C6G6QNRDOT66YSX4TZSUG2JUFQK2F/#VK3C6G6QNRDOT66YSX4TZSUG2JUFQK2F) (Oct 2006, python-dev, 3 msgs)\n\n## GitHub repos, issues, and projects\n\n* [PEP 581/588 RFC: Collecting feedback about GitHub Issues](https://github.com/python/core-workflow/issues/359) (core-workflow repo): a long list of features/issues with comments and votes (from Aug 19th)\n* [Consider whether or not to migrate bugs.python.org source code to this repo](https://github.com/python/bugs.python.org/issues/2) (bugs.python.org repo): contains info about different repos related to our fork of Roundup, b.p.o, and the other instances\n* [Backup GitHub information](https://github.com/python/core-workflow/issues/20) (core-workflow repo): discussion about backing up GitHub data\n\n* [Adding triagers role into CPython GitHub](https://github.com/python/core-workflow/projects/3) project (core-workflow repo)\n* [Migrating to CLA Assistant](https://github.com/python/core-workflow/projects/1) project (core-workflow repo)\n\n## Wiki links\n\n* How to make the tracker read-only: https://wiki.roundup-tracker.org/ReadOnlyTracker\n* The [Desired Tracker Features](https://wiki.python.org/moin/DesiredTrackerFeatures) page discusses features we wanted for Roundup, and different ways to handle labels\n* The [Tracker Development](https://wiki.python.org/moin/TrackerDevelopment) page contains (mostly outdated) info about setting up and maintaining Roundup and irker, and using roundup-admin\n* The [Tracker Development Planning](https://wiki.python.org/moin/TrackerDevelopmentPlanning) page contains other discussions\n\n## Zulip streams\n\n* https://python.zulipchat.com/#narrow/stream/130206-pep581\n\n## Twitter threads\n\n* https://twitter.com/mariatta/status/1128531347914407936 : Tweet about PEP 581 being approved, with some comments/concerns/suggestions\n* 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\n\n## Blog posts\n\n* [Python Core Sprint 2018: Part Two / PEP 581](https://mariatta.ca/core-sprint-2018-part-2.html#pep-581) (Sep 2018, Mariatta's blog)\n* [Mariatta Wijaya: Let's Use GitHub Issues Already!](https://pyfound.blogspot.com/2019/05/mariatta-wijaya-lets-use-github-issues.html) (May 2019, PSF blog)\n\n## Other links\n\n* [Karthikeyan test tracker on GitLab](https://gitlab.com/tirkarthi/python-bugs/-/issues) (from [a python-dev mail](https://mail.python.org/archives/list/python-dev@python.org/message/O7MIL7DLR6HZ7XMZIUTZE6VWY2ROCY4F/))\n\n\n\n# Other instances\n\nIn addition to bugs.python.org, we are also hosting two other instances:\n\n## Jython\n\n* Jython is already using [GitHub issues](https://github.com/jython/jython/issues)\n* Still has a legacy instance of Roundup at https://bugs.jython.org/ (bjo)\n* [Thread on the Jython ML that suggests to switch to GitHub issues but keep bugs.jython.org around](https://sourceforge.net/p/jython/mailman/jython-dev/thread/CAOhO%3DaNp9oPkMwO58vK0L5gqL_nG8UD0mWom%3D1XLqxdbyfU34w%40mail.gmail.com/#msg37020624)\n* They are using [the form on python.org](https://www.python.org/psf/contrib/contrib-form) to sign the CLA and bpo to check it.\n* They would be fine with a mostly read-only bjo\n\n## Roundup\n\n* The tracker for Roundup is at https://issues.roundup-tracker.org/\n* They are not planning to migrate\n* They depend on us for hosting, unless they find another place\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fpsf%2Fgh-migration","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fpsf%2Fgh-migration","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fpsf%2Fgh-migration/lists"}