Opened 13 years ago

Closed 12 years ago

#85 closed task (fixed)

Methodology for handling bugs

Reported by: Elrond Owned by:
Priority: minor Milestone:
Component: infrastructure Keywords:
Cc: Parent Tickets:

Description (last modified by Christopher Allan Webber) 

Background¶
===========

There are currently a few bugs, that sit at "New", don't have a
single comment and are just there. For now this is fine. People
know from irc, that their bug will be handled sometime.

When the project grows, this sort of bug handling isn't good. It
leaves a feeling of "they don't listen, they don't care" to the
users.

Brainstorming ideas¶
====================

Maybe some new bug status thingies could be helpful?


-  "Accepted - Your bug is valid"
-  "Okay, this is true, we should consider that"
-  "Yes, we'll fix that, but just not now"

Another brainstormy thing: Maybe allow users/developers to care
more for bugs. This works nicely in Debian, where everybody can
nearly change any bug.

Warning notice¶
===============

On the other hand, things should not be overorganized.

Other ideas¶
============


-  Have a feed of "New" bugs

Change History (2)

comment:1 by Will Kahn-Greene, 12 years ago

The original url for this bug was ​http://bugs.foocorp.net/issues/371 .
Relations:
#106: related

comment:2 by Christopher Allan Webber, 12 years ago

Description: modified (diff)
Resolution: → fixed
Status: accepted → closed

I feel like this can be closed. Things are not perfect, but we are iterating as we go.

Note: See TracTickets for help on using tickets.