Bugsquad

This is the startpage for everybody interesting in dealing with bug reports in maemo.org Bugzilla.

Contents

What is a Bugsquad?

The maemo.org Bugsquad is a team that takes a look at the incoming and existing bug reports in maemo.org Bugzilla to make sure that they are in good shape before a developer spends time on the reports.

How everybody can help

Triaging

Triaging means to make sure that a problem has not already been reported before and that it has correct, enough and recent information.

  • Triage guide: A guide for triagers that explains good practices when triaging bug reports.
  • Stock answers: List of stock replies to use for various types of bug reports. We collect and provide product-specific information and knowledge for triagers that can be used as a first feedback for reports that are too vague to be helpful or interesting for developers.
  • Tasks: You can take a look at new reports, reproduce reports in your favorite application, or clean up old "moreinfo" reports. Just pick your favourite area. The section "Potential Tasks" of the Triage Guide lists some ideas.

Reporting

How to join the Bugsquad

  • Read the "How everybody can help" section above again in case you skipped the link to the Triage Guide.
  • Send an email to bugzilla@maemo.org or chat with us (e.g. andre__) in the #maemo channel on Freenode IRC and ask for triaging permissions.
  • Add yourself to the "Bugsquad Members" list below.
  • Welcome to the team! :-)

Bugdays

The Bugsquad will have a regular monthly day where we look through old Bugzilla bugs to clean up. Of course we don't just do this on bugdays, but it's more fun together and a cool way to introduce new people. Sometimes there also might be specific bugday subjects, for example "Email issues" or "older bugs about Maemo4". Our first bugday will be in December - more information to come.

What everybody should know

Bug and Feature Jars

Bug resolutions and what they mean

  • In general: https://bugs.maemo.org/page.cgi?id=fields.html#resolution
  • RESOLVED FIXED:
    • Bugs are closed as RESOLVED FIXED when the code has been internally written and verified to fix the issue.
    • Enhancements can be closed as RESOLVED FIXED when the issue has been added to the Roadmap or Specification for a next version.

What applications maintainers should know

  • Adding Extra products: A guide for Extras maintainers of packages in the Extras repository what information to provide for getting added in Bugzilla.

What Nokia developers should know

What Bugzilla administrators should know

  • Administration guide: A guide for administrators for creating products, components and virtual users.

Bugsquad Members

  1. Andre (maemo.org bugmaster) 11:07, 13 June 2008 (UTC)
  2. Karsten (maemo.org bugmaster) 11:07, 13 June 2008 (UTC)
  3. GeneralAntilles 11:05, 13 June 2008 (UTC)
  4. sjgadsby
  5. brontide 19:11, 12 August 2008 (UTC)
  6. Tim Samoff 14:57, 21 August 2008 (UTC)
  7. lma 06:25, 3 October 2008 (UTC)
  8. jukey 19:29, 6 October 2008 (UTC)
  9. yerga
  10. zerojay
  11. arnims
  12. prometoys
  13. qwerty12 17:41, 3 November 2009 (UTC)

Future plans

  • Technical plans:
    • We plan to either improve the template used in the enter_bug textarea, or also enhance/switch to something like the guided submission form.
    • Upgrade to Bugzilla 3.4

Documentation

Please use the "Bugs:" namespace for any subpages to keep consistency with other namespace schemes used in this wiki.

Acknowledgement