QA/Community/Bug Day: Difference between revisions
(Formatting) |
|||
| (148 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
= | == Contacts == | ||
Outdated: | |||
* [[IRC]] ([[Mozilla IRC Server]]): #qa | |||
== 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: | |||
[[Bugdays/Bug-Triage | Bug Triage]] days are generally Fridays. | |||
[[Bugdays/Bug-verification | 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 [https://quality.mozilla.org/category/events/ QMO events calendar] | |||
= Staying Connected = | |||
Join the mailing list - <s><code>https://lists.mozilla.org/listinfo/dev-quality</code></s> | |||
<br>Hang out in [[#Contact | IRC]] when we're not scheduled in #testday | |||
<br>Watch the [https://quality.mozilla.org/category/events/ 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: | |||
* 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.'' | |||
'''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 48: | 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. | ||
' | == 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]] | |||
Latest revision as of 23:11, 31 January 2024
Contacts
Outdated:
- IRC (Mozilla IRC Server): #qa
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:
- 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