[17:13] marcoceppi: ping, does that answer make sense. We've tried to split "problem #1: charm development" from problem #2 "distributing your charm" by keying off a central point that there comes a time in development when you want to share it and get testing. [17:14] marcoceppi: the doc picks up from that point solving "prloblem #2: charm distribution" [17:15] marcoceppi: I'm happy to help think o nthe first part, but as the recent email thread brought up, that starts to hit upon VCS choices, patterns, and really we want to draw the line on the charmstore that it's not VCS aware, that's the dev's world. [17:15] marcoceppi: much as google's/chrome store and such you publish to it, and can publish alphas/betas, but don't hack directly in via vcs [17:53] rick_h_: google and chrome's store are end user, we're dealing with developers and operations [17:54] rick_h_: designing a store for end users and expecting dev and ops to use it will continue to create conflict [17:54] rick_h_: I want to discuss this more, for sure, if not before Oct then at that sprint [17:58] marcoceppi: I understand. Please let me know anytime and happy to talk through. The team is going to work on parts of this sooner than the sprint, but we can agree to work on parts that are a bit generic like juju store get/xx and such. [17:59] rick_h_: sure, we're sprinting atm, so we'll collect our thoughts and hopefully have a hangout early next week to chat about our impressions/needs for things and discuss where the store is going [18:00] marcoceppi: sounds good, thanks for making the time to give it a first pass [18:00] rick_h_: thanks for getting publish as priority still [18:01] marcoceppi: rgr, some work has started. Uploading now picks up git/bzr rev info [18:01] marcoceppi: the team did some work in our sprint a couple of weeks ago but got held up that I'd not finished that spec up yet. [18:01] and moved to some other things for a little bit