Difference between revisions of "Submit Bugs/Problems"

Revision as of 13:49, 14 May 2016

If you find a bug or would like to report an issue with Sugar, visit https://github.com/sugarlabs and look for the activity or a sugar component tepository hat you think is relevant.

If you don't know which one to use, use https://github.com/sugarlabs/sugar, and be sure to sign up and sign in to Github.

Then visit the issues tab of the repo, and rit the big green button to report your issue.

If you haven't written issue reports before, here's a great guide: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

@@ Line 1: / Line 1: @@
 __TOC__
-<big>'''Where to Describe Bugs & Problems'''</big>
+If you find a bug or would like to report an issue with Sugar, visit <nowiki>https://github.com/sugarlabs</nowiki> and look for the activity or a sugar component tepository hat you think is relevant.
-* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find with Sugar on the various distributions.
-* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
-* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
-* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org).  Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.
-* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem.
-: See [[BugSquad/Bug Report]] for reporting guidance.
-: You may also [[Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile| report your hardware profile]] and upload log files as described in [[BugSquad/Get Logs]].
-* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.
-Email sent to feedback AT sugarlabs.org will be forwarded to the IAEP mailing list, which is used for general discussion of the Sugar Labs education project.
+If you don't know which one to use, use <nowiki>https://github.com/sugarlabs/sugar</nowiki>, and be sure to sign up and sign in to Github.
-== bugs.sugarlabs.org/timeline ==
-{{Iframe|collapsed=|http://bugs.sugarlabs.org/timeline
+Then visit the issues tab of the repo, and rit the big green button to report your issue.
-|http://bugs.sugarlabs.org/timeline|900|800|1}}
+If you haven't written issue reports before, here's a great guide: <nowiki>http://www.chiark.greenend.org.uk/~sgtatham/bugs.html</nowiki>
+:

Difference between revisions of "Submit Bugs/Problems"

Revision as of 13:49, 14 May 2016

Navigation menu

Search