Skip to content
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 3 commits into from
Oct 27, 2022
Merged

Conversation

bwplotka
Copy link
Member

@bwplotka bwplotka commented Aug 4, 2022

Signed-off-by: bwplotka [email protected]


> 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
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator

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

Copy link
Contributor

@douglascamata douglascamata Aug 9, 2022

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.

Copy link
Member Author

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.

kakkoyun
kakkoyun previously approved these changes Aug 4, 2022
Copy link
Member

@kakkoyun kakkoyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

@Akshit42-hue
Copy link
Contributor

Akshit42-hue commented Aug 4, 2022

Community Office Shepherds is really a good idea :)
LGTM!

matej-g
matej-g previously approved these changes Aug 5, 2022
Copy link
Collaborator

@matej-g matej-g left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Beautiful 💅


> 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
Copy link
Collaborator

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

docs/contributing/community.md Outdated Show resolved Hide resolved
@matej-g matej-g dismissed stale reviews from kakkoyun and themself via d48680f October 27, 2022 14:51
Signed-off-by: Matej Gera <[email protected]>
@matej-g matej-g merged commit 203a295 into main Oct 27, 2022
ngraham20 pushed a commit to ngraham20/thanos that referenced this pull request May 18, 2023
…5568)

* docs: Added guide for Community Office Hours shepherding.

Signed-off-by: bwplotka <[email protected]>

* Update docs/contributing/community.md

Signed-off-by: Matej Gera <[email protected]>

* Fix whitespaces

Signed-off-by: Matej Gera <[email protected]>

Signed-off-by: bwplotka <[email protected]>
Signed-off-by: Matej Gera <[email protected]>
Signed-off-by: Matej Gera <[email protected]>
Co-authored-by: Matej Gera <[email protected]>
Co-authored-by: Matej Gera <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants