Confirmed users
14,525
edits
(→Tips) |
No edit summary |
||
| Line 29: | Line 29: | ||
''Bugdays are the easiest entry point for people wanting to learn about Firefox bugs''. | ''Bugdays are the easiest entry point for people wanting to learn about Firefox bugs''. | ||
== Tips == | == Tips == | ||
| Line 47: | Line 39: | ||
;I don't have access to make changes to bugs. | ;I don't have access to make changes to bugs. | ||
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 on IRC in the #bugday, #testday, or #qa channel; one of the moderators or an experienced volunteer will assist you. | 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 on IRC in the #bugday, #testday, or #qa channel; one of the moderators or an experienced volunteer will assist you. | ||
== Staying Connected == | |||
Want to stay connected to testing between test events? Here are some tips for how you can stay connected to Mozilla QA and testing between the testdays and bugdays. | |||
* Watch our [http://quality.mozilla.org/ community site] | |||
* Join our [https://lists.mozilla.org/listinfo/dev-quality mailing list] | |||
* Join us on [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23qa irc.mozilla.org #qa] | |||
* Watch our [https://www.facebook.com/pages/Mozilla-QA/122167964300?ref=ts Facebook page] | |||
* Follow our [http://twitter.com/MozillaQA Twitter feed] | |||
== Organizing a Test Event == | == Organizing a Test Event == | ||