Fate of Roundup and the instances

[ezio-melotti]

Roundup has a "core" and one or more tracker "instances". The fork of Roundup that we are currently hosting/running is used by 3 instances:

• https://bugs.python.org/ (bpo), used to track CPython issues
• https://bugs.jython.org/ (bjo), used to track Jython issues
• https://issues.roundup-tracker.org/, used to track Roundup issues

Since the other two instances rely on us, we need to keep this into account before we shut down Roundup/bpo.

Jython

• Jython is already using GitHub issues
• Still has a legacy instance of Roundup at https://bugs.jython.org/ (bjo)
• They haven't migrated the old issues
• They are also using bjo for the CLA
• They would be fine with a mostly read-only bjo
• See also this thread on the Jython ML that suggests to switch to GitHub issues but keep bugs.jython.org around

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

CPython

After the migration to GitHub issues is completed, we have at least 3 options:

1. Make bpo read-only and keep Roundup running;

   • the other instances can keep running;
   • it will be possible to access old issues and their metadata;
   • it will be possible to add messages with redirect links;
   • it will be possible to search and filter old issues;
   • we need to make it read-only;

2. Create a static mirror of bpo and shut down Roundup:

   • other instances will need to find an alternative solution;
   • it will be possible to access old issues and their metadata (HTML only);
   • it will be possible to add messages with redirect links (before making it static);
   • it will not be possible to search and filter old issues;
   • we need to create the static mirror;

3. Create a script that redirects to the corresponding GH issue:

   • other instances will need to find an alternative solution;
   • it will not be possible to access/search old issues;
   • we need to create a redirect script that maps the issue numbers;

Since this issue is non-blocking, we can adopt the first option and then switch to the second or third down the line, depending on what the other projects do.

[ammaraskar]

Make bpo read-only and keep Roundup running;

I really like this option but coupled with (3), maybe a read-only instance could be available on archive.bugs.python.org or similar and then bugs.python.org/issueXXXX links could redirect to the new Github issue. That way existing links continue to take you to the latest place for discussion but people still have the ability to search on the archived read-only roundup instance.