We were thinking of blocking the "recommended" procedure to an entity without those values set. So, you want to have a recommended charm, make sure URLs are set and valid.
I don't think we need to make it mandatory for all charms, as it introduces a barrier maybe not everyone wants to cover at the beginning of their charming path ... On Wed, Sep 14, 2016 at 4:00 PM, Jorge O. Castro <[email protected]> wrote: > Good morning, > > I'd like to propose a policy change as a for incoming new charms. The > homepage and bugs-url fields are used to point users to where they can file > bugs, and where they can find the source code to the charm. The store uses > these fields to generate the page for each charm on jujucharms.com. > > Some promulgated charms are missing this (kubernetes and keystone for > example), so I'd like to encourage charm authors to set these two fields > with charm set: > > charm set wordpress bugs-url=https://bugspageforwordpress.none > charm set wordpress homepage=https://homepageforwordpress.none > > You can also tack a --channel on there, see: > https://jujucharms.com/docs/2.0/tools-charm-tools > > I'd like to propose a new policy to submission to the charm store metadata > guidelines: https://jujucharms.com/docs/stable/ > authors-charm-policy#metadata-guidelines > > MUST include bug reporting URL and homepage URL link to the source > code in metadata. > > While a bunch of charms written before this feature do put this sort of > information in the bottom of the readme I would like to get us filling out > the metadata for programmatic reasons and visibility on the charm's page in > the store. > > -- > Jorge Castro > Canonical Ltd. > http://jujucharms.com/ - The fastest way to model your application > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju > >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
