Thread by @dims

Hey, you are all at #kubeconEU and drinking from the fire hose this week. I'd like to pitch to you to consider contributing actively to the community if you haven't already to help us all avoid the tragedy of the commons. Here's some things to get your started (1/16)

Every SIG is short handed when it comes to reviews! example sig-node put out a call for folks to help with issue triage. IMHO all sigs need help with both Issue triage and PR reviews - groups.google.com/forum/#!msg/ku… (2/16)

There is a few of us working on migrating Kubernetes project infrastructure over to the CNCF, this work crosses a whole bunch of SIGs. Here's where to find info on that work - github.com/kubernetes/com… (3/16)

Docs! can there ever be enough docs? No, join SIG-Docs. Challenges faced are nicely enumerated by @bgrant0607 here - lists.cncf.io/g/cncf-toc/mes… (4/16)

We are constantly fighting flakes in your CI system, we could use your help finding and fixing them - storage.googleapis.com/k8s-gubernator… (5/16)

We take it for granted that k8s APIs work the same across vendors and managed offerings, the hard work is being done in the k8s-conformance working group and the sig-arch subproject. there's a lot more tests to write and review - github.com/kubernetes/com… (6/16)

Everyone wants their pet feature. right? how do we vet those? How do we make things consistent? here's where we make the sausage - github.com/kubernetes/com… (7/16)

There's plenty of debt that has gotten collected, including the mono-repo problem, need for feature branches, the staging repos etc - we need help cleaning stuff up and make it easier for everyone to consume k8s - github.com/kubernetes/com… (8/16)

There's tons of friction for both "full-time" folks and folks who occasionally contribute to k8s. The SIG-contribex is where we try to find ways to address issues and make things better (they use a lot of emojis!) - github.com/kubernetes/com… (9/16)

SIG-release has a lot of folks signing up for different roles for every release (3 months), but we have lot of tasks that we need to work on across multiple releases. just for example take this one - github.com/kubernetes/kub… (10/16)

SIG-testing needs help as well, we need folks who can help trouble shoot the various CI jobs when they break or flake, help reviewing new jobs that are getting added etc - github.com/kubernetes/com… (11/16)

It's not just about code, we spend a lot of time thinking about and documenting how we go about doing all this, here's a recent example about how to formalize sub projects - github.com/kubernetes/ste… (12/16)

We need folks who can moderate Slack, Zoom, Mailing lists, discuss forums, Youtube. If you have some spare time ... it does not take much! github.com/kubernetes/com… (13/16)

if you feel like you can help with improving our best practices here where we could use your help - github.com/kubernetes/com… (14/16)

We use labels like "good first issue" "help wanted", we use github milestones and project boards. So find those for the SIG you are interested in. If these are not enough, talk to various sigs in their slack channels (15/16)

- github.com/kubernetes/kub…
- github.com/kubernetes/kub…

join #kubernetes-dev slack channel and hit me up with any follow ups! Thanks for listening if you managed to read read till the end :) (16/16)