ErrTooMuchHelm = fmt Errorf"A Maintainer's Story About Helping with Helm"
summary
Maintainers outline concrete contribution paths: join Slack channels and weekly dev calls (Thursdays 9:30 PST), post to helm.sh/blog, and update helm.sh/docs; reproduce bugs with a scaffold chart and attach a minimal chart plus reproduction steps; include unit tests (and expect forthcoming acceptance tests in the helm org) and mark issues with labels like good-first-issue, bug, feature or support; expect long turnaround while core team splits time between Helm v2 support and pushing Helm v3 to GA.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:12Question
- 5:13How can we help open the community
- 8:16How to find Helm Docs
- 15:45Using the scaffold chart
- 18:10Code and test
- 20:45How to merge
- 22:20How to get started
- 23:50Acceptance tests
- 24:40QA
related talks
35mTaking the Helm: Becoming a Maintainer
46mClear Your Own Path to Open Source Maintainer
13mOpen Source Opening Doors - Michelle Noorali, Sr. Software Engineer, Microsoft (Part 1)
22mCreating a Micro Open-Source Community with Helm
03mPull Requests Welcome! - How to Contribute to the Argo Community
01h 27mMeet the Maintainers: Discuss Roles and Responsibilities, Areas of Improvements and...
42mBuilding On-Ramps for Non-Code Contributors in Open Source
09mMaintaining the Maintainers