Introducing the Non-Code Contributor’s Information
It was Might 2018 in Copenhagen, and the Kubernetes group was having fun with the contributor summit at KubeCon/CloudNativeCon, full with the primary run of the New Contributor Workshop. As a time of large collaboration between contributors, the matters coated ranged from signing the CLA to deep technical conversations. Together with the huge trade of data and concepts, nevertheless, got here continued scrutiny of the matters at hand to make sure that the group was being as inclusive and accommodating as doable. Over that spring week, among the items underneath the microscope included the numerous themes being coated, and the way they had been being offered, but additionally the overarching traits of the individuals contributing and the talent units concerned. From the discussions and evaluation that adopted grew the concept the group was not benefiting as a lot because it might from the many individuals who wished to contribute, however whose strengths had been in areas aside from writing code.
This all led to an effort referred to as the Non-Code Contributor’s Information.
Now, it’s necessary to notice that Kubernetes is uncommon, if not distinctive, within the open supply world, in that it was outlined very early on as each a venture and a group. Whereas the venture itself is concentrated on the codebase, it’s the group of individuals driving it ahead that makes the venture profitable. The group works along with an express set of group values, guiding the day-to-day habits of contributors whether or not on GitHub, Slack, Discourse, or sitting collectively over tea or espresso.
By having a group that values individuals first, and explicitly values a range of individuals, the Kubernetes venture is constructing a product to serve individuals with numerous wants. The totally different backgrounds of the contributors deliver totally different approaches to the issue fixing, with totally different strategies of collaboration, and all these totally different viewpoints in the end create a greater venture.
The Non-Code Contributor’s Information goals to make it simple for anybody to contribute to the Kubernetes venture in a method that is sensible for them. This may be in lots of kinds, technical and non-technical, primarily based on the individual’s information of the venture and their accessible time. Most people are usually not builders, and a lot of the world’s builders are usually not paid to totally work on open supply initiatives. Primarily based on this we’ve got began an ever-growing record of doable methods to contribute to the Kubernetes venture in a Non-Code method!
Among the methods that you could contribute to the Kubernetes group with out writing a single line of code embody:
The information to get began with Kubernetes venture contribution is documented on Github, and because the Non-Code Contributors Information is part of that Kubernetes Contributors Information, it may be discovered right here. As acknowledged earlier, this record will not be exhaustive and can proceed to be a piece in progress.
So far, the standard Non-Code contributions fall into the next classes:
Roles which are primarily based on talent units aside from “software program developer”
Non-Code contributions in primarily code-based roles
“Put up-Code” roles, that aren’t code-based, however require information of both the code base or administration of the code base
If you happen to, expensive reader, have any extra concepts for a Non-Code solution to contribute, whether or not or not it suits in an present class, the crew will all the time respect if you happen to might assist us increase the record.
If a contribution of the Non-Code nature appeals to you, please learn the Non-Code Contributions doc, after which test the Contributor Position Board to see if there are any open positions the place your experience may very well be finest used! If there aren’t any listed open positions that match your talent set, drop on by the #sig-contribex channel on Slack, and we’ll level you in the best path.
We hope to see you contributing to the Kubernetes group quickly!
This text initially appeared on the Kubernetes Weblog.