Why Consider Linux Kernel Patent Risks?
chromatic writes "After the hoopla about OSRM's study of patent risks in the Linux kernel, I talked to Dan Ravicher, the patent attorney and free software afficionado who conducted the study. Contrary to my initial reaction, I've come to believe that the study is actually very valuable. Linux and Patent Risks on the O'Reilly Network explains why."
Visit Tim's Journal, yes?
Linus owns the trademark to the kernel, but not the copyright, except for the portions he wrote himself. As far as I know, Linux does not require copyright assignment as a condition for code inclusion.
Copyright != Patent != Trademark.
No weapon in the arsenals of the world is so formidable as the will and moral courage of free men.-Ronald Reagan
It seems to me that an individual with ordinary skill in the art of developing software, coming up with a patented solution to a problem, poses as much a problem for the owner of a patent as it does for the individual developer.
One of the requirements for granting a patent is that it describe an invention or process that is nonobvious to one skilled in the art...
Even proprietary vendors make their source code available to important customers "to conduct security reviews of the products" - why shouldn't they do the same for Intellectual Property Rights?
Furthermore, you could have third-party auditing companies provide that service in the same way they audit other confidential information such as company finances.
Also, thanks to Groklaw, I learned about this thing called Promissory Estoppel that would pretty much stop them from bringing a patent suit at this point.
-
If somebody decides to sue Linux for copyright
infringement, who defends it?
IBM, Apparently.Bruce
Bruce Perens.
Also, the international treaties covering patents are still evolving (there's a bunch of 'em -- not just WIPO but PLT, PCT, TRIPS and more I'm sure I'm forgetting), so it's still necessary to check out the local laws.