Overview

This is our general outline for IT Production Acceptance. More details are available at http://wiki.mozilla.org/Design/CreativeCollective.

Start of project

Name each of the following:

• Project sponsor: John Slater
• Main IT contact: TBD
• Main WebDev contact: Mike Morgan
• Main QA contact: Krupa Raj
• Main third party contact (if developed externally): Ryan Snyder, Craig Cook
• Final application owner/maintainer: John Slater

Overall goal of the project

• Build the Mozilla Creative Collective website to provide a central hub for our growing visual design community. This site will combine elements of other sites like DeviantArt, Threadless and Digg to help us build our design community and spread Firefox-themed art around the internet.

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

• image uploader
• backend database to host images
• admin panel to control content on the site
• user account creation/artist profiles
• ability for people to "like" designs they enjoy
• ability to hold regular "design challenges" (sort of like mini-contests) based on number of likes
• ability to tag designs or place them into different categories (wallpaper, posters, personas, etc)
• ability for users to sort designs by popularity, recency, category, etc
• ability for users to download the original working files of an image (ex. the PSD), do a remix, then upload it again with attribution to the original image
• Share This functionality so people can post favorite images to Digg, Facebook, etc
• ability for users to earn profile badges depending on their actions
• blog aggregator to display headlines from design-themed Mozilla blogs
• basic monitoring

Initial timeline (note: very rough)

• December 08 - finalize plans, begin sourcing design agencies
• January 09 - choose design agency, begin design process
• June 09 - begin development
• Late July 09 - begin QA
• Early August 09 - launch MCC Phase 1 (account creation, artist profiles, upload, gallery, badges?)
• Early September 09 - launch MCC Phase 2 (design challenges)

External dependencies

• Dev environment specs
• Does this project use any plugins or proprietary technology?
  • no

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