6 ms·
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
by andrew_deane_ 9y ago
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.
- romwell 9y agoGreat! 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!
- rurban 9y agoRiak and riak core are already Apache 2. Sounds fine. https://github.com/basho/riak/blob/develop/LICENSE https://github.com/basho/riak/blob/develop/LICENSE https://github.com/basho/riak_core/blob/develop/LICENSE https://github.com/basho/riak_core/blob/develop/LICENSE
- zzzcpan 9y agoLike BSD or MIT licenses? That would be great.
- catwell 9y agoApache 2 is probably the best choice here to avoid potential future issues related to patents.
- exbet 9y agoWould make sense to use the same license as Erlang - Apache2
- kuwze 9y agoGPLv3 and Apachev2 are the best in regards to dealing with patents.
- grkvlt 9y agoI 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.
- AlimJaffer 9y agoSeconded on Apache-2.0 - it's what we use. GPL is not attractive to enterprise and will limit the adoption of the tech.
- aaronchall 9y agoAnecdotally, 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.
- mst 9y agoI 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.
- atonse 9y agoPlease 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.
- jhoechtl 9y agoYou 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 ...
- elcritch 9y agoFantastic 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)]
- gordonguthrie 9y agohttps://www.tiot.jp/riak-docs/ https://www.tiot.jp/riak-docs/
- ex_amazon_sde 9y agoGPLv3, 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.