QA/Community/Bug Day: Difference between revisions

From MozillaWiki
< QA‎ | Community
Jump to navigation Jump to search
(Formatting)
 
(30 intermediate revisions by 6 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.


== Firefox Trunk unconfirmed triage - Platform Testing ==
== Next Bug Day==
We are looking at unconfirmed Bugs for Firefox Trunk. This time we have 2 Buglists :


Buglist 1 [http://tinyurl.com/2yags Buglist 1]. This Buglist contains unconfirmed Trunk Bugs marked as OS= All. So hammer on this bugs and see if you can confirm this bug for your platform.
=== TBD ===


The second Buglist Buglist 2 [http://tinyurl.com/29vppw Buglist 2] is the List of unconfirmed bugs for the Sun Solaris Plattform. Check out this List and see if you can reproduce this bug on your Plattform (like Windows, Linux, Mac) or even Solaris.
As of April 2014:


We'll be actively pinging anyone in the channel to take a couple bugs.  So if you're there be prepared to do a little bugzilla work. :-)
[[Bugdays/Bug-Triage | Bug Triage]] days are generally Fridays.
[[Bugdays/Bug-verification | Bug Verification]] days are on Wednesday!


Please use [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ Nightly Trunk Builds] to test with.
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!


= Schedule =
= Future Bug Days =
Bug days are arranged into three sessions so as to be convenient for participants around the world. The three sessions target for those in Asia/Australia, Europe/Africa, and North/South America, of course anyone may attend any session as they wish.
Please find future topics on the [https://quality.mozilla.org/category/events/ QMO events calendar]
 
 
{| border="1"
|-
|| '''Timezone / Session'''
|bgcolor=#DDDDFF|'''E. Asia/Australia session'''
|bgcolor=#FFFFDD|'''Europe/Africa session'''
|bgcolor=#DDFFDD|'''Americas session'''
|-
! Los Angeles, USA (PST=UTC-8+DST)
||Mon 23:00-01:00
||Tue 05:00-07:00
|bgcolor=#DDFFDD|*Tue 12:00-14:00
|-
! UTC
|bgcolor=#F0F0F0|Tue 06:00-08:00
|bgcolor=#F0F0F0|Tue 12:00-14:00
|bgcolor=#F0F0F0|Tue 19:00-21:00
|-
! UK (BST=UTC+DST)
||Tue 07:00-09:00
||Tue 13:00-15:00
||Tue 20:00-22:00
|-
! Berlin, Germany (CEST=UTC+1+DST)
||Tue 08:00-10:00
|bgcolor=#FFFFDD|*Tue 14:00-16:00
||Tue 21:00-23:00
|-
! Moscow, Russia (UTC+3+DST)
||Tue 10:00-12:00
||Tue 16:00-18:00
||Tue 23:00-01:00
|-
! Beiging, China (UTC+8, DST n/a)
|bgcolor=#DDDDFF|*Tue 14:00-16:00
||Tue 20:00-22:00
||Wed 03:00-05:00
|}
 
 
A bit simpler schedule:
 
'''Asia session - 14:00-16:00 UTC/GMT +8 hours (Beijing) (06:00-08:00 UTC)'''<br>
'''Euro session - 14:00-16:00 UTC/GMT +2 hours (Berlin) (12:00-14:00 UTC)'''<br>
'''Amer. session - 12:00-14:00 UTC/GMT -7 hours (Los Angeles) (19:00-21:00 UTC)'''
 
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.
 
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.
 
= 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 =


'''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 110: 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"