Re: separating out golang juju client from

2015-01-04 Thread Andrew Wilkins
On Fri, Dec 19, 2014 at 9:59 PM, Dimiter Naydenov < dimiter.nayde...@canonical.com> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I think having a separate juju/api repo containing the api client as a > reusable library will definitely improve collaboration/integration > with extern

Re: separating out golang juju client from

2014-12-19 Thread Dimiter Naydenov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think having a separate juju/api repo containing the api client as a reusable library will definitely improve collaboration/integration with external projects. It will require some refactoring to make it easier to reuse, but that's also a good thing.

Re: separating out golang juju client from

2014-12-19 Thread Richard Harding
Any time there's an API I'd rather we help own and build the community by providing the client vs relying on others to manage and control the experience there. Can't +1 it enough. Rick On Sat, 20 Dec 2014, David Cheney wrote: > There is no reason for the 130 (at last count) packages that > const

Re: separating out golang juju client from

2014-12-19 Thread David Cheney
There is no reason for the 130 (at last count) packages that constitute juju-core (not counting the dozens of other packages we bring in as dependencies) to live in the same repository. If licensing is the lever that we use to break up this monolithic repository, consider me +1 On Fri, Dec 19, 20

Re: separating out golang juju client from

2014-12-19 Thread Kapil Thangavelu
On Fri, Dec 19, 2014 at 7:02 AM, Nate Finch wrote: > > While I am generally for using more permissive licenses, I'm not sure how > useful that might be... most significant changes require modifications to > both the client and the server, or at least to libraries used by both. > That sort of miss

Re: separating out golang juju client from

2014-12-19 Thread Nate Finch
While I am generally for using more permissive licenses, I'm not sure how useful that might be... most significant changes require modifications to both the client and the server, or at least to libraries used by both. There's not that much code under cmd/juju compared to the whole rest of the repo

separating out golang juju client from

2014-12-19 Thread Kapil Thangavelu
one of the issues with having it in tree, means client usage falls under the AGPL. We want to have the client used widely under a more permissive license. I've already had contributions to other projects n'acked due to license on our libraries. I'd like to see it moved to a separate repo so that's