[tor-project] Follow up Gitlab next steps (Re: update on ticket system discussion)
atagar at torproject.org
Sat Sep 7 22:28:37 UTC 2019
Hi Gaba, would you mind adding a section that discusses 'Gitlab vs
Github'? I realize some folks feel self-hosting is a must, but I value
other equities more (like prevalence within the wider open source
community and migration redirects).
Ooni chose GitHub  and the Network Team has partially migrated in
that direction as well . I'd like to give Gitlab a fair shake, but
I'm not spotting where within the planning doc we persuasively pitch
for Gitlab over its alternatives (and by extension why my subprojects
shouldn't follow Ooni and the Network Team's lead as trac is
On Fri, Sep 6, 2019 at 1:52 PM Gaba <gaba at torproject.org> wrote:
> With Pili we have been working on this document to compare features
> between trac and gitlab as well as proposal for a structure and
> workflows. Please take a look and send
> It seems that the next step will be to get together between everybody
> interested in this transition (or in not doing it) and discuss this plan
> as well as how to move forward.
> We are going to meet on
> September 17th, at 18UTC in #tor-meeting
> Please, send me, pili or to the mailing list any comment if you can not
> make it to the meeting.
> El 7/29/19 a las 8:07 AM, Gaba escribió:
> > Hi!
> > There has been some discussion in the 'corridors' of Tor and in the last
> > meeting face to face during the session on 'internal tooling' and
> > specifically about tickets system. I'm sending this mail to try to
> > summarize what the discussion has been until now, make it transparent
> > and try to get an agreement on how to move forward.
> > Problem:
> > - Trac software is not being mantained (from our perspective of users of
> > Trac this is a bomb getting ready to explode) 
> > Solution
> > - Move out into a better (possible feature parity with what we use now
> > AND integration between project management tool and tickets) and
> > mantained ticketing system.
> > Discussion until now
> > - A few years ago there was a survey  on which features people would
> > like to see in a new ticketing system.
> > - There is a ticket  that has a discussion on features needed and a
> > document  that brainstorm features between trac and gitlab.
> > - The last meeting in Stockholm there has been several discussions on
> > what is needed. 
> > - In 2017 Hiro and the network team experimented with the oniongit.eu
> > Gitlab instance.
> > - In 2019, a test instance was setup, called "dip.torproject.org",
> > that a few projects are using right now to test its use.
> > We are mostly considering Gitlab (until now) because:
> > 1. We can host it ourselves and not have other company control the data.
> > 2. It is open source .
> > 3. It is mantained .
> > 4. It supports the project management tool that we are interested in.
> > Before moving forward we need:
> > 1. Consensus or a clear compromise on what to move into.
> > 2. A plan on how the migration to a new ticketing system will happen. I
> > started drafting it here (thinking that Gitlab would be the new one)
> > . This plan is still a work in progress and we will continue doing it
> > when we all agree on which system to move into.
> > cheers,
> > gaba
> >  https://trac.edgewall.org/roadmap
> > 
> > https://docs.google.com/spreadsheets/d/1V4Faq2y9vv8XTp-OADl4YRMTiRB0G9DHvj23NRpwzcc/edit#gid=0
> >  https://trac.torproject.org/projects/tor/ticket/30857
> >  https://nc.riseup.net/s/TYX37BDT4eQfTiW
> > 
> > https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/Notes/InternalTooling
> >  https://dip.torproject.org
> >  https://gitlab.com/gitlab-org
> >  https://gitlab.com/groups/gitlab-org/-/roadmap?layout=MONTHS
> >  https://nc.riseup.net/s/SnQy3yMJewRBwA7
> Project Manager: Network, Anti-Censorship and Metrics teams
> gaba at torproject.org
> she/her are my pronouns
> GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19
> tor-project mailing list
> tor-project at lists.torproject.org
More information about the tor-project