Websites/Processes/Terminology

This document contains a list of roles and process terminology used by the web development groups throughout a website's development process.

Roles

A primary person and secondary person must be identified for each of the following roles before a project commences:

• Product owner - The person who is the decider of all business decisions regarding a website, and is responsible the overall success of the site.

• Project driver - A technically-focused project manager from the Web Productions team.

• Steward - A web developer from the Mozilla web dev team who interacts with external development groups to ensure submitted code is appropriate, clean and secure. Project driver may also fill the Steward role.

• Web Developer - The team of developers responsible for writing the code that will run the website.

• Graphic Designer - A person in charge of site branding, graphics and possibly mockups of the website.

• Markup Designer - A person who writes the HTML, CSS and Javascript for a website. This person may be involved in UX decisions and creating mockups of the website.

• IT - The team responsible for maintaining the servers upon which the website is located, for both the stage and production instances.

• QA - The quality assurance team, which executes manual tests and creates automated tests across the website both after it is staged and after it is pushed to production.

• Security - The infrasec team, which performs a security check over the website after QA has finished executing their initial battery of tests on the site.

• Legal - The team that examines all of the privacy and legal concerns surrounding a website.

• L10N - A person responsible for leading the localization and translation efforts for a website, including coordinating volunteer efforts.

Terminology

• Channel - The IRC channel in which the project communication will take place on irc.mozilla.org. e.g. #spark, #markup

• Code freeze - The point at which code can no longer be pushed to the primary Mozilla code repository. The project driver will notify the team when the repository is once again writeable.

• Code review - The process of examining the code pushed to the code repository. A Steward will be responsible for the code review, and will communicate code approval, or code disapproval with constructive comments on how to fix the code.

• Product owner - The person who is the champion for bringing a new website online, or managing the encompassing tasks of an existing website. This person is the final decider for a website.

• Project driver - The project manager for the development of a website; typically a person who is experienced in all aspects of launching a website.

• String freeze - The point at which text on the website will cease to be added to or changed. The localization team will commence translating text at this time.

• Steward - A web developer who is responsible for interacting with external developers to help them write code appropriate for Mozilla environments.