Websites/Processes/New Website
Jump to navigation
Jump to search
This lists all of the tasks necessary to get a new website started. After receiving a project from a Product Owner and agreeing to move forward, the Project Driver will execute all of the tasks on this list.
New Website Process
- Create a wiki page for this website, if not already available.
- Create a new Component in Bugzilla
- Define primary and secondary individuals for project roles.
- Create a Github repo for this project; grant access to team members.
- Create under mozilla organization
- Make public repo unless it's a sekrit project
- For private repos Give IT, l10n, and other teams access
- Create the Bugzilla Tickets for this project.
- Schedule the Kickoff Meeting.
- Schedule a weekly check-in meeting.
- Add site info to WhoWorksOnWhat
- Place HTTP Auth password (if available) on Stage Credentials page.
Bugzilla Tickets
Create the following bugs for a new website project:
- Create the Project Tracking Ticket.
- Create the Webtrends Ticket.
- Create the Goals and Measurements Ticket.
- Create the End of Life Ticket.
- Create the Security Ticket.
- Create the Privacy and Legal Ticket.
- Create the Stage Server Ticket.
- Create the Production Server Ticket.
Kickoff Meeting
Schedule a kickoff meeting to bring the people defined as having roles to help prepare this website for launch.
Text to attach to the meeting details for the kickoff meeting:
A new website project has been started. You have been identified as a core
member who will help bring this website to fruition. The details:
Project Title:
{Title}
Elevator Pitch:
{Text}
Estimated Launch Date:
{Date}
The wiki page describing this project:
{URL}
The tracking bug for this project:
{URL}
Project Tracking Ticket
This ticket is required for all new websites.
- Create a new Bugzilla ticket.
- Assign the bug to the Project Driver.
Title:
Project Tracking Ticket for {Website Name}.
Body:
This is the project tracking ticket for the launch of {Website Name}.
Project Title:
{Title}
Elevator Pitch:
{Text}
Estimated Launch Date:
{Date}
The wiki page describing this project:
{URL}
Webtrends Ticket
This ticket is required for all new websites.
- Create a new Bugzilla ticket.
- Make this bug a dependency for the tracking bug for this website's launch.
- Assign the bug to the Developer.
Title:
Add Webtrends Tracking for {Website Name}
Body:
Add Webtrends Tracking code to this website per the instructions in: https://intranet.mozilla.org/Webanalytics#Track_a_New_Domain
Goals and Measurements Ticket
This ticket is required for all new websites.
- Create a new Bugzilla ticket.
- Make this bug a dependency for the tracking bug for this website's launch.
- Assign the bug to the Product Owner.
Title:
Define Goals and Measurements for {Website Name}
Body:
Before this campaign launches, let's document how we will measure the campaign. Create a wiki page to document these numbers at: http://wiki.mozilla.org/Websites/Website_Name/Goals Please record: * What are the goals for this campaign? * How do we plan to measure this campaign? ** Which goals will be measured in Webtrends? ** Which goals need to have a stats area in the app's admin panel? *** Create tickets for stats area in admin panel as needed * How will we determine whether this campaign was a success? * When do we need to schedule a post-mortem for this project? Each of these goals should be measurable. Provide a start date and an end date by which to measure each goal. Each goal will need to have a documented way of how of that data will be tracked and measured. Starting numbers that will not be maintained externally (Twitter followers, Facebook fans, etc.) must be recorded before the site launches.
End of Life Ticket
This ticket is only required for websites that have a known end of life, such as a marketing campaign.
- Create a new Bugzilla ticket.
- Make this bug a dependency for the tracking bug for this website's launch.
- Assign the bug to the Product Owner.
Title:
Document End of Life Plan for {Website Name}
Body:
Before this campaign launches, let's document the end of life plans.
Create a wiki page to document these numbers at:
http://wiki.mozilla.org/Websites/{Website_Name}/End_Of_Life
Please record:
* When will the campaign end?
* When is the estimated date that we will retire this website?
* What are the privacy concerns for this website?
* Identify where are we collecting and storing:
** Name
** Email address
** IP Address
Privacy and Legal Ticket
This ticket is required for all new websites.
- Create a new Bugzilla ticket.
- Make this bug a dependency for the tracking bug for this website's launch.
- Assign this bug to the Legal contact.
Title:
Perform Privacy and Legal Review for {Website Name}.
Body:
This is a placeholder for the privacy and legal review of {Website Name}.
Current site documentation is available at:
{Wiki Page}
Security Ticket
This ticket is required for all new websites.
- Create a new Security:%20Web%20Security Bugzilla ticket.
- Make this bug a dependency for the tracking bug for this website's launch.
- Assign this bug to the Security contact.
Title:
Perform Security Review for {Website Name}.
Body:
This is a placeholder for the security review of {Website Name}.
Current site documentation is available at:
{Wiki Page}
Stage Server Ticket
This ticket is required for all new websites.
- Create a new Bugzilla ticket.
- Make this bug a dependency for the tracking bug for this website's launch.
- Do not assign this bug to anyone.
- Copy the following text into the ticket and update accordingly.
Title:
Create Stage Instance for {Website Name}.
Body:
(This is a placeholder to create a stage instance for this project.)
Please create a stage instance for {Website Name}.
== Date Needed By ==
* 2011/01/01
== Language ==
* Language: Python
* Framework: Django
* Base: Playdoh
== URL ==
* Production URL: {URL}
* Stage URL: {URL}
== HTTP Auth ==
* HTTP Auth is required to access this site.
* Please record username / password in this ticket.
== HTTP / HTTPS ==
* Both HTTP and HTTPS are required this site.
== Code Repository ==
* Github Repo: {URL}
* Github Vendor Repo: {URL}
** Setup Github to auto-update every 5 minutes.
* SVN Localization Repo: {URL}
** Setup SVN to auto-update every 15 minutes.
== Database ==
* This site requires a MySQL database.
== Other Services ==
* Note Any other dependencies and to look in settings_local.py-dist.
** Responsys
** Memcache
== Settings ==
* cp settings_local.py-dist settings_local.py
* Update settings values accordingly.
* Set DEBUG to False in settings_local.py.
== Cron ==
* bin/update_site.py -e stage
** frequency?
== Tracebacks ==
* Please configure Django tracebacks to be sent to:
** {email1}, {email2}, {email3}
Production Server Ticket
This ticket is required for all new websites.
- Create a new Bugzilla ticket.
- Make this bug a dependency for the tracking bug for this website's launch.
- Do not assign this bug to anyone.
- Copy the following text into the ticket and update accordingly.
Title:
Create Production Instance for {Website Name}
Body:
(This is a placeholder to create a production instance for this project.)
Please create a production instance for {Website Name}.
== Date Needed By ==
* 2011/01/01
== Language ==
* Language: Python
* Framework: Django
== URL ==
* Production URL: {URL}
== HTTP / HTTPS ==
* Both HTTP and HTTPS are required this site.
== VPN ==
* The /admin section should be accessible only via SSL VPN.
== Code Repository ==
* Github Repo: {URL}
* Github Vendor Repo: {URL}
* SVN Localization Repo: {URL}
== Database ==
* This site requires a MySQL database.
== Settings ==
* cp settings_local.py-dist settings_local.py
* Update settings values accordingly.
* Set DEBUG to False in settings_local.py.
== Cron ==
* bin/update_site.py -e prod
** frequency?
== Tracebacks ==
* Please configure Django tracebacks to be sent to:
** {email1}, {email2}, {email3}