Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • H HTTPS Everywhere EFF
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • HTTPS Everywhere EFF
  • Issues
  • #33790
Closed
Open
Issue created Apr 02, 2020 by Roger Dingledine@armaReporter

Does https-everywhere still use tor trac for bugtracker?

Hi https-everywhere folks!

I see on https://www.eff.org/https-everywhere/development that you still point folks towards github and Tor trac, for filing bugs. Great.

But I also see a bunch of tickets just sitting around in trac in the https-everywhere component, including many very old ones.

I see the github issue tracker has some recent activity, whereas the tor trac component has a few tickets here and there, like legacy/trac#33694 (moved), but not much attention.

So: should you all do a triage of old tickets and clean things up and then either keep using both issue trackers or consolidate into one? Or did you essentially already move to one in practice and not yet update your docs?

I ask because one possible future is that Tor's trac will move to our gitlab instance, and carrying over a bunch of deadweight tickets might not be the optimal move if there is a better one. :)

[Cc'ing Woswos on the ticket because they were the one who noticed this issue and asked about it. Thanks!]

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