You found some behavior you think isn’t right in a piece of software and you are thinking about reporting a bug.. Wait, stop, read this first as it will save you time in back/forth with the developer.
Is this actually a bug or desired behaviour?
Ask on the mailing list for the software first. Most developers do things for a reason.
Does a bug already exist for this?
Look through the bug tracker / issues for this software, it’s possible a bug already exists. If so you can throw a +1 at it, +1 is a universal “bump” to show your interest. You can also track issues on tools like Github.
Are you reporting the bug in the right place?
Etherpad, as an example doesn’t take plug-in bug reports on the core bug tracker. Plug-in bugs should be reported on the individual plug-in bug trackers.
Want it fixing quickly?
Create a bounty. You will be more likely to get a fix in a timely fashion. This is especially true for feature/enhancement requests.
Bug reports like “I can’t click on anything” are completely useless. Include information such as:
- Operating system
- Your browser
- Your browser version
- The page you are on
Provide Steps to replicate.
Provide how you got the problem to happen.. IE
- click on page X
- click on element Y
- do Z.
Don’t be a leech.
When you file a bug developers will look at your repository and if this is your first ever bug report and you don’t contribute anything back to any other projects it’s likely you will be ignored.
Provide Expected behavior
It’s useful for the developer to know what you actually expect to happen IE:
Expected behavior: Z element gets big.
Actual behavior: Z dissapears.
Actually, I don’t care about this. I’d rather you were clear.
Other things to consider..
Is this a security issue? If so use the software packages responsible security disclosure. Can’t find it? Post to the mailing list or bump them on IRC.