[tor-bugs] #30857 [Internal Services/Services Admin Team]: migrate (some projects? everything?) from trac to gitlab

[Tor Bug Tracker & Wiki]

#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):

 >  We need to find a way to get this requirement (ticket number unique
 across tor project group but in its own project) with tickets in its own
 project. Check the plan document to see the structure we are proposing (it
 is at the end of the document)

 The process I'm suggesting (import everything in a single project and move
 in a separate projects in a subsequent operation) fulfills this
 requirement.

 >  Ahf is working on that already. I think the idea is to have gaps in
 ticket numbers in projects to be able to fullfill this requirement.

 I don't think it does. It will work for a single project (say the tor
 little t project), but it can't work for all.

 Just to be clear, I'm fine with having tickets split up in different
 projects. I just don't think it's possible to have redirections working if
 we split them up '''at import time'''.

 Say you have:

  * ticket #1 in Component: Core Tor/Tor
 (https://trac.torproject.org/projects/tor/ticket/1)
  * ticket #2 in Component: Internal Service/Services Admin Team
 (https://trac.torproject.org/projects/tor/ticket/2)

 Under the process you propose, those would map into:

  * https://dip.torproject.org/tor/tor/issues/1
  * https://dip.torproject.org/tor/sysadmin/issues/2

 (project names may vary, this is just an example)

 How do I map https://trac.torproject.org/projects/tor/ticket/2 to
 https://dip.torproject.org/tor/sysadmin/issues/2? More generally, how
 would I know which ''GitLab project'' an arbitrary
 https://trac.torproject.org/projects/tor/ticket/N would map into?

 The answer is: there's no way to know, short of making an explicit, 40
 '''thousand''' long list of redirections. I think that's deeply
 impractical, and counter to the spirit of the requirement.

 Instead, what I am proposing is this: tickets #1 and #2 would map into:

  * ​https://dip.torproject.org/tor/legacy/issues/1
  * ​https://dip.torproject.org/tor/legacy/issues/2

 Issue #1 in GitLab would have a label "component: Core tor/tor" and #2
 would have a label "component: Internal servives/Services Admin team".
 Then a '''post-processing''' script, which can easily be made by only
 talking with the GitLab API, '''moves''' those tickets to the right
 project, their final destination stated above:

  * https://dip.torproject.org/tor/tor/issues/1
  * https://dip.torproject.org/tor/sysadmin/issues/2

 ... but because ticket moves in GitLab leave a trace, we can *still*
 redirect from:

  * https://trac.torproject.org/projects/tor/ticket/1 to
 https://dip.torproject.org/tor/legacy/issues/1 which redirects to
 https://dip.torproject.org/tor/tor/issues/1
  * https://trac.torproject.org/projects/tor/ticket/2 to
 https://dip.torproject.org/tor/legacy/issues/2 which redirects to
 https://dip.torproject.org/tor/sysadmin/issues/2

 And we can therefore have a '''generic''' redirector that looks like:

 https://trac.torproject.org/projects/tor/ticket/N ->
 https://dip.torproject.org/tor/legacy/issues/N

 It's fundamentally the same idea, it just differs as to where we
 '''first''' import the tickets.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30857#comment:46>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online