Bugs and features

You can help improving the maemo software, documentation, website... Please file all bug reports, feature requests and patches in maemo's bugzilla.

Reporting bugs doesn't take longer than writing emails after some practice. Bug reports are way more efficient for you because bugzilla never forgets and always shows the status and history of any bug. Registration is needed to file bugs and receive email updates. It takes less than a minute.

Bug reporting newbies

If this is your first bug have a look to the guidelines. You might also want to have a look to these unofficial but illustrative guides published at TabletBlog.com:

• Getting Involved: Bugzilla
• Want a feature on the Nokia 770 or Nokia N800? Ask!

Some shortcuts to submit new bugs and feature requests:

• maemo SDK and developer tools
• maemo website (maemo.org, garage, planet, wiki, bugzilla...)
• ... and more.

Tips and instructions

Follow these steps to improve your contributor/developer performance - and help others do their work better too.

Search and vote bugs first

Before filing a bug make sure it is not already filed by someone else. Use the Search field for that, either introducing just keywords or narrowing the results using the Advanced search. Note that you can vote on existing votes to increase its visibility and priority. Developers do look to these votes when prioritizing work.

File the bugs in their best place

bugs.maemo.org is organized in so-called products, and each product is divided in components. Try to find the best product and component for your bug, otherwise it might get longer for your reportjust to reach the developer that can fix it.

Get the email notifications that interest you

If you comment on a bug remember to add yourself to the CC (there is a checkbox right below the comments textarea), otherwise you might not receive the replies to your comment.

If you are interested or in charge of a specific component make sure your are watching the default assignee of that component in order to receive an email notification when there is activity on that component. Go to your Email preferences to define the users you want to watch and the type of notifications you want to receive.

NOTE: you don't want to do this if the default assignee of a component is "qa@maemo". We are fixing this by creating own alias for each component. In the meantime try watching the assignee for the whole product or file a bug requesting an own assignee for a specific component.

Psst! to developers

• If you know a bug is for you, reassign it to you - no matter how long it will take to actually start working on it.
• If you have acknowledged a bug and you reckon that needs to be processed, change the NEW value to ASSIGNED.
• Specially if you are working or planning to work on a bug, the flag ASSIGNED is required. Flying from NEW to FIXED should happen only for those bugs you fix in minutes, hours, no more than one day.