kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2446 from castrojo/sig-status 

Add some ideas for what a SIG Update should contain
This commit is contained in:
k8s-ci-robot 2018-08-08 16:10:16 -07:00 committed by GitHub
parent c8accb41b8 b66bb7c331
commit f79277a047
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
events/community-meeting.md
View File

@ -66,6 +66,22 @@ Also, if you are doing a live coding demo, please make sure it has a reasonable
## SIG Updates
SIGs will give a community update at least once per release cycle per the [schedule](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k).
The SIG Update should mention:
- Topics where input is being sought from other SIGs
- Topics that could affect other SIGs
- Currently active themes and goals in the SIG
- Broad description of future themes and goals if possible
- Status of any notable features that are transitioning across the spectrum of incubation, alpha, beta, stable/GA, or are being deprecated
- New or deprecated subprojects
- Leadership position changes or updates
- Charter status and updates, if any
- How people can contribute, areas where help is needed
- Any pending Kubernetes Enhancement Proposals (KEPs) or general big ideas that might warrant outside input
- Prior 1.X.Y release patches in flight status
- Current 1.X release targeted feature status
Since you only usually have ~10 minutes generally speaking if something is internal only to your SIG and doesn't affect others it doesn't need to be mentioned, people can always attend your SIG meeting for the details.
## Archives