IT/Production Acceptance/CommunityStore

From MozillaWiki
Jump to: navigation, search

Start of project

Name each of the following:

  • Project sponsor: Tara
  • Main IT contact: Aravind
  • Main WebDev contact: Ryan Doherty
  • Main QA contact: S.Donner (TBD)
  • Main third party contact: Tracy Clements (Zazzle), tracy.clements@zazzle.com
  • Final application owner/maintainer: Tara

Overall goal of the project:

  • Continue to grow and establish the design community through a new channel of engagement.
  • Open-Source the T-shirt design process and inspire new community members to get involved.
  • Empower global community to design, create, and buy customizable merchandise.
  • Strengthen and spread Mozilla brand through community generated products.
  • Introduce Firefox to new users
  • Break inventory and fulfillment limitations with current Store operations.
  • Feature as main SFx project (www.spreadfirefox.com/CommunityStore

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

  • Domain name "communitystore.mozilla.org" (bug 460688)
  • Zazzle contract agreement -- done (bug 438468)
  • Terms of use click agreement -- pending cbrady (inactive bug 449631)

Development:

  • Target launch date is 12/2/08.
  • Create Store Gallery, Website and Upload Tool utilizing Zazzle's API.
    • Mockups, flow charts, and detailed breakdown of project provided.

Initial timeline

  • Development week of 10/19 - 11/10 (TBD)
    • Development of Upload tool already started
    • Design files and feedback provided on 10/17.
  • Development complete on xx/xx (TBD)
  • Target Launch on 12/2

External dependencies

  • TBD

Dev environment specs

  • TBD

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