Websites/Mozilla.org/Get Involved Redesign: Difference between revisions
< Websites | Mozilla.org
Jump to navigation
Jump to search
No edit summary |
(→RACI) |
||
Line 44: | Line 44: | ||
* Accountable: Jess Davis | * Accountable: Jess Davis | ||
* Supportive: Web prod and creative teams for web work and Justin for CRM integration | * Supportive: Web prod and creative teams for web work and Justin for CRM integration | ||
* Consulted: Community builders team (Larissa) | * Consulted: Community builders team (Larissa, Sean) | ||
* Informed: Enabling Communities Integrated team & Engagement leads | * Informed: Enabling Communities Integrated team & Engagement leads | ||
Revision as of 17:08, 30 July 2014
Overview
The Get Involved page is the first page most people see when they want to become a contributor at Mozilla. It is important that this page be reflective of the people in our community. In order to do that we have opened up the design process to incorporate your feedback. Mozilla is not just one voice and the way we build our products, especially the Get Involved page, needs to reflect that.
We have involved the community on this project so far (e.g. meetings, blogs, etherpads, surveys, mail lists, MozCamps, etc.) and will continue to do so. Please check back on this wiki page for updates.
Prototype Testing
URLS
URLS
Info & Specs
URLS
Specs
Team
The primary and secondary contacts for each role of this project:
- Visual design:
- Copy:
- UX: Holly Habstritt
- Web dev:
- Product Manager: Jennifer Bertsch
- Project Manager: Mike Alexis
- Metrics: Gareth Cull
- QA - Raymond Etornam
- Security -
- Privacy -
- L10N - Pascal Chevrel, flod
RACI
- Responsible: Jen Bertsch
- Accountable: Jess Davis
- Supportive: Web prod and creative teams for web work and Justin for CRM integration
- Consulted: Community builders team (Larissa, Sean)
- Informed: Enabling Communities Integrated team & Engagement leads
L10N
Project Management
Schedule
Meetings
- Prototyping 2014-06-09
- Weekly status 2014-06-18
- Weekly status 2014-06-25
- feedback from stakeholder review July 2
- coding and content check-in 2014-07-14
- Weekly status 2014-07-16
- Weekly status 2014-07-24