|
|
|
|
|
by boomboomsubban
2116 days ago
|
|
I'm saying that Oracle couldn't retract the releases already released under a free license, getting rid of OpenZFS altogether. They can and have relicensed the codebase, but we can just pull from the last version released under the CDDL. From my understanding of open source projects released under a new license, they often can create a similar fork at the license change time where a version exists under the old license too. The exception is if they use the GPL version that allows updating the license |
|
Nobody is suggesting they retract older version. In fact the exact opposite has been said on multiple occasions: any new license would be signified by a semver (semantic version) bump. So you're arguing against a point that was never made in the first place.
> getting rid of OpenZFS altogether
OpenZFS code would be unaffected because it's forked from a version prior to the semver re-license bump.
> From my understanding of open source projects released under a new license, they often can create a similar fork at the license change time where a version exists under the old license too.
Fork or semver bump. Which is exactly what I was talking about. Also notice that what you described there contradicts what you said would happen ("getting rid of OpenZFS") in literally the same comment.
---
If Oracle own the copyright then Oracle can re-license. They'd have to bump the version number and the previous versions with the older license would forever remain CDDL. But legally they can do it and it wouldn't affect OpenZFS licensing (aside that OpenZFS might then no longer be able to incorporate ZFS code -- assuming ZFS's new license is incompatible with CDDL. But things start to get very murky down that road.)