Flynn - Open Source PaaS powered by Docker • Hacker News Board

Re: Flynn - Open Source PaaS powered by Docker

#151

Post by girvo » Fri, Jul 19, 2013, 7:25 AM UTC

js4all wrote: post #150

girvo wrote: post #132

Earlier quoted context omitted.

Do you mind explaining that? Would the fact that they use AGPL for Juju matter if you're not hacking on Juju itself? I don't see how it would be an issue, it wouldn't extend to the proprietary software you run on a Juju-setup service, would it? I could be completely wrong, mind you.

GPL is viral and imposes restriction which you can't foresee. A recent example is the AppStore fiasco VLC had. It required a complete rewrite and additional development years to get it in the store just because the original code was GPL. Please think twice before using (A)GPL and make sure you have checked all consequences.

GPL is indeed viral, however it's viral under certain circumstances, not all. AGPL changes some of those circumstances.

I do not believe that _running_ your software on top of AGPL-licensed Juju makes one iota of difference.

The App Store is different: the restrictions the App store adds are at odds with GPL's defined freedoms. Not the same issue here.

Re: Flynn - Open Source PaaS powered by Docker

#152

Post by js4all » Fri, Jul 19, 2013, 4:04 PM UTC

girvo wrote: post #151

js4all wrote: post #150

Earlier quoted context omitted.

GPL is viral and imposes restriction which you can't foresee. A recent example is the AppStore fiasco VLC had. It required a complete rewrite and additional development years to get it in the store just because the original code was GPL. Please think twice before using (A)GPL and make sure you have checked all consequences.

GPL is indeed viral, however it's viral under certain circumstances, not all. AGPL changes some of those circumstances. I do not believe that _running_ your software on top of AGPL-licensed Juju makes one iota of difference. The App Store is different: the restrictions the App store adds are at odds with GPL's defined freedoms. Not the same issue here.

Everything you program that uses Juju's API, automatically also gets AGPL licensed and that's a big no-go for any commercial development.

Re: Flynn - Open Source PaaS powered by Docker

#153

Post by js4all » Fri, Jul 19, 2013, 4:09 PM UTC

markramm wrote: post #146

girvo wrote: post #132

Earlier quoted context omitted.

Do you mind explaining that? Would the fact that they use AGPL for Juju matter if you're not hacking on Juju itself? I don't see how it would be an issue, it wouldn't extend to the proprietary software you run on a Juju-setup service, would it? I could be completely wrong, mind you.

Yea, it's exactly like MongoDB which is also AGPL. Using the database doesn't impose any restrictions on your software. Even hacking on juju to add API'S you for your client software doesn't impose restrictions on the client -- it just means you are subject to the AGPL licence source distribution rules on the patched version of Juju.

Mongo is a different beast, because the mongo client has a GPL exception which allows your code, that is linked to the mongo client, to use a different license. This is a friendly exception, that the mongo developers allowed. Without that exception everything using mongo even over the Internet would automatically also be AGPL licensed.

Re: Flynn - Open Source PaaS powered by Docker

#154

Post by danielsiders » Fri, Jul 19, 2013, 5:28 PM UTC

soapdog wrote: post #46

I wanted to contribute but I am a single freelance developer, I don't have the amount of money shown on the sponsorship options. I would be great to have a USD 50 option there.

We've added a "fill in the blank" contribution option to the form.

Re: Flynn - Open Source PaaS powered by Docker

#155

Post by soapdog » Tue, Jul 23, 2013, 12:05 AM UTC

danielsiders wrote: post #154

soapdog wrote: post #46

I wanted to contribute but I am a single freelance developer, I don't have the amount of money shown on the sponsorship options. I would be great to have a USD 50 option there.

We've added a "fill in the blank" contribution option to the form.

Thanks, just contributed! :D