Update contact, zoom, and calendar information #1215
Merged
Conversation
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
Add team calendar information Add Zoom account specifics
k8s-ci-robot
added
size/S
|
/LGTM |
k8s-ci-robot
added
the
lgtm
|
/lgtm |
|
|
||
| ### Prerequisites | ||
|
|
||
| * Propose the new SIG publicly, including a brief mission statement, by emailing kubernetes-dev@googlegroups.com and kubernetes-users@googlegroups.com, then wait a couple of days for feedback | ||
| * Ask a repo maintainer to create a github label, if one doesn't already exist: sig/foo | ||
| * Request a new [kubernetes.slack.com](http://kubernetes.slack.com) channel (#sig-foo) from **@sarahnovotny**. New users can join at [slack.kubernetes.io](http://slack.kubernetes.io). | ||
| * Request a new [kubernetes.slack.com](http://kubernetes.slack.com) channel (#sig-foo) from **@paris** or **@jorge**. New users can join at [slack.kubernetes.io](http://slack.kubernetes.io). |
There was a problem hiding this comment.
These should be actual github handles, not just your name.
| * 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 pyao@linuxfoundation.org cc'ing sarahnovotny@google.com. | ||
| * Add the meeting to the community meeting calendar by inviting cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com. | ||
| * 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. |
There was a problem hiding this comment.
how to submit the request now that there is no email? slack?
| * Read [how to use YouTube](https://github.com/kubernetes/community/blob/master/community/K8sYoutubeCollaboration.md) for publishing your videos to the Kubernetes channel. | ||
| * Calendars | ||
| - Add the meeting to the community meeting calendar by inviting cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com. | ||
| - 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. |
There was a problem hiding this comment.
I don't think this is prescriptive enough. Here are the exact steps that Tim and I came up with:
-
Create a calendar on your own account. Make it public.
-
Share it with all SIG leads with full ownership of the calendar -
they can edit, rename, or even delete it. -
Share it with sc1@kubernetes.io, sc2@kubernetes.io,
sc3@kubernetes.io, with full ownership. This is just in case SIG
leads ever disappear. -
Share it with the SIG mailing list, lowest privs.
-
Share it with cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com
to publish on the universal calendar.
wking
added a commit
to wking/kubernetes-community
that referenced
this pull request
May 22, 2018
This is mostly replacing https://github.com/kubernetes/community/blob/master/... links with relative links, because relative links are easier to maintain. For example, if you rename a.md to b.md in a feature branch, updating an ../a.md to ../b.md target will work immediately (e.g. during pull-request review), while updating https://github.com/kubernetes/community/blob/master/a.md to https://github.com/kubernetes/community/blob/master/b.md will only work after your branch lands the rename in master. I'm not sure why the #L1454 fragment was part of the old sig-governance template sigs.yaml link, but it's been there since the template landed in 68658bf (Provide short template for SIG governance, 2018-02-23, kubernetes#1830). I've removed it in this commit. The Kubernetes Charter README link in the sig-governance template could just be: [Kubernetes Charter README]: README.md but I've sent it down to the project root and back to make life easier on new SIGs which copy/paste the file to a new location in this repository. With this commit they'll just need to drop one level of ../ to get the references working from places like sig-contributor-experience/charter.md. I've also chased a few files and anchors as they've moved around (e.g. the OBSOLETE_templates.md rename from 18958f8 (addressing Brians comments, 2017-09-06, kubernetes#1010) and the "and maintenance" header addition from f471f6b (Add new contact info for Paris and me, 2017-10-17, kubernetes#1215). This commit isn't complete, but it's a step in the right direction and all I had time for tonight ;).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.