QA/Community/Bug Day

From MozillaWiki
Jump to navigation Jump to search


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

Community Representatives

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.

  • Asian/Australian Session :
    • Still in need of a volunteer.
    • 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 :
    • Still in need of a volunteer.
    • Current Moderator - tracy

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

Schedule

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
  • Europe/Africa session: 8pm-10pm in Paris, France gmt+1
  • Americas session: 9pm-11pm in N.Y., NY. gmt-5, 6pm-8pm in San Francisco, CA. gmt-8

Topic of the Day

Tuesday, Jan. 16th, 2007

  • Triage Firefox Trunk Unconfirmed bugs in the General component. We'll use this Bugzilla Search query.
    • Confirm or WFM these bugs
    • Move them out of the General category and into the appropriate component.
  • Next week: If we clean up the general category this week, then we'll work on a similar list for all the other categories next week

Review of last week

Bug day participation saw 4-6 visitors per session.

FAQ

Where do I start?

What build should I be testing with?