This is going on far too long and round in circles. Greg and Alex - pick
something, stick a license on it all , say so publically and be done. It
does more harm now than whichever is picked
I've been through the licenses with respect to embedded system issues
o GPL Means people can't provide nonfree apps of any
kind using nanogui without writing a nonfree library
clone. The only one that stops users writing binary
only extensions/modules.
o LGPL Means people can build apps and servers with some non
free components and programs. This still causes big
problems for some standard embedded uses - DVD is the
big one. The rules on protecting the DVD crypto are
draconic and not the vendors fault. Only when the
DVD cracking is finished would they go away.
o MPL Easier than (L)GPL to add private extensions. Doesn't
require relinkable object modules and the like. Does
require source is made available to MPL'd modules
The MPL is also the only one that sanely reflects embedded system licensing
because it doesn't require written offers of media which are difficult to
manage but instead requires the source is somewhere publically available - eg
for FTP.
Alan
