IT/Production Acceptance/CommunityStore: Difference between revisions

 
(11 intermediate revisions by 3 users not shown)
Line 3: Line 3:
Name each of the following:
Name each of the following:
* Project sponsor: Tara
* Project sponsor: Tara
* Main IT contact: TBD
* Main IT contact: Aravind
* Main WebDev contact: M.Morgan
* Main WebDev contact: Ryan Doherty
* Main QA contact: TBD
* Main QA contact: S.Donner (TBD)
* Main third party contact: Tracy Clements (Zazzle), tracy.clements@zazzle.com
* Main third party contact: Tracy Clements (Zazzle), tracy.clements@zazzle.com
* Final application owner/maintainer: Tara
* Final application owner/maintainer: Tara
Line 14: Line 14:
* Empower global community to design, create, and buy customizable merchandise.  
* Empower global community to design, create, and buy customizable merchandise.  
* Strengthen and spread Mozilla brand through community generated products.
* Strengthen and spread Mozilla brand through community generated products.
* Introduce Firefox to new users
* Break inventory and fulfillment limitations with current Store operations.
* Break inventory and fulfillment limitations with current Store operations.
* Introduce Firefox to new users
* Feature as main SFx project (www.spreadfirefox.com/CommunityStore
* Feature as main SFx project (www.spreadfirefox.com/CommunityStore


Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc):
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:=
=Development:=
* Target launch date is 11/19/08.
* Target launch date is 12/2/08.
* Create Store Gallery, Website and Upload Tool utilizing Zazzle's API.
* Create Store Gallery, Website and Upload Tool utilizing Zazzle's API.
** Mockups, flow charts, and detailed breakdown of project provided.


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


External dependencies
External dependencies
Line 35: Line 41:
Dev environment specs
Dev environment specs
* TBD
* 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
3,035

edits