Re: Charm Store policy updates and refinement for 2.0

2016-03-22 Thread Stuart Bishop
On 23 March 2016 at 06:37, Jorge O. Castro wrote: > Thanks for the feedback Stuart, I've pushed up a new revision. > >> I think the acceptable software sources needs to be expanded. > > I've added your recommendations for this section except for: > >> In addition, any software sources not in the m

Re: Charm Store policy updates and refinement for 2.0

2016-03-22 Thread Jorge O. Castro
Thanks for the feedback Stuart, I've pushed up a new revision. > I think the acceptable software sources needs to be expanded. I've added your recommendations for this section except for: > In addition, any software sources not in the main Ubuntu or CentOS > archives should be listed in configur

Re: Charm Store policy updates and refinement for 2.0

2016-03-22 Thread Charles Butler
Hey Stuart! Thats a really good point about SSL on the interfaces service. I saw the bug a few weeks back but it slipped my mind, and it surprised me to discover its been there since 2015. I'll work towards having a resolution on this in the next week or so and will re-ping the list once its been

Re: Charm Store policy updates and refinement for 2.0

2016-03-21 Thread Stuart Bishop
On 19 March 2016 at 02:58, Jorge O. Castro wrote: > Recommendations from everyone on what we should include here would be > most welcome, specifically our recommendations around Windows charms > is non-existent. I think the acceptable software sources needs to be expanded. Launchpad PPAs should

Re: Charm Store policy updates and refinement for 2.0

2016-03-20 Thread Antonio Rosales
On Fri, Mar 18, 2016 at 1:28 PM, Charles Butler wrote: > Big +1 to the categories > > What i'd like to see is the policy document move to strong language where we > can build tooling around the automated checking of policy. > > Refactoring the MUSTS and SHOULDS give us a strong lead on that langua

Re: Charm Store policy updates and refinement for 2.0

2016-03-20 Thread Tom Barber
Bundles must only use charms which are already in the store, they cannot reference charms in personal namespaces. I assume this apples to only bundles that get promoted to recommended otherwise how would you enforce it? -- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)56

Re: Charm Store policy updates and refinement for 2.0

2016-03-19 Thread Jorge O. Castro
On Fri, Mar 18, 2016 at 12:11 PM, Tom Barber wrote: > I assume this apples to only bundles that get promoted to recommended > otherwise how would you enforce it? Yes, to be clear these policies only apply to things that are in the recommended/promulgated space. So jujucharms.com/haproxy, not juju

Charm Store policy updates and refinement for 2.0

2016-03-19 Thread Jorge O. Castro
Hello everyone, With 2.0 around the corner we decided to spend some time cleaning up the page everyone loves to hate, the Juju Charm Store policy: https://jujucharms.com/docs/1.25/authors-charm-policy and here is what I would like to propose: https://github.com/castrojo/docs/blob/master/src/en/

Re: Charm Store policy updates and refinement for 2.0

2016-03-19 Thread Charles Butler
Big +1 to the categories What i'd like to see is the policy document move to strong language where we can build tooling around the automated checking of policy. Refactoring the MUSTS and SHOULDS give us a strong lead on that language. MUST == has to be satisfied SHOULD = area for improvement - (p

Re: Charm Store policy updates and refinement for 2.0

2016-03-19 Thread Tom Barber
Cool! -- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)5603641316 (Thanks to the Saiku community we reached our Kickstart goal, but you can always help by sponsoring the project