Version 2 (modified by roh, 11 years ago) (diff)


Important: Read This Before Creating a Ticket

Please note that this trac is used for Openmoko related software / hardware / distribution bugs only. Its intend is to help coordinating the development effort around the Openmoko universe.

Support and installation questions should be asked on the support mailing list or on IRC channel, not filed as tickets. Also, you can check the official Openmoko Wiki to get detailed technical instructions how to get started / available packages / distributions / reflashing / etc.

When to not create a ticket here

If you have found a genuine bug, then there's a good chance you're not the first person to notice it... Please take the time to search for an already existing ticket. A good tip is to look for the verbatim text of the error you're seeing, e.g.

Alternatively, check our list of recently closed duplicates.

If you found your bug, read the given descriptions and comments carefully. Maybe you are able to add useful hints.

The advantage of finding a pre-existing ticket is that there's often an existing workaround, or a patch waiting for feedback. In this case, please take the next step and participate in fixing the bug.

Beware: A "me too" without log messages, additional information or new ideas is just noise and makes the engineers life harder without adding any valuable information.

Yes, I think I've found a new bug

Then please, by all means let us know!

If you haven't done it before, read the Bug Filing Policy which will give you some tips about how to create a good bug report. Then proceed to create the bug report having the following basic guidelines in mind:

  • Choose a meaningful summary which enables others to recognize / find your bug, e.g. "[GSM] not working properly after x hours of usage"
  • Always add the used distribution / image / installed packages / kernel / build date in the bug report. E.g. "kernel: 20080723-asu.stable-uImage.bin, rootfs: 20080805-asu.stable-rootfs.jffs2"
  • Add a step by step instruction how to reproduce the bug, the current result and the expected result.
  • Do not fiddle with the component unless you are 150% sure you know what you are doing. The QA team or the engineers will take care of the correct assignment.
  • Never set Priority, Severity or Milestone - thats for the QA team only!
  • Add yourself to the CC list in order to get informed about updates regarding the bug.

Of course, improvement ideas (preferably with patches!) are also welcomed, and you also can create enhancement requests.

-- The Openmoko Team