Audit Charms

Registered by Antonio Rosales

Review all charm store charms for accurate descriptions, examples, ratings, metadata, icons, and embedded tests.

As the charm store redesign includes new features we need to review charms to ensure they take advantage of those features. In addition, we need to ensure the charm information exposed to users in charm searching is accurate, and helpful.

Blueprint information

Antonio Rosales
Jorge Castro
Series goal:
Accepted for saucy
Milestone target:
Completed by
Antonio Rosales

Related branches


Reminder to talk about interfaces and locking those down


James just attended an amazing Charm School and went to try something but the README doesn't tell him how to use the charm.

Kirk is a sysadmin and is only willing to deploy something that is dogfooded, well-tested, and has the same quality requirements as the packages he deploys from main.

Robert is deciding which nosql database of the day he wants to deploy and wants to compare the charms for them so he can make an informed decision.

Lars hears his project is now in the charm store and he wants to make sure that his project is represented with the same TLC that he puts into it upstream.

Jason wants to know how many people are using his software that is in the charm store.

Cliff just deployed something from the charm store only to find that the information is out of date and doesn't know how to fix it.






- The new Charm store offers everything you need to chose which service to deploy, including built-in testing results, quality ratings, examples for deployment, and support status.

vUDS 1305 notes:
vUDS 1308 notes:

Work for the T-series is documented in:


Work Items

Work items for ubuntu-13.09:
[jorge] Publicize criteria guidelines ( DONE
[jorge] Update Charm Store review workflow ( to include auditing workflow ( DONE

Work items:
[curtis] Build queue to display bitesize ingest errors, modify existing proof list to be this queue (aka fix charm proof): DONE
[curtis] Find average response times for charm reviews, display latency from responses and show a sparkline graph to show trends: DONE
[curtis] Team owned charms are broken: DONE
[curtis] Build the 2nd queue or a combined queue: DONE
[curtis] Mass file audit bugs for every charm sorted by descending by last-touched time: POSTPONED
[marcoceppi] Send reminder email to list for people to subscribe to their charm bugs as maintainers: POSTPONED
[marcoceppi] Ensure the charm tools subscribers thing runs on a regular basis: POSTPONED
[marcoceppi] Ensure the charm tools subscribers thing runs bi-monthly.: POSTPONED
[curtis] Add 7 unmaintained charms to the top of the queue: POSTPONED
[jorge] Add "file a bug if the interfaces don't match" as part of the review criteria: POSTPONED
[jorge] Put review policy for re-review criteria in the docs ( POSTPONED
[marcoceppi] Extract charm interface documentation using sentry: POSTPONED
[mark-mims] keep `charm review-queue` in sync with POSTPONED
[mark-mims] update charm tooling (proof): DONE
[jorge] how do we get them off the queue: DONE

This blueprint contains Public information 
Everyone can see this information.