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

[Help Ubuntu]

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=252&rev2=253

Comment:
1) Due to LP# 131094 created new etiquette note about e-mail responses. 2) Misc. wording and bold fixes for emphasis and clarity.

  
  = 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:
+ 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. While this is targeted to the new bug reporter, experienced reporters would find these tips invaluable in getting their bugs looked at by a developer and ultimately fixed:
  <<BR>><<BR>>
- Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). Also, please don't make the invalid argument that because it works in Windows, but doesn't in linux, this isn't caused by an outdated BIOS. This is due to how buggy BIOS problems may manifest themselves in linux, but not in Windows. As well, because BIOS vendors typically test to Windows only and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In addition, BIOS updates are for collatoral damage avoidance. In summation, if your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report.
+ Before filing any hardware related reports on Launchpad, please '''update your BIOS''', and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). Also, please don't make the invalid argument that because it works in Windows, but doesn't in linux, this isn't caused by an outdated BIOS. This is due to how buggy BIOS problems may manifest themselves in linux, but not in Windows. As well, because BIOS vendors typically test to Windows only and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In addition, BIOS updates are for collatoral damage avoidance. In summation, if your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report.
  <<BR>><<BR>>
  Please do not claim because you or someone else filed a bug report upstream or downstream (which is publicly viewable, and has no restrictions on who can file) you are somehow exempt from providing the information a developer or triager requested. You are being asked for this information so that it would provide more information on how to fix the problem.
  <<BR>><<BR>>
- Please do not speculate on what you think is or isn't a duplicate report (ex. I googled around and found bug report...). This is largely unhelpful as it tends not to be a duplicate, and already has been or easily done by triagers and developers. Instead, ensuring the report has all the requested testing information performed would be the fastest way to ensure your bug is resolved as soon as possible.
+ '''Please do not speculate on what you think is or isn't a duplicate report''' (ex. I googled around and found bug report...). This is largely unhelpful as it tends not to be a duplicate, and already has been or easily done by triagers and developers. Instead, ensuring the report has all the requested testing information performed would be the fastest way to ensure your bug is resolved as soon as possible.
  <<BR>><<BR>>
- Please '''do not quote''' Wikipedia and other non-primary resource information as fact on [[Launchpad]].
+ Please '''do not quote Wikipedia''' and other non-primary resource information as fact on [[Launchpad]].
  <<BR>><<BR>>
  Many [[https://launchpad.net/ubuntu/+source/linux|Linux]] package, hardware, and other non-user space bugs are hardware dependent on both the hardware itself, and what other hardware the problematic hardware is connected to. The rule of thumb is '''''one report, per person, per hardware combination, per bug'''''. For more on this please see [[https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue|here]], and further below in this article. As well, please do not post comments to another person's report, claiming you have the same problem, because you have the same hardware, or same computer model. Instead, please file a separate report, and make comments there. This is because no one can verify if you would have the same problem or not, because your hardware can not be analyzed.
+ <<BR>><<BR>>
+ '''Please do not complain because someone sent what one perceives to be a automated or "canned" response'''. If the response is asking you to do something that you have't done (ex. test the latest development release, file a new report, etc.) do it, as it would get you closer to having your bug fixed. Complaining about this is inconsiderate of the Ubuntu triagers and developers who are saving time in comparison to hand typing every single character in an e-mail that goes out their inbox.
  <<BR>><<BR>>
  For bugs in the [[https://launchpad.net/ubuntu/+source/linux|Linux (Ubuntu)]] package, unless the upstream maintainer or kernel developer notes otherwise, if a new mainline kernel comes out, and you haven't tested with it, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report.
  <<BR>><<BR>>