├── .github └── CODE_OF_CONDUCT.rst └── README.md /.github/CODE_OF_CONDUCT.rst: -------------------------------------------------------------------------------- 1 | :orphan: 2 | 3 | Code of Conduct 4 | =============== 5 | 6 | Please note that all interactions on 7 | `Python Software Foundation `__-supported 8 | infrastructure is `covered 9 | `__ 10 | by the `PSF Code of Conduct `__, 11 | which includes all infrastructure used in the development of Python itself 12 | (e.g. mailing lists, issue trackers, GitHub, etc.). 13 | 14 | In general this means everyone is expected to be open, considerate, and 15 | respectful of others no matter what their position is within the project. 16 | 17 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Meta-tracker for bugs.python.org 2 | 3 | bugs.python.org is essentially a custom workflow engine for the CPython core 4 | development team. This means it needs a meta-tracker to track feature requests, 5 | as well as a general issue tracker to track maintainability and usability issues. 6 | 7 | Historically that meta-tracker has been maintained at http://psf.upfronthosting.co.za/roundup/meta, 8 | but it doesn't need any kind of heavy customisation or integration with other tools, so GitHub 9 | Issues serve the purpose better than maintaining a second Roundup instance does. 10 | 11 | ## Development workflow for bugs.python.org 12 | 13 | bugs.python.org is a Roundup deployment, maintained as described in https://wiki.python.org/moin/TrackerDevelopment. 14 | 15 | It uses Mercurial in order to simplify updating to new version of Roundup (which is still using Mercurial upstream). 16 | 17 | See https://github.com/python/bugs.python.org/issues/2 for the discussion on potentially moving to a GitHub based 18 | workflow that better aligns with the workflows used by other CPython core-workflow projects (while still accounting 19 | for the need to periodically rebase on new upstream releases). 20 | --------------------------------------------------------------------------------