diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-04-02 10:28:04 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-04-02 10:28:04 -0700 |
| commit | 5d5e4d968d10feb809041375495aa18eed24df51 (patch) | |
| tree | 2f91bfeb2cc94e4b3a33befaea511df70c740627 | |
| parent | 1da55a4e58c45d254a55fd6d41bfe90899c15146 (diff) | |
| parent | 094c5e46a7f62d4e65f9ae5f9c831f36894609d0 (diff) | |
Merge pull request #1996 from castrojo/more-items
Add section on the community meeting
| -rw-r--r-- | sig-contributor-experience/community-maintenance.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/sig-contributor-experience/community-maintenance.md b/sig-contributor-experience/community-maintenance.md index d47b0463..8dba9f0f 100644 --- a/sig-contributor-experience/community-maintenance.md +++ b/sig-contributor-experience/community-maintenance.md @@ -59,6 +59,15 @@ If you find that any one person is in charge of a resource it is your responsibi - Brendan Burns (@brendandburns) - Tim Hockin (@thockin) +### Community Meeting + +- [ ] Generate an archive of the [communtiy meeting notes](https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY/edit#heading=h.2gp5yf2snwg5) for the quarter if necessary + - [ ] Ensure the retrospective section has links to the retrospective for the releases + - [ ] Ensure the demo section is filled out and demos are assigned dates + - [ ] Ensure the [agenda template and hosting guide](https://docs.google.com/document/d/1g7fR5cvCGFq15SJ4iQMclbj0QIeREKu_QP8ftnSaJ4o/edit) are up to date +- [ ] Ensure the [SIG Schedule](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=1543199895) have SIGs assigned for the next few months + - [ ] Ensure the assigned SIGs in this sheet match the actual SIGs in sigs.yaml. Double check that a SIG hasn't missed an update this past cycle and if they have schedule them for an upcoming meeting + ### Properties Managed by the CNCF The CNCF provides support to Kubernetes for the following properties, you do not need to check them, however members of SIG Contributor Experience should have a working relationship with the administrators of the following properties: |