I’ve been wondering what we could do to assist the charm ecosystem. If one visits the charm store today, it can feel like visiting a ghost town. It’s impossible to know what’s reliable. We know that experienced community members stick to charms/bundles that are maintained by Canonical, e.g. anything under the banner of Charmed OpenStack and Charmed Kubernetes.
The conventional approach is to add ratings. But rating systems are flawed.
I’m not convinced that the move the CharmHub will address this issue. In fact, I believe that removing namespacing will make things worse. Today, I know that if I see a charm written by someone I trust, I can probably trust their next charm.
We don’t have infinite resources… but perhaps we can brainstorm some ideas? How practical would it be to set up a GitHub repository that deploys models via, for example, GitHub Actions?
As someone deploying charms, I want to know that the
juju deploy command works and, with the requisite relations/config in place, the application gets to the ready state without error. This should be as simple as a shell script.
We don’t need a perfect solution, just a gradual improvement from where we are now.