News for hackers. Stuff that matters.
Re:Elastic and Amazon reach agreement on trademark infringem... by madeofpalk on Wednesday February 16, 2022 @05:31PM (#30366715)
There is. AGPL + dual licensing.
Re:Elastic and Amazon reach agreement on trademark infringem... by skrtskrt on Wednesday February 16, 2022 @05:43PM (#30366858)
How would dual licensing go down, ideally in these cases?

I figured if that worked, Elastic, Redis, MariaDB, Mongo, Timescale, and Cockroach Labs would have gone that route

Re:Elastic and Amazon reach agreement on trademark infringem... by Macha on Wednesday February 16, 2022 @05:50PM (#30366941)
Start out that way, and you'll find it harder to build a user base. So instead companies have done it as a bait and switch (planned or otherwise)
Re:Elastic and Amazon reach agreement on trademark infringem... by skrtskrt on Wednesday February 16, 2022 @06:20PM (#30367214)
Would it be fair to do something where you start off with the BSL approach where older code automatically becomes fully open source (like GPL or Apache), with the exceptions that the first N versions or N years of work will start off fully open, then the BSL stuff will kick in later?
Re:Elastic and Amazon reach agreement on trademark infringem... by sanxiyn on Wednesday February 16, 2022 @07:16PM (#30367759)
I think this would be fair, and it has been done. Ghostscript had two branches, Aladdin Ghostscript and GNU Ghostscript, where GNU Ghostscript is approximately one year behind.
Re:Elastic and Amazon reach agreement on trademark infringem... by wmf on Wednesday February 16, 2022 @07:36PM (#30367984)
The idea behind dual licensing is that hosting providers would pay for a license and others wouldn't. The arguments that AGPL isn't strong enough are pretty speculative.