Working Toward a Patent-Agnostic Open Source License
Glyn Moody writes "Are there ever circumstances when software patents that require payment might be permitted by an open source license? That's the question posed by a new license that is being submitted to the Open Source Initiative (OSI) for review. The MPEG Working Group wants to release a reference implementation of the new MPEG eXtensible Middleware (MXM) standard as open source, but it also wants to be able to sell patent licenses. If it can't, it might not make the implementation open source; but if it does, it might undermine the fight against software patent proliferation."
It's just a way of trying to make software patents more valid.
I would say that any patent that lacks hardware (chemical compound or physical device) wouldn't be valid.
If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
They should use the BSD or MIT licenses if they're more interested in releasing code than promoting public policy. It would provide the key functionality they claim to need without dragging their whole process through the muck and mire.
I think it boils down to this. The open source community can feel free to contribute code and documentation to our project. But we will feel free to keep you from being able to run it on an open source platform and we have the force of patents to stop you. If you want to fork the code we just drop the patent bomb.
The MPEG group and the other douche bags they hang with are the most anti open source group there is. Am I ever going to play Blu-ray movies on my Linux computer? Not likely.
It really seems to me that in common use "Open Source" *does* now mean you are free to do whatever you want with the source. Just being able to *look* at the source is not called Open Source, it is probably best to call it "published source code" or "the source code is available for you to look at".
"Free Software" means the enforced-freeness of the GPL, which is a subset of Open Source.
So for most uses this is neither Open Source or Free Software.
The open source definition is a set of 10 criteria that "distribution terms" (i.e. a copyright license) must meet to be legitimately called "open source". The problem is that, if you're dishonest (and many people are), you can still use patent law or other means to render most of those criteria moot while still nominally meeting them.
On the other hand, FSF's free software definition only deals with the necessary results of those rules, rather than the rules themselves. It doesn't matter whether somebody's lawyers have figured out a clever way to cover all the "open source" checkboxes, unless you have the actual, meaningful freedoms to run, study, adapt, improve, and redistribute a program (including improved versions) to anyone for any purpose at any price, then the program is not free software.
The FSF has a fairly decent (and reasonably fair) comparison of "free software" vs "open source", entitled Why "Open Source" misses the point of Free Software
"Agnostic" comes from roots meaning "not knowing", but its use in the sense of "not having an opinion about" is well-established.
Would it kill you to check a dictionary before trying to go all vocabulary-Nazi on someone? :-)
Tom Swiss | the infamous tms | my blog
You cannot wash away blood with blood
Does this mean that the source code would be freely available, but that you couldn't use it without paying them? I skimmed the artical and linked pages, but can't figure out what this would actually mean.
TFA says that it includes a patent covenant not to sue two classes of people: Those distributing only the source, and those compiling for 'internal purposes' only.
It seems to me that the second case would handle e.g. Linux users that compile and run the code on their machine, and use it to view content. The first case is less clear, it seems that it might be intended to cover people 'working' with the code, and that might possibly extend to Linux distros that distribute the code (but not binaries) to their users (who can then compile it).
Not sure if it's achieved, but the goal seems to be to sell patent licenses to big corporations that make lots of money off of this sort of thing, while not bothering with individuals and hobbyists.