Open May-Lee opened 3 years ago
Some project notes: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Migration in Four Phases (budget is 1k - 2k phase)
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
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.
We have servers with Hetzner and they now have some apps, including GitLab:
https://github.com/hetznercloud/apps/tree/main/apps/hetzner/gitlab
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.