-
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
Conversation
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 |
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.
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.
❤️
Community Office Shepherds is really a good idea :) |
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.
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 |
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
Signed-off-by: Matej Gera <[email protected]>
Signed-off-by: Matej Gera <[email protected]>
…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]>
Signed-off-by: bwplotka [email protected]