Im torn- End users must have a way to report bugs, and I feel that the forums is an ineffective place for that. But on the flip side Ive seen enough bugzilla installs full of untouched bugs, duplicates, and non-issue reports to make me somewhat wary of giving “easy” access to all.
I like the idea of having some process to be given a “bug reporter” status. It dosnt have to be a high bar, but something. Maybe something as simple as you need to have an account on the forums and 50 points before you can request an account (and you must request it, its not automatic). It stops the drive-by bug reporting, but makes it easy for people to report things.
As we open up the bug reporting (and feature requests, etc) I think we need more options of what to do with them. I only see “resolve” and “close” options. To be able to handle some of the junk that comes from opening it up, I would like to see some other options for an issue status such as:
wont-fix: Its a known issue/bug, but for some reason we cant/wont fix it. Might apply better to feature requests (we wont implement XEP-9999, etc) but sometimes a bug is so weird, and there just isnt the manpower to fix it. The oddball OCSP problem I ran into would be an example. If I personally was not willing to fix it, it never would have happened.
not-a-bug: Someone reports a bug, and it isnt. Im not a fan of deleting things unless there is strong cause for it. Spam can be deleted (but with a vetting process we hopfully wont have too much), but sometimes keeping these other not-a-bug reports around can be useful (25 people report the same not-a-bug; maybe we should look at it closer)
need-a-developer: A bug/feature that is highly desired, but there simply isnt the manpower to fix it, and no one is assigned the task. Think like the virtual hosting request- we all want it. No one has the time. By giving it this status, people will understand why no progress is being made. I dont like just assigning bugs/features to a person if there is no intention of working on it. Maybe this is a placeholder account instead of a status, or maybe its a status with “UNASSIGNED” as the developer.
Is anyone in the group familiar enough with Jira to help “take over” some of these changes? Im not terribly familiar with Jira, but in the absence of anyone else, I would be willing to step up to the plate.