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:

• Project driver
• Product owner (should be different from Project driver)
• Steward
• Designer
• Developers
• IT
• QA
• Security
• Legal
• Localization (L10N)

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.