Cairngorm Project Roles

This page describes the various roles related to the Cairngorm project.

Management Committee

The Cairngorm management committee that takes on the following responsibilities:

• Coordinates planning and scheduling of major and minor releases
• Manages the decision process for what enhancements and bug fixes are accepted
• Provides community oversight to ensure guiding principles are being followed

The management committee is currently composed of Adobe employees. As the Cairngorm community matures the committee may invite non-Adobe members to become more active in the management of the project.

Contributor

A contributor is someone who is playing an active role in the Cairngorm community. Contributors participate in a number of ways including:

• Being active in forums and email lists
• Filing bugs and feature requests on the public bug system
• Helping moderate the bug system by noticing duplicates, adding clarifications, contributing workarounds
• Contributing bug fixes and small enhancements by submitting patches to the public bug system

Anyone is welcome to be a contributor. If you would like to submit patches through the bug system you should ensure that you are familiar with Subversion, JIRA, the coding guidelines, and all other information that can be found on the project website.

Partial-Committers

A partial-committer is a contributor who has been given some additional privileges, for example:

• The ability to check in to certain areas of the source control system (e.g., sample applications)
• The ability to modify the project web site

Partial-committers also play an important role in the framework, especially those who know the framework documentation well and can contribute to correcting documentation errors, or those who have some excellent sample applications to contribute. See the Developer Documentation page for more details.

To be considered as a partial-committer you should contact the Management Committee.

Committers

A committer is someone who is entitled to check code or documentation into any area of the source control system. Being a committer requires certain attributes including:

• Knowing the framework well, and not just from a technical/coding perspective
• Being active in forums and email lists
• Having a strong track record of bug fixes and workarounds
• Being able to work independently
• And most importantly, possessing good judgment when it comes to a solution, being able to code it, and making sure it benefits the community

Committers for the Cairngorm are primarily members of Adobe Consulting. On occasion, the Management Committee will determine that a particular contributor would provide great value in becoming a committer and will invite that contributor to upgrade their status.