QA/Community/Bug Day: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 3: | Line 3: | ||
= Welcome to the Mozilla QA Community Bug Day wiki!! = | = Welcome to the Mozilla QA Community Bug Day wiki!! = | ||
Join us on IRC in #bugday every other Tuesday to discuss and work on Bugzilla bug topics and get help from the Mozilla QA team. | 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. | 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. | ||
| Line 13: | Line 13: | ||
More information at the [http://quality.mozilla.org/events/2010/apr/06/bug-day-dupeme-april-6th-2010 Bug Day Event] | More information at the [http://quality.mozilla.org/events/2010/apr/06/bug-day-dupeme-april-6th-2010 Bug Day Event] | ||
Some of us hang around before or after sessions, so 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 = | |||
Please find future topics on the [http://quality.mozilla.org/events QMO events calendar] | |||
= Staying Connected = | = Staying Connected = | ||
* Click [http://mail.mozilla.org/listinfo/communityqateam here] to join the mailing list. | * 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 | * Hang out in #qa when we're not scheduled in #bugday or #testday | ||
* Keep an eye on this page. | * Keep an eye on this page. Regular updates will be posted for changing Bug Day topics | ||
* Read the [http://weblogs.mozillazine.org/qa/ Mozilla QA blog] | * Read the [http://weblogs.mozillazine.org/qa/ Mozilla QA blog] | ||
| Line 88: | Line 27: | ||
'''Where do I start?''' | '''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: | |||
* | * 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. | ||
''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.'' | ||
What to do next? | |||
* 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 45: | ||
** 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. | ||
= 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 [[QA/Community/Bug Day/Planner|Bug Day Planner]] | |||
' | |||
For contributors planning and hosting Bug Days please see the [[QA/Community/Bug Day/Planner|Bug Day Planner]] | |||
Revision as of 20:26, 29 March 2010
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.
Next Bug Day
April 6th, 2010 - DUPEME - finding similar bugs of suspected duplicates
More information at the Bug Day Event
Some of us hang around before or after sessions, so 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
Please find future topics on the QMO events calendar
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. Regular updates will be posted for changing Bug Day topics
- Read the Mozilla QA blog
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:
- Read Bug Writing Guidelines to learn how to write effective bug reports that lead to bug 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.
What to do next?
- 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.
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