Justification: Policy 2.3
http://marc.theaimsgroup.com/?l=xine-devel&m=107261185004445&w=2 , since
they can't find where to contact the author of majormms, either in
majormms website, http://www.geocities.com/majormms/ , and its source,
http://www.geocities.com/majormms/mms_client-0.0.3.tar.gz , it still
can't ensure that the author of majormms will allow relicensing to LGPL
What if later, the majormms's author come out and claim that libmms
violate his license? He may request a fee to compensate for this
What if someone use this package to develop a non GPL program?
This may violate the original purpose of majormms's author, and he may
claim for a compensation.
Can debian relicense this package back to GPL to avoid this conflict?
Now libmms code has 2 parts,
1. The original code of majormms which is still GPL.
2. The code modified by xine project and libmms project is LGPL.
GPL + LGPL ==> GPL ?
BTW: For another point of view, the code with no author name like in
majormms will be protected by the copyright law or not?
If not, it will be public domain?
-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Kernel: Linux 2.6.10-5-386
Locale: LANG=C, LC_CTYPE=thai