The presentation discusses the Helm project, its code base, and ways to contribute to it.
- The Helm project is comprised of several repositories, including the primary Helm repository, Helm www, Helm testing, Helm releaser, GitHub actions, and Chart Museum.
- Contributions to the Helm project can be made through proposing new features, enhancing the code base, reporting and fixing bugs, and contributing to documentation and translations.
- Improvement proposals (HIPs) can be created to propose how to improve the Helm code base.
- The presentation emphasizes the importance of testing and documentation in contributing to the Helm project.
The presenter mentions that the Helm project is like a cruise ship that takes a long time to turn, but is relied on by many in the Kubernetes community. They also mention the importance of not breaking Helm, as many people depend on it.
Helm is the best way to package, find, share, and use software on Kubernetes. It's ease of use and ability to be integrated into a wider ecosystem of projects, products and solutions make Helm one of the most popular tools in the cloud native community. But, in addition to the features you know and love, there are even more exciting contributions waiting to be added to the project. In this session, Helm maintainers will highlight several exciting pending enhancements, and show you how you can help speed up the process of getting them landed upstream. This includes an introduction to the Helm codebase as well as demystifying the community Pull Request review process including how to choose an open PR to review, and reproduce and test the original issues and proposed fixes. Opportunities are abound for community members to step up the contributor ladder to join the Helm team to become a 'Triage Maintainer' and more!