Move community meeting to a monthly cadence (#4323)

* Move community meeting to a monthly cadence

Signed-off-by: Jorge O. Castro <jorgec@vmware.com>

* Let's not meet in December or during KubeCon

Signed-off-by: Jorge O. Castro <jorgec@vmware.com>

* Add options for SIGs to update the community

Signed-off-by: Jorge O. Castro <jorgec@vmware.com>

* Be more explicit about SIGs posting their updates to k-dev

Signed-off-by: Jorge O. Castro <jorgec@vmware.com>

committee-steering/governance/sig-governance.md

@@ -8,12 +8,16 @@ In order to standardize Special Interest Group efforts, create maximum transpare
 - Meet regularly, at least for 30 minutes every 3 weeks, except November and December
 - Keep up-to-date meeting notes, linked from the SIG's page in the community repo
 - Record meetings and make them publicly available on a YouTube playlist
-- Report activity in the weekly community meeting at least once every quarter
+- Report activity with the community via the kubernetes-dev mailing list at least once a quarter. Whichever format the SIG uses should _always_ be reported to the kubernetes-dev mailing list as this is the list the community depends on for SIG updates.  
+  - Each SIG is assigned an update during the monthly community meeting throughout the year. The meeting host will publish the notes to the kubernetes-dev mailing list with the update.  
+  - If a SIG is doing an update during KubeCon + CloudNativeCon, the SIG Chairs should ensure that a link to the recording of the video is sent to the kubernetes-dev mailing list.  
+  - YouTube presentation or mailing list update sent to the kubernetes-dev mailing list.
 - Participate in release planning meetings and retrospectives, and burndown meetings, as needed
 - Ensure related work happens in a project-owned github org and repository, with code and tests explicitly owned and supported by the SIG, including issue triage, PR reviews, test-failure response, bug fixes, etc.
 - Use the [forums provided] as the primary means of working, communicating, and collaborating, as opposed to private emails and meetings
 
 The process for setting up a SIG or Working Group (WG) is listed in the [sig-wg-lifecycle] document.
+
 ## Roles
 
 ### Notes on Roles

events/community-meeting.md

@@ -1,7 +1,7 @@
-# Kubernetes Weekly Community Meeting
+# Kubernetes Monthly Community Meeting
 
-We have PUBLIC and RECORDED [weekly meeting](https://zoom.us/my/kubernetescommunity) every Thursday at [10am PT](http://www.thetimezoneconverter.com/?t=10:00&tz=PT%20%28Pacific%20Time%29)
-a).
+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)
+a). There will be no community meeting in the month of December, or in a week that conflicts with KubeCon + CloudNativeCon.
 
 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 a 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. 
 
@@ -31,15 +31,15 @@ please propose a specific date on the [Kubernetes Community Meeting Agenda](http
 General speaking the meeting is structured as follows:
 
 - Introduction by Host (~3 minutes)
-- Community Demo (~10 minutes)
-- Release Updates
+- Community Demo (~10 minutes, Optional)
+- Release Updates (~10 minutes, Optional, release manager's discretion)
   - Development Release
   - Stable Release and point releases
   - Older stable releases and point releases
-- Contributor Tip of the Week (~2 minutes)
+- Contributor Tip of the Week (~2 minutes, Optional)
   - These can be a variety of topics, including [devstats graphs](https://k8s.devstats.cncf.io/)
 - SIG Updates
-  - Three SIGs per meeting, 10 minutes per SIG 
+  - Three SIGs per meeting, 10 minutes per SIG, if time allows 4 SIGs may present 
 - Announcements (~5 minutes)
   - Any other community announcements should go here
   - Shoutouts, an aggregation of thanks from community members to other contributors via the #shoutouts channel 
@@ -50,15 +50,15 @@ The first 10 minutes of a meeting is dedicated to demonstrations from the commun
 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 requirements listed below. 
+Demo submissions MUST follow the requirements listed below: 
 
 ### Requirements
 
 This meeting has a large number of attendees. 
 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. 
 Also, if you are doing a live coding demo, please make sure it has a reasonable chance of completing within the allotted time box.
 
-- Your demo should provide clear, valuable information to the community without being commercial in nature. Typical sales pitches are not permitted, and could potentially alienate your audience. Commercial software and services can be demo'ed, but a prior discussion with the community team is advised to ensure a positive experience.
+- 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/).
 - 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.
 - 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.
 - 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.