SeaMonkey:Project Organization
 | ||
| Resources | ||
|---|---|---|
| SeaMonkey Homepage | ||
| FAQ / Help | ||
| Goals | ||
| Organization | ||
| QA | ||
| Supporters | ||
| Add-ons | ||
| Localization | ||
| Reasons | ||
| Branding | ||
| Release History | ||
| Tasks & Projects | ||
| ||
| Discussion | ||
| Suiterunner |
This page describes the structure of the SeaMonkey project. For now, only drivers are listed, but it will be updated with the structure for the rest of the project as soon as we have figured it out.
SeaMonkey Council
The SeaMonkey Council is the team responsible for project and release management, and can be contacted via the email address seamonkey-council@mozilla.org. Its responsibilities include release management (deciding when to cut releases and what code is included in a release; the release engineer of the Council is responsible for actually doing the release) and being the final instance for decisions about features when developers disagree. The SeaMonkey Council also decides on legal issues concerning the SeaMonkey project, in conjunction with the Mozilla Foundation, which provides legal backing for the project.
Project Area Owners and Peers
The SeaMonkey Project is divided into several areas, which are listed on our project areas list. Each of those areas should have an owner and possibly several peers (people who know the code well enough to give reviews there), who together care about that area. The sum of those areas build a strong group of developers, who can move the SeaMonkey project forward.
Community
Additionally, there's a vibrant community surrounding those developers, see the SeaMonkey community page for how to get in touch with those people.
