IT/Production Acceptance/Headrush

Start of project

• Name each of the following:
  • Project sponsor - Mike Morgan
  • Main IT contact - TBD
  • Main WebDev contact - Mike Morgan, Alex Buchanan (abuchanan@mozilla.com)
  • Main QA contact - TBD
  • Main third party contact (if developed externally) - N/A
  • Final application owner/maintainer - TBD
• Outline the following:
  • Overall goal of the project - "to create an online community with the purpose of generating, evaluating, improving, and harvesting ideas." Basically we want to create an simple, easy way for the community to contribute their ideas.
  • Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc)
    • before going to production:
      • Project owner
      • IT/QA contacts
      • An official name and URL (name.mozilla.org)
      • Process for evaluating popular ideas
      • Performance/scalability testing
  • Initial timeline
    • In company alpha stage site, to generate thoughts/feedback, week of 4/28-5/2/08
    • Production beta by end of Q2, 2008 ?
  • External dependencies
  • Dev environment specs
    • PHP (5.x is preferable, but Drupal works with 4)
    • MySQL (no specific version)
    • shared disk space for Drupal uploads directory
    • web server

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
• 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