What you should know ● The K8s community is organized into subgroups as below: ● Special Interest Groups, SIGs ○ Subprojects ● Working Groups, WGs ● Committees ● User Groups
Special Interest Group SIG sounds like of like a meetup group, and it both isn't and also is. Each SIG is its own sub-community in Kubernetes, because it's a huge project and we can't all be in one giant pool of 2000 contributors.
Working Groups and Subprojects Working Groups: inter-SIG efforts Subprojects: focus areas for SIGs For specific: ● Tools (ex. Kubectl) ● Goals (ex. Code Cleanup, Contributor Site) ● Areas (ex. Machine Learning)
Committees project governance oriented join by invite or election only there are currently three committees: Steering Security Response Code of Conduct https://github.com/kubernetes/community/blob/master/README.md#governance
Picking the right SIG 1. Figure out what specific projects/areas you want to work on. 2. Find out which SIG/WG/subproject covers that a. Ask on #sig-contribex b. Go to the SIG intros at this conference 3. Join that SIG/subproject a. If joining a WG/subproject, also join a SIG
Keeping in touch ● How do we do it? ○ Mailing List ○ Slack ○ Zoom meetings ● Some async initiatives: ○ Alternating between Slack threads & Zoom meetings in #sig-contribex ○ APAC friendly timings introduced for Release team meetings ○ More talk on Slack and Mailing Lists, less reliance on Meetings
When should you file a KEP? ● Significant changes to Kubernetes features ● Changes involving multiple stakeholders ● Notable policy changes in the codebase ● Changes impacting the UX of Kubernetes
When should you file a KEP? ● Significant changes to Kubernetes features ● Changes involving multiple stakeholders ● Notable policy changes in the codebase ● Changes impacting the UX of Kubernetes ● Test fixes ● Code Refactors ● Increasing log verbosity ● Adding more events ● Performance improvements not changing UX
Core Repository Most SIGs are stakeholders in the monolith. Areas of SIG ownership can be found in https://git.k8s.io/community/sigs.yaml kubernetes/kubernetes
Mentorship Programs ● Meet Our Contributors - #meet-our-contributors ● Group Mentoring ● Google Summer of Code ● Outreachy ● Linux Foundation LFX Mentorship Program
Kubernetes Release Team ● Periodically releases a new version of Kubernetes ● Collects features in a time frame and tracks whether the features go past the line ● Ensures quality of the artefacts generated as part of the release Image Source: https://git.k8s.io/sig-release/release-team/release-team.svg
What is the Release Shadow program? ● Follows the apprenticeship model ● Learn by doing and tagging along the lead ● Helps contributors broaden their area of knowledge https://git.k8s.io/sig-release/release-team/shadows.md
What do I need to do? 1. Read the role handbooks to understand the responsibilities of each role 2. Ask on #sig-release if in doubt 3. Fill up the form 4. Wait for the selection announcements
Contributor License Agreement ● Contributions to the Kubernetes project require you to sign a CLA ● Required to determine the legal status of contributions ● There are two kinds of CLA: 1. Individual 2. Corporate Note: Check in with your organization if you would need to sign the corporate CLA https://git.k8s.io/community/CLA.md
Labels can help you find your first issue! help wanted ● Low Barrier to Entry ● Clear Task good first issue ● Vetted for new contributors ● Provides ongoing support and guidance
Command /assign @username /retest /close /cc @username Result Assigns a Reviewer Reruns failed tests Closes PR Tags a user PRs and Bots: Useful Commands
PRs and Bots: Reviewers/Approvers ● Attach /sig label ● Contact your mentor(s) ● Contact the SIG ○ attend SIG meeting ○ ask Slack ○ send email to list ● Contact OWNERS
palnabarun
takemikami
red_frasco
ymty
k1low
rponte
.png){kind=icon}
pharma_x_tech
interu
tsutaj
shohata
cyberagentdevelopers
inesmontani
microcms
hannesfritz
destraynor
bkeepers
shlominoach
bermonpainter
jnunemaker
62gerente
speakerdeck
soudai
sferik
zenorocha
jeffersonlam