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.

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

Migrate from Trac to GitLab #5

Open
May-Lee opened this issue Jun 4, 2021 · 3 comments
Open

Migrate from Trac to GitLab #5

May-Lee opened this issue Jun 4, 2021 · 3 comments

Comments

@May-Lee
Copy link
Collaborator

May-Lee commented Jun 4, 2021

Actions to resolve this issue:

Set a deadline for finding a contractor.

Set this deadline knowing that we would have to schedule about a month to do this on our own, if no contractor has been found.

Choose the month this work would take place.

@May-Lee
Copy link
Collaborator Author

May-Lee commented Jun 7, 2021

Some project notes:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Migration in Four Phases (budget is 1k - 2k phase)

  1. Migrate Tickets, Ticket History (including attachemnts, patches, comments - okay if it has to be just one long thing) from Trac to GitLab
  2. Migrate CI Config from GitHub to GitLab
  3. Migrate GitHub PRs to GitLab - GitLab has a button to import GH PRs; making a GitLab export version
    NOTE: Migration must be ended before we add an issue tracker
  4. Add issue tracker on GitLab
    OTHER:We likely won't move the Wiki, but if so, it would be contents and edit history
    Don't worry about milestones
    Person should overwhelmingly use IRC
    Work should be done in a public repo and published

Posted on 14.03.2021https://tahoe-lafs.discourse.group/t/migrate-trac-to-gitlab-phase-1/12
Ultimate goal is a self-hosted GitLab instance, but that would require some kindof support (managed offering is 800/mo including licenses and server support)
Need to get issue tracker
Consensus reached in March was Sajith was going to look more into it, with zFECas a test case
Jean-Paul has suggested using the GitLab export format from the Trac DB(presumably an artifact) vs. the GitLab API
We need to come up with a budget for that
At this stage, this type of thing should be offered to the Discourse, mailing list, and linked to the IRC
Should parts of the Trac be archived? As they might actually no longer be
relevant (e.g., general speculative features older than 5 years)
GitLab to GitLab is about 30 hours
Dealing with:In-progress PRs Links between tickets should still work
Links between pages should still work
Authorship is important
Custom metadata to tickets

@exarkun
Copy link
Member

exarkun commented Jun 9, 2021

Ultimate goal is a self-hosted GitLab instance, but that would require some kindof support (managed offering is 800/mo including licenses and server support)

Of course someone has to run it but it doesn't seem clear that we have to out-source the management.

@May-Lee
Copy link
Collaborator Author

May-Lee commented Jul 26, 2021

We have servers with Hetzner and they now have some apps, including GitLab:

https://github.com/hetznercloud/apps/tree/main/apps/hetzner/gitlab

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants