Slashdot Mirror
OSI Approves Two New Licenses
An anonymous reader writes "The Open Source Initiative approved two new licenses. One, the Academic Free License is a MIT/BSD-like license . The other one, the Open Software License is an apparently GPL-incompatible "viral" license with some obnoxious clauses. Both have an interesting "mutual termination for patent action" clause - basically, the license terminates if you file a lawsuit in any court against any software that is licensed under an OSI approved license containing the same clause."
But that 'external deployment' stuff restricts how you may *use* the software, not just how you may distribute copies. It seems like enough to make the program non-free. Consider the DFSG: 'no discrimination against fields of endeavour'. Doesn't that mean no special requirements for using the program in a web page as opposed to a command-line app?
Also this means that the licence becomes an EULA, because it purports to restrict use of the software and not just to grant permissions for copying. The GPL's enforceability is based on copyright, but copyright (in most countries) does not require you to get permission before merely running a computer program.
Look at the text: 'you agree that any external deployment shall be deemed a distribution'. But you can't 'agree' that unless the licence is considered some kind of contract. With the GPL, it is up to copyright law to decide what counts as distributing the software. Here the licence attempts to extend copyright to count all sorts of random things as infringement, but I don't see how a court would agree with that.
Personally I've long since given up taking notice of anything the Open Source Initiative certifies. Ever since they gave their stamp of approval to that Apple licence which allows 'revokation' at any point in the future when Apple's lawyers decide not to contest a patent infringement in court. The FSF may wrap its pronouncements in ideological justification which is offputting to some, but at least when they say that a program is free software you can be sure it is.
-- Ed Avis ed@membled.com
In that regard, if the idea is to protect the developer (and OSI / OSS / FS developers in general) from a lawsuite, why not just say "by accepting this license, you agree not to file lawsuites against any OSI / OSS / FS software developer?
Because then nobody would use the software, probably even including you. Imagine the following hypothetical:
Some 31337 h4x0r roots your box. This rooting of your box costs you lots of money (say he stole your credit card number, or took down your business website, or something). It just so happens that this particulat 31337 h4x0r also contributed some code to $yourGPLdMailClient. Instead of being able to sue the little brat, you're high and dry.
Now, if we limit the clause to "licensees may not sue any OSS developer for patent infringement", the problems you or I would have using the software go away. However, this is a Bad Thing for large-scale corporate adoption of OSS. If the company has any software patent portfolio at all, their legal department will demand that all OSS stays off all of their boxen, since otherwise they may as well forget about ever enforcing their software patents on anyone. (Say I'm sued for doing some really egregious and horrible software patent infringement. But hey -- I once contributed some code to Mozilla! I'm off the hook!)
Rosen's license is cool, but scary. It's far too easy to come up with hypos that make patent-suit-stopping clauses bad news.