As someone with an opensource project that ships a helm package, I wish you the best of luck. Helm has many flaws, and we can definitely do better. It sounds l

As someone with an opensource project that ships a helm package, I wish you the best of luck. Helm has many flaws, and we can definitely do better. It sounds like your pitch is focused on users, but I think you might want to think about how to attract a package ecosystem. Some things that would make my life easier as a packager: * Statically typed config language. It's insane that we're generating YAML files with Go templates. I'm a big fan of jsonnet, but whatever it is it should not be possible to have errors at runtime. * A better way to document to users the various options and how they play together. For any moderately complex package it become very challenging to communicate how to configure the chart for your environment * Better testing infrastructure; am I creating valid k8s resources given all of the possible configuration options?