diff --git a/communication/README.md b/communication/README.md index cb1f288e9dd..621f87cd8e6 100644 --- a/communication/README.md +++ b/communication/README.md @@ -28,7 +28,7 @@ groups/[SIGs] page. You can actively or passively participate in one of the following ways: - The community group's public meeting(s) listed on the above community groups page -- Every Third Thursday at our [monthly community meeting] over [zoom] at [10am US Pacific Time] +- Every Friday at our [Weekly Contributor Comms Meeting] over [zoom] at [10am US Pacific Time] - Intro sessions at KubeCon/CloudNativeCon live or [recordings on YouTube] Nevertheless, below find a list of many general channels, groups, and meetings @@ -191,7 +191,7 @@ place! [Josh Berkus]: https://github.com/jberkus [zoom]: https://zoom.us/my/kubernetescommunity [k-dev moderators]: ./moderators.md#kubernetes-dev -[monthly community meeting]: https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY/edit# +[Weekly Contributor Comms Meeting]: https://docs.google.com/document/d/1DUhWysUkwpIKKo_3A_sjDM8JVfQZs4NY8w6OKzzr1tE/edit [recordings on YouTube]: https://www.youtube.com/channel/UCvqbFHwN-nwalWPjPUKpvTA [community groups]: /governance.md#community-groups [these instructions]: /communication/slack-guidelines.md#requesting-a-channel diff --git a/communication/youtube/youtube-guidelines.md b/communication/youtube/youtube-guidelines.md index 43611d7220f..260a2fb10c3 100644 --- a/communication/youtube/youtube-guidelines.md +++ b/communication/youtube/youtube-guidelines.md @@ -21,9 +21,9 @@ and includes all communications such as YouTube. ## Meeting Playlists -The [Kubernetes YouTube Channel] has separate playlists for each SIG or WG -meeting recordings, as well as recordings of other recurring events such as the -Kubernetes [community meeting], and others. +The [Kubernetes YouTube Channel] has separate playlists for each SIG +or WG meeting recordings, as well as recordings of other recurring +events such as the [New Contributor Orientation], and others. [Subprojects], in addition to SIGs and WGs may request their own playlists to better target their contributors and increase general discoverability. @@ -212,8 +212,8 @@ to hear from you. ### Streaming Events YouTube admins with a system capable of streaming may be asked to stream public -Kubernetes Community events such as the weekly [Community Meeting], or other -publicly streamed events. For detailed information about streaming, see our +Kubernetes Community events such as publicly streamed events. For detailed +information about streaming, see our [Streaming Config]. ### Migrating Content @@ -237,7 +237,7 @@ downloaded and then reuploaded to the Kubernetes channel. [coc]: /code-of-conduct.md [admins]: /communication/moderators.md [Kubernetes YouTube Channel]: https://www.youtube.com/channel/UCZ2bu0qutTOM0tHYa_jkIwg -[community meeting]: /events/community-meeting.md +[New Contributor Orientation]: /mentoring/new-contributor-orientation/README.md [Subprojects]: /governance.md#subprojects [collaboration]: https://support.google.com/youtube/answer/6109639 [update the permissions in your YouTube settings]: https://support.google.com/a/answer/6212415 diff --git a/communication/zoom-guidelines.md b/communication/zoom-guidelines.md index 572c5e504a2..35e0e0851e6 100644 --- a/communication/zoom-guidelines.md +++ b/communication/zoom-guidelines.md @@ -5,11 +5,10 @@ description: | --- Zoom is the main video communication platform for Kubernetes. It is used for -running the [community meeting], [SIG/WG meetings], -and many other Kubernetes online events. Since the Zoom -meetings are open to the general public, a Zoom host or co-host has to moderate -a meeting in all senses of the word, from starting and stopping the meeting to -acting on [Kubernetes code of conduct] issues. +running the [SIG/WG/Committee meetings],and many other Kubernetes online events. +Since the Zoom meetings are open to the general public, a Zoom host or co-host +has to moderate a meeting in all senses of the word, from starting and stopping +the meeting to acting on [Kubernetes code of conduct] issues. These guidelines are meant as a tool to help Kubernetes members manage their Zoom resources. @@ -190,8 +189,8 @@ for which models work best. Thanks for making Kubernetes meetings work great! -[community meeting]: /events/community-meeting.md -[SIG/WG meetings]: /sig-list.md +[New Contributor Orientation]: /mentoring/new-contributor-orientation/README.md +[SIG/WG/Committee meetings]: /sig-list.md [Kubernetes code of conduct]: /code-of-conduct.md [moderation]: ./moderation.md [CNCF Service Desk]: https://github.com/cncf/servicedesk diff --git a/contributors/guide/non-code-contributions.md b/contributors/guide/non-code-contributions.md index 7678a7221da..82551a3f1ed 100644 --- a/contributors/guide/non-code-contributions.md +++ b/contributors/guide/non-code-contributions.md @@ -34,7 +34,7 @@ These are roles that either span the project as a whole, or span several areas o - Getting more people to [SIG-Docs](https://github.com/kubernetes/community/tree/master/sig-docs) - [Contribute to Kubernetes docs](https://kubernetes.io/docs/contribute/) - Doing demos - - [Kubernetes Weekly Community Meeting](https://github.com/kubernetes/community/blob/master/events/community-meeting.md) + - For example : [Kubernetes Weekly Community Meeting](https://github.com/kubernetes/community/blob/master/events/community-meeting.md) - [YouTube](https://www.youtube.com/playlist?list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ) - Outward facing community work (might be more CNCF-oriented) - Hosting meetups and general evangelism diff --git a/events/community-meeting.md b/events/community-meeting.md index 6ef5559b83f..4176410dd54 100644 --- a/events/community-meeting.md +++ b/events/community-meeting.md @@ -1,5 +1,5 @@ --- -title: Monthly Community Meeting +title: Monthly Community Meeting [currently inactive] weight: 1 description: | The Kubernetes community meeting is intended to provide a holistic overview of @@ -10,6 +10,8 @@ description: | # Kubernetes Monthly Community Meeting +**Note:** The Kubernetes Monthly Community Meetings are currently inactive. + We have PUBLIC and RECORDED [monthly meeting][community-meeting] the third Thursday of the month at [10am PT]; with the exception of December, or in the event it clashes with KubeCon + CloudNativeCon. diff --git a/events/events-team/best-practices.md b/events/events-team/best-practices.md index ac4ce84f4bd..04d8ed6abff 100644 --- a/events/events-team/best-practices.md +++ b/events/events-team/best-practices.md @@ -68,7 +68,6 @@ Slack - [#contributor-summit], [#kubecon], [#kubernetes-contributors] [Twitter] [Kubernetes blog] [discuss.kubernetes.io] -[Weekly Thursday Community Meetings][community-meetings] ## Sponsorship We like to keep our events clear from sponsorships as it distracts from the mission. diff --git a/mentoring/programs/mentoring-lead.md b/mentoring/programs/mentoring-lead.md index 5fa68e1d5f1..d3ab93ad48c 100644 --- a/mentoring/programs/mentoring-lead.md +++ b/mentoring/programs/mentoring-lead.md @@ -11,8 +11,8 @@ The Mentoring Lead role is created to help upstream Kubernetes contributors to p - Reach out to SIGs to submit proposals/projects so as to ensure healthy number of projects for an internship cohort. - Coordinate all submissions and participation in each one, responsible for following up with mentors during evaluation period. - Go to sig meetings and slack channels to proactively help with scoping and planning work / job descriptions. -- Help onboard interns to the k8s specific community items like coordinate a hello for them at the k8s monthly community meeting, -- Help off board interns to the k8s specific community items like demo at monthly community meeting. +- Help onboard interns to the k8s specific community items like coordinate a hello for them at the community meetings, +- Help off board interns to the k8s specific community items like demo at community meetings. - Be a point of contact (unless delegated otherwise) for applicants and mentees, and should respond to queries within a reasonable amount of time. - Should try and delegate work among shadows and mentor the shadows along the way. - Should train and pass on the responsibility to a shadow in 24 months time period. diff --git a/sig-wg-lifecycle.md b/sig-wg-lifecycle.md index 061cce194d1..ad9133549dd 100644 --- a/sig-wg-lifecycle.md +++ b/sig-wg-lifecycle.md @@ -57,7 +57,6 @@ Each one of these has a linked canonical source guideline from set up to moderat - [ ] Join the #chairs-and-techleads slack channel ...with the community as part of [sig-governance.md] -- [ ] Get on the schedule for [Thursday community updates]; info at the top of the agenda - [ ] Create a shared calendar and schedule your weekly/biweekly/triweekly weeks [update meetings] - This calendar creation process will allow all of your leads to edit SIG/WG Meetings. This is important as we all change jobs, email addresses, and take breaks from the project. Shared calendars will also provide consistency with contributors looking for your subproject meetings, office hours, and anything else that the SIG/WGs contributors should know about.