3 ms·
> Ignoring the ad hominem attacks The presentation itself discusses the fall of OpenSolaris and the lack of Sun/Oracle support for it, as though if Sun or Orac
by JoshTriplett 12y ago
> Ignoring the ad hominem attacks
The presentation itself discusses the fall of OpenSolaris and the lack of Sun/Oracle support for it, as though if Sun or Oracle was fully committed to it, it would have succeeded. My mentioning and questioning that, and referring to it as spin, is not at attempt at an ad hominem attack; it's an attempt at a well-founded argument.
> I didn't actually advocate a contributor agreement -- to the contrary, I cautioned against them.
You cautioned against copyright assignments (and thank you for that), but regarding contributor agreements you said (on slide 21) "Corporate entities may (and indeed, should) have a contributor agreement ..."
Have I missed something there?
> And indeed, the reason that this two-year-old presentation is on HN today is because today we did away with the node.js CLA[1]; we're walking the talk here.
A change that's deeply appreciated; thank you for doing that.
Regarding the licensing: I'm not going to quibble over intent, but intentional or not, it had the same effect. The MPL and its various forks were well-known as GPL-incompatible licenses; that was not hard to predict, and people started talking about it right away. Even if you had proprietary binary-only components, you could still use the GPL with an explicit exception, or alternatively any number of GPL-compatible FOSS licenses, rather than something GPL-incompatible. You could also use a dual-license with GPL or LGPL, providing GPL compatibility along with any other license you might wish to use, as OO.o once did (dual LGPL/SISSL).
More importantly, it seems quite disingenuous to release software under a GPL-incompatible license and then complain that the GPL caused the problem and fragmented the community ("Was it the intent of those who licensed their work under GPLv2..."). If nothing else, I'd suggest that we both should make fewer assumptions about intent, and talk about results instead.
Finally, I'm certainly not going to dispute that more new projects have arisen using non-copyleft licenses. That hardly makes the GPL obsolete, nor does it invalidate the large number of existing GPLed projects. More importantly, GPL compatibility remains critical; people choosing all-permissive licenses still tend to choose GPL-compatible ones, Apache being the most notable exception (and it still has GPLv3 compatibility).