Cisco Cisco MediaSense Release 9.1(1) Licensing Information

be called something other than 'show w' and 'show c'; they could even be 

mouse-clicks or menu items--whatever suits your program. 

 

You should also get your employer (if you work as a programmer) or your 

school, if any, to sign a "copyright disclaimer" for the program, if 

necessary.  Here is a sample; alter the names: 

 

 Yoyodyne, Inc., hereby disclaims all copyright interest in the program 

 'Gnomovision' (which makes passes at compilers) written by James Hacker. 

 

 <signature of Ty Coon>, 1 April 1989 

 Ty Coon, President of Vice 

 

This General Public License does not permit incorporating your program into 

proprietary programs.  If your program is a subroutine library, you may 

consider it more useful to permit linking proprietary applications with the 

library.  If this is what you want to do, use the GNU Library General 

Public License instead of this License.

 

HAPROXY's license - 2006/06/15

 

Historically, haproxy has been covered by GPL version 2. However, an issue

appeared in GPL which will prevent external non-GPL code from being built

using the headers provided with haproxy. My long-term goal is to build a core

system able to load external modules to support specific application protocols.

 

Since some protocols are found in rare environments (finance, industry, ...),

some of them might be accessible only after signing an NDA. Enforcing GPL on

such modules would only prevent them from ever being implemented, while not

providing anything useful to ordinary users.

 

For this reason, I *want* to be able to support binary only external modules

when needed, with a GPL core and GPL modules for standard protocols, so that

people fixing bugs don't keep them secretly to try to stay over competition.

 

The solution was then to apply the LGPL license to the exportable include

files, while keeping the GPL for all the rest. This way, it still is mandatory

to redistribute modified code under customer request, but at the same time, it

is expressly permitted to write, compile, link and load non-GPL code using the

LGPL header files and not to distribute them if it causes a legal problem.

 

Of course, users are strongly encouraged to continue the work under GPL as long

as possible, since this license has allowed useful enhancements, contributions

and fixes from talented people around the world.