Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 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.

Committer

...

Rights and Responsibilities

  • Committers have write access to the code repository.
  • Committers have an @apache.org email address.
  • Committers can make short-term decisions for the project, approving and merging pull requests.
  • Committer Vote is NOT considered binding thus the vote you cast do not have Veto on issues that require consensus.
  • Committer's can request changes on Pull Requests but it does not constitute Veto, PMC can agree to approve or reject requested changes.

PMC

...

Rights and Responsibilities

  • PMC makes the long-term decisions with regard to the project.
  • PMC members have write access to the code repository.
  • PMC members have @apache.org email address.
  • PMC has access to private@ email list
  • PMC has the right to vote for the community-related decisions, PMC Votes are binding.
  • PMC has the right to propose active users for committership.
  • PMC must vote on any formal release of the project's software product.

...