Opened 21 months ago

Last modified 5 weeks ago

#30363 new task

Meta-ticket: Migration to GitHub

Reported by: gh-tobiasdiez Owned by:
Priority: critical Milestone: sage-wishlist
Component: misc Keywords:
Cc: slelievre, dimpase Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by mkoeppe)

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

Change History (13)

comment:1 Changed 21 months ago by gh-tobiasdiez

  • Component changed from PLEASE CHANGE to misc
  • Priority changed from major to critical

comment:2 Changed 21 months ago by slelievre

  • Type changed from PLEASE CHANGE to task

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:

comment:3 Changed 21 months ago by slelievre

Note another discussion on this theme:

comment:4 Changed 21 months ago by 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.

comment:5 Changed 21 months ago by mkoeppe

  • Milestone changed from sage-9.2 to sage-9.3

comment:6 Changed 15 months ago by mkoeppe

  • Milestone changed from sage-9.3 to sage-9.4

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

comment:7 Changed 14 months ago by 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

comment:8 Changed 14 months ago by slelievre

  • Cc slelievre added
  • Description modified (diff)

comment:9 Changed 14 months ago by 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

comment:10 Changed 14 months ago by embray

  • Milestone changed from sage-9.4 to sage-wishlist

comment:11 Changed 5 weeks ago by mkoeppe

  • Description modified (diff)
  • Summary changed from Migration to GitHub to Meta-ticket: Migration to GitHub

comment:12 Changed 5 weeks ago by mkoeppe

  • Cc dimpase added
  • Description modified (diff)

comment:13 Changed 5 weeks ago by mkoeppe

  • Description modified (diff)
Note: See TracTickets for help on using tickets.