News for hackers. Stuff that matters.
Re:Riak and the demise of Basho by andrew_deane_ on Wednesday September 06, 2017 @08:19AM (#15183008)
Today bet365 have signed the agreement to purchase all Basho IP. We expect the agreement to be ratified in the US courts next week. Once cleared, our intention is to open source all code, help rebuild the community and collaboratively take the development of RIAK forward.

In the coming weeks we will hopefully answer the questions people have and will be calling on the community to help forge the initial RIAK Roadmap.

One of the initial questions we have for the community is which OSS license would people like applied to the code? Our thought is the most open and permissive.

Re:Riak and the demise of Basho by ex_amazon_sde on Wednesday September 06, 2017 @01:14PM (#15185315)
GPLv3, as it protects from patent trolls and also encourages creating an better ecosystem.

There are companies that refuse to use GPLed code. They want to modify and then sell closed forks of your product, without paying you, and by doing so they fragment the userbase. GPL prevents this.

If you want to allow them to do so you can always switch to BSD or dual-license - perhaps after a private agreement and if you find the companies reputable.

Re:Riak and the demise of Basho by exbet on Wednesday September 06, 2017 @09:29AM (#15183494)
Would make sense to use the same license as Erlang - Apache2
Re:Riak and the demise of Basho by elcritch on Wednesday September 06, 2017 @12:34PM (#15184967)
Fantastic news! I just used Riak Core for making a multi-master service. It was impressively straightforward! Glad to hear there are people intents to continue the project as OSS.

Will this include the Basho technical documents? Much of the better technical documentation lives on basho.com and was returning 404's.

[edit: and a +1 for Apache V2 (or MPL)]

Re:Riak and the demise of Basho by gordonguthrie on Thursday September 07, 2017 @07:46AM (#15190892)
Re:Riak and the demise of Basho by romwell on Wednesday September 06, 2017 @11:08PM (#15188902)
Great! There aren't that many persistent (disk-based) KV-stores out there. I planned to, but didn't get to actually use Riak, and was sad when the company seemed to go down.

As far as licensing goes, it would be great to have one that would allow me to link the client code libraries and run the servers without having to worry about anything. If I understand correctly, Apache2 goes way beyond that, while GPL is somewhat ambiguous on that. (Yes, one could implement their own client, but that'd be reinventing the wheel).

Thank you for keeping this work alive!

Re:Riak and the demise of Basho by kuwze on Wednesday September 06, 2017 @09:57AM (#15183664)
GPLv3 and Apachev2 are the best in regards to dealing with patents.
Re:Riak and the demise of Basho by atonse on Wednesday September 06, 2017 @10:56AM (#15184161)
Please don't do GPL – It's a no-go and too restrictive for a lot of organizations.

Apache 2 or MIT would be the most permissive.

Re:Riak and the demise of Basho by jhoechtl on Wednesday September 06, 2017 @11:34AM (#15184459)
You mean its a no go for a company to go away with the work of others without giving credit beside naming?

Strange world we are living in ...

Re:Riak and the demise of Basho by atonse on Wednesday September 06, 2017 @02:30PM (#15185963)
As I replied below, the distinction between libraries and servers is a good one. I was too extreme in my statement without making that distinction.

For libraries, yes, absolutely, companies should rightly be cautious, because it's relatively easy to expose yourself to legal risk.

Nobody is "going away with the work of others" – the whole point of a license is so contributors decide how others can use their work. What exactly is the issue here?

Re:Riak and the demise of Basho by bluejekyll on Wednesday September 06, 2017 @02:28PM (#15185950)
GPLv3 is for a lot of companies too aggressive on requirements around patent defense, etc. Though many were never fond of the copy-left nature of GPLv2(and 1), they allowed it. GPLv3 upped the bar, to a degree that many lawyers won't sign off on its use.

Apache 2.0 is the standard for almost every company I've dealt with, with MIT and BSD 3 clause being accepted as well. But Apache 2 seems to make most lawyers happy.

Re:Riak and the demise of Basho by maheart on Thursday September 07, 2017 @09:23PM (#15197241)
You say the GPLv3 is too aggressive on requirements around patent defense, but the Apache 2.0 is okay? The Apache 2.0 license requires a patent grant. How do they differ in the patent grant?

I'd speculate that for many companies the GPLv3 is too strong in its copy-left stance, by disallowing Tivoization.

Re:Riak and the demise of Basho by belorn on Friday September 08, 2017 @01:00PM (#15201915)
GPLv3 patent text was created by literally copying the part from the Apache 2.0 text, and then adding a paragraph to handle patent agreements such as the one between Novel and Microsoft.

The distinction between the two text is case of paten agreements.

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. :)
Re:Riak and the demise of Basho by grkvlt on Wednesday September 06, 2017 @10:50AM (#15184111)
I think APACHE-2.0 is probably the best for end users in terms of acceptability in enterprises etc. A lot of places have issues with the virality of GPL licensing.
Re:Riak and the demise of Basho by AlimJaffer on Wednesday September 06, 2017 @10:57AM (#15184166)
Seconded on Apache-2.0 - it's what we use. GPL is not attractive to enterprise and will limit the adoption of the tech.
Re:Riak and the demise of Basho by aaronchall on Wednesday September 06, 2017 @11:35AM (#15184466)
Anecdotally, those who decide to use GPL don't like the results - users are afraid to extend functionality, and conscientious extenders provide code that specific to their use-case and that can't be used.
Re:Riak and the demise of Basho by mst on Wednesday September 06, 2017 @02:22PM (#15185906)
I think the GPL worked brilliantly for forcing companies to e.g. contribute gcc ports to the commons.

But that doesn't mean it would work for most projects.

Re:Riak and the demise of Basho by arielweisberg on Wednesday September 06, 2017 @11:15AM (#15184318)
-1 on GPL. Apache 2 generates very little friction.
Re:Riak and the demise of Basho by rurban on Thursday September 07, 2017 @02:30AM (#15189540)
Re:Riak and the demise of Basho by zzzcpan on Wednesday September 06, 2017 @08:21AM (#15183019)
Like BSD or MIT licenses? That would be great.
Re:Riak and the demise of Basho by catwell on Wednesday September 06, 2017 @08:39AM (#15183111)
Apache 2 is probably the best choice here to avoid potential future issues related to patents.