<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Dec 19, 2014 at 9:59 PM, Dimiter Naydenov <span dir="ltr"><<a href="mailto:dimiter.naydenov@canonical.com" target="_blank">dimiter.naydenov@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
I think having a separate juju/api repo containing the api client as a<br>
reusable library will definitely improve collaboration/integration<br>
with external projects. It will require some refactoring to make it<br>
easier to reuse, but that's also a good thing. We should split the<br>
agent api and client api so the latter can move in a separate repo,<br>
but leave the former in juju-core.<br>
<br>
The apiserver should remain in juju/juju as it's closely tied with the<br>
state package and it does not make sense to have it separately (as<br>
long as state is also in juju-core).<br>
<br>
However, this should not be done at the expense of more complicated<br>
workflow: juju/api should be treated the same way as juju/juju - CI<br>
gated merges, bot running integration / upgrade tests, RB integration.<br></blockquote><div><br></div><div>+1 to OP, +1 to this</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Happy holidays ;)<br>
Dimiter<br>
<div><div class="h5"><br>
On 19.12.2014 15:43, David Cheney wrote:<br>
> There is no reason for the 130 (at last count) packages that<br>
> constitute juju-core (not counting the dozens of other packages we<br>
> bring in as dependencies) to live in the same repository.<br>
><br>
> If licensing is the lever that we use to break up this monolithic<br>
> repository, consider me +1<br>
><br>
> On Fri, Dec 19, 2014 at 11:05 PM, Kapil Thangavelu<br>
> <<a href="mailto:kapil.thangavelu@canonical.com">kapil.thangavelu@canonical.com</a>> wrote:<br>
>><br>
>><br>
>> On Fri, Dec 19, 2014 at 7:02 AM, Nate Finch<br>
>> <<a href="mailto:nate.finch@canonical.com">nate.finch@canonical.com</a>> wrote:<br>
>>><br>
>>> While I am generally for using more permissive licenses, I'm<br>
>>> not sure how useful that might be... most significant changes<br>
>>> require modifications to both the client and the server, or at<br>
>>> least to libraries used by both.<br>
>><br>
>><br>
>> That sort of misses the point of building apps that use juju<br>
>> apis. Yes the two packages need to be updated together for new<br>
>> changes same as today.<br>
>><br>
>>><br>
>>> There's not that much code under cmd/juju compared to the whole<br>
>>> rest of the repo.<br>
>><br>
>><br>
>> Again its not about that code, its about building other<br>
>> applications and facilitating integrations.<br>
>><br>
>><br>
>> cheers, Kapil<br>
>>><br>
>>><br>
>>> On Fri, Dec 19, 2014 at 6:03 AM, Kapil Thangavelu<br>
>>> <<a href="mailto:kapil.thangavelu@canonical.com">kapil.thangavelu@canonical.com</a>> wrote:<br>
>>>><br>
>>>> one of the issues with having it in tree, means client usage<br>
>>>> falls under the AGPL. We want to have the client used widely<br>
>>>> under a more permissive license. I've already had<br>
>>>> contributions to other projects n'acked due to license on our<br>
>>>> libraries. I'd like to see it moved to a separate repo so<br>
>>>> that's possible. Thoughts?<br>
>>>><br>
>>>> cheers, Kapil<br>
>>>><br>
>>>><br>
>>>><br>
>>>> -- Juju-dev mailing list <a href="mailto:Juju-dev@lists.ubuntu.com">Juju-dev@lists.ubuntu.com</a> Modify<br>
>>>> settings or unsubscribe at:<br>
>>>> <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a><br>
>>>><br>
>><br>
>> -- Juju-dev mailing list <a href="mailto:Juju-dev@lists.ubuntu.com">Juju-dev@lists.ubuntu.com</a> Modify<br>
>> settings or unsubscribe at:<br>
>> <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a><br>
>><br>
><br>
<br>
<br>
</div></div>- --<br>
Dimiter Naydenov <<a href="mailto:dimiter.naydenov@canonical.com">dimiter.naydenov@canonical.com</a>><br>
juju-core team<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1<br>
<br>
iQEcBAEBAgAGBQJUlC8pAAoJENzxV2TbLzHweucH/39/0D1WQt9pNT2yFrFb+Bt8<br>
JNO0shKqC1Spyblqn7WKI32H7unWVcI4qF2PMYdm3wYA84Xx+ySbislIRv5fJbPo<br>
9ex90IfKJxeEvE6Oq8guavQz6FR7Ks9BzZDnuQUt+gVeZP2QyPwu3v4963ZGIch2<br>
vVOPwR+B9hr+eah00o8HSX2qx7ycdAxuB+yEL0Yg5gBpEcHSACcChBKiF/WAk4wc<br>
rhEAbHDH5DdjbBmE6pJtaGavd5bs/FEsh5OgdFh5YEOSth5B9aRg9DhyzbouYr8Y<br>
RhVu7LiewnQxpq0kyiAjl4Mjzk4m6pT7/uzzoUqPgX7Q0A6OS/bj9fXghDs7Gpo=<br>
=PWBM<br>
-----END PGP SIGNATURE-----<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Juju-dev mailing list<br>
<a href="mailto:Juju-dev@lists.ubuntu.com">Juju-dev@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a><br>
</div></div></blockquote></div><br></div></div>