diff options
| author | Jorge O. Castro <jorge.castro@gmail.com> | 2018-01-23 13:49:54 -0500 |
|---|---|---|
| committer | Jorge O. Castro <jorge.castro@gmail.com> | 2018-01-23 13:49:54 -0500 |
| commit | 8d60a3ce31f2c82cc0de848187ecb7f28dd8b5b3 (patch) | |
| tree | 9034e29701dc0ceaa162bc81bf741d5401be6e55 | |
| parent | 67deb6a7ea7783d938ac5dbd9368411fec362fab (diff) | |
Add notetaker encouragement
| -rw-r--r-- | events/community-meeting.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/events/community-meeting.md b/events/community-meeting.md index 382b4200..8855e1c1 100644 --- a/events/community-meeting.md +++ b/events/community-meeting.md @@ -21,6 +21,12 @@ Quick links: The Kubernetes community meeting is intended to provide a holistic overview of community activities, critical release information, and governance updates. It also provides a forum for discussion of project-level concerns that might need a wider audience than a single special interest group (SIG). +## Notetaker(s) + +Notes from the meeting are published to the [Kubernetes dev](https://groups.google.com/forum/#!forum/kubernetes-dev) list. +A good notetaker is important to help get the information out to people who cannot attend. +Volunteers are always welcome to either add their notes directly to the document, or inform the host that they would like to help take notes at the beginning of the call. + ## Meeting Agenda If you have a topic you'd like to present or would like to see discussed, @@ -62,8 +68,6 @@ Also, if you are doing a live coding demo, please make sure it has a reasonable - Ensure you are presenting from a quiet environment. - If you run out of time while performing your demo, you may ask the audience if they would like a follow-up at a subsequent meeting. If there is enthusiastic support, the community team will help schedule a continuation. - - ## SIG Updates SIGs will give a community update at least once per release cycle per the [schedule](TBD). |