QA/Community/Bug Day: Difference between revisions
(New "getting started" section.) |
(→Schedule: cleanup and reword session.) |
||
| Line 19: | Line 19: | ||
= Schedule = | = Schedule = | ||
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. | |||
The table below shows the three sessions, as well as how the times for each of the sessions translate into various time zones. | |||
{| border="1" | {| border="1" | ||
| Line 75: | Line 71: | ||
|} | |} | ||
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 = | = Community Representatives = | ||
Revision as of 19:56, 8 March 2007
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.
Topic of the Day
- No topic selected yet...
Getting Started
While the topic of day may have a particular focus for the session, we always want to try to do the following:
- Replicate the problems specified in bug reports and mark them as "confirmed" whenever we are able to do so.
- Clarify bug reports whenever we can do so without distorting the problems.
- 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.
Schedule
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.
The table below shows the three sessions, as well as how the times for each of the sessions translate into various time zones.
| Timezone \ Session | East Asia / Australia | Europe / Africa | Americas |
|---|---|---|---|
| GMT-10 Hawaii | Tue 01:00-03:00 | Tue 09:00-11:00 | Tue 16:00-18:00 |
| GMT-8 N.America, PST | Tue 03:00-05:00 | Tue 11:00-13:00 | Tue 18:00-20:00 |
| GMT-5 N.America, EST | Tue 06:00-08:00 | Tue 14:00-16:00 | Tue 21:00-23:00 |
| GMT UK/Ireland | Tue 11:00-13:00 | Tue 19:00-21:00 | Wed 02:00-04:00 |
| GMT+1 Europe, CET | Tue 12:00-14:00 | Tue 20:00-22:00 | Wed 03:00-05:00 |
| GMT+3 Moscow | Tue 14:00-16:00 | Tue 22:00-00:00 | Wed 05:00-07:00 |
| GMT+8 Beijing | Tue 19:00-21:00 | Wed 03:00-05:00 | Wed 10:00-12:00 |
| GMT+9 Japan | Tue 20:00-22:00 | Wed 04:00-06:00 | Wed 11:00-13: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.
Community Representatives
Bug days are led by Mozilla's QA staff and by experienced volunteers from our community.
Staying Connected
- Click 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 Mozilla QA blog
FAQ
Where do I start?
- The following documentation is good to become familiar with for anyone working on Mozilla projects:
- Mozilla QA linked to from the "For Testers" section of mozilla.org/developer
- A good document on how to find existing bugs
- Read 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.
- Join the #bugday channel
- Go to your favorite IRC client
- Connect to irc.mozilla.org and "/join #bugday"
- Then, just ask the moderators how you can help for the topic of the day.
What build should I be testing with?
- Get the latest Firefox Trunk builds, the next version of Firefox in development.