[ Services ] [ Documentation ] [ Community ] [ About ] [ Contact ]
This FAQ contains some information on common questions asked by vendors using GPL licensed executable code.
This is not legal advice. If you have doubts consult a legal advisor.
Fix it. This works in exactly the same way as you would fix a violation of a proprietary software license.
If you violate the licence on GNU/Linux you are violating the copyright of countless parties, including companies like Intel, IBM and HP; all three companies have copyright on significant portions of the Linux kernel. Violation is a serious matter and must be rectified.
There are a variety of sources of help and information. The first port of call should probably be your supplier of GPL software components. You may also wish to consult a lawyer. The GPL licence is written to be as clear as possible but a lawyer can be helpful for complex issues like derivative works.
Sites such as Savannah can help by providing hosting for GPL versions of software.
The biggest contribution you can make to the community is giving access to code. One of the most useful things that a company can do is to contribute back changes they made. Putting the software somewhere accessible to all like Savannah is really helpful too. Some vendors try and build communities around code and get involved with community development, others simply release it and forget about it. The choice is yours.
No. Your duty is to provide either the source code of the GPL components or a written offer to provide the source code for no more than the cost of delivery. There is no obligation to third parties, there is no obligation to support software created using your changes. The GPL also includes warranty disclaimers.
It is possible to meet the license requirements simply by including a copy of the GPL licence in the application manual, and appropriate credit and a zip file of the relevant source code on your product CD-ROM.
The only situation where GPL code might cost you a lot is if you set out to violate the licence.
Copyright (c) 2004-2006 The gpl-violations.org webmaster
Copyright (c) 2006 FSFE e.V.