Websites/Processes: Difference between revisions
< Websites
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
= Instantiation = | = Instantiation = | ||
The Project Manager will assign a Web | The Project Manager will assign a Web Project Engineer and drive the instantiation phase. | ||
* Checklists for Instantiating Projects: | * Checklists for Instantiating Projects: | ||
Revision as of 21:25, 28 April 2011
The following processes are used to cover every aspect of a website's lifespan from beginning to end.
Overview
- Temp Notes - http://etherpad.mozilla.org:9000/webdev-processes
- Website roles and terminology.
- Running meetings.
Ideation
The Product Owner will drive the Ideation phase.
- Submit your Project to the Web Dev project manager.
- Create a wiki page for this site based on the Website Template.
- If this project is for an existing website, use the Existing Website Template.
- Meet requirements for each group to begin Project Instantiation (forthcoming).
Instantiation
The Project Manager will assign a Web Project Engineer and drive the instantiation phase.
- Checklists for Instantiating Projects:
- Kickoff Meeting Agenda
Bringing New Developers on Board
If web developers are new to Mozilla projects, please use the following:
- Email boiler plate for New Contractors
- Email boiler plate for New Employees
- Getting started with Bugzilla
Development
The Web Steward will drive the development phase.
- Weekly Meeting Agenda
- Code Best Practices Guidelines
- Code Review
- Bugzilla Workflow
- QA Process
- Security Guidelines
- Accessibility Review
- SEO Review
Release
The Web Steward will drive each release phase.
End of Life
The Project Manager will assign a Web Steward to drive the End of Life phase.
At the end of its lifespan, a website may be archived, but the preference is to retire the site.
- Website / Campaign Retrospective
- Retire a Page or part of a Website
- Retire a Website
- Archive a Website