4 ms·
From TFA: "Divide the functionality into open source and commercial parts. Use a GNU license and a commercial license for the respective parts." I really don'
by notacoward 12y ago
From TFA:
"Divide the functionality into open source and commercial parts. Use a GNU license and a commercial license for the respective parts."
I really don't want to be That Guy, but this sentence takes us away from full-time open source. At least part time is spent working on source that's not open. "Open core" is the most common term for this hybrid strategy. I'm not going to get into the debate about whether that's a valid strategy, but it does make the headline misleading.
- warcode 12y agoI'd say you are correct. How is this different from just having a commercial and non-commercial license? At least then people don't get locked out of features by not paying.
- davidw 12y agoI think you're right. It's all about scarcity, ultimately: http://journal.dedasys.com/2007/02/03/in-thrall-to-scarcity/ http://journal.dedasys.com/2007/02/03/in-thrall-to-scarcity/ It can be very tricky to find something that's scarce enough with an open source project to make money at it. In any event, I'm happy for him!
- jordigh 12y agoYeah, fully free would be something like selling GPL exceptions for the exact same product. I really like selling exceptions. The product is available to everyone in its entirety without restriction, but the copyright holders are the only ones who can sell non-copyleft versions of it. Everyone else can still sell it under the terms of the GPL, like selling Debian CDs. It shifts the scarcity in a different direction, treats everyone fairly, and everyone who creates derivative works pays: either by giving back code or by paying for the privilege to not give back code. Selling exceptions seems to me to be the right way to commercialise the actual product itself instead of support around that product. I know of FFTW and hg4j who do this now, and Qt used to do it. It's a good business model.
- jamespo 12y agoWhen the software is typically used for SAAS products and not "distributed" in the same way as something using eg Qt libraries the business case isn't as compelling however.
- jordigh 12y agoIn that case, you sell AGPL exceptions.
- sanderjd 12y agoIs there any really good documentation (book, article, series, etc.) on all the different models for this sort of thing, how they work, and it what situations they are appropriate?
- davidw 12y agohttp://en.wikipedia.org/wiki/Business_models_for_open-source_software http://en.wikipedia.org/wiki/Business_models_for_open-source... is a decent starting point.
- sarciszewski 12y agoNot that I've seen, but there should be. Maybe we can motivate some lawyers to put something together? :D
- sanderjd 12y agoYeah a "from the trenches" collaboration between some people who have taken different approaches and the lawyers who worked with them would be really valuable to me. (Hint: if anybody fits that description, I'm saying I'd pay good money for it!)
- saosebastiao 12y agoIt is worth noting that this is also the opinion of RMS.
- dangoor 12y agoYou're right in this case. There have been a number of other cases where the whole software is open source (under a GPL or AGPL license) and the author sells a "non-viral" commercial license. Qt comes to mind as an example of this. In this particular case, the author seems to be doing a hybrid. The original library is LGPL. If you buy the "Pro" version, you not only get the closed source bits but you also get a non-viral license for the open source bit. The headline does indeed seem misleading though. FWIW, I've been earning a living via open source software since late 2007 – I've just been doing it as a full-time employee at companies (SitePen, Mozilla and now Adobe).
- sroerick 12y agoLets forge a path to FLOSS software, eh?