You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Archives: Discussions on most channels are archived at kubernetes.slackarchive.io. Start archiving by inviting the slackarchive bot to a channel via /invite @slackarchive
To add new channels, contact one of the admins. Currently that includes briangrant, goltermann, jbeda, sarahnovotny and thockin.
kubernetes mailing lists
Many important announcements and discussions end up on the main development group.
Much of the community activity is organized into a community meeting, numerous SIGs and time bounded WGs. Each of those groups operates a little differently which is reflected in how they capture notes, examples, and other information. Each groups material is in its subdirectory in this project.
Propose the new SIG publicly, including a brief mission statement, by emailing [email protected] and [email protected], then wait a couple of days for feedback
Create a group with at least 2 owners (and one of which should be sarahnovotny at google.com): [email protected]
Put a description of the topic in the welcome message
Set "Join the group" and "Post" to "Public"
Ask a repo maintainer to create a github label, if one doesn't already exist: area/foo
Organize video meetings as needed. No need to wait for the Weekly Community Video Conference to discuss. Please report summary of SIG activities there.
Request a Zoom account from @sarahnovotny if you expect more than 30 attendees or attendees from China.
Add the meeting to the community meeting calendar by inviting [email protected].
Use existing proposal and PR process
Announce new SIG on [email protected] and ask a repo maintainer to create a kubernetes/community directory and github team for the new group
Submit a PR to add any SIG-related docs, schedules, roadmaps, etc. to your new kubernetes/community/SIG-foo directory.
Slack activity is archived at kubernetes.slackarchive.io. To start archiving a new channel invite the slackarchive bot to the channel via /invite @slackarchive