Has anyone ever NOT used Ogre because of LGPL?
Personally I don't see why anybody would ever be scared off anymore considering you can purchase the OUL at any time if you decide you don't like the terms of LGPL licensing. And if you're releasing a game the tiny cost of an OUL license is the least of your concerns.
source
How Does The LGPL Apply To Web and defining distribution?
The two major restrictions on the LGPL are modification and dynamic linking. The LGPL was written with compiled languages in mind, and since JavaScript is not compiled, I do not understand how it can be linked. As it stands, the LGPL and JavaScript are a poor combination.
source
How many developers would use LGPL library code in their own projects?
I would use an LGPL library, if it doesn't clash with the licensing conditions and other requirements of the project I am working on. For example, as I understand it, the LGPL code has to be replaceable by the user if something changes, such as a new version being released. If there are versioning requirements that clash with this, I couldn't use the code.
source
What are the extents of the meaning of "distributing" under the LGPL license?
Any time you give someone else a copy of some software you have distributed that software. It does not have to be to the public at large to qualify as distribution.
source
Does the GPL license contaminate?
If you are the original copyright owner, then you can release a copy or a modified work under any license you like. That doesn't change the license of the previously released software of course.
source
)