Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #1986
Closed
Open
Created Oct 01, 2010 by Roger Dingledine@arma

migrate vidalia's trac into tor's trac

Vidalia's bugs are getting lonely because people don't look at them much.

If they were in tor's trac, I would help prioritize them and nag people to fix the important usability issues.

Bug we don't just want to import all the vidalia trac entries into our trac, because the numbers won't line up.

Maybe the best answer is to let the old trac die, and put it up somewhere in a read-only way, and add a new Vidalia component to our trac and cherry-pick the bugs we want to keep active?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking