diff options
| -rw-r--r-- | communication.md | 13 | ||||
| -rw-r--r-- | events/community-meeting.md | 73 |
2 files changed, 74 insertions, 12 deletions
diff --git a/communication.md b/communication.md index c045fbe2..7cc5c9cc 100644 --- a/communication.md +++ b/communication.md @@ -53,18 +53,7 @@ Office hours are held once a month. Please refer to [this document](events/offic ## Weekly Meeting -We have PUBLIC and RECORDED [weekly meeting] every Thursday at 10am US Pacific Time over Zoom. - -Map that to your local time with this [timezone table]. - -See it on the web at [calendar.google.com], or paste this [iCal url] into any iCal client. - -To be added to the calendar items, join the Google group -[kubernetes-community-video-chat] for further instructions. - -If you have a topic you'd like to present or would like to see discussed, -please propose a specific date on the [Kubernetes Community Meeting Agenda]. - +Refer to the [community meeting document](events/community-meeting.md) for information on our weekly meeting. ## Conferences diff --git a/events/community-meeting.md b/events/community-meeting.md new file mode 100644 index 00000000..eafb0f03 --- /dev/null +++ b/events/community-meeting.md @@ -0,0 +1,73 @@ +# Kubernetes Weekly Community Meeting + +We have PUBLIC and RECORDED [weekly meeting](https://zoom.us/my/kubernetescommunity) every Thursday at 6pm UTC (1pm EST / 10am PST) + +Map that to your local time with this [timezone table](https://www.google.com/search?q=1800+in+utc) + +See it on the web at [calendar.google.com](https://calendar.google.com/calendar/embed?src=cgnt364vd8s86hr2phapfjc6uk%40group.calendar.google.com&ctz=America/Los_Angeles) , or paste this [iCal url](https://calendar.google.com/calendar/ical/cgnt364vd8s86hr2phapfjc6uk%40group.calendar.google.com/public/basic.ics) into any iCal client. + +To be added to the calendar items, join the Google group +[kubernetes-community-video-chat](https://groups.google.com/forum/#!forum/kubernetes-community-video-chat) for further instructions. + +All meetings are archived on the [Youtube Channel](https://www.youtube.com/watch?v=onlFHICYB4Q&list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ) + +Quick links: + +- [Agenda document](https://k8s.devstats.cncf.io/) +- [Zoom meeting link](https://zoom.us/my/kubernetescommunity) + +## Purpose + +The purpose of the community meeting is the dissemination of information throughout the project. +Large changes in an area of Kubernetes that affect groups of people should be mentioned here. + + +## Meeting Agenda + +If you have a topic you'd like to present or would like to see discussed, +please propose a specific date on the [Kubernetes Community Meeting Agenda](https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY/edit#). + +General speaking the meeting is structured like this: + +- Introduction by Host (~3 minutes) +- Community Demo (~10 minutes) +- Release Updates + - Development Release + - Stable Release and point releases + - Older stable releases and point releases +- Graph of the Week (~2 minutes) + - This is meant to bring attention to different [devstats graphs](https://k8s.devstats.cncf.io/) +- SIG Updates + - Three SIGs per meeting, 10 minutes per SIG +- Announcements (~5 minutes) + - Any other community announcements should go here + +## Demos + +The first 10 minutes of a meeting is dedicated to demonstrations from the community. +These demos are noted at the top of the community document. +There is a hard stop of the demo at 10 minutes, with up to 5 more minutes for questions. +Feel free to add your demo request to the bottom of the list, then one of the organizers will get back to you to schedule an exact date. +Demo submissions MUST follow the the requirements listed below. + +### Requirements + +This meeting is the largest meeting in the community, and is attended by many people, therefore we ask that you _prepare ahead of time_ and not waste this opportunity. + +- Your demo MUST NOT be a commercial pitch and MUST be related to Kubernetes. Commercial software and services can be demo'ed but _keep it classy_ and relevant to the audience. +- You MUST show up to the community meeting _10 minutes_ prior to the start to test your audio and screensharing with the hosts. If you are not present on time, you will _lose your spot_ and be kicked back to the end of the demo queue. +- You MUST also commit to being available the week before your demo date in case there is an issue with that week's demo. +- The use of a headset or other high quality gear is _strongly_ recommended, typing from the same laptop you are speaking into is distracting +- Ensure you are presenting from a quiet environment. +- If you run out of time and your demo is a smashing hit we encourage you to schedule follow on events. + +## SIG Updates + +SIGs will give a community update at least once per release cycle per the [schedule](TBD). + +## Archives + +The document gets slow as we add notes, so it is archived regularly into another document: + +- [2017](https://docs.google.com/document/d/1sAH-74kIGROvM5MhyAkbJPVcuE9-RDHiOqfv_4PAGdw/edit#heading=h.en8cy6hno0c6) +- [2014-1016](https://docs.google.com/a/google.com/document/d/1fcs_POhXJCL1dqYrG3IxE4Ivh8jh2JYLCCdgRmBQeb8/edit?usp=sharing) |