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:21 teor]:
 > Replying to [comment:19 atagar]:
 > > >  How does that sound?
 > >
 > > Great! Think we're completely on the same page. :)
 > >
 > > > Some team (snowflake?) to use gitlab exclusively... So there's a
 precedent in the idea of migrating at *least* some teams to GitLab
 permanently.
 > >
 > > Gotcha. My understanding is that Snowflake uses GitLab whereas the
 Network team and Ooni (?) are moving toward GitHub. Snowflake is tiny by
 comparison, which is why I suspect if we're going to move at all it will
 be toward GitHub rather than GitLab. That said, delighted for folks to
 experiment.
 >
 > Ooni use GitHub as their main development platform, including tickets
 and pull requests.
 >
 > In the network team, we've tried using GitHub and various GitLab
 instances for a few different things. But we tend to want to retain
 control of our git and tickets. So at the moment, we use GitHub as a git
 mirror, for pull request review, and to trigger branch and pull request CI
 on Travis and Appveyor. If GitLab can work with Travis and Appveyor, then
 that would make the transition easier for us. (We also use tor's git and
 Jenkins, for CI, and to build nightly binaries.)
 >
 > 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

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30857#comment:23>
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