IT/Production Acceptance/CAD

Start of project

• Name each of the following:
  • Project sponsor: Marketing
  • Main IT contact: oremj
  • Main WebDev contact: aking
  • Main QA contact: TBD
  • Main third party contact (if developed externally): TBD -- we are considering using Social Applications API & will engage a design agency.
  • Final application owner/maintainer: Mary Colvig & Jane Finette
• Outline the following:
  • Overall goal of the project:
    • Community Action Day/Week will be our first foray into mission-based marketing and aims to differentiate our brand as the competitive landscape heats up.
    • It will aim to inspire our community to take action to improve the Web for others
    • Mozilla will host a platform that will connect volunteers with requests from organizations around the world
    • Our goal is to have over 125,000 volunteer hours
  • Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc)
    • Mozilla will need to create a site that aggregrates volunteer opportunities & local sites.
    • Auto-detect locale for up to 10 languages – remaining locales directed to EN/Global version.
    • Site to offer:
      • Call to action & public goal
      • Volunteer opportunity search by category & location
      • Volunteer opportunity submission
      • Volunteer pledge page name/location/email
      • “LizardFeeder” or similar functionality to share anecdotes & “stories” http://feeds.mozilla.com/
      • Certificate generator similar to Download Day
  • Initial timeline (Contingent on WebDev discussion)
    • CAD Date: in late June (tbd – contingent on WebDev)
    • CAD Launch: 30 days prior
    • Week of March 2: Issue Creative brief
    • Week of April 6: Final artwork
  • External dependencies
    • Local volunteer sites
    • Design agency
    • Copy writer
    • Summer timeframe (need to conduct CAD/W before July)
  • Dev environment specs
    • Stage + Prod env
    • PHP, MySQL, cron + python (lizard feeder)
  • Does this project use any plugins or proprietary technology?
    • No

Complete info on Community Take Action Week

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