diff options
| author | Jorge O. Castro <jorgec@vmware.com> | 2020-01-09 10:33:45 -0500 |
|---|---|---|
| committer | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2020-01-09 07:33:45 -0800 |
| commit | 3167a89614c4041a45e36a0084441ff29e5e2e7e (patch) | |
| tree | bd889200bc4f90650e8e9a8e68c90eb7d73bd956 /committee-steering | |
| parent | d496f5ebeabca5c7bbc3dbdf234a4daae52db569 (diff) | |
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>
Diffstat (limited to 'committee-steering')
| -rw-r--r-- | committee-steering/governance/sig-governance.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/committee-steering/governance/sig-governance.md b/committee-steering/governance/sig-governance.md index 1c7cedd4..141946aa 100644 --- a/committee-steering/governance/sig-governance.md +++ b/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 |