QA/Community/Bug Day: Difference between revisions

From MozillaWiki
< QA‎ | Community
Jump to navigation Jump to search
(Formatting)
 
(52 intermediate revisions by 7 users not shown)
Line 1: Line 1:
'''[[Mozilla_QA_Community|&laquo; back to Mozilla_QA_Community]]'''
== Contacts ==
= Welcome to the Mozilla QA Community Bug Day wiki!! = 
Outdated:
'''Note - New bugday times throughout the world. See the new schedule below.''' After discussion with several community members, we decided to move bugday times a bit earlier for each region. This change is an attempt to increase bugday participation by having regional session in the afternoon when people are at work or on university campus rather than in the evening when most people aren't willing or able to volunteer their time.
* [[IRC]] ([[Mozilla IRC Server]]): #qa


Join us on IRC in #bugday every Tuesday for your regional time to discuss and work on Bugzilla bug topics and get help from the Mozilla QA team.
== Welcome to the Mozilla QA Community Bug Day wiki!! == 


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 focus on particular 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.
Join us on IRC any time to talk about QA at Mozilla.


= Topic of the Day =
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.


== Tbird 2.0 unconfirmed triage ==
== Next Bug Day==
With the pending release of Thunderbird 2.0 we'd like to make a pass over the unconfirmed bugs to be certain nothing creeps into the release undetected.


Let's triage this [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Client+Software&product=Thunderbird&version=2.0&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=  bug list]. [http://tinyurl.com/25yfo5 http://tinyurl.com/25yfo5]
=== TBD ===


please use [http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2.0b2-candidates/rc1/ these builds] or even nightlies to test with.
As of April 2014:


= Schedule =
[[Bugdays/Bug-Triage | Bug Triage]] days are generally Fridays.
Bug days are arranged into three sessions so as to be convenient for participants around the world. The three sessions target "prime time" for those in Asia/Australia, Europe/Africa, and North/South America, but anyone may attend the sessions as they wish.
[[Bugdays/Bug-verification | Bug Verification]] days are on Wednesday!


'''note: After considering input from a few regular Bugday participants, we will try another time of day for each session. Instead of in the evening, we'll try afternoons. This change will occur for the Bugday sessions on April 3rd.'''
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!


The full chart below confuses the heck out of me and is now incorrect for the new sessions and DST changes around the world.
= Future Bug Days =
 
Please find future topics on the [https://quality.mozilla.org/category/events/ QMO events calendar]
A bit simpler schedule:
 
'''Asia session - 14:00-16:00 UTC/GMT +8 hours (Beijing)'''<br>
'''Euro session - 14:00-16:00 UTC/GMT +2 hours (Berlin)'''<br>
'''Amer. session - 12:00-14:00 UTC/GMT -7 hours (Los Angeles)'''
 
Please use that and the tools at [http://www.timeanddate.com/worldclock/ The World Clock] to help determine when a session is happening for you.
 
{| border="1"
|-
|| '''Timezone / Session'''
|bgcolor=#CCCCFF| '''E. Asia / Aus.'''
|bgcolor=#FFFFCC| '''Europe / Africa'''
|bgcolor=#CCFFCC|'''Americas'''
|-
! GMT-7 Los Angeles, PDT*
|bgcolor=#CCCCFF|Tue 04:00-06:00
|bgcolor=#FFFFCC|Tue 12:00-14:00
|bgcolor=#CCFF99|*Tue 18:00-20:00
|-
! GMT-6 Denver, MDT*
|bgcolor=#CCCCFF|Tue 05:00-07:00
|bgcolor=#FFFFCC|Tue 13:00-15:00
|bgcolor=#CCFF99|*Tue 19:00-21:00
|-
! GMT-5 Chicago, CDT*
|bgcolor=#CCCCFF|Tue 06:00-08:00
|bgcolor=#FFFFCC|Tue 14:00-16:00
|bgcolor=#CCFF99|*Tue 20:00-22:00
|-
! GMT-4 New York, EDT*
|bgcolor=#CCCCFF|Tue 07:00-09:00
|bgcolor=#FFFFCC|Tue 15:00-17:00
|bgcolor=#CCFF99|*Tue 21:00-23:00
|-
! GMT UK/Ireland
|bgcolor=#CCCCFF|Tue 11:00-13:00
|bgcolor=#FFFF99|*Tue 19:00-21:00
|bgcolor=#CCFFCC|Wed 01:00-03:00
|-
! GMT+1 Europe, CET
|bgcolor=#CCCCFF|Tue 12:00-14:00
|bgcolor=#FFFF99|*Tue 20:00-22:00
|bgcolor=#CCFFCC|Wed 02:00-04:00
|-
! GMT+2 Europe
|bgcolor=#CCCCFF|Tue 13:00-15:00
|bgcolor=#FFFF99|*Tue 21:00-23:00
|bgcolor=#CCFFCC|Wed 03:00-05:00
|-
! GMT+3 Moscow
|bgcolor=#CCCCFF|Tue 14:00-16:00
|bgcolor=#FFFF99|*Tue 22:00-00:00
|bgcolor=#CCFFCC|Wed 04:00-06:00
|-
! GMT+8 Beijing
|bgcolor=#99CCFF|*Tue 19:00-21:00
|bgcolor=#FFFFCC|Wed 03:00-05:00
|bgcolor=#CCFFCC|Wed 09:00-11:00
|-
! GMT+9 Japan
|bgcolor=#99CCFF|*Tue 20:00-22:00
|bgcolor=#FFFFCC|Wed 04:00-06:00
|bgcolor=#CCFFCC|Wed 10:00-12:00
|}
 
 
Some of us hang around between or after sessions, so you may find someone in #bugday outside of this time, and if not, you can always find people in #qa.
 
* Calculated with DST
 
= Community Representatives =
 
Bug days are led by Mozilla's QA staff and by experienced volunteers from our community.
 
* Asia - Tracy (future - Emily?)
* Euro - Tomcat
* Americas - Tracy (future - Triona?)


= Staying Connected =
= Staying Connected =
* Click [http://mail.mozilla.org/listinfo/communityqateam here] to join the mailing list.
Join the mailing list - <s><code>https://lists.mozilla.org/listinfo/dev-quality</code></s>
* Hang out in #qa when we're not scheduled in #bugday or #testday
<br>Hang out in [[#Contact | IRC]] when we're not scheduled in #testday
* Keep an eye on this page. Weekly updates will be posted by Thursday afternoon (California time)
<br>Watch the [https://quality.mozilla.org/category/events/ QMO Events page] for new event announcements.
* Read the [http://weblogs.mozillazine.org/qa/ Mozilla QA blog]


= FAQ =
= FAQ =
<center>[[Image:G431a.jpg]]</center>


[[Category:Excrement]]
[[Category:Buttfucking]]
[[Category:Herman's Penis]]
'''Where do I start?'''
'''Where do I start?'''
While the topic of day may have a particular focus for the session, we usually want to try to do the following:
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:


* Replicate the problems specified in bug reports and mark them as "confirmed" whenever we are able to do so.
The following documentation is good to become familiar with for anyone trying to work in Bugzilla projects:
* Clarify bug reports whenever we can do so without distorting the problems.
* 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.
* Close bug reports as WORKSFORME or INVALID when it's appropriate to do so.
* Ask reporters to provide missing information that would help to replicate and ultimately fix the bugs they report.


''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.''
''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.''


* The following documentation is good to become familiar with for anyone working on Mozilla projects:
'''What to do next?'''
** [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 135: 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?'''
*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 Day History'''
* [http://www.mozillazine.org/talkback.html?article=954 Asa's "Original" Bug Day post]
* [http://weblogs.mozillazine.org/qa/archives/2006/04/bug_day_revival_starts_may_2_2.html Tracy's "Bug Day Revival" QA Blog post]
 
*[http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day:Archive Archive of bugday topics]


'''Bug Day Planning'''
== Community Representatives ==
For contributors planning and hosting Bug Days please see the [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day:Planner Bug Day Plannner]
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"