[tor-bugs] #30857 [Internal Services/Services Admin Team]: migrate (some projects? everything?) from trac to gitlab
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Sep 12 13:40:38 UTC 2019
#30857: migrate (some projects? everything?) from trac to gitlab
-------------------------------------------------+-------------------------
Reporter: anarcat | Owner: (none)
Type: project | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Services Admin | Version:
Team |
Severity: Normal | Resolution:
Keywords: tickets-migration | Actual Points:
Parent ID: #29400 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by anarcat):
I added comments in the GitLab migration plan. The gist of my
modifications is as follows:
1. added the migration itself as a "challenge"
2. added "milestones" as a possible solution for "ticket relationships"
3. added details and possible solutions for the irc bot problem
4. added another possible solution (OpenPGP signatures on commits and
tags) to the "gitolite" problem
5. expanded on the CI section (we will still use jenkins at first)
6. i'm not sure it's totally accurate to say trac is unmaintained
upstream. the 1.2.x branch had a release about a month ago (aug. 2019) and
they also released a new stable branch (1.4) not long ago... so it's
still maintained
7. also outlined that Trac also uses javascript in the table
8. finally, i think i identified a new issue with git repository
redirections:
== New issue: git repository redirections
Finally, i'm a little confused about the way the group/project namespace
is organized... i see that everything seems to be under "torproject/foo"
*except* "web/foo" and i wonder why it's been done that way. I would
definitely put stuff under `tpa/*` for example, and have one project per
service, with all the service admins stuff under `services/` maybe?
I'm not sure how best to organize this, but having "everything under
torproject/ except not quite" doesn't seem like a great match ;) Couldn't
we replicate the hierarchy from https://gitweb.torproject.org/ ? that
would make git repository redirections much easier...
Note that renaming projects in gitlab is cheap and reliable (it keeps
redirects) so we can also fix this later if we need to, i think, but i'd
like to get it right, at least in terms of redirections. After all, we
don't want to tell people that all their git URLs are broken now
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30857#comment:49>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list