{lozenge:title=Roles and Responsibilities|width=100%|icon=!Users 3 48x48.png!}
Apache projects define a set of roles with associated rights and responsibilities. These roles govern what tasks an individual may perform within the project.
{lozenge}UsersThe most important participants in the project are people who use our software. The majority of our developers start out as users and guide their development efforts from the user's perspective. Users contribute to the Apache projects by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apache community by helping other users on mailing lists and user support forums. ContributorsAll of the volunteers who are contributing time, code, documentation, or resources to the Apache Flex Project. A contributor that makes sustained, useful contributions to the project may be invited to become a Committer. CommittersThe project's Committers are responsible for the project's technical management. Committers have write access to the projects source code repositories. The responsibilities of an committer include: - Upholding and promoting the Apache Way
- Helping out users
- Reviewing code check ins
- Testing releases
- Maintaining the project's shared resources, including the repository, mailing lists and website
It is up to each individual committer exactly where they focus their attention and how how much time they spend on the project. Committer access is by invitation only and must be approved by Consensus of the PMC members. All Apache committers are required to have a signed Contributor License Agreement (CLA) on file with the Apache Software Foundation. Any committer can make a release candidate and call for a vote on making it an official release. The forms of contribution are not limited to only code. It can also include code reviews, helping out users on the mailing lists, documentation, testing, etc. A committer is considered inactive by their own declaration and can rejoin at any time. Committers can veto code check ins but committers votes are not binding on releases. A committer who makes a sustained contribution to the project may be invited to become a member of the PMC. Release ManagerA Release Manager (RM) is a committer who volunteers to produce a Release Candidate. The RM is responsible for building consensus around the content of the Release Candidate, in order to achieve a successful Product Release vote. Project Management CommitteeThe Project Management Committee (PMC) for Apache Flex was created by the Apache Board. In December 2012 Apache Flex became a top level project at Apache. The PMC is responsible to the board and the ASF for the management and oversight of the Apache Flex project. The responsibilities of the PMC include: - Upholding and promoting the Apache Way
- Deciding what is in a release
- Voting on releases
- Maintaining the project's shared resources, including the repository, mailing lists and website
- Speaking on behalf of the project
- Resolving any disputes (licensing or otherwise)
- Nominating new PMC members and committers
- Maintaining these guidelines of the project
Membership of the PMC is by invitation only and must be approved by Consensus of PMC members. A PMC member is considered inactive by their own declaration and they can rejoin at any time. ChairThe chair of the PMC is appointed by the ASF board. The chair is an office holder of the Apache Software Foundation (Vice President, Apache Flex) and has primary responsibility to the board for the management of the projects within the scope of the Apache Flex PMC. The chair reports to the board quarterly on developments within the project. The term of chair is for one one year or until they retire. After one year the chair can elect to stand for another year or a vote by the PMC be taken for a new chair. |