Hello everyone! We now have 20 interfaces and 18 layers published to the index: http://interfaces.juju.solutions - this is amazing, and I know there are even more layers out there in flight still. With the sudden burst of layers (both charm and interface) we've started seeing charms in the review queue built on layers. Cory sent an email out earlier[0] about how to handle the submission of charms built with layers, which is great.
I wanted to start discussing how we should handle the curation of these layers. Ideally I'd like to follow something along the lines of the charm review process, where charms are reviewed to make sure they promote the best possible practice. This helps to make sure deployments are high quality and means any charm could be used as an example of how to write a charm. Applying this to layers seems like a good start, but I don't want to overburden the current review process and I don't want to stifle the positive trajectory of layers being created. One idea, which I think would be simple enough is to continue to keep an open registry but simply have new layers announced on the list by the authors. This will help expose the layers being created, invite feedback from the community to the authors, and give us a chance to make sure layers implement the latest workflow since the charm build process is still evolving. Opinions? Thanks, Marco Ceppi
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
