Skip to content

Latest commit

 

History

History
41 lines (34 loc) · 3.01 KB

GOVERNANCE.md

File metadata and controls

41 lines (34 loc) · 3.01 KB
Raw

Argo Governance

This document outlines the governance for the overall Argo Project and the four sub-projects contained within.

Roles and Membership

Roles are described in the Community Membership document. For the purpose of governance, reviewers, approvers and leads are considered maintainers. The list of current maintainers and their project and organizational affiliations are maintained in the MAINTAINERS file.

Conflict Resolution and Voting

The vast majority of issues are resolved by consensus. If consensus cannot be reached, issues are resolved by voting. All decisions should be recorded publicly in GitHub or meeting notes and recordings.

  • A vote requires a simple majority to pass.
  • A vote requires participation by a quorum of at least 30% of maintainers.
  • Voting is done by adding +1/-1 on the PR submitted for the issue.
  • Each maintainer gets a binding vote. Non-binding votes from the community are encouraged.
  • No organization should be allowed more than 40% of eligible votes. If any organization has more than 40% of the maintainers, the organization will have to decide which maintainers will cast votes.
  • Voting should be open for one week.

Changes to governance

Any changes to governance require a vote by the maintainers.

  • A vote requires a 2/3 supermajority to pass.
  • A vote requires participation by a quorum of at least 30% of maintainers.
  • Voting is done by adding +1/-1 on the PR submitted for the issue.
  • Each maintainer gets a binding vote. Non-binding votes from the community are encouraged.
  • No organization should be allowed more than 40% of eligible votes. If any organization has more than 40% of the maintainers, the organization will have to decide which maintainers will cast votes.
  • Voting should be open for two weeks.

Community Support and Inclusion

The project strives for full transparency and community inclusion in all aspects of the governance of the project. All decisions regarding the project should be public, either in the official GitHub repositories or in the public meetings below. The maintainers are encouraged to run three recurring public meetings to foster transparency and community participation in the project.

Maintainers meeting

This meeting is for the maintainers to discuss topics that relate to governance, membership and the future direction of the project.

Contributors meeting

This is a meeting for maintainers mainly to discuss and resolve technical issues. Future milestones and roadmaps will also be covered in this meeting.

Community Meeting

This meeting is focused on the community and end users and will include project updates, user presentation and other items of interest to the user community.

Meeting Calendar