On Mon, 2011-09-12 at 15:57 +0200, Karsten Loesing wrote:
> On 9/6/11 11:01 PM, katmagic wrote:
> > Sorry for the late reply — I haven't checked my email in a while — but
> > I'm replying anyway because I've some strong feelings on this issue. In
> > short, Trac sucks. My issues with it are as foll
On 9/12/11 3:51 PM, Roger Dingledine wrote:
> On Tue, Sep 06, 2011 at 10:44:11AM +0200, Karsten Loesing wrote:
>> The Component field (10, 1, 1) is used to find/filter tickets and guess
>> who's paying attention to a ticket. 1 person said that the many Tor
>> components make it hard to refer to th
On 9/6/11 11:01 PM, katmagic wrote:
> Sorry for the late reply — I haven't checked my email in a while — but
> I'm replying anyway because I've some strong feelings on this issue. In
> short, Trac sucks. My issues with it are as follows:
>
> 1. The design sucks.
You're right, it needs more green!
On Tue, Sep 06, 2011 at 10:44:11AM +0200, Karsten Loesing wrote:
> The Component field (10, 1, 1) is used to find/filter tickets and guess
> who's paying attention to a ticket. 1 person said that the many Tor
> components make it hard to refer to the software "tor" and that it's
> easier to look a
On 9/6/11 2:19 PM, Robert Ransom wrote:
> On 2011-09-06, Karsten Loesing wrote:
>
>>> 1.1 Which of the reports (stored ticket queries) do you use most often?
>>
>> From all the replies, there's 1 person using 5 reports, 2 persons using
>> 3 reports, 1 person using 2 reports, 4 persons using 1 rep
On 9/6/11 12:06 PM, Christian Fromme wrote:
>> [Suggestion: Backup and delete all reports with a component name in
>> them. The current list of Available Reports list is mostly useless for
>> newcomers who don't care much about components, but who are interested
>> in finding something to work on.
