IT/Production Acceptance/CMT
Start of project
- Name each of the following:
- Paul Kim / Jane Finette
- Main IT contact
- Main WebDev contact
- Main QA contact
- Main third party contact (if developed externally) n/a
- Final application owner/maintainer [Mary, is this a business owner, or an IT owner?]
- Outline the following:
- Overall goal of the project
The Community Marketing Toolkit is a central destination where Mozilla can effectively communicate with existing and prospective community members who have an interest in marketing Mozilla. The marketing communities around Mozilla will be one of the areas where both technical and non-technical members can join, and contribute to the Mozilla project. To be successful the community needs to be a welcoming place, and navigable, but also free to grow organically. The CMT will be accessible from community.mozilla.org and Sfx. The CMT will contain verbiage and links to all resources which the Mozilla marketing team considers relevant and appropriate. However, we shall be continually asking our community for advice on what materials and guidelines would be helpful. While it is not the intent that Mozilla should control the community's activity, it will control which resources and forums it promotes to the community for use. Furthermore, there are a number of resources which are created or maintained by MoCo or MoFo which require version control (such as formal messaging documents for products, or blog banners promoting specifc marketing campaigns or products). The Toolkit can also become the vehicle for managing version control of all such materials, by being a record of the public materials which MoCo or MoFo owns.
- Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc)
The CMT should have the same criteria in place as other pages on http://contribute.mozilla.org/Mozilla_Community
- Initial timeline
To go live in Q1
- External dependencies
None identified
- Dev environment specs
[Mary, any idea on what is standard here]
- Does this project use any plugins or proprietary technology?
No
Staging Signoff
In order to get an app into staging, the following should be completed:
- Code committed to Mozilla source control and tagged
- Initial architecture review by IT and WebDev
- Plugin/tech review by Evangelism
- Site must be password protected
- Review timeline to go live
- Review any production requirements so IT can order any new hardware needed
Production Signoff/Launch
- Final WebDev signoff
- Final IT signoff
- Final QA signoff
- Operations documents filled for support & any training complete
- Monitors in place