You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Kubernetes community meeting is intended to provide a holistic overview of
6
+
community activities, critical release information, and governance updates. It
7
+
also provides a forum for discussion of project-level concerns that might need
8
+
a wider audience than a single special interest group (SIG).
9
+
---
10
+
1
11
# Kubernetes Monthly Community Meeting
2
12
3
-
We have PUBLIC and RECORDED [monthly meeting](https://zoom.us/my/kubernetescommunity) the third Thursday of the month at [10am PT](http://www.thetimezoneconverter.com/?t=10:00&tz=PT%20%28Pacific%20Time%29)
4
-
a). There will be no community meeting in the month of December, or in a week that conflicts with KubeCon + CloudNativeCon.
13
+
We have PUBLIC and RECORDED [monthly meeting][community-meeting] the third
14
+
Thursday of the month at [10am PT]; with the exception of December, or in the
15
+
event it clashes with KubeCon + CloudNativeCon.
5
16
6
-
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](https://en.wikipedia.org/wiki/ICalendar). Do NOT copy the meetings over to your personal calendar, you will miss meeting updates. Instead use your client's calendaring feature to say you are attending the meeting so that any changes made to meetings will be reflected on your personal calendar.
17
+
See it on the web at [calendar.google.com], or paste this [iCal url] into any
18
+
[iCal client]. Do NOT copy the meetings over to your personal calendar, you will
19
+
miss meeting updates. Instead use your client's calendaring feature to say you
20
+
are attending the meeting so that any changes made to meetings will be reflected
21
+
on your personal calendar.
7
22
8
-
All meetings are archived on the [YouTube Channel](https://www.youtube.com/playlist?list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ).
23
+
All meetings are archived on the [YouTube Channel].
The Kubernetes community meeting is intended to provide a holistic overview of community activities, critical release information, and governance updates.
18
-
It also provides a forum for discussion of project-level concerns that might need a wider audience than a single special interest group (SIG).
33
+
The Kubernetes community meeting is intended to provide a holistic overview of
34
+
community activities, critical release information, and governance updates. It
35
+
also provides a forum for discussion of project-level concerns that might need a
36
+
wider audience than a single special interest group (SIG).
37
+
19
38
20
39
## Notetaker(s)
21
40
22
-
Notes from the meeting are published to [this forum thread](https://discuss.kubernetes.io/t/kubernetes-weekly-community-meeting-notes/35/53) for wider distribution.
23
-
A good notetaker is important to help get the information out to people who cannot attend.
24
-
Volunteers are always welcome to either add their notes directly to the document, or inform the host that they would like to help take notes at the beginning of the call.
41
+
Notes from the meeting are published to [this forum thread] for wider distribution.
42
+
A good notetaker is important to help get the information out to people who
43
+
cannot attend. Volunteers are always welcome to either add their notes directly
44
+
to the document, or inform the host that they would like to help take notes at
45
+
the beginning of the call.
46
+
25
47
26
48
## Meeting Agenda
27
49
28
50
If you have a topic you'd like to present or would like to see discussed,
29
-
please propose a specific date on the [Kubernetes Community Meeting Agenda](http://bit.ly/k8scommunity).
51
+
please propose a specific date on the [Kubernetes Community Meeting Agenda][agenda].
30
52
31
53
General speaking the meeting is structured as follows:
32
54
@@ -37,58 +59,104 @@ General speaking the meeting is structured as follows:
37
59
- Stable Release and point releases
38
60
- Older stable releases and point releases
39
61
- Contributor Tip of the Week (~2 minutes, Optional)
40
-
- These can be a variety of topics, including [devstats graphs](https://k8s.devstats.cncf.io/)
62
+
- These can be a variety of topics, including [devstats graphs]
41
63
- SIG Updates
42
64
- Three SIGs per meeting, 10 minutes per SIG, if time allows 4 SIGs may present
43
65
- Announcements (~5 minutes)
44
66
- Any other community announcements should go here
45
-
- Shoutouts, an aggregation of thanks from community members to other contributors via the #shoutouts channel
67
+
- Shoutouts, an aggregation of thanks from community members to other
68
+
contributors via the `#shoutouts` channel
69
+
46
70
47
71
## Demos
48
72
49
-
The first 10 minutes of a meeting is dedicated to demonstrations from the community.
50
-
These demos are noted at the top of the community document.
51
-
There is a hard stop of the demo at 10 minutes, with up to 5 more minutes for questions.
52
-
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.
53
-
Demo submissions MUST follow the requirements listed below:
73
+
The first 10 minutes of a meeting is dedicated to demonstrations from the
74
+
community. These demos are noted at the top of the community document. There is
75
+
a hard stop of the demo at 10 minutes, with up to 5 more minutes for questions.
76
+
Feel free to add your demo request to the bottom of the list, then one of the
77
+
organizers will get back to you to schedule an exact date. Demo submissions MUST
78
+
follow the requirements listed below:
54
79
55
-
### Requirements
56
80
57
-
This meeting has a large number of attendees.
58
-
Out of respect for their time, we ask that you be fully prepared for your demo. Make sure slides are clear if applicable, and the link to them is posted in the meeting agenda.
59
-
Also, if you are doing a live coding demo, please make sure it has a reasonable chance of completing within the allotted time box.
81
+
### Requirements
60
82
61
-
- Demos must be about a core component of Kubernetes or a related project that is owned by a SIG. For projects in the Kubernetes ecosystem, you can sign up for a [CNCF Webinar](https://www.cncf.io/webinars/).
62
-
- You are required to show up 10 minutes before the meeting to verify your audio and screensharing capabilities with the hosts. If you cannot make and keep this commitment, you will not be allowed to proceed with your demo until such time you can.
63
-
- You also required to commit to being available the week before your demo date in case there is an issue with that week's demo.
64
-
- The use of a headset or other high-quality audio equipment is strongly encouraged. Typing on a laptop while using the system microphone is distracting, so please insulate your microphone from key noises.
83
+
This meeting has a large number of attendees. Out of respect for their time, we
84
+
ask that you be fully prepared for your demo. Make sure slides are clear if
85
+
applicable, and the link to them is posted in the meeting agenda. Also, if you
86
+
are doing a live coding demo, please make sure it has a reasonable chance of
87
+
completing within the allotted time box.
88
+
89
+
- Demos must be about a core component of Kubernetes or a related project that
90
+
is owned by a SIG. For projects in the Kubernetes ecosystem, you can sign up
91
+
for a [CNCF Webinar].
92
+
- You are required to show up 10 minutes before the meeting to verify your audio
93
+
and screensharing capabilities with the hosts. If you cannot make and keep this
94
+
commitment, you will not be allowed to proceed with your demo until such time
95
+
you can.
96
+
- You also required to commit to being available the week before your demo date
97
+
in case there is an issue with that week's demo.
98
+
- The use of a headset or other high-quality audio equipment is strongly
99
+
encouraged. Typing on a laptop while using the system microphone is distracting,
100
+
so please insulate your microphone from key noises.
65
101
- Ensure you are presenting from a quiet environment.
66
-
- If you run out of time while performing your demo, you may ask the audience if they would like a follow-up at a subsequent meeting. If there is enthusiastic support, the community team will help schedule a continuation.
102
+
- If you run out of time while performing your demo, you may ask the audience
103
+
if they would like a follow-up at a subsequent meeting. If there is
104
+
enthusiastic support, the community team will help schedule a continuation.
105
+
67
106
68
107
## SIG Updates
69
108
70
-
SIGs will give a community update at least once per release cycle per the [schedule](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k).
109
+
SIGs will give a community update at least once per release cycle per the [schedule].
71
110
The SIG Update should mention:
72
111
73
112
- Topics where input is being sought from other SIGs
74
113
- Topics that could affect other SIGs
75
114
- Currently active themes and goals in the SIG
76
115
- Broad description of future themes and goals if possible
77
-
- Status of any notable features that are transitioning across the spectrum of incubation, alpha, beta, stable/GA, or are being deprecated
116
+
- Status of any notable features that are transitioning across the spectrum of
117
+
incubation, alpha, beta, stable/GA, or are being deprecated
78
118
- New or deprecated subprojects
79
119
- Leadership position changes or updates
80
120
- Charter status and updates, if any
81
121
- How people can contribute, areas where help is needed
82
-
- Any pending Kubernetes Enhancement Proposals (KEPs) or general big ideas that might warrant outside input
122
+
- Any pending Kubernetes Enhancement Proposals (KEPs) or general big ideas that
123
+
might warrant outside input
83
124
- Prior 1.X.Y release patches in flight status
84
125
- Current 1.X release targeted feature status
85
-
- Rescheduling an update can happen, but is strongly discouraged as the schedule is done with as much lead time as possible to allow SIGs time to plan ahead
86
-
- SIGs should consider asking someone who is not a chair or lead to give this update as a mentorship/growth opportunity to newer members
87
-
- There is a [pregenerated slide template](https://docs.google.com/presentation/d/1-nTvKCiqu9UvFYUeM6p6RIqHS5-H-u3_x-V4xj_eIWo/edit#slide=id.g401c104a3c_0_0) that you can use for your status
88
-
- The update belongs entirely to the SIG, there will be periods when "boring" work happens and the SIG might want to not give a status update, instead consider a shorter update that at least lets the community know if you're in a quiet period. Informing the community that you've been clearing out the backlog in a 1 minute status is much better than not having a status report because you're concerned about not filling out the template in full. Just cut out what doesn't apply to you.
126
+
- Rescheduling an update can happen, but is strongly discouraged as the schedule
127
+
is done with as much lead time as possible to allow SIGs time to plan ahead
128
+
- SIGs should consider asking someone who is not a chair or lead to give this
129
+
update as a mentorship/growth opportunity to newer members
130
+
- There is a [pregenerated slide template] that you can use for your status
131
+
- The update belongs entirely to the SIG, there will be periods when "boring"
132
+
work happens and the SIG might want to not give a status update, instead
133
+
consider a shorter update that at least lets the community know if you're in
134
+
a quiet period. Informing the community that you've been clearing out the
135
+
backlog in a 1 minute status is much better than not having a status report
136
+
because you're concerned about not filling out the template in full. Just
137
+
cut out what doesn't apply to you.
138
+
139
+
Since you only usually have ~10 minutes generally speaking if something is
140
+
internal only to your SIG and doesn't affect others it doesn't need to be
141
+
mentioned, people can always attend your SIG meeting for the details.
89
142
90
-
Since you only usually have ~10 minutes generally speaking if something is internal only to your SIG and doesn't affect others it doesn't need to be mentioned, people can always attend your SIG meeting for the details.
91
143
92
144
## Archives
93
145
94
-
The document gets slow as we add notes, so it is archived regularly into the [Meeting Notes Archive](https://git.kubernetes.io/community/communication/meeting-notes-archive).
146
+
The document gets slow as we add notes, so it is archived regularly into the
0 commit comments