Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:45:32Zhttps://gitlab.torproject.org/legacy/trac/-/issues/4553Let's have a new ticket status: needs_revision?2020-06-13T16:45:32ZNick MathewsonLet's have a new ticket status: needs_revision?Right now, needs_review means one of two things: either a ticket that actually needs code review of some kind, or a ticket that has _received_ code review and is waiting for somebody to revise the code.
This makes it harder for me to fi...Right now, needs_review means one of two things: either a ticket that actually needs code review of some kind, or a ticket that has _received_ code review and is waiting for somebody to revise the code.
This makes it harder for me to figure out which tickets I actually need to review, which ones I need to bug somebody to finish up, and so on. It also sometimes makes people think that their code is waiting on me for review, when it is actually waiting on them to fix up.
(Why not just re-assign the ticket back to them, and remove it from needs_review? Because I find that it's really important to keep tickets with fixable code separate, so I can remember to bug the people to finish up the code, and so I can jump in and do the final cleanups if the aren't to big and the person who did the first version can't finish the patch.)
This should probably get a little discussion before anybody goes and implements it; I don't know whether anybody but me thinks it's a great idea. But I do think that it's a great idea!Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4632Trac does not allow a ticket in ‘needs_information’ to be set directly to ‘ne...2020-06-13T16:45:33ZRobert RansomTrac does not allow a ticket in ‘needs_information’ to be set directly to ‘needs_review’Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4871I can edit ticket descriptions2020-06-13T16:45:33ZRobert RansomI can edit ticket descriptionsI now have the ability to edit ticket descriptions. Is there a reason for this change?I now have the ability to edit ticket descriptions. Is there a reason for this change?Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4876Stem trac component2020-06-13T16:45:34ZDamian JohnsonStem trac componentHi, I'd appreciate a "Stem" trac component for bug reports.
Thanks! -DamianHi, I'd appreciate a "Stem" trac component for bug reports.
Thanks! -DamianErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4945Trac won't allow ticket to change from "needs_information" to "needs_review"2020-06-13T16:45:35ZTracTrac won't allow ticket to change from "needs_information" to "needs_review"Trac does not appear to give the option for a ticket to change to needs_review status once it has been set to needs_information status. This behavior can be seen in bug ticket [https://trac.torproject.org/projects/tor/ticket/3842]
**Tra...Trac does not appear to give the option for a ticket to change to needs_review status once it has been set to needs_information status. This behavior can be seen in bug ticket [https://trac.torproject.org/projects/tor/ticket/3842]
**Trac**:
**Username**: blackpawErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5030Stop auto-assigning Trac tickets based on the component2020-06-13T16:45:36ZKarsten LoesingStop auto-assigning Trac tickets based on the componentTrac assigns new tickets to the component owner if no ticket owner is specified. But in my understanding the ticket owner is the person who's supposed to work on a ticket. This requires a commitment from the person. Auto-assigning a t...Trac assigns new tickets to the component owner if no ticket owner is specified. But in my understanding the ticket owner is the person who's supposed to work on a ticket. This requires a commitment from the person. Auto-assigning a ticket is the wrong concept here.
Should we remove component owners to stop auto-assigning tickets based on the component?
The question is: how we can ensure that the right persons learn about new tickets. Can we assume that current "component owners" know how to filter their tor-bugs email?
(Cc'ing all component owners.)Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5240spoiler plugin2020-06-13T16:45:36Zproperspoiler pluginCan you please install the spoiler plugin?
A spoiler enhances the wiki. You can hide text with a spoiler which will be revealed after pressing a button.
There is a [video demonstration](https://www.youtube.com/watch?v=TyuelS_e0Js) avai...Can you please install the spoiler plugin?
A spoiler enhances the wiki. You can hide text with a spoiler which will be revealed after pressing a button.
There is a [video demonstration](https://www.youtube.com/watch?v=TyuelS_e0Js) available (html5, only 9 seconds). It does not need javascript. [Here](http://trac-hacks.org/wiki/SpoilerMacro) are instructions how to install it and the source code. If there are technical questions, the author of the plugin is very friendly and [answers fast](https://groups.google.com/group/trac-users/browse_thread/thread/f55ceee3a26abaa9).
This plugin would be very useful for [my project](https://trac.torproject.org/projects/tor/wiki/doc/TorBOX).Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5395Change owner of HTTPS Everywhere Chrome to pde2020-06-13T16:45:37ZaaronswChange owner of HTTPS Everywhere Chrome to pdeI don't maintain this anymore, it's been picked up officially.I don't maintain this anymore, it's been picked up officially.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5513Trac wiki disclaimer2020-06-13T16:45:37ZDamian JohnsonTrac wiki disclaimerTrac's domain and tor logo lends it an air of being official but, as we all know, the vast majority of its content is either provided from people outside the core community and/or vastly out of date.
We could use a disclaimer on trac's ...Trac's domain and tor logo lends it an air of being official but, as we all know, the vast majority of its content is either provided from people outside the core community and/or vastly out of date.
We could use a disclaimer on trac's wiki pages, something to the effect of "This is a community supported wiki. Content may not be accurate nor reviewed by Tor's developers."
I have somewhat mixed feelings about where to put this. It would be eye jarring in the header, but barely noticeable in the footer. Thoughts?Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5777Create ‘component’ for Excito B3 Tor configurator bugs or close tickets2020-06-13T16:45:38ZRobert RansomCreate ‘component’ for Excito B3 Tor configurator bugs or close ticketsSomeone created #5770, #5771, #5772, and #5774 for bugs in the Excito B3 Tor configuration interface, and #5775 for a bug in the Excito B3 configuration interface in general. If these bugs belong in Tor's bug tracker, someone should cre...Someone created #5770, #5771, #5772, and #5774 for bugs in the Excito B3 Tor configuration interface, and #5775 for a bug in the Excito B3 configuration interface in general. If these bugs belong in Tor's bug tracker, someone should create a Trac ‘component’ for them; if they don't belong here, someone should close the tickets and send the reports upstream.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5800Please deprecate the "HTTPS Everywhere: Chrome" component2020-06-13T16:45:38ZPeter EckersleyPlease deprecate the "HTTPS Everywhere: Chrome" componentIt seems to be saner for us just to use the EFF-HTTPS Everywhere component for now.It seems to be saner for us just to use the EFF-HTTPS Everywhere component for now.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/5924Ticket creators don't get mail about ticket updates2020-06-13T16:45:39ZRoger DingledineTicket creators don't get mail about ticket updatesIf you make a ticket, and then somebody else comments on it, you don't get email about the comment.
Once you have commented on your ticket, you start getting emails about updates.
Workaround is to set yourself as cc to all the tickets ...If you make a ticket, and then somebody else comments on it, you don't get email about the comment.
Once you have commented on your ticket, you start getting emails about updates.
Workaround is to set yourself as cc to all the tickets you make. That works for me (now that I've realized it), but most new ticket creators won't realize it.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/6332add blockfinder component2020-06-13T16:45:46ZJacob Appelbaumadd blockfinder componentWe need a blockfinder componentWe need a blockfinder componentAndrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/6365Use keywords like SponsorG20120930 for sponsor deliverables instead of milest...2020-06-13T16:45:47ZKarsten LoesingUse keywords like SponsorG20120930 for sponsor deliverables instead of milestonesWe're currently using Trac's milestone field for two things: version milestone and sponsor milestone. It would be good to assign a ticket to both a version like Tor 0.2.4.x-final and to a sponsor milestone like Sponsor G, September 30, ...We're currently using Trac's milestone field for two things: version milestone and sponsor milestone. It would be good to assign a ticket to both a version like Tor 0.2.4.x-final and to a sponsor milestone like Sponsor G, September 30, 2012. Mike and Nick suggested to use Trac keywords for this purpose.
Two questions:
- Is SponsorG20120930 a good format for such keywords?
- Is there an easy way to modify existing tickets in bulk? I don't mind so much doing it manually, but it's going to generate a lot of emails.Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/6403Make a Stegotorus trac component?2020-06-13T16:45:52ZRoger DingledineMake a Stegotorus trac component?Zack (and others),
Is now a good time to make a Stegotorus component in Tor's trac? Or do you still prefer keeping your tickets elsewhere?Zack (and others),
Is now a good time to make a Stegotorus component in Tor's trac? Or do you still prefer keeping your tickets elsewhere?Roger DingledineRoger Dingledinehttps://gitlab.torproject.org/legacy/trac/-/issues/6405Merge torclient/torrelay/torbridge/etc into one Tor component2020-06-13T16:45:53ZRoger DingledineMerge torclient/torrelay/torbridge/etc into one Tor componentNick has been asking for a long time now for us to make a single Tor component, and use keywords to mark them as TorClient, TorBridge, etc. Using different components to describe what sort of Tor category a ticket is for drives him nuts....Nick has been asking for a long time now for us to make a single Tor component, and use keywords to mark them as TorClient, TorBridge, etc. Using different components to describe what sort of Tor category a ticket is for drives him nuts.
Roger and Robert were pushing back because trac's search feature is abysmal, and our way of finding a ticket was to guess its Tor component and then look at the list of tickets under that component. But we should be able to do the same thing just narrowing by keyword.
Ultimately, since Nick is the primary user of this component, I think it makes the most sense to let him pick the conventions.Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/6477"Newest 50 tickets" shows 500 hits2020-06-13T16:45:54Zbastik"Newest 50 tickets" shows 500 hitsI like this category and found it always strange that "50 tickets" finds 500 tickets.
I suggest renaming it to "500 tickets". It just looks better when it matches each other. Please see the attached pictures.I like this category and found it always strange that "50 tickets" finds 500 tickets.
I suggest renaming it to "500 tickets". It just looks better when it matches each other. Please see the attached pictures.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/6497Allow track users to mange their self-originated ticket content2020-06-13T16:45:55ZgrarpampAllow track users to mange their self-originated ticket contentTrac users should be able to edit/delete their own ticket content that they added.
Such as the Subject, 'Description' and 'Comment's they created in any given ticket.
It can yield more concise tickets by reducing spoken corrections.
And ...Trac users should be able to edit/delete their own ticket content that they added.
Such as the Subject, 'Description' and 'Comment's they created in any given ticket.
It can yield more concise tickets by reducing spoken corrections.
And quicker/safer handling of errantly included data.Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/6574Cant create new page in wiki2020-06-13T16:45:57ZTracCant create new page in wikiI would like to create a page with information on how to prevent bittorrent through Tor, but I have no way of creating a new page.
Its the result of research after an altercation with Paramount Pictures :)
**Trac**:
**Username**: ker...I would like to create a page with information on how to prevent bittorrent through Tor, but I have no way of creating a new page.
Its the result of research after an altercation with Paramount Pictures :)
**Trac**:
**Username**: kerruptErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/6723Vidalia's milestones in Trac are outdated2020-06-13T16:46:02ZKarsten LoesingVidalia's milestones in Trac are outdatedThere's an open milestone "Vidalia: 0.2.15" in Trac, even though I'm using 0.2.20. Should I close that milestone and create a new milestone "Vidalia: 0.2.x"?There's an open milestone "Vidalia: 0.2.15" in Trac, even though I'm using 0.2.20. Should I close that milestone and create a new milestone "Vidalia: 0.2.x"?Karsten LoesingKarsten Loesing