Changes

Jump to: navigation, search

QA/Community/Bug Day

2,617 bytes removed, 20:26, 29 March 2010
m
no edit summary
= Welcome to the Mozilla QA Community Bug Day wiki!! =
Join us on IRC in #bugday every other Tuesday from 8:00am to 2:00pm Pacific Daylight Time (UTC-7)to discuss and work on Bugzilla bug topics and get help from the Mozilla QA team.
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 will vary each event. But the general idea is to work through some sort of bug list as a team.
More information at the [http://quality.mozilla.org/events/2010/apr/06/bug-day-dupeme-april-6th-2010 Bug Day Event]
On Bugday on TuesdaySome of us hang around before or after sessions, June th our [http://tinyurl.com/yqspe4 Bugday Query] about Unconfirmed Firefox:Menus bugsso you may find someone in #bugday outside of the scheduled time, and if not, you can always find people in #qa that would be willing to help with Bug Day topic tasks.
== Future Bug Days ==We'll be holding Bug Days every other Tuesday. Please find future topics on the [http://quality.mozilla.org/events QMO events calendar] = Schedule =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.  {| 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 - Community Rep needed* Euro - Tomcat (Community Rep needed)* Americas - Community Rep needed
= Staying Connected =
* 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 Regular updates will be posted by Thursday afternoon (California time)for changing Bug Day topics
* Read the [http://weblogs.mozillazine.org/qa/ Mozilla QA blog]
'''Where do I start?'''
While the Each Bug Day topic of day may will have a particular specific focus for the session, we usually want to try . Instruction on what needs to do be done should be included in the followingQMO Bug Day Event post:
* Replicate the problems specified The following documentation is good to become familiar with for anyone trying to work in bug reports and mark them as "confirmed" whenever we are able to do so.Bugzilla projects:* Clarify Read [http://www.mozilla.org/quality/bug reports whenever we can do so without distorting the problems-writing-guidelines.* Close html Bug Writing Guidelines] to learn how to write effective bug reports as WORKSFORME or INVALID when it's appropriate to do so.* Ask reporters to provide missing information that would help lead to replicate and ultimately fix the bugs they reportbug fixes.
''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 What to become familiar with for anyone working on Mozilla projects: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.
* Join the '''#bugday''' channel
** 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 Bug days are led by members of Firefox in development. Mozilla'''Bug Day History'''* [http://wwws QA staff.mozillazineWe are always willing to guide and teach communities members who are willing to take on more responsibility.org/talkback.html?article=954 Asa's "Original" If you want to host or moderate a Bug Day post]* [http://weblogs.mozillazine.org/qa/archives/2006/04/bug_day_revival_starts_may_2_2, Please let us know.html Tracy's "Bug Day Revival" QA Blog post] *[[QA/Community/Bug Day/Archive|Archive of Bug Day topics]] '''Bug Day Planning'''For contributors planning and hosting Bug Days please see the [[QA/Community/Bug Day/Planner|Bug Day Planner]]
Confirm
4,072
edits

Navigation menu