Welcome to the Helm community!
This is the starting point for becoming a contributor to the Helm project - improving docs, improving code, giving talks etc.
The communication page lists communication channels like chat, issues, mailing lists, conferences, etc.
The Helm community holds regular public meetings, including those supporting Helm client development and charts. You can view the calendar of meetings and subscribe via an ical feed.
Documentation (like the text you are reading now) can always use improvement!
There's always code that can be clarified and variables or functions that can be renamed or commented.
There's always a need for more test coverage.
We recommend that you work on existing issues before attempting to develop a new feature.
Find an existing issue (e.g. one marked starter, or simply ask an owner for suggestions), and respond on the issue thread expressing interest in working on it.
This helps other people know that the issue is active, and hopefully prevents duplicated efforts.
Each commit must be signed off in git, as described by the article describing Helm's switch to DCO.
If you want to work on a new idea of relatively small scope:
- Submit an issue describing your proposed change to the repo in question.
- The repo owners will respond to your issue promptly.
- If your proposed change is accepted, start work in your fork, signing off each commit as described above
- Submit a pull request containing a tested change.