[Bug 464804] Review Request: hunspell-fy - Frisian hunspell dictionary

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=464804





--- Comment #2 from Caolan McNamara <caolanm at redhat.com>  2008-10-01 03:41:25 EDT ---
I tried to follow our own documents on this, i.e. 
http://fedoraproject.org/wiki/Licensing/FAQ
and 
http://fedoraproject.org/wiki/Licensing#Frequently_Asked_Questions

"1. What does the code say? If it specifies a version, that's what it is."

and it doesn't :-)

"2. Does the code conflict with itself? (file1.c and file2.c are compiled
together but have different licensing)"

nope

"3. What does the documentation say? ... NOTE: COPYING does not count as
documentation, since the author(s) didn't write it"

Just a link in this case to the GNU LGPL page, which always has the latest
version available on it.

"4. If neither the source, nor the upstream composed documentation says
anything about the license version, then it could be under _ANY_ version of the
GPL. The version listed in COPYING is irrelevant from this perspective.
Technically it could be under any license, but if all we have to go by is
COPYING, we'll guess COPYING is accurate. "

and from the other page we have...

"A GPL or LGPL licensed package that lacks any statement of what version that
it's licensed under in the source code/program output/accompanying docs is
technically licensed under *any* version of the GPL or LGPL, not just the
version in whatever COPYING file they include. Note that this is LGPLv2+, not
LGPL+, because version 2 was the first version of LGPL."

So I followed the logic of 4. and that other snippet of "it is under any LGPL
license because it the source and documentation don't specify an exact LGPL
version" which gave me a output tag of "LGPLv2+ "

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.