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, and using that code as commercial project, then changes to Juju need to come back - as part of the AGPL. Tim On 09/02/16 05:17, Ramesh Nethi wrote: > 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 <marco.ce...@canonical.com > <mailto:marco.ce...@canonical.com>> wrote: > > 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 Ramesh Nethi <ramesh.ne...@gmail.com > <mailto:ramesh.ne...@gmail.com>> wrote: > > 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 > Ramesh > > -- > Juju mailing list > Juju@lists.ubuntu.com <mailto:Juju@lists.ubuntu.com> > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
