Re:Badger – A fast key-value store written natively in Go
by codebeaker on Monday May 15, 2017 @09:37AM
(#14341417)
Having just gone through a lengthy review process identifying a suitable license for our soon to be open-source software which has a commercial aspect, and selected AGPLv3, I'm very curious to know what companies have it "categorically banned". We did some research and didn't find that anyone had an issue with it. Whilst AGPL does open up come grey-areas which aren't as well understood as GPL the general reason to use it seems to be as part of a dual licensing scheme where companies with AGPL issues can simply purchase a non-transferrable limited MIT license or similar.
Can you give me any more info on your sources?
Re:Badger – A fast key-value store written natively in Go
by tpush on Monday May 15, 2017 @12:35PM
(#14342921)
Google bans it for example: https://opensource.google.com/docs/using/agpl-policy/.
I would also be surprised if Apple (being so allergic to the GPLv3) used AGPLv3 software, though that's just speculation.
Re:Badger – A fast key-value store written natively in Go
by zellyn on Tuesday May 16, 2017 @01:52PM
(#14351681)
There's a perennial discussion of AGPLv3 here on hacker news. A surprising number of projects select it, then revert to something less toxic to corporations.
Re:Badger – A fast key-value store written natively in Go
by sangnoir on Monday May 15, 2017 @08:40AM
(#14341074)
> I think what fortytw2 was trying to say is that the AGPL is not a wise choice for software that wants to gain the most popularity and usage as possible
Why should that be a laudable goal? Not all projects are megalomaniac.
As an aside, one can certainly describe something as draconic(or whatever else) if one views it as such; it's just an opinion.