File Bugs

From GNU MediaGoblin Wiki
(Difference between revisions)
Jump to: navigation, search
m (moved Filing Bugs to File Bugs)
(Link to Feature Ideas)
Line 8: Line 8:
 
* A description that describes the issue (bug, feature request, ...) as well as the context. Consider:
 
* 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 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?
+
** If you’re intending to submit a feature request, please take a look at [[Feature Ideas]] first. After that: Are there related links on the Internet for more information? Would you be willing to help implement or test the feature?
  
 
That’s it!
 
That’s it!

Revision as of 16:46, 26 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 intending to submit a feature request, please take a look at Feature Ideas first. After that: 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.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox