[Community Ubuntu Documentation] Update of "ReportingBugs" by penalvch

Help Ubuntu webmaster at ubuntu.com
Wed Jul 25 16:03:13 UTC 2012


Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification.

The "ReportingBugs" page has been changed by penalvch:
http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=182&rev2=183

Comment:
Added = Bug Reporting Etiquette = as many in the community would benefit by being familiar with these bug tracker colloquialisms.

  
  <<Anchor(Top)>>
  
+ ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents(3)>>||
+ 
+ = Bug Reporting Etiquette =
+ 
+ Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. Here are a few guiding principles that lead to success in getting bugs fixed:
+ 
+  * Please do not stack multiple issues into one report. For example, many jam suspend and hibernate into one report. Please do not do this. Make one report for each against the Linux package via a terminal: {{{ubuntu-bug linux}}}
+  * Please do not complain about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", XYZ person(s) do not care about fixing bugs, etc. Especially, if you have not followed the directions mentioned in this article, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your E-Mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources.
+  * Please keep the bug objective as possible. It is desired for you to provide a fact based, technical impact statement on you, your environment, and the potential or actual impact on the community at large.
+  * Please provide all relevant information from [[https://wiki.ubuntu.com/DebuggingProcedures]] when you first report your bug. This is the number one reason why bugs do not get marked [[https://wiki.ubuntu.com/Bugs/Status|Triaged]], as the minimum requirements for dealing with the problem by a developer are not provided.
+  * If a triager or developer asks you to provide information, please avoid arguing with them. Just provide the information as requested. If you have a strong disagreement with what a triager or developer is asking of you, please resolve it with them via personal message, instead of turning a bug development report into a "let's talk about talking about the problem" report. The Ubuntu community takes a favor to objective, technical discourse.
+  * Many of the triagers and developers who are providing support to you, are volunteers doing so out of altruism. Please keep this in mind when making your comments.
+  * The high majority of [[https://launchpad.net/ubuntu/+source/linux|linux]] package, hardware, non-user space bugs are hardware dependent on both the hardware itself, and what it is connected to. For more on this please see below sections:
+ [[https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported]]
+ 
+ [[https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug]]
+ 
  = How to report bugs =
- 
- ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents(3)>>||
  
  Ubuntu uses Launchpad to keep track of bugs and their fixes. This page will guide you through the steps required to file a good and detailed report.
  
@@ -43, +58 @@

  
  If the problem is not in the package [[https://launchpad.net/ubuntu/+source/linux|linux]], and you have further information about an already reported bug, add this information to the existing report, rather than opening a new one.
  
- /!\ '''For sound, X drivers, and kernel bugs''': please open a '''new''' bug instead of commenting on a similar bug: chances are that your hardware does not match the existing bug's hardware, so the bug will not be addressed. As well, unless asked of you by a developer or experienced triager, please do not mark your bug a duplicate of another reporter's bug.
+ /!\ '''For sound, X drivers, and [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel bugs''': please open a '''new''' bug instead of adding debugging information, attachments, or "Me too!" comments on what may appear to be a similar bug: chances are that your hardware does not match the existing bug's hardware, so your bug and comments will not be addressed. As well, unless asked of you by a developer or triager, please do not mark your bug a duplicate of another reporter's bug.
  
  [[#Top|Back to top]]
  



More information about the Ubuntu-bugsquad mailing list