-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Add calendar specifics #1225
Add calendar specifics #1225
Conversation
Creating a SIG Calendar seems to have gotten more complex, these steps are from @roberthbailey when he created a new SIG Calendar. Just going to add them to the SIG creation process. |
sig-governance.md
Outdated
* Slack activity is archived at [kubernetes.slackarchive.io](http://kubernetes.slackarchive.io). To start archiving a new channel invite the slackarchive bot to the channel via `/invite @slackarchive` | ||
* Organize video meetings as needed. No need to wait for the [Weekly Community Video Conference](community/README.md) to discuss. Please report summary of SIG activities there. | ||
* Request a Zoom account from from **@paris** or **@jorge**. You must set up a google group (see below) for the SIG leads so that all the SIG leads have the ability to reset the password if necessary. | ||
* Request a Zoom account from from [@parispittman](https://github.com/parispittman) or [@castrojo](https://github.com/castrojo). You must set up a google group (see below) for the SIG leads so that all the SIG leads have the ability to reset the password if necessary. |
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.
Still doesn't explain how to request it, just from whom. Can you put your slack handles and say to use that (or email) to make it explicit how to contact you?
sig-governance.md
Outdated
- If you want a team calendar ensure that it is managed with the SIG team lead list you will create (see below). Leads and jobs can change over time and it is important that no SIG resources are tied to a single user's account. | ||
1. Create a calendar on your own account. Make it public. | ||
2. Share it with all SIG leads with full ownership of the calendar - | ||
they can edit, rename, or even delete it. |
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.
why is there a weird line break here?
Thanks, please squash before merging. |
/lgtm |
Automatic merge from submit-queue. |
No description provided.