Opened 7 months ago

Last modified 7 months ago

#33790 new defect

Does https-everywhere still use tor trac for bugtracker?

Reported by: arma Owned by: legind
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Normal Keywords:
Cc: woswos Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Hi https-everywhere folks!

I see on
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!]

Child Tickets

Change History (1)

comment:1 Changed 7 months ago by legind

Hey arma.

I've removed the Tor trac from the list of ways to file bugs, since Github is the preferred way, and we check that regularly.

It is likely many of the old tickets no longer apply, either because they have been fixed separately or they apply to the old XPCOM extension. Would it be possible to mass-close HTTPS Everywhere tickets older than, say, 18 months, with a notice to the issuer to re-open the ticket if it is still valid?

Then with the remaining tickets we should triage them into github.

Note: See TracTickets for help on using tickets.