Note: this is a draft written by individual(s) and no way represents the guidance or stand of the CloudStack PMC.

Not always a prerequisite but generally a committer becomes a PMC member (see on how to become a committer: DRAFT).

Other references about PMC membership and CloudStack project bylaws and other links and docs:

Becoming a PMC member, it largely a support building exercise where other PMC members can review anybody in the community, discuss/propose, vote and invite them to become a PMC member.

Some criteria could be following: 

  • Demonstrated commitment and built trust over sustained period of time.
  • Be visible in the community as an ambassador of the project.
  • Doing work around technical or non-technical activities, but most importantly be involved in decision making that are in support and favour of the community.
  • Participating and supporting project governance related activities, release management or other technical/non-technical activities such as documentation/blog/website work, support/participation in marketing, events and conferences.

Bottomline: it's really up to the PMC members to maintain a healthy and active PMCs and committers base in the project by regularly reviewing, proposing, voting and inviting new PMC members and committers. Any community member can propose a candidate on the private@ mailing list. It is then up to the PMC to discuss those candidates, build support and vote on the new candidate.


Misc links and references:

  • No labels