Merge lp:~brunogirin/ubuntu-community-accomplishments/first-bug-confirmed-update1 into lp:~ubuntu-community-accomplishments-reviewers/ubuntu-community-accomplishments/0.1

[Bruno Girin]

Extended description to be more explicit about what constitutes a good bug report.

[Jono Bacon (jonobacon)]

Wonderful, Bruno. Thanks for the contribution! As an added bonus, you discovered a new bug - https://bugs.launchpad.net/ubuntu-accomplishments-system/+bug/945796 - this is good to know so I can get this fixed. :-)

Thanks, and merged!

review: Approve

[Bruno Girin (brunogirin)]

On 03/03/12 19:22, Jono Bacon wrote:
> Review: Approve
>
> Wonderful, Bruno. Thanks for the contribution! As an added bonus, you discovered a new bug - https://bugs.launchpad.net/ubuntu-accomplishments-system/+bug/945796 - this is good to know so I can get this fixed. :-)
>
> Thanks, and merged!
Hi Jono,

I just proposed a merge with a fix for that one and filed a new one
while I was at it:
https://bugs.launchpad.net/ubuntu-accomplishments-system/+bug/946251

Cheers,

Bruno

=== modified file 'accomplishments/ubuntu-community/first-bug-confirmed.accomplishment'
--- accomplishments/ubuntu-community/first-bug-confirmed.accomplishment	2012-03-02 14:14:47 +0000
+++ accomplishments/ubuntu-community/first-bug-confirmed.accomplishment	2012-03-03 00:01:19 +0000
@@ -8,7 +8,12 @@
 needs-signing=true
 needs-information=launchpad-email
 summary = A bug is a defect in a piece of software. Filing bugs is a great way to help improve Ubuntu and in order for the bug to be fixed, someone else needs to be able to reproduce and confirm it. The more detailed and precise your bug report is, the most likely it is that it can be reproduced by someone else. This achievement reflects that at least one of your bug reports was of good quality and was confirmed by someone else.
-steps: File a bug as you would normally (see the Filed First Bug accomplishments for more details) and ensure that the description is detailed enough to enable others to reproduce it.
+steps: File a bug as you would normally (see the Filed First Bug accomplishments for more details) and ensure that the description is detailed enough to enable others to reproduce it. To write a good bug report, include the following:
+		A clear and concise description of the problem. Don't forget to mention whether the bug can be triggered every time or whether it is intermittent.
+		A set of steps to reproduce the problem. Make sure that they are explicit. For instance, if a step involves selecting a menu item, specify whether selecting it using the mouse or keyboard shortcuts makes a difference.
+		A description of the failure when following those steps.
+		A description of what you expected the application to do instead. This is an important piece of information: sometimes, what the application does is what the developers expected it to do and they didn't realise it would cause you problems so describing what you expect is helpful to understand the defect.
+		Any additional information you think can help diagnose the problem. For instance, if the application used to work and suddenly stopped working, specify when it started mis-behaving.
 links: http://www.ubuntu.com
 	https://help.ubuntu.com/community/ReportingBugs
 	http://www.chiark.greenend.org.uk/~sgtatham/bugs.html