...
The Apache MXNet PPMC makes someone a committer via nomination, discussion, and then Consensus Approval: i.e. at least 3 +1 votes and no vetoes. Any veto must be accompanied by reasoning and the vetoer must be prepared to defend it. Other PPMC members can attempt to encourage them to change their minds. PPMC members should strive to nominate committers from outside their own organization.
We use data from as many sources as possible to inform our reasoning. Here are some examples:
...
In addition to the contributions as committer they participated at a community level, not just a technical one. In general, a contributor considered as project committer will be considered for PPMC membership at the same time. In the exception, that a nominee for committer has only shown technical contributions, but no active engagement with the broader developer or user community the PPMC might decide to delay consideration for PPMC membership. In general, a PPMC members should strive to identify nominee for PPMC will be evaluated based on the merit and contribution, independent of his affiliation. However, as an exception to improve the affiliation diversity within the PPMC, the PPMC might apply a higher bar for nominees affiliated with Amazon AWS.membership outside of their own organization.
The Apache MXNet PPMC makes someone a PPMC member via nomination, discussion, and then Consensus Approval: i.e. at least 3 +1 votes and no vetoes. Any Any veto must be accompanied by reasoning and the vetoer must be prepared to defend it. Other PPMC member can attempt to encourage them to change their minds. The PPMC decides on an individual basis to have a single vote for committer and PPMC membership or to hold to separate votes.