We’ve had to make a change in our testing policy. Going forward, users who produce a plethora of bug reports that are not reproducible or are working as documented will be penalized in terms of how their feature requests are handled. If you would like a behavior change, please file a feature request.
Greg, I understand that investigating bug reports which cannot be reproduced or concern documented behaviour can be frustrating and time-consuming.
However, I find the idea of penalizing users for submitting such reports rather concerning.
A bug that cannot be reproduced is not necessarily a bug that does not exist. Furthermore, users cannot always distinguish between unintended behaviour, unclear documentation, and genuine bugs. That is precisely why reporting unexpected behaviour is important.
Penalizing users by giving their future feature requests lower priority risks discouraging people from reporting legitimate problems.
Wouldn’t it be more constructive to provide clearer guidelines for submitting bug reports and simply reclassify reports as feature requests when appropriate?
Software development benefits from open communication between developers and users. I believe encouraging constructive feedback is far more productive than introducing penalties.
You are right about the issue list. It is quite a mess, and I do understand Greg’s reasons and respect his position.
I don’t believe Greg is wrong in wanting to address the situation, but “penalised” is rather strong wording, in my opinion. Wouldn’t “given lower priority” be a more appropriate expression?
Of course, this is merely a suggestion. Greg is entirely free to decide which wording he prefers.
I also want to emphasise that I have a great deal of respect for what Greg has accomplished on his own. My earlier reply was written out of genuine concern for Buoy and its future, not out of a desire to criticise Greg personally or undermine his work in any way.
Just as I want Objo to succeed, I also want Buoy to succeed.