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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed
Open
Opened Feb 20, 2012 by Damian Johnson@atagar

Move new torstatus (atlas?) to git

I've spoken to hellais and it would be nice if we started moving the new (third) TorStatus to tor's infrastructure. The first step would be to move it into tor's git repo.

This looks like it'll be non-trivial since multiple projects are subdirectories in the 'hellais.github.com' repository so my guess is that keeping history will be a no-go. That said, maybe I'm misunderstanding GitHub or Sebastian knows some gitfu to pluck it out.

https://github.com/hellais/hellais.github.com/tree/master/TorStatus

Also, it's confusing to keep calling each new incarnation 'TorStatus' (this is the third one), so Karsten and I have proposed renaming it to Atlas. We'd then also host it under 'atlas.torproject.org'. Other suggestions are welcome.

Assigning to hellais first for approval and a description for the git repository.

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