News for hackers. Stuff that matters.
Re:Riak and the demise of Basho by pron on Wednesday September 06, 2017 @12:01PM (#15184684)
If your organization uses any of: Linux, Android, emacs, gcc or any GNU utility, OpenJDK, or MongoDB, then GPL is clearly not a no-go. GPL only poses issues when the product is a library. For standalone products or ones with linking/access exceptions like OpenJDK, GPL poses no issues, and organizations aren't afraid to use it, especially when they don't intend to modify it.

GPL is a great license that ensures that improvements to the product are shared back with the community. In fact, for a database like Riak, Affero GPL, like the MongoDB license may even be better, as organizations that make improvements to Riak but don't redistribute it but run it internally on their servers would also be required to contribute back their modifications.

Re:Riak and the demise of Basho by mirashii on Wednesday September 06, 2017 @12:43PM (#15185043)
> If your organization uses any of: Linux, Android, emacs, gcc or any GNU utility,

Two things wrong with this right off the bat. First, not all of these are GPLv3, which is the version with the problematic patent clauses that scare companies away. Second, it is not just in libraries that the GPLv3 is generally accepted to pose potential issues. You need look no further than Apple and the great investment they went through to avoid ever shipping GPLv3 software. The GPL kicks in as soon as you distribute the software.

Re:Riak and the demise of Basho by pron on Wednesday September 06, 2017 @04:26PM (#15186858)
> First, not all of these are GPLv3, which is the version with the problematic patent clauses that scare companies away.

So, if Linux were GPLv3 you're saying that most companies wouldn't use it?

> You need look no further than Apple and the great investment they went through to avoid ever shipping GPLv3 software.

Most companies aren't like Apple.

> The GPL kicks in as soon as you distribute the software.

That's right, and that's a good thing. If you distribute GPL software that you modify, you need to make your modifications public. But as Riak is not a library, it does not infect any other component. If you distribute software with (say, Android) Linux but don't modify Linux then the GPL doesn't infect the other components of your software, as they're not actually linked (or Linux has some explicit exceptions).

Re:Riak and the demise of Basho by romwell on Wednesday September 06, 2017 @11:12PM (#15188913)
> GPL only poses issues when the product is a library

What about the client libraries? Do you consider them to be a part of the product? It might make sense to release the client code (library) and the server code under different licenses (Apache2/GPL, respectively) if GPL is to be used.

Re:Riak and the demise of Basho by pron on Thursday September 07, 2017 @07:16AM (#15190713)
> It might make sense to release the client code (library) and the server code under different licenses (Apache2/GPL, respectively) if GPL is to be used.

Yep.

Re:Riak and the demise of Basho by atonse on Wednesday September 06, 2017 @02:25PM (#15185931)
That's a valid point, GPL is especially scary for libraries, less so with server software. Maybe I was a bit hyperbolic. :)