Community Email Response Signup
Week of Apr 18 DONE
|Mon 4/18||Tues 4/19||Weds 4/20||Thurs 4/21||Fri 4/22||Sat 4/23||Sun 4/24|
Week of Apr 25
|Mon 4/25||Tues 4/26||Weds 4/27||Thurs 4/28||Fri 4/29||Sat 4/30||Sun 5/01|
- Totals for the week:
- Replies to inquiries (staff):
- Follow-up emails from users after we've responded original inquiry:
Week of May 02
|Mon 5/02||Tues 5/03||Weds 5/04||Thurs 5/05||Fri 5/06||Sat 5/07||Sun 5/08|
Week of May 09
|Mon 5/09||Tues 5/10||Weds 5/11||Thurs 5/12||Fri 5/13||Sat 5/14||Sun 5/15|
Week of May 23
|Mon 5/23||Tues 5/24||Weds 5/25||Thurs 5/26||Fri 5/27||Sat 5/28||Sun 5/29|
Week of May 30
|Mon 5/30||Tues 5/31||Weds 6/1||Thurs 6/2||Fri 6/3||Sat 6/4||Sun 6/5|
If the emails are very vague about interest, let's use the sample response and point them to our online self-serve resources, and if they reply back, then we can engage them at an individual level answering their specific questions:
We're happy to hear of your interest in Mozilla QA. Our team consists of five groups Web QA, Browser Technologies, Automation,Thunderbird, Services, and Desktop & Mobile Firefox.
You can see a quick overview of our teams in this page: http://quality.mozilla.org/
Depending your area or areas of interest I can help you explore some of the things you can help with.
We've just started a new development process that should allow us to release a few new features in the browser every six weeks, as opposed to tons of features every year or so. We are going to need lots of help tracking the status of new features, creating test plans for new features, creating test cases, testing these new features and making sure these are in good shape before they are deemed ready to go out in a specific release. You can see a list of features we are working on: https://wiki.mozilla.org/Features/Firefox
Many of those features currently have no QA ownership, so depending on your interest and how much time you can invest, you could for example take on one of those features to test it. Of course, there are many more things we do on a daily basis which you can engage in to become familiar with the project before you commit to "owning" a feature. These tasks include triaging bugs that have been filed by community members but which have not been confirmed, verifying new bugs fixes, finding regression ranges for identified issues and so on.
If you'd like you can also come to one of our weekly testdays, where we gather on irc://irc.mozilla.com/#testday and we go through some of the tasks I described above. It's a good opportunity to say hi and get to know the team and other volunteers and try on some new features or just hang out. These happen every Friday from 8am to 5pm Pacific time, and you can find details of upcoming testdays and other events on http://quality.mozilla.org/. In addition, you'll find our online forums on http://quality.mozilla.org/. I encourage you to sign up for the team forums you may be interested in. Once you register there, you can ask questions, get more in depth answers, read some interesting discussion and of course we are very interested in any feedback you have regarding Mozilla QA or Mozilla in general.
Thanks again for your interest in participating in the project.