[mythtv-users] Can anyone tell me why Ticket 6382 has been closed?

[Paul Gardiner]

Nick Rout wrote:
> On Tue, Sep 29, 2009 at 10:46 AM,  <f-myth-users at media.mit.edu> wrote:
>>    > Date: Mon, 28 Sep 2009 09:49:59 -0700
>>    > From: Robert McNamara <robert.mcnamara at gmail.com>
>>
>>    > It just comes down to project philosophy/bureaucracy, and the general
>>    > MO of this project is that trac is a place for bugs, and that the wiki
>>    > feature request page is for feature requests.  Trac would quickly
>>    > become very very painful to navigate if we were tracking feature
>>    > requests there as well-- we already get behind enough with just bug
>>    > tickets, as evidenced by the wait between the opening and closing of
>>    > this ticket.
>>
>> Since this seems to come up with great regularity and obviously
>> confuses many who are new to the way Myth handles Trac:
>>
>> Is there any possibility of adding a flag to a bugreport in Trac that
>> says "feature request" and then allowing each Trac user to set a flag
>> (once) that then -excludes- such reports from day-to-day usage?  (This
>> would presumably also have to include not automatically sending mail
>> or they're not really "excluded" from spamming the inboxes of people
>> who don't want them.  I don't know if that's easy to do in Trac.)
>> Then they wouldn't get lost, and could remain open, but wouldn't get
>> in the way of triaging the database.
>>
>> (The bug there is that if all devs turns off the feature-request view,
>> then everyone but the devs believes that developers might someday look
>> at them, when in fact they will never be seen.  That could already
>> happen on the wiki, but there's less of an implicit statement that
>> things on the wiki will be regularly seen and/or triaged. Nonetheless,
>> doing something like this might stop the steady stream of feature-
>> request/closed/please-explain/let's-discuss/etc that has been going
>> on forever.  And it'd be way more organized than trying to use the
>> wiki to track the same kind of thing.)

What a great idea.

> Or how about a large message in trac to tell people that it is NOT the
> place for feature requests, and directing them to the right place?

The problem with that is it is impossible for the reporter to tell
whether they have a bug or a feature request because what looks
like a bug can turn out to be intended - although undesirable -
behaviour. It's those cases that seem to be the main cause of
angst.