Add a status like "Postponed" for bugs/RFEs which are not rejected but won't be eagerly fixed either
Over the time that I'm involved with this project, I have seen and submitted a number of bug reports and RFEs that were rejected because "the breadth and scope of this problem is too much all over the place to tackle it with out limited engineering resources" and the reporter (such as myself) did not fix the issues in a timely manner. Well, some people are better at proposing ideas and finding stuff to fix, while others are better at actually fixing that stuff :)
Currently such bugs are marked as "closed", although there is no strong reason to REJECT them per se (i.e. as insane, incompatible, etc.)
I propose to set some different mark, like "Indefinitely postponed", to mark these bugs as something worth doing for people who would like to help out with their programming skills and find those bugs/RFEs interesting and worth their time, and/or allowing them to learn something new - if only the contribution procedure, by fixing and RTIing some trivial bite-sized bug.
Updated by Joshua M. Clulow over 7 years ago
A status of Closed is, I believe, different to a status of Rejected. I do both see your point, though, and worry about what an "indefinite" status would mean for the state of our bug tracker.
If something is actually broken, then it should definitely have a bug and it should remain open until it's fixed. If something is essentially a request or a basic plan for some new feature, though, without anybody having committed to work on it then allowing these to exist in the tracker with some indefinite status will presumably mean they'll (mostly) just pile up forever.
If people are just spit-balling about things they'd like to see one day, perhaps it would be better to do it with some combination of the mailing lists and the wiki until somebody actually starts designing and coding?
Updated by Jim Klimov over 7 years ago
If something is essentially a request or a basic plan for some new feature, though, without anybody having committed to work on it then allowing these to exist in the tracker with some indefinite status will presumably mean they'll (mostly) just pile up forever. If people are just spit-balling about things they'd like to see one day, perhaps it would be better to do it with some combination of the mailing lists and the wiki until somebody actually starts designing and coding?
I understand and share your concerns, still - there is always room for improvement in the OS, and sometimes things are not easy to keep track of in one's memory. Even upon discussion in the mailing lists - minor matters are not worth the time of the gurus to respond, let alone fix, and they would sink in the archives forever without visibility. With a bugtracker one could see that some idea has already been proposed - and hopefully some details like a summary of the mailing list discussion, which could kick-start the interested individual's work on the solution. Alternately, some people might just want to help out by squashing a few minor bugs that nobody came around to because they were small, but fixing them would make the world a bit cleaner and brighter ;)
I am not sure it is a good strategy overall to keep the bugtracker small (like under 10000 entries) or with seemingly nothing easy to do (10 open quests, and all require months of work and a lifetime of knowledge). On the contrary, I believe there's always something to do, and if one can't think of a task himself - just click a random "Postponed" issue :)
Updated by Jim Klimov over 7 years ago
UPD: At the very least, if people use the bugtracker properly (search, then post), the issues will not so much "pile up" in duplicates, but rather "grow" in details of one bug regarding that issue. That's what I meant implicitly about storing details of discussion of some unimplemented ideas.
Updated by Milan Jurik over 7 years ago
I agree with Jim. We have:
"New" - request arrived
"In Progress" - somebody is looking at it actively, or did it.
"Feedback" - incomplete situation, requesting some data
"Rejected" - obviously not accepted
"Closed" - done, resolved etc.
We need something like "postponed" or "defer". E.g. if some analysis was done on it, but no implementation and no real target set, it is not "new".
I see no point in blocking people in use of one place to track all ideas. It is much better than split it to bugtracking and some "idea wiki".