QA/Firefox3/Strategy: Difference between revisions

Jump to navigation Jump to search
Line 292: Line 292:


== Community Involvement ==
== Community Involvement ==
The goal is to actively involve more community members in testing Minefield, Gran Paradiso, and ultimately Firefox 3 as it moves into beta and to final release.


This goal is to actively involve more community members to assist with testing the firefox project in different aspects of the area.  There are many active participants in the community that are enthusiastic with Firefox and want to give back their time and effort to help test this project.  However, this involves heavy coordination, planning of work areas, and enforcing the correct process and procedures constantly produces challengesThere is a seperate community team in QA that is currently working on incorporating a new strategy to promote more community involvement.   
There are many active participants in the community that are enthusiastic about Firefox and want to contribute to our quality assurance efforts.  However, getting them involved and maximizing the value of their time and effort requires a lot of coordination, planning, and enforcing of the correct processes and procedures.  Since such activities create constant challenges for our QA team,  we are working on a new strategy to promote more community involvement.   


Current avenues of community involvement includes:
Current avenues of community involvement include:
* friday testdays - a full day dedicated to testing firefox and thunderbird.  Activities include triage unconfirmed bugs, running tests in litmus, QnA, testing the trunk builds, and many other firefox-related topics
 
* tuesday bugdays - a full day dedicated to triaging bugs unconfirmed and confirmed.  
* Friday Test Days
* QMO - [quality.mozilla.org quality.mozilla.org]: website to promote news and articles on mozilla QA.
** increased the frequency of these events to allow people to show up each week to try out new features and help us run through test cases.  Activities include triaging unconfirmed bugs, running tests in Litmus with trunk builds (and alphas/betas), Q&A/Help sessions.  We will be focusing on a new Firefox 3 feature/component every week.
* Campus evangelism - [https://www.mozilla.com/en-US/university/ Targeting the university students] with an exposure to testing open source and particularly firefox
 
* Others?
* Tuesday Bug Days
** a full day each week dedicated to working with various bug lists in Bugzilla.  Activities will rotate between unconfirmed bug triage, bug verifications, test case writing, and reproducing crash bugs.
 
* QMO - [quality.mozilla.org quality.mozilla.org]
** Using the website to promote news and articles on what the Mozilla QA team is working on
** Provide events and forums for the community to get involved.
** Create closer relationships with regular contributors and help them become leaders for our events and projects.
** Promote the QA Extension to get more people connected to our tools and processes.
** Update/migrate outdated QA pages on mozilla.org and showcase them on QMO
* Campus Evangelism - [https://www.mozilla.com/en-US/university/ Targeting the university students]  
** Leverage the Campus Reps program to reach out to students and professors at schools.
** Reach out to folks interested in open source and help them discover Mozilla project and get involved in Firefox development and testing.
 
* Better "Beta" product pages and programs
** Update Minefield and Gran Paradiso pages to direct folks to QMO and other useful channels for getting involved and providing feedback.
** Coordinate community testing with marketing/pr plans for Firefox 3 Beta release
1,926

edits

Navigation menu