Skip to content

Latest commit

 

History

History
57 lines (43 loc) · 8.34 KB

README.md

File metadata and controls

57 lines (43 loc) · 8.34 KB
Raw

Kubernetes Community Documentation

Welcome to the Kubernetes community documentation. Here you can learn about what's happening in the community.

Slack Chat

Kubernetes uses Slack for community discussions.

Join: Joining is self service. Go to slack.k8s.io to join.

Access: Once you join, the team can be found at kubernetes.slack.io

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, and thockin.

Weekly Community Video Conference

The weekly community meeting provides an opportunity for the different SIGs and other parts of the community to come together.

Special Interest Groups (SIG)

Much of the community activity is organized into a community meeting and numerous SIGs. 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.

Name Leads Group Slack Channel Meetings
API Machinery @lavalamp (Daniel Smith, Google) Group #sig-api-machinery Every other Wednesday at 11:00 AM PST
Apps @michelleN (Michelle Noorali, Deis)
@mattfarina (Matt Farina, HPE)		 Group TBD Slack TBD Weekly on Wednesday at 9:00 AM PST
Auth @ erictune (Eric Tune, Google) Group #sig-auth Biweekly Wednesdays at 1100 to 1200 PT
Autoscaling @fgrzadkowski (Filip Grządkowski, Google) Group #sig-autoscaling Biweekly (or triweekly) on Thurs at 0830 PT
AWS @justinsb (Justin Santa Barbara)
@mfburnett (Mackenzie Burnett)		 Group #sig-aws TBD
Big Data @zmerlynn (Zach Loafman, Google)
@timothysc (Timothy St. Clair, Red Hat)
@wattsteve (Steve Watt, Red Hat)		 Group #sig-big-data Bi-weekly on Mondays at 1300 PT
Cluster Ops @zehicle (Rob Hirschfeld, RackN) Group #sig-cluster-ops Thursdays at 1:00 PM PST on hangouts
Federation @quinton-hoole (Quinton Hoole, Google) Group #sig-federation ???
Network @thockin (Tim Hockin, Google)
@dcbw (Dan Williams, Red Hat)		 Group #sig-network (unknown frequency) 0700 Fridays
Node @dchen1107 (Dawn Chen, Google)
@jonboulle (Jonathan Boulle, CoreOS)
@derekwaynecarr (Derek Carr, Red Hat)		 Group #sig-node Weekly on Wednesdays at 11:00 PT
OpenStack [@idvoretskyi (Ihor Dvoretskyi, Mirantis)] (https://github.com/idvoretskyi)
[@xsgordon (Steve Gordon, Redhat)] (https://github.com/xsgordon)		 Group #sig-openstack Biweekly on Tuesdays at 14:00 PT
Scalability @lavalamp (Daniel Smith, Google)
@countspongebob (Bob Wise, Samsung SDS)
@jbeda (Joe Beda)		 Group #sig-scale Weekly on Thursdays at 0900 PT
Scheduling @davidopp (David Oppenheimer, Google)
@timothysc (Timothy St. Clair, Red Hat)		 Group #sig-scheduling Alternate between Mondays at 1 PM PT and Wednesdays at 12:30 AM PT
Storage @saad-ali (Saad Ali, Google)
@childsb (Brad Childs, Red Hat)		 Group #sig-storage Bi-weekly Thursdays 9 AM PST (or more frequently)
Testing @spiffxp (Aaron Crickenberger, Samsung)
@ixdy (Jeff Grafton, Google)		 Group #sig-testing Tuesdays at 9:30 AM PT
UI @dodwyer (David O'Dwyer, Livewyer)
@preillyme (Patrick Reilly, Kismatic)
@bryk (Piotr Bryk, Google)		 Group #sig-ui Bi-weekly Wednesdays at 9 AM PT
Windows @preillyme (Patrick Reilly, Kismatic)
@sschuller (Sinclair Schuller, Apprenda		 Group #sig-windows Bi-weekly Tuesdays at 10:00 AM PT

How to start a SIG

  • Create a group with at least 2 owners: [email protected]
    • Put a description of the topic in the welcome message
  • Ask a repo maintainer to create a github label, if one doesn't already exist: area/foo
  • If you wish, create a new kubernetes.slack.com channel (#sig-foo). Users can join at slack.kubernetes.io.
  • Organize video meetings as needed. No need to wait for the Weekly Community Video Conference to discuss. Can 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 add it to this wiki
  • Submit a PR to add any SIG-related docs, schedules, roadmaps, etc. to docs/devel/sigs/
  • Slack activity is archived at kubernetes.slackarchive.io. To start archiving a new channel invite the slackarchive bot to the channel via /invite @slackarchive