Community

Thanos Community Office Hour (previously Contributor Office Hour) is a public weekly meeting focused on Thanos community, development, and contributions. It’s meant for users, developers, and maintainers to meet and get unblocked, pair review, and discuss development aspects of Thanos and related projects.
Everyone is welcome to join & add items to the agenda.

NOTE: If no agenda items will be added 1h before the meeting, the meeting will be cancelled.

Meeting Time: Every-second Thursday 14:00 GMT
Calendar Event: https://www.cncf.io/calendar/
Agenda: Google Doc
Link to join Zoom Meeting: https://zoom.us/j/99647108799
Meeting Passcode (avoids robot scrapers): thanos

NOTE: Maintainers, see community office hours shepherding section.

Slack

• General channel: #thanos https://slack.cncf.io/
• Development related channel, PR discussions: #thanos-dev https://slack.cncf.io/
• Try to timebox discussions to max 15-20min, unless there are no other agenda items. (:
• No announcements and marketing, just pure discussions over pending features/bugs/PRs especially contributed by other contributors than maintainers.

Community Websites for discussions and meeting:

• https://slack.cncf.io/
• #thanos - https://slack.cncf.io/
• #thanos-dev - https://slack.cncf.io/
• GitHub Discussions - discussions

Getting Involved

• Ask questions: If you have a quick question, you might want to also ask on #thanos or #thanos-dev Slack channel in the CNCF workspace. We recommend using GitHub issues for issues and feedback, because GitHub issues are trackable. CONTRIBUTING.md
• Contribute code: Before contributing a complex change to the Thanos repository, please discuss the change you wish to make within a Github issue, in Slack, or by another method with the owners of this repository before making the change. CONTRIBUTING.md
• Help others: If you feel like your PR is waiting too long for a review, feel free to ping the #thanos-dev channel on our Slack for a review! CONTRIBUTING.md

Shepherding

Each month we rotate the role of Community Office Shepherds among Team Members. This role is focused on leading the safe and friendly discussions during our Community Office Hours.

NOTE: Being shepherd does not mean other team members can chill out completely. (: It’s a joint effort, so ideally there are multiple team members on those meetings to make decisions if needed.
NOTE: If for some reason you as a shepherd can’t make it, find replacement or cancel the meeting.

Responsibilities

The Same Day Morning Before Meeting:

• Check agenda: Make sure it’s up to date and add any new items to the agenda that haven’t been addressed by maintainers.
• Notify maintainers: Remind maintainers of the meeting and any agenda items they should be prepared to discuss.
• Notify the community: Send a reminder to the community about the meeting and any agenda items that have been added since the previous meeting.
• Prepare meeting materials: Share the agenda and any other relevant materials with the community in advance of the meeting.

1 Day After Meeting (if meeting was not cancelled):

• Record the meeting: Check Recording tab in Zoom and share recording on Twitter.
• Update the agenda: If any action items or decisions were made during the meeting, update the agenda to reflect these changes.
• Update the meeting notes: If there were any key discussions or decisions made during the meeting, document these in the meeting notes.

Decisions

• 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. docs/governance.md
• For financial, private, or personnel matters, discussion and voting takes place on the docs/governance.md
• Otherwise discussion and votes are held in public on the GitHub issues or #thanos-dev CNCF slack channel. docs/governance.md
• Discussion and votes on personnel matters (including but not limited to team membership and maintainership) are held in private on the docs/governance.md
• Smaller technical decisions are made informally and lazy consensus is assumed. docs/governance.md
• Technical decisions that span multiple parts of the Thanos project should be discussed and made on the GitHub issues and in most cases followed by proposal as described here. docs/governance.md
• Material changes to this document are discussed publicly on the Thanos GitHub. Any change requires a supermajority in favor. Editorial changes may be made by lazy consensus unless challenged. docs/governance.md
• For public discussions, anyone interested is encouraged to participate. Formal power to object or vote is limited to Maintainers Team. docs/governance.md
• 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. docs/governance.md
• 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. docs/governance.md
• 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. docs/governance.md
• All members may resign by notifying the docs/governance.md
• If you think a team member should be removed against their will, propose this to the docs/governance.md
• Discussions will be held there in private. docs/governance.md

Schedule