summaryrefslogtreecommitdiff
path: root/events
diff options
context:
space:
mode:
authorParis Pittman <paris_pittman@apple.com>2020-06-21 21:34:56 -0700
committerParis Pittman <paris_pittman@apple.com>2020-06-21 21:34:56 -0700
commite39d805f00df4169e2d617cd07907127ff17c33c (patch)
treeb7754ed861a9217a71b1fe00c16c957b63a46e76 /events
parentfd5df0deed97536095a28c4f881bb5ce6247f85f (diff)
reducing meetingpolicy
Diffstat (limited to 'events')
-rw-r--r--events/community-meeting.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/events/community-meeting.md b/events/community-meeting.md
index 3716ab69..9606f05b 100644
--- a/events/community-meeting.md
+++ b/events/community-meeting.md
@@ -60,8 +60,8 @@ General speaking the meeting is structured as follows:
- Older stable releases and point releases
- Contributor Tip of the Week (~2 minutes, Optional)
- These can be a variety of topics, including [devstats graphs]
-- SIG Updates
- - Three SIGs per meeting, 10 minutes per SIG, if time allows 4 SIGs may present
+- Community Group Updates
+ - Three SIGs per meeting, 10 minutes per SIG, if time allows 4 SIGs may present. This includes committees and working groups.
- Announcements (~5 minutes)
- Any other community announcements should go here
- Shoutouts, an aggregation of thanks from community members to other
@@ -104,10 +104,10 @@ completing within the allotted time box.
enthusiastic support, the community team will help schedule a continuation.
-## SIG Updates
+## Community Group Updates
-SIGs will give a community update at least once per release cycle per the [schedule].
-The SIG Update should mention:
+SIGs and other community groups like committees and WGs (Working Groups) will give an update at least once a year.
+The update should mention:
- Topics where input is being sought from other SIGs
- Topics that could affect other SIGs