Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #33537

Closed (moved)
Open
Opened Mar 05, 2020 by anarcat@anarcat💬

audit SVN accesses

one of things that came out of the SVN retirement discussion is that we don't exactly know how to tell who has access to what. we hope that access controls are correct and tight, but that institutional knowledge somewhat bitrotten over the years, so we can't easily tell.

the task is to figure out exactly which set of users has access to which files.

this is in the context that the SVN service will be eventually retired, but we have hit a roadblock in the corpsvn retirement (#32025 (moved)) where there are concerns about where to move the files to. so while we resolve those concerns, we will keep hosting corpsvn for a little longer and that means cleaning up the accesses.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#33537