QA/Community/QMO Design/Planning: Difference between revisions
Line 2: | Line 2: | ||
Getting QMO off the ground is going to require a lot of collaboration between the QA and marketing teams, as well as the community. In trying to stay in sync with marketing's branding strategy and the SpreadFirefox launch, we will have a couple of alpha cycles to give a few folks a chance to use the site and give feedback, and will make an official announcement when everything is in place (site features + branding). | Getting QMO off the ground is going to require a lot of collaboration between the QA and marketing teams, as well as the community. In trying to stay in sync with marketing's branding strategy and the SpreadFirefox launch, we will have a couple of alpha cycles to give a few folks a chance to use the site and give feedback, and will make an official announcement when everything is in place (site features + branding). | ||
We hope to be able to open the site up for public use before beta, in order to give existing members an opportunity to get involved early...and | We hope to be able to open the site up for public use before beta, in order to give existing members an opportunity to get involved early...and to accelerate the QA team's transition from the old blog to the new site. | ||
== Roadmap == | == Roadmap == |
Revision as of 21:47, 9 April 2007
Overview
Getting QMO off the ground is going to require a lot of collaboration between the QA and marketing teams, as well as the community. In trying to stay in sync with marketing's branding strategy and the SpreadFirefox launch, we will have a couple of alpha cycles to give a few folks a chance to use the site and give feedback, and will make an official announcement when everything is in place (site features + branding).
We hope to be able to open the site up for public use before beta, in order to give existing members an opportunity to get involved early...and to accelerate the QA team's transition from the old blog to the new site.
Roadmap
Prep (April 9 - April 27)
- Branding cycle (john slater, jay, design team)
- Website configuration (jay)
Alpha 1 (April 30) - Mozilla QA team and select community members
- QA team feedback and content generation(April 30 - May 4)
- Events and Calendar (marcia, tracy)
- Stories and Blog (juanb, tony)
- General site layout (sam)
- Website updates and testing (May 7 - 11)
- Review new docs and events (jay)
- Talk to IT about performance/usage numbers
Alpha 2 (May 14) - QA community evaluation and feedback
- Branding refresh (jay, design team)
- Public events and calendar
- Start forum topics
Beta (TBD) - Official QMO release/live
- Migration to production cluster
- Marketing push and promotion
- UE review and feedback
- Community usage analysis and feedback
Tasks
Alpha 1
- Branding
- Branding brainstorming
- Creative Brief
- Logo/Design mockups
- Pick logo and design
- Website development
- Profile system and user gallery
- Events Calendar
- Stories/Blog setup
- Forums setup
- Book/Docs setup
Alpha 2
- Website development
- Integrate Drupal theme + logo + icons from design team
- Badge system
- Performance/module tweaks
- Content development
- Bug and Test Day documentation
- Litmus tutorial
- Bug writing guidelines
- "Coming soon..." for Groups, Projects, Analysis, and Automation pages
Beta
- TBD