Red hat’s Open Source Assurance program is already used to safeguard customers developing and deploying open source solutions. Red hat now asking court to limit patents on software:
Open source software is one of the most dynamic, innovative sectors of the U.S. economy, but the U.S. patent system is a costly hindrance to open source innovation. We believe that although the patent system was created to foster innovation, it’s simply not an engine for innovation for open source. Software patents were barely recognized when open source began, and so the hope of obtaining a patent did not motivate the first developers. Those pioneers were generally opposed to software patents. The open, collaborative activity at the heart of open source is at odds with the patent system, which excludes the public from making, using or selling a patented invention. Open source developers seek to contribute code to the community – not to exclude others from using the code.
There is also Open Invention Network (OIN) backed by IBN, Red Hat, Novell, Sony and others. OIN is a company that acquires patents and offers them royalty free “to any company, institution or individual that agrees not to assert its patents against the Linux operating system or certain Linux-related applications”. On a related note, Microsoft has claimed that free software such as OpenOffice.org and the Linux kernel violate 235 Microsoft patents and said that it will seek license fees.
=> Read more : Red Hat Asks Federal Court To Limit Patents On Software
This is a must read if you or your organization associated with open source software project. If you are interested in a basic understanding of the legal issues that impact FOSS development and distribution, this primer is for you. The guide, written for developers, has sections on copyrights, trademarks, patents, organizational structure and other legal issues:
First, we provide creative, productive hackers insight on how to interact with the legal system—insofar as it affects the projects they work on—with a minimum of cost, fuss and risk. Second, we present a starting point for lawyers and risk managers for thinking about the particular, at times counter-intuitive, logic of software freedom. While these are the primary audiences we intend to reach, we hope others will benefit from this Primer as well, and we have purposefully given it a non-lawyer style of communication (for example, by intentionally omitting dense citation of judicial or other legal authority that is the hallmark of lawyers writing for lawyers).
While FOSS development can raise many legal issues, a few topics predominate in our work; these are the issues most integral to FOSS projects. This Primer provides a baseline of knowledge about those areas of the law, intending to support productive conversations between clients and lawyers about specific legal needs. We aim to improve the conversation between lawyer and client, but not to make it unnecessary, because law, like most things in life, very rarely has clear cut answers. Solutions for legal problems must be crafted in light of the particulars of each client’s situation. What is best for one client in one situation, may very well not be best for another client in the same situation, or even the same client in the same situation at a later date or in a different place. Law cannot yield attainable certainty because it is dynamic, inconsistent, and incapable of mastery by pure rote memorization
The Legal Issues Primer for Open Source and Free Software Projects is available in following formats:
- Online HTML version
- PDF version [318K]
- Postscript version [1.2M]