File Bugs: Difference between revisions
Jump to navigation
Jump to search
(moving bug filing material to a separate page) |
m (moved Filing Bugs to File Bugs) |
(No difference)
| |
Revision as of 13:18, 4 September 2011
MediaGoblin uses a bug tracker called Redmine.
Our instance is located at http://bugs.foocorp.net/projects/mediagoblin
The most useful bug reports have the following components:
- A short summary that’s 60 characters or less.
- A description that describes the issue (bug, feature request, ...) as well as the context. Consider:
- If you think you’ve found a bug, can you reproduce it in a controlled environment? Is the issue specific to a browser, computer, image, media type, or other dimension? All data helps.
- If you’re submitting a feature request, are there related links on the Internet for more information? Would you be willing to help implement or test the feature?
That’s it!
The better the issue report, the easier it is to address the bug, and the more likely that the developers will be able to resolve the issue. If someone has questions about the bug report, they may reach out to the reporter directly.
If you get a response after a couple of weeks, find someone on IRC.