Michael Bell wrote:
Hi Oli,
GPL means, every modification you make to the code must go back to the
project.
This is my idea of GPL too.
The GPL certainly allows people to make modifications to code without
contributing it back to the project. And it might very well be that
projects are not interested in the type or quality of all modifications
which are submitted as patches :-)
If you just make the source code of the modifications available with the
distribution of the package, then you have satisfied the GPL. For
example, if I take a GPL package and add a new feature for my customers,
the only people I am required to provide those source code modifications
to are my customers. However, nothing stops them from contributing said
code back to the project... As well, I could simply make the patch
publicly available via my website - linksys does this with their WRT54G
linux modifications.
Also, there are very many companies who modify GPL code for internal
usage. As long as they don't distribute the modified package outside of
the company, they aren't required to provided those changes to anybody.
--
mike
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
OpenCA-Devel mailing list
OpenCA-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openca-devel
