Charm Store Freshness

Etherpad from UDS Session:
Charm Store Freshness
Ideas:

    We need something like debian/watch for charms.

    Upstream source repos

    charms using old formats

    More Charm Schools and Resources

Discussion:

    How does a user tell what attributes a charm has, specifically what security attributs does a charm have. Ideally this should be per charm on the charm browser

    Charm Quality Rating: https://juju.ubuntu.com/docs/charm-quality.html

    Need a way for a user to be easily to identify where the package is pulling from (ie, main, or a private ppa).

    Right now it is up to the maintainer of the charm to determine where the packaged is pulled from.

    Reviewed charm store policy: https://juju.ubuntu.com/docs/policy.html

Remote Questions:

Work Items:

    [jorge] Add criteria for things supported in main. Specifcially detail where a charm (by default) pulls its package from.

    [bkerensa] open bug for tags to track [1072653]

    [jorge] Test removal policy by removing alice-irc from the store.

    [clint-fewbar] Version information in config.yaml, make that policy.

    ooh, then we can have debian/watch files.

    [clint-fewbar] Implement debian/watch for charms, determine if this should live in jenkins instead (just fail a test if you're out of date).

    [clint-fewbar] file juju bug - upgrade-charm must take the same config.yaml as deploy

    [clint-fewbar] document best practice with regard to versions and defaults in config.yaml (materialized vs. lazy-load)