IT/Production Acceptance/QMO2

Start of project

Name each of the following:

• Project sponsor: Jay Patel
• Main IT contact: Oremj
• Main WebDev contact: Morgamic
• Main QA contact: Stephend
• Main third party contact (if developed externally): TBD
• Final application owner/maintainer: Jay Patel

Overall goal of the project

• Improve Mozilla QA team and community collaboration; centralize all QA related documentation and make it easy to keep updated; organize QA related activities and encourage more participation from the Mozilla community (betatesters, bug triage, data analysis, etc)

Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc):

• Access to SVN needed for Jay and any potential developers working on project
  • Will https://bugzilla.mozilla.org/show_bug.cgi?id=431872 give me access to QMO2?
• Staging server required
  • Bug files https://bugzilla.mozilla.org/show_bug.cgi?id=432498

Initial timeline

• Goal is to have new QMO site live in "beta" form by July 2008.
• Rough schedule:
  • Staging server of Drupal 5 (5/12)
  • [P1] Drupal views and module integration (5/19)
  • Content creation and site configuration (Ongoing)
  • [P1] Theme implementation (6/6)
    • Live templates at http://people.mozilla.com/~jpatel/qmo/templates/
    • Download files at http://people.mozilla.com/~jpatel/qmo/templates/templates.zip
  • [P2] Custom module development and projects/events improvements (TBD)
    • RFP has more info: http://people.mozilla.com/~jpatel/qmo/QMO_Drupal_Dev.pdf

External dependencies

• Might outsource:
  • Drupal theme development
  • Custom module/feature development

Dev environment specs

• Same as SFX work with Raincity

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