[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #20821 [Internal Services/Tor Sysadmin Team]: VM to install gitlab
#20821: VM to install gitlab
-------------------------------------------------+---------------------
Reporter: hiro | Owner: tpa
Type: task | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Tor Sysadmin Team | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+---------------------
Comment (by dgoulet):
Seems there are some confusion about this so I'll layout what network team
wants from that Gitlab.
For now, we only want to use Gitlab for code review which implies two
things. Either we link our personal user repository to that instance
(mount bind or what not) or we isolate the instance to have some new
personal repository in there for each users that we'll use to push the
code for review (currently what we do with gitlab.com).
Both works for us, of course it would be much easier to link our current
git/user/... repo in there but if too complicated, let's not go overboard.
Furthermore, IN NO CIRCUMSTANCES that gitlab instance should be able to
write to our tpo git. So it MUST be Read-Only if we pull it off.
Depending on what is chosen here, I guess you can `du -sh` at least the
personal repository of asn, dgoulet, nickm, teor, isis, Yawning to have an
idea of how much we push (for little-t tor).
This instance will NOT be used for anything else for now. Moving our trac
ticketing to a Gitlab instance is a whole new big project itself and not
in scope for this.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20821#comment:6>
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