Meta-ticket: Migration to GitHub

[gh-tobiasdiez]

GitHub has many features that are superior to the ones trac provides. For example, pull request reviews, code view and navigation, issue management with projects and labels, GitHub actions for automatic code checks and other automation. Moreover, it's the de facto standard for open source projects.

For this reason, I would propose to migrate to GitHub. The following needs to be done in this process:

• #30406: Make it possible to contribute via GitHub Pull Requests (this is the most important one for me as a 'simple' contributor).
• #33457 Meta-ticket: migrate from patchbot to github actions
• Migrate existing issues

See also:

• #33725 Migrate wiki.sagemath.org to trac.sagemath.org/wiki
• #28936 Meta-ticket: Adopt mainstream Python testing/linting infrastructure: tox, pytest, ..., describe in Developer's Guide

• ​https://groups.google.com/g/sage-devel/c/ayOL8_bzOfk/m/8ljxgU--BgAJ (sage-devel 2016-01, 2020-12, 2021-01, 2021-03)

[slelievre]

There once was a bot called sageb0t that would transform any pull request opened on the SageMath repo at GitHub to a ticket on the Sage Trac server. The bot was lost.

There is now a mechanism that will transform any merge request opened against the SageMath repo at GitLab into a ticket on the Sage Trac server. Read more about this mechanism:

• ​sage-devel, 2019-07, New contributor experience

• ​sage-devel, 2019-04, gitlab status

• ​sage-devel, 2018-08, Enabling Merge Requests from GitLab

[slelievre]

Note another discussion on this theme:

• ​sage-devel, 2018-07, talk

[gh-tobiasdiez]

Thanks for these links.

I would argue that a simple bot that converts github pull requests and issues to trac is not enough in the long term. It might ease the transition period, but also duplicates the infrastructure. Moreover, you don't get to enjoy the above mentioned benefits if pull requests are still reviewed here on trac etc.

Are there any issues that prevent a clear one-time migration of the current issues and code contributions to github, say using tools like ​https://github.com/trustmaster/trac2github.

[mkoeppe]

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

[swenson]

I wrote some of the sageb0t code, and it is still available here: ​https://github.com/swenson/sage-workflow/blob/master/sagedev/pr_export.py

[embray]

-1 we have already put a significant amount of work into migration to GitLab which doesn't take money from the US government to imprison migrant children: ​https://gitlab.com/sagemath