Project Management Committee
From AdempiereWiki
Contents |
[edit]
Proposal
This is to document and outline the proposed role and responsibilities of the ADempiere Project Management Committee. If adopted, the PMC will replace the present Commit Committee and should also oversee the admin role before this by the Council.
[edit]
Overview
The Project Management Committee (PMC) is comprised of experienced technical and functional resources within the bazaar. They work together to protect the stability and dynamic growth of the project. The PMC takes a largely tactical role in making sure the processes of development and contributions runs smoothly. Their foremost responsibility is to protect the stability of the trunk.
The PMC will include functional experts, implementors and also key developers of the project.
[edit]
Goals
- Protect the stability of the trunk
- Provide guidance and direction for functional and technical development
- Serve as liaison with end users from the community to promote further enhancements and testing
- Help the project operate effectively by providing leadership, removing obstacles, solving problems, and resolving conflicts
- Ensure that additional functionality is discussed and reviewed appropriately from both a functional and technical standpoint
[edit]
Responsibilities
- Manage the Roadmap
- Coordinate the Release schedule
- Manage the committer layer mentoring process
- Schedule and conduct a regular triage session on IRC as a channel for people to escalate and also to discuss their patch or feature request
- Define architecture for new developments
- Establish the development processes and infrastructure needed for the development team to be effective
- Produce “how to get involved” guidelines to help new potential contributors get started
- Facilitating code or other donations by individuals or companies
- Working with Committers to ensure in-bound contributions are made in accordance with the ADempiere IP Policy.
- Establish rules and guidelines for QA
- Manage guidelines for trunk access control
- Maintain branch rules
- encourage and breed more skilled developers
- Manage release policies for:
- New features under development
- high risk bug fixes
- high risk enhancements
- experimental stuff
- oversee merging proven stuff from branch into trunk
- Implement rules on the commit of new code into trunk. Some of the measurements might include:
- Unit testing
- Peer review
- Detail test case or scenario
- Contribution is Fully Documented
- reverting when something goes wrong
[edit]
Member Guidelines
- In the unlikely event that a member of the PMC becomes disruptive to the process or ceases to contribute for an extended period, the member may be removed by unanimous vote of remaining PMC members. PMC members may resign at any time by delivering notice of their resignation to the PMC Lead.
- The work of the PMC is shared by the PMC members. All PMC members are expected to contribute actively.
- Active participation in the user newsgroups and the appropriate developer mailing lists is a responsibility of all PMC members, and is critical to the success of the Project. PMC members are required to monitor the main Project mailing list, and the developer mailing lists
[edit]
Member Nominations
- Heng Sin Low (PMC-C +2) (Commit Chair +5)
- Carlos Ruiz (PMC-C +5)
- Susanne Schöningh-Calderon
- Victor Perez [1]
- Red1 [2]
- Joel Stangeland [3]
- Colin Rooney
- Fred Tsang
[edit]
Links
[edit]
