Project: Thanos (Observability and Analysis / Observability)
File: governance.md

This document describes the rules and governance of the project. It is a slightly modified version of the . It is meant to be followed by all the developers of the Thanos project and the Thanos community. Common terminology used in this governance document are listed below: Maintainers Team*: A core Thanos team that have owner access to http://github.com/thanos-io organization and all projects within it. Current list is available . Triage Team*: Contributors who does not belong to Maintainer's team, but has `Triage` GitHub role on repository allowing to change GitHub issues and PRs statuses and labels. They are listed . The Thanos project*: The sum of all activities performed under the , concerning one or more repositories or the community. Both Triage and Maintainers have are part of email list. The Thanos developers and community are expected to follow the values defined in the , including the . Furthermore, the Thanos community strives for kindness, giving feedback effectively, and building a welcoming environment. The Thanos developers generally decide by consensus and only resort to conflict resolution by a majority vote if consensus cannot be reached. Team member status may be given to those who have made ongoing contributions to the Thanos 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 Maintainer by email to . It is highly desirable to reach consensus about acceptance of a new member. However, the proposal is ultimately voted on by a formal of Team Maintainers. 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 for record-keeping purposes. If they choose to accept, the following steps are taken: Maintainer is added to the as Owner*. Maintainer is added to the . Maintainer is added to the list of team members New maintainer is announced on the by an existing team member. Team members may retire at any time by emailing . Team members can be removed by on . For this vote, the member in question is not eligible to vote and does not count towards the quorum. Upon death of a member, their team membership ends automatically. Triage team has similar rules, however the contributions made to the projects does not need to be as significant as expected by potential maintainer. New members as well may be proposed by any existing Maintainer or Triage person by email to . It is highly desirable to reach consensus about acceptance of a new member. However, the proposal is ultimately voted on by a formal (in comparison to Maintainer's vote which requires supermajority). 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 for record-keeping purposes. If they choose to accept, the following steps are taken: Triage member is added to the with `Triage` access. Triage member is added to the . Triage member is added to the list of Triage members . New team Triage member are announced on the by an existing team

Triage member may retire at any time by emailing . It can be proposed to step up as Maintainer in any time as well. Triage member can be removed by on . For this vote, the member in question is not eligible to vote and does not count towards the quorum. Only Maintainers team has right to vote. Upon death of a member, their Triage team membership ends automatically. Smaller technical decisions are made informally and is assumed. Technical decisions that span multiple parts of the Thanos project should be discussed and made on the and in most cases followed by proposal as described . Decisions are usually made by . If no consensus can be reached, the matter may be resolved by . Material changes to this document are discussed publicly on the . Any change requires a in favor. Editorial changes may be made by unless challenged. Any matter that needs a decision, including but not limited to financial matters, may be called to a vote by any Maintainer if they deem it necessary. For financial, private, or personnel matters, discussion and voting takes place on the ; Otherwise discussion and votes are held in public on the GitHub issues or #thanos-dev CNCF slack channel. The Thanos project usually runs by informal consensus, however sometimes a formal decision must be made. Depending on the subject matter, as laid out , 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 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 . All other discussion and votes are held in public on the GitHub issues or #thanos-dev CNCF slack channel. For public discussions, anyone interested is encouraged to participate. Formal power to object or vote is limited to . It's important for the project to stay independent and focused on shared interest instead of single use case of one company or organization. We value open source values and freedom, that's why we limit Maintainers Team votes to maximum two from a single organization or company. We also encourage any other company interested in helping maintaining Thanos to join us to make sure we stay independent. The default decision making mechanism for the Thanos project is . This means that any decision on technical issues is considered supported by the 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. Consensus decisions can never override or go against the spirit of an earlier explicit vote. If any 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, anyone from may call a formal . Majority votes must be called explicitly in a separate thread on the appropriate mailing

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 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. This section is informational. In case of disagreement, the rules above overrule any FAQ. It has to be majority so the vote will be declined. It's about number of up votes to agree on the decision. majority: Majority of voters has to agree. supermajority: 2/3 voters has to agree. See To become an official member of Maintainers Team, 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 As a team member, propose the new project on the . However, currently to maintain project in our organization you have to become Thanos Maintainers. All are encourage to start their own project related to Thanos. Thanos team is happy to link to your project inappropriate page e.g https://thanos.io/tip/thanos/integrations.md/ All members may resign by notifying the . If you think a team member should be removed against their will, propose this to the . Discussions will be held there in private. No,`[VOTE]` email has to be created. For majority voting this means that member that did not send a response agree with the proposal. For supermajority voting team has to wait for all answers.