> If, for example, my company takes a GPLd program and modifies it, we could use > it in-house with impunity, but we could not distribute it to anyone else > without including *the sources for any changes we made*. > > We aren't compelled to distribute those changes, though, merely because > we *made* them to GPLd code.
While we're on the subject, I'll chip in with the reason I chose LGPL for PyKaraoke. In the interest of widespread usage of the PyKaraoke modules, I specifically wanted to allow anyone to import and use it within their own applications without fear of having to open up the rest of their code (i.e. the non-PyKaraoke parts). I'm not sure what the consensus is with respect to GPL on whether importing a Python module would cause the rest of your code to be GPL, but for the avoidance of doubt I went with LGPL. Cheers, Kelvin. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Pykaraoke-discuss mailing list Pykaraoke-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pykaraoke-discuss
