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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#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:                                       |  Actual Points:
Parent ID:  #29400                               |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by gaba):

 Replying to [comment:24 teor]:
 > Replying to [comment:23 gaba]:
 > > Replying to [comment:21 teor]:
 > > >
 > > > But I have no idea what GitLab will do for us. So it's very hard for
 me to have an informed opinion on any transition.
 > > >
 > > > Can we please create a list of:
 > > > * the things GitLab MUST give us
 > > >   * these are our acceptance criteria: if the migration doesn't do
 the thing, we should roll it back and try again
 > > > * the things GitLab SHOULD NOT give us:
 > > >   * these are our known sacrifices: if the migration loses the
 thing, we agree to accept it anyway
 > > >
 > > > Anything not listed might be included, if it's easy to do. But we
 can't rely on it.
 > > >
 > > > Who can create a list like this, and when can we have it ready?
 > > > (Or is there an existing list?)
 > >
 > >
 > > ok. It started here: https://nc.riseup.net/s/TYX37BDT4eQfTiW
 >
 > It looks like you've written a wish list: a list of features that we
 want GitLab to have.
 > That's a good start.

 Actually I was mostly thinking about the things that we *already* have in
 gitlab that are things we use in trac or we can use when we migrate.

 >
 > But I was asking for acceptance criteria for the data migration:
 > * a list of features that GitLab must have
 > * a list of data that we must migrate from Trac to GitLab

 >
 > And known sacrifices:
 > * a list of features that we use in Trac, that GitLab doesn't have
 > * a list of data that we won't migrate to GitLab
 >
 > Maybe we should set up a table for each feature, so we can track our
 progress:
 > * how important is this feature?
 > * who needs this feature?
 > * are they happy with the gitlab version of this feature?
 > * does trac have it?
 > * does gitlab have it?
 > * can we migrate the data for this feature?
 > * does the data migration actually work?
 >

 Sounds good.

 > We should also look at the survey we did in 2018? so we can make sure we
 are not missing anything.

 I saw the survey data before at the end of 2018 but when I went to look
 for it recently I couldn't find it. Maybe it was in a riseup pad...

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

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs