The Project Management Committee (PMC) was formed by the ASF Board in October 2003, and is responsible to the ASF Board for oversight of the project. The list of current members can be found in our Project Credits.
Roles
The PMC is responsible for the strategic direction
and success of the Portals Project. This governing body is expected to
ensure the project's welfare and guide its overall direction. The PMC
may not necessarily participate in the day-to-day coding but is
involved in the overall development plans, the alleviation of any
bottlenecks, the resolution of conflicts, and the overall technical
success of the project.
The PMC is answerable to the ASF Board with its Chairman serving as primary liaison.
Board reports
Quarterly, the PMC is responsible for sending a report to the ASF Board.
Membership
PMC members may resign at any time. The Chairman
may resign as Chairman at any time without resigning membership to the
PMC. The Chairman or any member may be removed from the PMC by a 3/4
vote of the PMC.
Committers are nominated for the PMC by an existing PMC member and a vote then follows.
Voting
Binary PMC voting is a majority-approval variant, with a minimum of 3 +1s
required and at least 3/4 of the votes being +1. This voting style is used
for anything with a yes/no, two-option choice; such as PMC member voting
or changes to this document.
Non-binary voting currently relies on community agreement; such as voting on the recommendation of a chairman to the board.
A week is deemed a fair length for a vote.
Subprojects of Portals use other voting variants, described on the Decisions page.
Creation of subprojects
The Apache Incubator is the primary source of new subprojects for Portals,
though the PMC may choose to waive this if the Incubator PMC is agreeable.
A common example of this is when an existing subproject contains a component
which wishes to become a full subproject. In such cases, there is unlikely
to be a need for incubation.