5 ms·
Corporate Open Source Anti-patterns (2012)
- tbirdz 12y agoI take issue with some of the points regarding the GPL license. The author says that "GPLv2 has prevented the integration of of open source technologies like DTrace and ZFS in Linux." However, surely this is also the fault of the CDDL rather than the GPL alone. The CDDL license was written after the GPL, and according to some sources was specifically designed to be GPL incompatible.
- mattl 12y agoYes, I've heard that was explicitly designed to be incompatible with the GPL.
- api 12y agoSlide 16 is absolute genius. If you're doing any kind of business with OSS, tattoo it on your forehead.
- JoshTriplett 12y agoThis presentation has an absurd amount of spin. It extensively discusses OpenSolaris, without raising the most important issue there: taking an unwanted and unloved project and making it open will not suddenly turn it into a good project everyone wants to use. Sun seemed to think that people would flock to Solaris, without realizing the exceptionally high bar for any non-Linux POSIX OS to take any mindshare from Linux; OpenSolaris didn't even manage to match the success of BSD, let alone Linux. The anti-copyleft discussion comes out of the same bitterness. Sun intentionally made OpenSolaris non-GPL-compatible, almost certainly because they didn't want Linux to adopt code from it; who would want to run OpenSolaris if all the interesting bits of it run on Linux instead? Copyleft is not obsolete; it'd be fair to say that some substantial communities exist around non-copyleft software (for instance, Android, or Ruby modules), but that's not the same thing. In any case, the lesson is "don't use a license incompatible with the GPL". Counting lines of code under various licenses is not a particularly useful metric, unless you take usage and mindshare into account. And counting code under GPL-compatible licenses will still show that the vast majority of FOSS code retains compatibility with the GPL. (Apart from an island of Apache code, compatible with GPLv3 but not GPLv2.) MPL is not a particularly good recommendation: it's GPLv3 compatible, but not GPLv2 compatible. If you want a weaker copyleft than the GPL, use the LGPL. Advocating a contributor agreement is a bad idea. Anything more heavyweight than "Signed-off-by", especially something requiring a signed contract, adds a significant barrier to contribution. At least this presentation doesn't recommend copyright assignemnt, though. Dual-licensing is a completely reasonable business model, and it doesn't require spreading FUD. The dual-licensing model just boils down to "free for FOSS software, pay us for proprietary software"; simple as that, unless you consider copyleft itself a problem as this presentation seems to. The bits about competitive paranoia and about forking/control do make sense, and provide useful advice that more projects need to follow.
- bcantrill 12y agoIgnoring the ad hominem attacks, I didn't actually advocate a contributor agreement -- to the contrary, I cautioned against them. 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. As for your misunderstanding of history with respect to OpenSolaris licensing: the decision to use a modified MPL (i.e., the CDDL) and not the GPLv2 had nothing to do with Linux (indeed, none of us predicted that the GPL would be so ardently perceived to be incompatible with the CDDL) and everything to do with the fact that (due to various covenants and agreements), we couldn't actually open source everything. That is, we needed to allow for proprietary in-kernel code from both ourselves and from third parties -- and we didn't want to end up in the legal no-mans land of "tainted" kernels. Simon Phipps has been very clear about this[2]: The difficulty with using the GPL was that it became clear as we did the licensing archaeology that there were going to be places in the software where we couldn't negotiate a free license for the source code. And, there were going to be some quite important places in the code, and there were going to be quite a lot of them for a long time. And, that was probably the deciding factor not to use GPL but to use the Mozilla license. Finally, I stand by my assertion that the GPL is in decline relative to MIT/BSD/Apache -- a trend that I elaborated on after my FISL talk[3] and has only accelerated in the two years since, declining from 36% to now 27% of projects.[4] [1] http://www.joyent.com/blog/broadening-node-js-contributions http://www.joyent.com/blog/broadening-node-js-contributions [2] http://www.linuxjournal.com/article/9624 http://www.linuxjournal.com/article/9624 [3] http://dtrace.org/blogs/bmc/2012/08/01/post-revolutionary-open-source/ http://dtrace.org/blogs/bmc/2012/08/01/post-revolutionary-op... [4] http://www.blackducksoftware.com/resources/data/top-20-open-source-licenses http://www.blackducksoftware.com/resources/data/top-20-open-...
- 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).
- Groxx 12y ago"The companies that adopt your technology are nearly tautologically not your competitors..." I don't follow. If they're using your tech (which you developed to do business) to do business, why are they clearly not competing with you?
- sokoloff 12y agoWatch the video: http://www.youtube.com/watch?v=NhgXQFk9noI http://www.youtube.com/watch?v=NhgXQFk9noI The slides don't exactly stand fully alone. I love watching the "bcantrill show". This video's audio is horrendous, but he explains what he means on that slide pretty well, starting at about 38m20s.
- Groxx 12y agoExcellent, thanks for that link! The argument seems to rest entirely on the shoulders of "NIH prevents them from ever touching your source". I very very very much don't believe this, especially if they know they're competing with you. Even if they don't use it directly (because, lets face it, it's probably crap for their precise needs), they can learn a lot from looking at it, for a lot lower cost than what you paid to discover it. It's the same thing as arguing copyrights / patents are entirely useless for the holder because nobody who competes with you would ever even consider looking at what you're doing. How is this not nonsense? The main (loud) complaints about e.g. patents revolve around them working too well for this purpose, giving too much of an advantage to the first mover, and suppressing others from using what is otherwise valuable to them.
- phkahler 12y agoThe number one ant-pattern is DON"T CREATE YOUR OWN LICENSE. To me there is GPL, BSD, MIT - and I'd have to read to discern the later two. MPL and Apache are there if you want a variation on the main ones. Everyone else creating a new license has some kind of agenda. This was apparent to a lot of us when SUN put out their license AND required assignment. Let me say that again. If you're not using one of the top 5 licenses you've got an agenda and may as well go home.
- bcantrill 12y agoAbsolutely agreed. (After all, the presentation is everything we got wrong, not everything we got right -- and I definitely agree that the world emphatically does not any more open source licenses.) I don't agree that this is the "number one" anti-pattern because we don't see it much anymore: the five licenses that are out there cover a wide range of philosophies and objectives, and one of them should suffice for just about any project.
- cpeterso 12y agoGitHub has a plain-language website that helps you choose an open-source license, though their list of "featured licenses" is just APL, GPL, and MIT. BSD, LGPL, and others are demoted to their list of "other licenses". http://choosealicense.com http://choosealicense.com
- deleted 12y ago[deleted]