Elastic promises "open"—delivers proprietary [LWN.net]

Elastic promises "open"—delivers proprietary

Posted Feb 4, 2021 21:12 UTC (Thu) by robert.berger (guest, #69236)
In reply to: Elastic promises "open"—delivers proprietary by IanKelling
Parent article: Elastic promises "open"—delivers proprietary

I am not a lawyer but also thought that Apache 2 does not require a CLA to be changed to a proprietary license. This might also be a reason why its usage is on the rise while copyleft license usage is declining.

to post comments

Elastic promises "open"—delivers proprietary

Posted Feb 5, 2021 15:13 UTC (Fri) by Wol (subscriber, #4433) [Link] (1 responses)

Does Apache 2 allow re-licencing? PROBABLY NOT.

Does it allow mixing with closed code? I think it does.

So no you probably can't *change* Apache 2 to closed, but there is no bar to inluding Apache 2 code in your closed project.

Okay, nit-picking, but get the legal nits wrong and it can be nasty - nits bite!

Cheers,
Wol

Elastic promises "open"—delivers proprietary

Posted Mar 12, 2023 9:10 UTC (Sun) by robert.berger (guest, #69236) [Link]

relicensing:

Here[1] it says: ". What are the Apache License terms & conditions?
The Apache License is a permissive open source software license - so you can release your modified version of the Apache licensed product under any license of your choice..."

"... However, you are required to release all the unmodified parts of the software under the same license (the Apache License)..."

[1] https://www.mend.io/resources/blog/top-10-apache-license-...