Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Meta-ticket: Migration from Trac to GitHub #30363

Closed
tobiasdiez opened this issue Aug 14, 2020 · 106 comments
Closed

Meta-ticket: Migration from Trac to GitHub #30363

tobiasdiez opened this issue Aug 14, 2020 · 106 comments
Milestone
sage-10.0

Comments

@tobiasdiez
Copy link
Contributor

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. Also, backlinks from any of the conversation branches are shown automatically. Moreover,

Discussion:

Pro/con overview: https://github.com/sagemath/trac-to-github/blob/master/docs/Github-vs-Gitlab-vs-trac.md

Vote: https://groups.google.com/g/sage-devel/c/7h5JoRgHpxY

The following needs to be done in this process (see also https://github.com/sagemath/trac-to-github/milestones?direction=asc&sort=due_date&state=open)

The proposed full migration to GitHub Issues in one shot makes the following tasks unnecessary:

See also:

CC: @slel @dimpase @roed314 @williamstein @kwankyu @seblabbe @videlec

Component: misc

Issue created by migration from https://trac.sagemath.org/ticket/30363
@tobiasdiez tobiasdiez added this to the sage-9.2 milestone Aug 14, 2020
@slel
Copy link
Member

slel commented Aug 14, 2020

comment:2

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:

@slel
Copy link
Member

slel commented Aug 14, 2020

comment:3

Note another discussion on this theme:

@tobiasdiez
Copy link
Contributor Author

comment:4

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 mkoeppe modified the milestones: sage-9.2, sage-9.3 Sep 5, 2020
@mkoeppe
Copy link
Member

mkoeppe commented Feb 13, 2021

comment:6

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

@mkoeppe mkoeppe modified the milestones: sage-9.3, sage-9.4 Feb 13, 2021
@swenson
Copy link
Contributor

swenson commented Mar 27, 2021

comment:7

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

@slel

This comment has been minimized.

Sign in to view
@embray
Copy link
Contributor

embray commented Mar 29, 2021

comment:9

-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

@embray embray removed this from the sage-9.4 milestone Mar 29, 2021
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe mkoeppe changed the title Migration to GitHub Meta-ticket: Migration to GitHub Apr 16, 2022
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe mkoeppe added this to the sage-9.8 milestone Sep 8, 2022
@dimpase
Copy link
Member

dimpase commented Sep 9, 2022

comment:15

Replying to Erik Bray:

-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

Let's not get bogged down in political discussions here - we're paying about US$4000 to Google for trac hosting, and Google is not an angel, either. Even if we create our own exclusively solar panel and wind power generator operating hosting site for trac, we still will be reliant on various arguably evil parties to be operational.

Besides, GitLab's free tier (and not only) is lacking in functionality compared to GitHub, and https://gitlab.com/sagemath
is semi-broken, in part due to this, in part due to lack of attention.

@dimpase

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe
Copy link
Member

mkoeppe commented Sep 10, 2022

comment:18

@vbraun, would it break any of your workflows if we protect the branches of the main Sage repo? (see https://github.com/sagemath/sage message "Your develop branch isn't protected")

@mkoeppe
Copy link
Member

mkoeppe commented Sep 10, 2022

comment:19

​https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b ready for broader review, what's missing

@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@kwankyu

This comment has been minimized.

Sign in to view
@kwankyu

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe mkoeppe mentioned this issue Jan 7, 2023
Open
@davidlowryduda davidlowryduda mentioned this issue Aug 21, 2020
Closed
This was referenced Jan 4, 2023
Closed
Open
Closed
Closed
Open
Closed
Closed
kryzar pushed a commit to kryzar/sage that referenced this issue Feb 6, 2023
Trac sagemath#34648: Developer's guide: warn the transition to GitHub…
ad68f15 
… and add links to the transition guide

Adding warnings and

- links to the transition guide https://github.com/sagemath/trac-to-
github/blob/master/docs/Migration-Trac-to-Github.md

As of this ticket (for Sage 9.8, assuming it can be released in January
2023), we keep the Trac instructions.

In a follow-up ticket (for Sage 9.9), we will remove the trac
instructions, update the developer manual according to the transition
guide, and add links to github command-line interface, e.g.,
https://cli.github.com/manual/gh_repo_fork

Part of Meta-ticket sagemath#30363: Migration from Trac to !GitHub

URL: https://trac.sagemath.org/34648
Reported by: mkoeppe
Ticket author(s): Matthias Koeppe, Kwankyu Lee
Reviewer(s): Kwankyu Lee, Matthias Koeppe
@mkoeppe mkoeppe modified the milestones: sage-9.8, sage-9.9 Feb 11, 2023
@tobiasdiez
Copy link
Contributor Author

Closing this now as the migration was successful and all (potential) follow-ups have their own issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
sage-10.0
Development

No branches or pull requests
9 participants
@roed314 @swenson @embray @dimpase @kwankyu @jhpalmieri @slel @tobiasdiez @mkoeppe