QA/Community/Bug Day: Difference between revisions

From MozillaWiki
< QA‎ | Community
Jump to navigation Jump to search
(Revert.)
(Formatting)
 
(125 intermediate revisions by 10 users not shown)
Line 1: Line 1:
= Welcome to the Mozilla QA Community Bug Day wiki!! = 
== Contacts ==
Outdated:
* [[IRC]] ([[Mozilla IRC Server]]): #qa


Bug Days are an excellent way to contribute to Mozilla's QA efforts.  It doesn't matter if you've been involved with Mozilla for years or if this is your first step into our amazing open source community. Anyone can participate and be a valuable contributor. We gather together at predetermined times to work on areas in Bugzilla. The exact area or topic for Bug Day may vary week to week. But the general idea is to work through some sort of bug list as a team.
== Welcome to the Mozilla QA Community Bug Day wiki!! == 


= Topic of the Day =
Join us on IRC any time to talk about QA at Mozilla.


'''Tuesday, Jan. 23rd, 2007'''
Test Days are an excellent way to contribute to Mozilla's QA efforts.  It doesn't matter if you've been involved with Mozilla for years or if this is your first step into our amazing open source community. Anyone can participate and be a valuable contributor. The exact area or topic for Bug Day will vary for each event. But the general idea is to work through some sort of bug list as a team.


* '''2nd of 3 sessions - Triage Firefox Trunk Unconfirmed bugs in the components listed before General.'''
== Next Bug Day==
** Use [http://tinyurl.com/tgluk this query] for unconfirmed bugs in components Bookmarks through Form Manager
** Confirm or WFM these bugs
** If confirmed, move them out of the General category and into the appropriate component.


* 3 session schedule to triage Firefox trunk unconfirmed bugs:
=== TBD ===
** Session 1) (Jan. 16th) We'll use this [http://tinyurl.com/yc5spd Bugzilla Search query] of general trunk unconfirmed bugs
** Session 2) (Jan. 23rd) We'll work on [http://tinyurl.com/tgluk this query] for unconfirmed bugs in components Bookmarks through Form Manager.
** Session 3) (Jan. 30th) We'll complete the sweep by working on [http://tinyurl.com/yx5c2w this query] for unconfirmed bugs in components Help Documentation through View Source


= Schedule =
As of April 2014:
In an effort to make Bug Days more accessible to interested folks around the globe, I've decided to split up Bug Day into three 2 hour sessions. Below is the schedule we'll use to catch East Asia, Europe and the USA in "prime time."


*East Asia/Australia session: 8pm-10pm in Tokyo, Japan gmt+9
[[Bugdays/Bug-Triage | Bug Triage]] days are generally Fridays.
*Europe/Africa session: 8pm-10pm in Paris, France gmt+1           
[[Bugdays/Bug-verification | Bug Verification]] days are on Wednesday!
*Americas session: 9pm-11pm in N.Y., NY. gmt-5, 6pm-8pm in San Francisco, CA. gmt-8


== Review of last week ==
Join us in #testday and introduce yourself. In triaging, we go through newly reported bugs. For verification, we try to make sure that "fixed" bugs really are fixed. See you in #testday!


*Asia Session: 8 vistors, 3 active - 9 bugs triaged
= Future Bug Days =
*Euro Session: 13 visitors, 5 active - 9 bugs triaged
Please find future topics on the [https://quality.mozilla.org/category/events/ QMO events calendar]
*Am Session: 12 visitors, 3 active - 2 bugs triaged (list cherry picked by first two sessions)


== Community Representatives ==
= Staying Connected =
We'd like to recruit a few individuals from the community to organize and run Bug Days.  tracy will be on vacation all of February.
Join the mailing list - <s><code>https://lists.mozilla.org/listinfo/dev-quality</code></s>
<br>Hang out in [[#Contact | IRC]] when we're not scheduled in #testday
<br>Watch the [https://quality.mozilla.org/category/events/ QMO Events page] for new event announcements.
 
= FAQ =
 
'''Where do I start?'''
Each Bug Day topic will have a specific focus. Instruction on what needs to be done should be included in the QMO Bug Day Event post:


* Asian/Australian Session :  
The following documentation is good to become familiar with for anyone trying to work in Bugzilla projects:
** Still in need of a volunteer.  
* Read [http://www.mozilla.org/quality/bug-writing-guidelines.html Bug Writing Guidelines] to learn how to write effective bug reports that lead to bug fixes.
** Current moderator - Tomcat and tracy - (tracy may have good enough access to host the Asian session while he is in Asia his entire vacation).
* European/African Session :
** Current moderator - Tomcat
* Americas Session :
** Catriona and Jackie have volunteered to share this during tracy's vacation.
** Current Moderator - tracy


== Staying Connected ==
''Note: If you don't have the necessary rights to make a change to a bug, add a comment to the bug detailing what should be changed and why. You can also make this known in the #bugday channel, and one of the moderators or an experienced volunteer will assist you.''
* Click [http://mail.mozilla.org/listinfo/communityqateam here] to join the mailing list.
* Hang out in #qa when we're not scheduled in #bugday or #testday
* Keep an eye on this page. Weekly updates will be posted by Thursday afternoon (California time)
* Read the [http://weblogs.mozillazine.org/qa/ Mozilla QA blog]


= FAQ =
'''What to do next?'''


'''Where do I start?'''
* The following documentation is good to become familiar with for anyone working on Mozilla projects:
** [http://www.mozilla.org/quality/ Mozilla QA] linked to from the "For Testers" section of [http://www.mozilla.org/developer/ mozilla.org/developer]
** A [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html good document] on how to find existing bugs
** Read [http://www.mozilla.org/quality/bug-writing-guidelines.html Bug Writing Guidelines] to learn how to write effective bug reports that lead to bug fixes.
* Review the documentation specific to the topic of the day.
* Review the documentation specific to the topic of the day.
* Join the '''#bugday''' channel
* Join the '''#bugday''' channel
Line 62: Line 47:
*** [http://www.ircreviews.org/clients/platforms-unix.html Linux clients]  
*** [http://www.ircreviews.org/clients/platforms-unix.html Linux clients]  
** Connect to [irc://irc.mozilla.org irc.mozilla.org] and "/join #bugday"
** Connect to [irc://irc.mozilla.org irc.mozilla.org] and "/join #bugday"
** Then, just ask the moderators how you can help for the topic of the day.  
** Then, just ask the moderators how you can help for the topic of the day.


'''What build should I be testing with?'''
== Community Representatives ==
*Get [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ the latest Firefox Trunk builds], the next version of Firefox in development.
Bug days are led by members of Mozilla's QA staff. We are always willing to guide and teach communities members who are willing to take on more responsibility. If you want to host or moderate a Bug Day, Please let us know. For contributors planning and hosting Bug Days please see the [[QA/Community/Bug Day/Planner|Bug Day Planner]]

Latest revision as of 23:11, 31 January 2024

Contacts

Outdated:

Welcome to the Mozilla QA Community Bug Day wiki!!

Join us on IRC any time to talk about QA at Mozilla.

Test Days are an excellent way to contribute to Mozilla's QA efforts. It doesn't matter if you've been involved with Mozilla for years or if this is your first step into our amazing open source community. Anyone can participate and be a valuable contributor. The exact area or topic for Bug Day will vary for each event. But the general idea is to work through some sort of bug list as a team.

Next Bug Day

TBD

As of April 2014:

Bug Triage days are generally Fridays. Bug Verification days are on Wednesday!

Join us in #testday and introduce yourself. In triaging, we go through newly reported bugs. For verification, we try to make sure that "fixed" bugs really are fixed. See you in #testday!

Future Bug Days

Please find future topics on the QMO events calendar

Staying Connected

Join the mailing list - https://lists.mozilla.org/listinfo/dev-quality
Hang out in IRC when we're not scheduled in #testday
Watch the QMO Events page for new event announcements.

FAQ

Where do I start? Each Bug Day topic will have a specific focus. Instruction on what needs to be done should be included in the QMO Bug Day Event post:

The following documentation is good to become familiar with for anyone trying to work in Bugzilla projects:

Note: If you don't have the necessary rights to make a change to a bug, add a comment to the bug detailing what should be changed and why. You can also make this known in the #bugday channel, and one of the moderators or an experienced volunteer will assist you.

What to do next?

Community Representatives

Bug days are led by members of Mozilla's QA staff. We are always willing to guide and teach communities members who are willing to take on more responsibility. If you want to host or moderate a Bug Day, Please let us know. For contributors planning and hosting Bug Days please see the Bug Day Planner

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Community/Bug_Day&oldid=1249867"