Bugsquad: Difference between revisions

Revision as of 20:31, 11 November 2009

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

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 "Bugs:Triage_guide#Potential_tasks Potential Tasks" of the Triage Guide lists some ideas.

Reporting

Useful and valuable reports: Provide a good quality report by taking a look at Bugzilla's Bug-writing page.

How to join the Bugsquad

Create a Bugzilla account.
Read the "How everybody can help" section below.
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! :-)

What everybody should know

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.

Bug and Feature Jars

Stephen Gadsby provides weekly Maemo Bug and Feature Jars.
Additionally, Andre Klapper provides monthly Feature Jars.

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

Information for people that also have access to Nokia's non-public Bugtracker

What Bugzilla administrators should know

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

Bugsquad Members

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

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.

Meetings

The QA team has occasional meetings.

Minutes of last QA meeting

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

@@ Line 1: / Line 1: @@
 This is the startpage for everybody interesting in dealing with bug reports in [https://bugs.maemo.org maemo.org Bugzilla].
-==Tasks==
+==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.
-=== Documentation ===
+==How everybody can help==
-''Please use the "Bugs:" namespace for subpages to keep consistency with other namespace schemes used in this wiki (e.g. MAG: for the Maemo Action Group)''
+=== Triaging ===
+Triaging means to make sure that a problem has not already been reported before and that it has correct, enough and recent information.
+* [[Bugs:Triage_guide|Triage guide]]: A guide ''for triagers'' that explains good practices when triaging bug reports.
+* [[Bugs:Stock answers|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 "[[Bugs:Triage_guide#Potential_tasks Potential Tasks]]" of the Triage Guide lists some ideas.
-==== For triagers ====
+=== Reporting ===
-* [[Bugs:Triage_guide|Triage guide]]: A guide ''for triagers'' that defines how to correctly prioritize and "prepare" incoming bug reports (see [http://lists.maemo.org/pipermail//maemo-developers/2008-June/033719.html maemo-developers - maemo Bug Jar #6]).
+* Useful and valuable reports: Provide a good quality report by taking a look at [https://maemo.org/bugzilla/page.cgi?id=bug-writing.html Bugzilla's Bug-writing page].
-* [[Bugs:Stock answers|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 vague bug reports.
-* [[Bugs:Cloning|Information for people that also have access to Nokia's non-public Bugtracker]]
-==== For reporters ====
+==How to join the Bugsquad==
-* Useful and valuable reports: Improve the quality of incoming reports by asking reporters to take a look at [https://maemo.org/bugzilla/page.cgi?id=bug-writing.html Bugzilla's static Bug-writing page].
+* Create a Bugzilla account.
+* Read the "How everybody can help" section below.
+* 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! :-)
-** We may either improve the template used in the enter_bug textarea, or also enhance/switch to something like the [https://bugs.maemo.org/enter_bug.cgi?product=applications&format=guided guided submission form].
+==What everybody should know==
+===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.
-==== For administrators ====
+=== Bug and Feature Jars ===
+* Stephen Gadsby provides weekly [http://www.octofish.net/bugjar/ Maemo Bug and Feature Jars].
+* Additionally, Andre Klapper provides monthly [http://talk.maemo.org/showthread.php?t=27833 Feature Jars].
-* [[Bugs:Administration_guide|Administration guide]]: A guide ''for administrators'' for creating products, components and virtual users.
+==What applications maintainers should know==
+* [[Bugs:Adding_Extra_products|Adding Extra products]]: A guide ''for Extras maintainers of packages in the Extras repository'' what information to provide for getting added in Bugzilla.
-==== For Extras package maintainers ====
+==What Nokia developers should know==
-* [[Bugs:Adding_Extra_products|Adding Extra products]]: A guide ''for Extras package maintainers'' what information to provide for getting added in Bugzilla.
+* [[Bugs:Cloning|Information for people that also have access to Nokia's non-public Bugtracker]]
-=== Bug Jar ===
-Setup a system for syndicating sjgadsby's [http://www.octofish.net/bugjar/ Maemo Bug Jars] to the wiki.
-* One possible solution is being put together in [[User:Generalantilles/Sandbox/Bug_Jar|GeneralAntilles' Sandbox]].
-* Will need some templates to make things easier.
-==Resolution guidelines==
+==What Bugzilla administrators should know==
-* In general: https://bugs.maemo.org/page.cgi?id=fields.html#resolution
+* [[Bugs:Administration_guide|Administration guide]]: A guide ''for administrators'' for creating products, components and virtual users.
-* RESOLVED FIXED:
-** '''Bugs''' are closed as FIXED when the code has been internally written and verified to fix the issue.
-** '''Enhancements''' can be closed as FIXED when the issue has been added to the Roadmap or Specification for a next version.
-==Members==
+==Bugsquad Members==
-New members should simply add their name to the bottom of the list and jump right into the project.
 # [[User:Andre|Andre]] (maemo.org bugmaster) 11:07, 13 June 2008 (UTC)
@@ Line 49: / Line 56: @@
 # [[User:prometoys|prometoys]]
 # [[User:qwerty12|qwerty12]] 17:41, 3 November 2009 (UTC)
+==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.
 == Meetings ==
 The QA team has occasional meetings.
+* [[QA meeting| Minutes of last QA meeting]]
+== 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 [https://bugs.maemo.org/enter_bug.cgi?product=applications&format=guided guided submission form].
+** Upgrade to Bugzilla 3.4
-* [[QA meeting| Minutes of last QA meeting]]
+== Documentation ==
+''Please use the "Bugs:" namespace for any subpages to keep consistency with other namespace schemes used in this wiki.
+== Acknowledgement ==
+* [http://live.gnome.org/Bugsquad GNOME Bugsquad]
+* [http://techbase.kde.org/Contribute/Bugsquad KDE Bugsquad]
 [[Category:Community]]