Re: Use of Jujucharms to launch non-opensource code

This is actually a non-issue. The codebase was moved to LGPL over a year ago, there was just two places this was not updated. First LaunchPad and second was the setup.py file. I've corrected both. On Tue, Feb 9, 2016 at 7:09 AM Marco Ceppi wrote: > I'll take a look

Re: Use of Jujucharms to launch non-opensource code

I agree, I was a bit surprised that charmhelpers was AGPL instead of LGPL. I think it makes sense as you still would contribute back to the layers you touch, but it doesn't turn your entire charm into GPL. John =-> On Tue, Feb 9, 2016 at 3:38 PM, Mark Shuttleworth wrote: > On

Re: Use of Jujucharms to launch non-opensource code

On 09/02/16 09:25, John Meinel wrote: > The more edge case is that charmhelpers itself is AGPL, so if your charm > imported charmhelpers, then that is more of a grey area. You likely need to > open source the actual charm, which sets up configuration, etc of the > program. However, you still don't

Re: Use of Jujucharms to launch non-opensource code

OK, let's explore moving that to LGPL which I think would be more appropriate for things like that and layers. Mark On 09/02/16 12:04, John Meinel wrote: > I agree, I was a bit surprised that charmhelpers was AGPL instead of LGPL. > I think it makes sense as you still would contribute back to

Re: Use of Jujucharms to launch non-opensource code

Thanks Marco! On Tue, Feb 9, 2016 at 1:33 PM, Marco Ceppi wrote: > This is actually a non-issue. The codebase was moved to LGPL over a year > ago, there was just two places this was not updated. First LaunchPad and > second was the setup.py file. I've corrected both.

Re: Use of Jujucharms to launch non-opensource code

Hi Marco, It is the former. Using Juju and charms in a commercial project/product. regards Ramesh On Sun, 7 Feb 2016 at 20:11 Marco Ceppi wrote: > Could you elaborate on your usage? Are you wrapping Juju itself in a > commercial project, using the charms in a

Re: Use of Jujucharms to launch non-opensource code

IANAL either, but if you are just using Juju and public charms to deploy a commercial project or product, then I think that is fine. Like deploying a private django app (which is what I do). This is just using the tools for what they were designed for. However, if you are modifying Juju source,

Re: Use of Jujucharms to launch non-opensource code

Also I would assume your charm code only needs to be open source if you are uploading it to the store. Local deployment etc wouldn't apply... -- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)5603641316 (Thanks to the Saiku community we reached our Kickstart

Use of Jujucharms to launch non-opensource code

Hello Jujucharmers, If one use Jujucharms in commercial projects where non-open source code is deployed using jujucharms, is this bound by AGPL ? I understand that modifying jujucharms code itself would call for open sourcing it. Are there any known commercial uses of jujucjarms ? regards

Re: Use of Jujucharms to launch non-opensource code

You can deploy proprietary software with a juju charm. However, the code for the charm (what installs the proprietary software) should have an open source license. -- José Antonio Rey On Sun, Feb 7, 2016, 23:01 Ramesh Nethi wrote: > Hello Jujucharmers, > > If one use

Re: Use of Jujucharms to launch non-opensource code

Could you elaborate on your usage? Are you wrapping Juju itself in a commercial project, using the charms in a commercial project, or producing a commercial charm? Either way, IANAL, so my responses would be moot, but I can try to offer some guidance. Marco On Sun, Feb 7, 2016 at 11:01 PM