[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #33790 [HTTPS Everywhere/EFF-HTTPS Everywhere]: Does https-everywhere still use tor trac for bugtracker?
#33790: Does https-everywhere still use tor trac for bugtracker?
-------------------------------------------------+-------------------------
Reporter: arma | Owner: legind
Type: defect | Status: new
Priority: Medium | Milestone:
Component: HTTPS Everywhere/EFF-HTTPS | Version:
Everywhere |
Severity: Normal | Keywords:
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
-------------------------------------------------+-------------------------
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 #33694, 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!]
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33790>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs