I do think that making it a release blocker might be interesting to help
users that find those charms. You can use/develop just fine without making
it a blocker to getting started, but at release time you're already doing
charm command work there.
On Wed, Sep 14, 2016 at 10:28 AM Jorge O. Castro
On Wed, Sep 14, 2016 at 10:05 AM, Uros Jovanovic <
uros.jovano...@canonical.com> wrote:
> 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 ...
Agreed, people's namespaces are their
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
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.
