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

Add calendar specifics #1225

Merged
merged 2 commits into from
Oct 18, 2017
Merged

Add calendar specifics #1225

merged 2 commits into from
Oct 18, 2017

Conversation

castrojo
Copy link
Member

No description provided.

@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Oct 18, 2017
@castrojo castrojo changed the title Add calendar specifics, thanks @roberthbailey Add calendar specifics Oct 18, 2017
@castrojo
Copy link
Member Author

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.

* 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.
Copy link
Contributor

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?

- 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.
Copy link
Contributor

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?

@roberthbailey
Copy link
Contributor

Thanks, please squash before merging.

@roberthbailey
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 18, 2017
@k8s-github-robot
Copy link

Automatic merge from submit-queue.

@k8s-github-robot k8s-github-robot merged commit be791ab into kubernetes:master Oct 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants