Bugsquad

2009-12-16T22:42:03Z

95.154.199.220: /* What is a Bugsquad? */

This is the startpage for everybody interesting in dealing with bug reports in [https://bugs.maemo.org maemo.org Bugzilla].

[[Image:Bugsquad-logo-wazd-small.png]]

==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.
* [[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.
* Greasemonkey triage helper script: A small helper script is available. After installing the [https://addons.mozilla.org/firefox/addon/748 Greasemonkey Add-on] in a Mozilla browser (e.g. Firefox), [http://home.arcor.de/ak-47/pub/bugsmaemoorg_triage_help.user.js click here] to install it. It provides common stock answers that can be inserted by one click from the list above the comment field in maemo.org Bugzilla. Just play with it a bit (You can reload a bug report website by using Control+F5). Enhancements and patches are welcome and should be sent to aklapper at openismus dot com.
* 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 [https://maemo.org/bugzilla/page.cgi?id=bug-writing.html Bugzilla's Bug-writing page].

==How to join the Bugsquad==
* Read the "[[Bugsquad#How_everybody_can_help|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#Bugsquad_Members|Bugsquad Members]]" list below.
* Welcome to the team! :-)

==Bugdays==
The Bugsquad will have a Bugday where we look through old Bugzilla reports 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.

'''Next bugday: Tuesday, December 15th, 18:00-03:00 UTC in #maemo-bugs on Freenode IRC.''' This bugday has no specific topic.

Potential tasks, not only for bugdays, are listed [http://wiki.maemo.org/Bugs:Tasks here]. Future plans are to have this on a monthly base with different topics that we concentrate on.

==What everybody should know==
=== 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].

===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==
* [[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.

==What Nokia developers should know==
* [[Bugs:Cloning|Information for people that also have access to Nokia's non-public Bugtracker]]

==What Bugzilla administrators should know==
* [[Bugs:Administration_guide|Administration guide]]: A guide ''for administrators'' for creating products, components and virtual users.

==Bugsquad Members==

# [[User:Andre|Andre]] (maemo.org bugmaster) 11:07, 13 June 2008 (UTC)
# [[User:Karstenb|Karsten]] (maemo.org bugmaster) 11:07, 13 June 2008 (UTC)
# [[User:generalantilles|GeneralAntilles]] 11:05, 13 June 2008 (UTC)
# [[User:sjgadsby|sjgadsby]]
# [[User:brontide|brontide]] 19:11, 12 August 2008 (UTC)
# [[User:timsamoff|Tim Samoff]] 14:57, 21 August 2008 (UTC)
# [[User:lma|lma]] 06:25, 3 October 2008 (UTC)
# [[User:jukey|jukey]] 19:29, 6 October 2008 (UTC)
# [[User:yerga|yerga]]
# [[User:zerojay|zerojay]]
# [[User:arnims|arnims]]
# [[User:prometoys|prometoys]]
# [[User:qwerty12|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 [https://bugs.maemo.org/enter_bug.cgi?product=Email&format=guided 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 ==
* [http://live.gnome.org/Bugsquad GNOME Bugsquad]
* [http://techbase.kde.org/Contribute/Bugsquad KDE Bugsquad]
* The [[FIXED in Fremantle Hall of Fame]]

[[Category:Community]]

Maemo Wiki Mirror - User contributions [en]

Bugsquad