Skip to main content

Governance

This document describes the rules and governance of the project. It is meant to be followed by all the developers of the project and the Parca community. It is a slightly modified version of the Prometheus Governance Common terminology used in this governance document are listed below:

  • Team members: Any members of the private parca-team Google group.

  • Maintainers: Maintainers lead an individual project or parts thereof (MAINTAINERS.md).

  • Projects: A single repository in the Parca GitHub organization is referred to as a project.

  • The Parca project: The sum of all activities performed under this governance, concerning one or more repositories or the community.

Values​

The Parca developers and community are expected to follow the values defined in the CNCF charter, including the CNCF Code of Conduct. Furthermore, the Parca community strives for kindness, giving feedback effectively, and building a welcoming environment. The Parca developers generally decide by consensus and only resort to conflict resolution by a majority vote if consensus cannot be reached.

Projects​

Each project must have a MAINTAINERS.md file with at least one maintainer. Where a project has a release process, access and documentation should be such that more than one person can perform a release. Releases should be announced on the parca-users mailing list. Any new projects should be first proposed on the developers mailing list following the voting procedures listed below. When a project is no longer relevant, it should be moved to the parca-junkyard GitHub organization.

Decision making​

Team members​

Team member status may be given to those who have made ongoing contributions to the Parca project for at least 3 months. This is usually in the form of code improvements and/or notable work on documentation, but organizing events or user support could also be taken into account.

New members may be proposed by any existing member by email to parca-team. It is highly desirable to reach consensus about acceptance of a new member. However, the proposal is ultimately voted on by a formal supermajority vote.

If the new member proposal is accepted, the proposed team member should be contacted privately via email to confirm or deny their acceptance of team membership. This email will also be CC'd to parca-team for record-keeping purposes.

If they choose to accept, the on-boarding procedure is followed.

Team members may retire at any time by emailing the team.

Team members can be removed by supermajority vote on the team mailing list. For this vote, the member in question is not eligible to vote and does not count towards the quorum. Any removal vote can cover only one single person.

Upon death of a member, they leave the team automatically.

In case a member leaves, the off-boarding procedure is applied.

The current team members are:

Please note that Parca had received significant contributions from a number of unlisted individuals before this governance document, and thus formal team membership, was created.

Maintainers​

Maintainers lead one or more project(s) or parts thereof and serve as a point of conflict resolution amongst the contributors to this project. Ideally, maintainers are also team members, but exceptions are possible for suitable maintainers that, for whatever reason, are not yet team members.

Changes in maintainership have to be announced on the developers mailing list. They are decided by lazy consensus and formalized by changing the MAINTAINERS.md file of the respective repository.

Maintainers are granted commit rights to all projects in the GitHub organization.

A maintainer or committer may resign by notifying the team mailing list. A maintainer with no project activity for a year is considered to have resigned. Maintainers that wish to resign are encouraged to propose another team member to take over the project.

A project may have multiple maintainers, as long as the responsibilities are clearly agreed upon between them. This includes coordinating who handles which issues and pull requests.

Emeritus Maintainers​

  • Javier Honduvilla Coto
  • Vaishali Thakkar

Technical decisions​

Technical decisions that only affect a single project are made informally by the maintainer of this project, and lazy consensus is assumed. Technical decisions that span multiple parts of the Parca project should be discussed and made on the Parca developer mailing list.

Decisions are usually made by lazy consensus. If no consensus can be reached, the matter may be resolved by majority vote.

Governance changes​

Material changes to this document are discussed publicly on the developer mailing list. Any change requires a supermajority in favor. Editorial changes may be made by lazy consensus unless challenged.

Editorial changes​

Editorial changes are changes which fix spelling or grammar, update work affiliation, or similar; they update style or reflect an outside and obvious reality. They do not change the intention or meaning of anything in this document. They must be made via PR and accepted via lazy consensus.

Other matters​

Any matter that needs a decision, including but not limited to financial matters, may be called to a vote by any member if they deem it necessary. For financial, private, or personnel matters, discussion and voting takes place on the team mailing list, otherwise on the developer mailing list.

Voting​

The Parca project usually runs by informal consensus, however sometimes a formal decision must be made.

Depending on the subject matter, as laid out above, different methods of voting are used.

For all votes, voting must be open for at least one week. The end date should be clearly stated in the call to vote. A vote may be called and closed early if enough votes have come in one way so that further votes cannot change the final decision.

In all cases, all and only team members are eligible to vote, with the sole exception of the forced removal of a team member, in which said member is not eligible to vote.

Discussion and votes on personnel matters (including but not limited to team membership and maintainership) are held in private on the team mailing list. All other discussion and votes are held in public on the developer mailing list.

For public discussions, anyone interested is encouraged to participate. Formal power to object or vote is limited to team members.

Consensus​

The default decision making mechanism for the Parca project is lazy consensus. This means that any decision on technical issues is considered supported by the team as long as nobody objects.

Silence on any consensus decision is implicit agreement and equivalent to explicit agreement. Explicit agreement may be stated at will. Decisions may, but do not need to be called out and put up for decision on the developers mailing list at any time and by anyone.

Consensus decisions can never override or go against the spirit of an earlier explicit vote.

If any team member raises objections, the team members work together towards a solution that all involved can accept. This solution is again subject to lazy consensus.

In case no consensus can be found, but a decision one way or the other must be made, any team member may call a formal majority vote.

Majority vote​

Majority votes must be called explicitly in a separate thread on the appropriate mailing list. The subject must be prefixed with [VOTE]. In the body, the call to vote must state the proposal being voted on. It should reference any discussion leading up to this point.

Votes may take the form of a single proposal, with the option to vote yes or no, or the form of multiple alternatives.

A vote on a single proposal is considered successful if more vote in favor than against.

If there are multiple alternatives, members may vote for one or more alternatives, or vote “no” to object to all alternatives. It is not possible to cast an “abstain” vote. A vote on multiple alternatives is considered decided in favor of one alternative if it has received the most votes in favor, and a vote from more than half of those voting. Should no alternative reach this quorum, another vote on a reduced number of options may be called separately.

Supermajority vote​

Supermajority votes must be called explicitly in a separate thread on the appropriate mailing list. The subject must be prefixed with [VOTE]. In the body, the call to vote must state the proposal being voted on. It should reference any discussion leading up to this point.

Votes may take the form of a single proposal, with the option to vote yes or no, or the form of multiple alternatives.

A vote on a single proposal is considered successful if at least two thirds of those eligible to vote vote in favor.

If there are multiple alternatives, members may vote for one or more alternatives, or vote “no” to object to all alternatives. A vote on multiple alternatives is considered decided in favor of one alternative if it has received the most votes in favor, and a vote from at least two thirds of those eligible to vote. Should no alternative reach this quorum, another vote on a reduced number of options may be called separately.

On- / Off-boarding​

The On- / Off-boarding section is informational and can be changed by lazy consensus unless challenged. If no consensus can be reached, the matter may be resolved by majority vote.

On-boarding​

The new member is

  • added to the list of team members. Ideally by sending a PR of their own, at least approving said PR.
  • announced on the developers mailing list by an existing team member. Ideally, the new member replies in this thread, acknowledging team membership.
  • added to the GitHub organization as Owner.
  • optionally added to the community, junkyard, and related organizations and repositories.
  • added to the team mailing list.

Off-boarding​

The ex-member is

  • removed from the list of team members. Ideally, by sending a PR of their own, at least approving said PR. In case of forced removal, no approval is needed.
  • removed from the GitHub organization and related organizations and repositories. Optionally, they can retain the maintainership of one or more repositories if the team agrees.
  • removed from the team mailing list and demoted to a normal member of the other mailing lists, i.e. developers, users, and announce.
  • removed from the shared password storage. All passwords, API tokens, etc., are cycled in due course (i.e. immediately in case of an involuntary departure but can be appropriately batched with other departures or routine cycling otherwise).
  • removed from group accounts where applicable. Services with some variety of a group account include but are not restricted to Vercel, Twitter, Youtube.
  • not allowed to call themselves an active team member anymore, nor allowed to imply this to be the case.
  • added to a list of previous members if they so choose.

If needed, we reserve the right to publicly announce removal.

FAQ​

The FAQ section is informational and can be changed by lazy consensus unless challenged. If no consensus can be reached, the matter may be resolved by majority vote.

How do I propose a decision?​

Send an email to the developer mailing list with your motion. If there is no objection within a reasonable amount of time, consider the decision made. If there are objections and no consensus can be found, a vote may be called by a team member.

How do I become a team member?​

To become an official team member, you should make ongoing contributions to one or more project(s) for at least three months. At that point, a team member (typically a maintainer of the project) may propose you for membership. The discussion about this will be held in private, and you will be informed privately when a decision has been made. A possible, but not required, graduation path is to become a maintainer first.

Should the decision be in favor, your new membership will also be announced on the developers mailing list.

How do I add a project?​

As a team member, propose the new project on the developer mailing list. If nobody objects, create the project in the GitHub organization. Add at least a README.md explaining the goal of the project, and a MAINTAINERS.md with the maintainers of the project (at this point, this probably means you).

How do I archive or remove a project?​

Send an email to the developer mailing list proposing the retirement of a project. If nobody objects, archive the project in the GitHub organization.

How do I remove an inactive maintainer?​

A maintainer may resign by notifying the team mailing list. A maintainer with no project activity for a year will be treated as if they had resigned. If there is an urgent need to replace a maintainer, discuss this on the team mailing list.

How do I remove a team member?​

Team members may resign by notifying the team mailing list. If you think a team member should be removed against their will, propose this to the team mailing list. Discussions will be held there in private.