Updates to the Kubernetes community meeting

[Jorge Castro]

Hello cochairs and leads, 

You might have seen my two mails to -dev announcing that the community meeting has moved to a monthly. Here are the details:

Schedule for the year is here: https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit?usp=sharing

Slide template if you need it: https://docs.google.com/presentation/d/1-nTvKCiqu9UvFYUeM6p6RIqHS5-H-u3_x-V4xj_eIWo/edit#slide=id.g401c104a3c_0_0

As always please let us know ahead of time if a date conflicts for you. Also note that the status update can be given by a representative of the SIG, so if a chair is travelling you can still send someone to meeting to give the status. In the past we were flexible with cancellations, since we're streamlining this we can't really afford to have SIGs cancelling their updates. Our hosts will start reaching out to you much earlier than before so that should help with your planning. 

Please note that the SIG Governance has been updated: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#sig-roles-and-organizational-governance

This gives you more options, if you can't make a meeting we can use a recent KubeCon status or you can record a one off status or worst case, send the slides to k-dev. 

Here is the updated text:

"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."