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
  • #22181

Closed (moved)
Open
Opened May 06, 2017 by Samdney@Samdney

What can we do for mirror operator community

Parent Ticket #22150 (moved)

arma wrote:

"B) We should figure out how to handle the community of mirror operators better. There's a mailing list, tor-mirrors, where people send mail to sign up their mirrors, and then nobody does anything. I bet we can improve on that process. :)"

  1. What can we do here for our mirror operator community?
  2. This ticket overlaps with the topics:
  3. perl back-end script (automatisation) <-> website redesign/support portal: mirror sites
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#22181