-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Added guide for Community Office Hours shepherding. #5568
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,17 +8,43 @@ Follow and interact with us on Twitter: [@ThanosMetrics](https://twitter.com/Tha | |
|
||
### Thanos Community Office Hours | ||
|
||
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**. [CoC applies](../../CODE_OF_CONDUCT.md). | ||
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. | ||
|
||
* When: Alternating weekly on Thursday: | ||
* One week EU friendly time: 11:00-12:00 UTC | ||
* One week US friendly time: 17:00-18:00 UTC | ||
* Calendar Event: https://www.cncf.io/calendar/ | ||
* Agenda: [Google Doc](https://docs.google.com/document/d/137XnxfOT2p1NcNUq6NWZjwmtlSdA6Wyti86Pd6cyQhs) | ||
* Link to join zoom webinar: [https://zoom.us/j/96037860612](https://zoom.us/j/96037860612) | ||
**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 15:00 CET | ||
|
||
**Calendar Event:** https://www.cncf.io/calendar/ | ||
|
||
**Agenda:** [Google Doc](https://docs.google.com/document/d/137XnxfOT2p1NcNUq6NWZjwmtlSdA6Wyti86Pd6cyQhs) | ||
|
||
**Link to join Zoom Meeting:** [https://zoom.us/j/99647108799](https://zoom.us/j/99647108799) | ||
|
||
**Meeting Passcode (avoids robot scrapers):** thanos | ||
|
||
> NOTE: Maintainers, see [community office hours shepherding](#community-office-hours-shepherding) section. | ||
|
||
#### How to Bring the Topic you are/want to Contribute to? | ||
|
||
1. Put your name (suggest Google Documents mode) on the Agenda with a related topic. | ||
2. Notify the maintainer that you wish to speak with or that maintains the component that the change refers to (Slack #thanos-dev channel) | ||
3. If the agenda topic is approved, we will make you a Panelist (you will be able to speak, show cam, present screen, etc), so we can collaborate and speak about the change (: | ||
|
||
#### Rules | ||
|
||
* The [CNCF Code of Conduct applies](../../CODE_OF_CONDUCT.md). | ||
* The meeting will happen in a form of a public, recorded Zoom Webinar. | ||
* Anyone can join as a viewer. | ||
* People that we know and those who have a "registered" agenda item will be added as panelists when the meeting starts (if they are present). | ||
* 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. | ||
* Focus on inclusiveness and friendliness: | ||
* No grumpiness allowed. (: | ||
* Any opinion is welcome, no straight rejections without nice explanations, etc. (: | ||
* We cancel the meeting if there aren’t any items on the agenda the day before the meeting. | ||
|
||
### Slack | ||
|
||
* General channel: [#thanos](https://slack.cncf.io/) | ||
|
@@ -43,3 +69,52 @@ We participate in periodic mentorship programs. Read more [here](mentorship.md). | |
### Further Questions | ||
|
||
Feel free to contact any of the [Maintainers](../../MAINTAINERS.md) | ||
|
||
### For Thanos Team Members | ||
|
||
#### Community Office Hours Shepherding | ||
|
||
Schedule: | ||
|
||
| Month | Shepherd (GitHub handle) | | ||
|---------|:-------------------------| | ||
| 2022.13 | TBD | | ||
| 2022.12 | TBD | | ||
| 2022.11 | TBD | | ||
| 2022.10 | TBD | | ||
| 2022.09 | `@bwplotka` | | ||
| 2022.08 | `@bwplotka` | | ||
|
||
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](#thanos-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: | ||
|
||
* Add entry for today on the [agenda document](https://docs.google.com/document/d/137XnxfOT2p1NcNUq6NWZjwmtlSdA6Wyti86Pd6cyQhs. | ||
* Announce meeting and call for agenda the same day morning on #thanos-dev and Twitter (`@ThanosMetrics` or your own account retweeted by ThanosMetrics). | ||
|
||
30 minutes Before: | ||
|
||
* Check agenda. If there are no topic, cancel the meeting. Announce cancellation on #thanos-dev and remove calendar item (anyone in `[email protected]` should have access). | ||
* If there are topics, clean and add suggestions if they make sense. | ||
|
||
2 minutes Before (if meeting was not cancelled): | ||
|
||
* Log in to Zoom as `[email protected]` to be a meeting Host. This will allow you to have a control over meeting and Meeting options. Passwords can be found in our Keybase files. | ||
* If 2FA kicks-in, you will get message in https://lists.cncf.io/ for `[email protected]` (`[email protected]` is just an alias). Login there (you need to be in this list, talked to `[email protected]` if you are not) and check `Admin > Pending` messages. | ||
* We moved to `Meetings` so there is no need to start the meeting - it will start automatically. Join as `[email protected]` to host conversation. | ||
* You don't need to answer all questions (or know how), just triage the potential questions and finish early if no other topics! | ||
* In case of problems start another meeting or edit options of recurring meeting `Meeting` tab: | ||
|
||
![img.png](../img/zoomedit.png) | ||
|
||
1 Day After Meeting (if meeting was not cancelled): | ||
|
||
* Check `Recording` tab in Zoom and share recording on Twitter. | ||
|
||
![img.png](../img/zoomrecording.png) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hour vote still pending (https://cloud-native.slack.com/archives/CL25937SP/p1659615345961049)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like 3PM still has the most votes, although there is some dissent in the thread
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens when the timezone changes from CET to CEST? We have to remember to come here and update this?
What about writing time always in UTC to make it friendly for people from different timezones to understand at what time the meeting happens? It's easy to convert UTC to my "my own" timezone and it's much more difficult to convert "other random" timezone to "my own".
Even if it's decided that the meeting will happen in different times in European summer or winter, writing it down in UTC is still the most friendly way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, I am always confused with UTC, plus it changes to maintainer team which is mostly CET (: - happy to change though.