Bugsquad
m (freenode -> Libera; changed a hardcoded wiki.maemo.org URL to use the fullurl: magic word to ensure that the link is always using the correct protocol (HTTPS))
 
(86 intermediate revisions not shown)
Line 1: Line 1:
-
This will become the startpage for everybody interesting in dealing with bug reports in [https://bugs.maemo.org Maemo Bugzilla].
+
This is the startpage for everybody interesting in dealing with bug reports in [https://bugs.maemo.org maemo.org Bugzilla].
-
==Tasks==
+
[[Image:Bugsquad-logo-wazd-small.png]]
-
* We want to establish a triage guide that defines how to correctly prioritize and "prepare" incoming bug reports - also see http://lists.maemo.org/pipermail//maemo-developers/2008-June/033719.html .
+
-
* Collect and provide product-specific information and knowledge ("stock answers") that can be used as a first feedback for vague bug reports: [[http://wiki.maemo.org/index.php?title=Bugs:Stock_answers StockAnswers]]
+
-
* Improve the quality of incoming reports by also having an information page for ''reporters''.
+
-
* In general: 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)
+
-
: ''Please avoid using block capitals for namespaces. See the MediaWiki naming guidelines for more details.'' --[[User:dneary|dneary]] 15:47, 13 June 2008 (UTC)
+
-
==Documentation==
+
==What is a Bugsquad?==
-
[[Bugs:Stock answers]]
+
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.
-
==Members==
+
==How everybody can help==
-
New members should simply add their name to the bottom of the list and jump right into the project.
+
=== 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.
-
# [[User:Andre|Andre]] (maemo.org bugmaster) 11:07, 13 June 2008 (UTC)
+
=== Reporting ===
-
# Karsten (maemo.org bugmaster) 11:07, 13 June 2008 (UTC)
+
* Useful and valuable reports: Provide a good quality report by taking a look at [https://bugs.maemo.org/page.cgi?id=bug-writing.html Bugzilla's Bug-writing page].
-
# [[User:generalantilles|GeneralAntilles]] 11:05, 13 June 2008 (UTC)
+
 
 +
==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 Libera IRC and ask for triaging permissions.
 +
* Add yourself to the "[[Bugsquad#Bugsquad_Members|Bugsquad Members]]" list below.
 +
* Welcome to the team! :-)
 +
 
 +
==Bugdays==
 +
The Bugsquad sometimes has 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.
 +
 
 +
The next bugday is unplanned.
 +
 
 +
Potential tasks, not only for bugdays, are listed [[Bugs:Tasks|here]]. Future plans are to have this on a monthly basis with different topics that we concentrate on.
 +
 
 +
*Topics to discuss at the next [[Bugs:Bugdays|Bugday]].
 +
 
 +
==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==
 +
The following list contains everybody who is (or was) part of the bugsquad. The column "Categories of major interest" is showing the parts of bugs.maemo.org which are watched regularly. The column "Categories of minor interest" is showing the parts of bugs.maemo.org which are watched irregularly (but more often than never).
 +
 
 +
The intention of this list is to see which places in bugs.maemo.org are monitored often (or by many Bugsquad members) and which categories are watched rarely (or by André only ;)).
 +
 
 +
 
 +
{| class="sortable" width="100%" cellspacing="1" cellpadding="1" border="1"
 +
|-
 +
! Member
 +
! Status
 +
! Categories of major interest
 +
! Categories of minor interest
 +
|-
 +
| [[User:Andre|Andre]] (maemo.org bugmaster)
 +
| active
 +
|
 +
*Everything in Maemo Official Apps
 +
*Everything in Maemo Official Platform
 +
*Everything under maemo.org Website > Bugzilla
 +
|
 +
*Everything else
 +
|-
 +
|[[User:generalantilles|GeneralAntilles]]
 +
|
 +
|
 +
|
 +
|-
 +
|[[User:sjgadsby|sjgadsby]]
 +
|
 +
|
 +
|
 +
|-
 +
|[[User:brontide|brontide]]
 +
|
 +
|
 +
|
 +
|-
 +
|[[User:timsamoff|Tim Samoff]]
 +
|
 +
|
 +
|
 +
|-
 +
|[[User:lma|lma]]
 +
|semi-active
 +
|
 +
* diablo-community-updates.
 +
* The open-standard parts of modest and rtcomm (ie IMAP, POP, SMTP, XMPP, SIP but not Nokia Messaging, Mail for Exchange, Skype etc).
 +
* Busybox
 +
* Input methods
 +
* SDK
 +
* Anything with "patch", "security" or "use-time" keywords.
 +
|
 +
*Everything else in Official Platform / Official Apps
 +
|-
 +
|Uwe '[[User:jukey|jukey]]' Kaminski
 +
|active
 +
|
 +
*browser-bugs@maemo.bugs (microb Browser)
 +
*modest-bugs@maemo.bugs (Mail Application)
 +
*general@miniature.garage.bugs (Miniature Chess)
 +
|
 +
*documentation@maemo.org
 +
*rtcomm@maemo.org
 +
*general-bugs@canola.garage.bugs
 +
*general-bugs@mer.garage.bugs
 +
|-
 +
|[[User:yerga|yerga]]
 +
|taking a break, but will return
 +
|
 +
*Multimedia related (mafw, camera, media-player, image-viewer, etc.)
 +
*Modest
 +
*Application manager
 +
*Hildon and GTK+
 +
*Pymaemo
 +
*My apps have lots of bugs too
 +
|
 +
*Website related (downloads, garage, repositories, etc.)
 +
*MicroB
 +
*Communication and PIM (telepathy, im-chat, contacts, calendar, etc.)
 +
*Location (framework and maps)
 +
|-
 +
|[[User:zerojay|zerojay]]
 +
|
 +
|
 +
|
 +
|-
 +
|[[User:arnims|arnims]]
 +
|
 +
|
 +
|
 +
|-
 +
|[[User:prometoys|prometoys]]
 +
|
 +
|
 +
|
 +
|-
 +
|[[User:qwerty12|qwerty12]]
 +
|
 +
|
 +
|
 +
|-
 +
|[[User:venomrush|venomrush]]
 +
|
 +
|
 +
|
 +
|-
 +
|[[User:mohammad7410|MohammadAG]]
 +
|
 +
|
 +
|
 +
|-
 +
| [{{fullurl:Bugsquad|action=edit&section=13}} Add Bugsquad member...]
 +
|
 +
|
 +
|
 +
|}
 +
 
 +
== Future plans ==
 +
None.
 +
 
 +
== 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]]
[[Category:Community]]
 +
[[Category:Quality Assurance]]

Latest revision as of 09:36, 9 November 2021

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

Image:Bugsquad-logo-wazd-small.png

Contents

[edit] 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.

[edit] How everybody can help

[edit] 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.
  • Greasemonkey triage helper script: A small helper script is available. After installing the Greasemonkey Add-on in a Mozilla browser (e.g. Firefox), 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 "Potential Tasks" of the Triage Guide lists some ideas.

[edit] Reporting

[edit] 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 Libera IRC and ask for triaging permissions.
  • Add yourself to the "Bugsquad Members" list below.
  • Welcome to the team! :-)

[edit] Bugdays

The Bugsquad sometimes has 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.

The next bugday is unplanned.

Potential tasks, not only for bugdays, are listed here. Future plans are to have this on a monthly basis with different topics that we concentrate on.

  • Topics to discuss at the next Bugday.

[edit] What everybody should know

[edit] Bug and Feature Jars

[edit] 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.

[edit] 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.

[edit] What Nokia developers should know

[edit] What Bugzilla administrators should know

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

[edit] Bugsquad Members

The following list contains everybody who is (or was) part of the bugsquad. The column "Categories of major interest" is showing the parts of bugs.maemo.org which are watched regularly. The column "Categories of minor interest" is showing the parts of bugs.maemo.org which are watched irregularly (but more often than never).

The intention of this list is to see which places in bugs.maemo.org are monitored often (or by many Bugsquad members) and which categories are watched rarely (or by André only ;)).


Member Status Categories of major interest Categories of minor interest
Andre (maemo.org bugmaster) active
  • Everything in Maemo Official Apps
  • Everything in Maemo Official Platform
  • Everything under maemo.org Website > Bugzilla
  • Everything else
GeneralAntilles
sjgadsby
brontide
Tim Samoff
lma semi-active
  • diablo-community-updates.
  • The open-standard parts of modest and rtcomm (ie IMAP, POP, SMTP, XMPP, SIP but not Nokia Messaging, Mail for Exchange, Skype etc).
  • Busybox
  • Input methods
  • SDK
  • Anything with "patch", "security" or "use-time" keywords.
  • Everything else in Official Platform / Official Apps
Uwe 'jukey' Kaminski active
  • browser-bugs@maemo.bugs (microb Browser)
  • modest-bugs@maemo.bugs (Mail Application)
  • general@miniature.garage.bugs (Miniature Chess)
  • documentation@maemo.org
  • rtcomm@maemo.org
  • general-bugs@canola.garage.bugs
  • general-bugs@mer.garage.bugs
yerga taking a break, but will return
  • Multimedia related (mafw, camera, media-player, image-viewer, etc.)
  • Modest
  • Application manager
  • Hildon and GTK+
  • Pymaemo
  • My apps have lots of bugs too
  • Website related (downloads, garage, repositories, etc.)
  • MicroB
  • Communication and PIM (telepathy, im-chat, contacts, calendar, etc.)
  • Location (framework and maps)
zerojay
arnims
prometoys
qwerty12
venomrush
MohammadAG
Add Bugsquad member...

[edit] Future plans

None.

[edit] Documentation

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

[edit] Acknowledgement

Retrieved from "http://bugs.maemo.org/Bugsquad"