I've submitted a review request (#461484) and have a couple of licensing
issues there (quoting from BZ):
>- from the licensing point of view, we have a small mess
> a) lots of files have headers defining them as GPLv2+ (good)
> b) headers of some other files specifu Public Domain as license (good
> c) however there are several files ( for instance
> clients/threadtest.c and
> many files under /lib ) which have no license specified. What reason
> can we invoke in order to assume that they are like all the others,
> Public Domain or GPLv2+ ?
> In addition to that, the sourcefarge page of the project
> (http://sourceforge.net/projects/twin/) claims that the project is
> licensed as GPL and LGPL, but LGPL is only mentioned in the source
> through the presence of the standard LGPL license file; I have not
> been able to locate any other trace of it. Public Domain + GPLv2+ =
no > problem, but the presence of files with no specific license make me
> ask for help. Anyone more experienced in licensing willing to shed
> some light ?
1) do I have to ask upstream to specify license in each
2) what license should this package be or do I have to ask upstream to
Thanks for any help,
I would like to check the validity of the Amazon Software License for
use in a package within Fedora. The text is below, with the original
text taken from the zip flie in this page:
> Amazon Software License
> This Amazon Software License ("License") governs your use,
> distribution of the accompanying software as specified below.
> 1. Definitions
> "Licensor" means any person or entity that distributes its Work.
> "Software" means the original work of authorship made available under
> "Work" means the Software and any additions to or derivative works of the
> Software that are made available under this License.
> The terms "reproduce," "reproduction," "derivative works," and
> have the meaning as provided under U.S. copyright law; provided,
> for the purposes of this License, derivative works shall not include
> remain separable from, or merely link (or bind by name) to the
> the Work.
> Works, including the Software, are "made available" under this License by
> including in or with the Work either (a) a copyright notice
> applicability of this License to the Work, or (b) a copy of this License.
> 2. License Grants
> 2.1 Copyright Grant. Subject to the terms and conditions of this
> Licensor grants to you a perpetual, worldwide, non-exclusive,
> copyright license to reproduce, prepare derivative works of, publicly
> publicly perform, sublicense and distribute its Work and any resulting
> derivative works in any form.
> 2.2 Patent Grant. Subject to the terms and conditions of this
> Licensor grants to you a perpetual, worldwide, non-exclusive,
> patent license to make, have made, use, sell, offer for sale, import, and
> otherwise transfer its Work, in whole or in part. The foregoing
> only to the patent claims licensable by Licensor that would be
> Licensor's Work (or portion thereof) individually and excluding any
> combinations with any other materials or technology.
> 3. Limitations
> 3.1 Redistribution. You may reproduce or distribute the Work only if
(a) you do
> so under this License, (b) you include a complete copy of this
> your distribution, and (c) you retain without modification any copyright,
> patent, trademark, or attribution notices that are present in the Work.
> 3.2 Derivative Works. You may specify that additional or different
> to the use, reproduction, and distribution of your derivative works
of the Work
> ("Your Terms") only if (a) Your Terms provide that the use limitation in
> Section 3.3 applies to your derivative works, and (b) you identify
> derivative works that are subject to Your Terms. Notwithstanding Your
> this License (including the redistribution requirements in Section
> continue to apply to the Work itself.
> 3.3 Use Limitation. The Work and any derivative works thereof only
may be used
> or intended for use with the web services, computing platforms or
> provided by Amazon.com, Inc. or its affiliates, including Amazon Web
> 3.4 Patent Claims. If you bring or threaten to bring a patent claim
> Licensor (including any claim, cross-claim or counterclaim in a
> enforce any patents that you allege are infringed by any Work, then
> under this License from such Licensor (including the grants in
Sections 2.1 and
> 2.2) will terminate immediately.
> 3.5 Trademarks. This License does not grant any rights to use any
> its affiliates' names, logos, or trademarks, except as necessary to
> the notices described in this License.
> 3.6 Termination. If you violate any term of this License, then your
> under this License (including the grants in Sections 2.1 and 2.2) will
> terminate immediately.
> 4. Disclaimer of Warranty. THE WORK IS PROVIDED "AS IS" WITHOUT
> CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING
> CONDITIONS OF M ERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
> NON-INFRINGEMENT. YOU BEAR THE RISK OF UNDERTAKING ANY ACTIVITIES
> LICENSE. SOME STATES' CONSUMER LAWS DO NOT ALLOW EXCLUSION OF AN IMPLIED
> WARRANTY, SO THIS DISCLAIMER MAY NOT APPLY TO YOU.
> 5. Limitation of Liability. EXCEPT AS PROHIBITED BY APPLICABLE LAW,
IN NO EVENT
> AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE),
> OTHERWISE SHALL ANY LICENSOR BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
> DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
ARISING OUT OF
> OR RELATED TO THIS LICENSE, THE USE OR INABILITY TO USE THE WORK
> NOT LIMITED TO LOSS OF GOODWILL, BUSINESS INTERRUPTION, LOST PROFITS
> COMPUTER FAILURE OR MALFUNCTION, OR ANY OTHER COMM ERCIAL DAMAGES OR
> EVEN IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
> [Note: Other license terms may apply to certain, identified software
> contained within or distributed with the accompanying software if
> are included in the notice folder accompanying the file. Such other
> terms will then apply in lieu of the terms of the Amazon Software License
I'm looking at Hanazono fonts license to be
packaging. that simply says:
This font is a free software.
Unlimited permission is granted to use, copy, and distribute
it, with or without modification, either commercially and
THIS FONT IS PROVIDED "AS IS" WITHOUT WARRANTY.
So what the license name should I use for spec file?
I began reviewing this scummvm-tools package:
scummvm is an engine to run old games, mainly Lucasarts (then Lucasfilm) adventure flicks. Most of these games are now abandonware. As far as I know, scummvm also runs other games, some of which are now free. scummvm is distibuted by Fedora.
On the other hand, scummvm-tools is a utility package. The only thing scummvm-tools does is to extract (and re-compress) data from these abandonware. Both scummvm and scummvm-tools come from the same project.
I am not sure if we can package scummvm-tools in Fedora. I blocked FE-Legal but on a second thought I felt unsure whether this is an issue that needs to be dealt by FE-Legal.
Can I get some help here? If not, whom should I ask?
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
Giulio Fidente wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Rahul Sundaram wrote:
>> Jon Stanley wrote:
>>> On Fri, Oct 10, 2008 at 5:40 PM, Rahul Sundaram
>>> <sundaram(a)fedoraproject.org> wrote:
>>>> There is no need to translate. Refer http://www.linux-xp.com/. I haven't
>>>> looked for source code.
>>> Interesting. I tried the "Buy Now" and "Download Now" links on the
>>> English version of the site and got nowhere. I do notice mention that
>>> I have to register in order to use the product beyond a 30-day
>>> evaluation period. I *think* that this may be an issue under GPLv3
>>> section 6, if there is any GPLv3 software in the distro, which cannot
>>> obviously be determined without a copy of it.
>> This is a Russian organization. I doubt we want to waste money trying to
>> get a hold of this product to hunt down whether the restrictions on the
>> end product is evasive of any specific license within. Wikipedia article
>> states that they do not respond to email. It doesn't appear to have made
>> any new releases and seems to be dead.
> btw it is availabe for download at:
> and or
CC'ing fedora-legal list.
Remember just last week when it was mentioned that folks would look at
CeCILL v1 when someone submitted something under that license? Well,
there was already something in the review queue and tonight I happened
upon it: https://bugzilla.redhat.com/show_bug.cgi?id=465750
R-GeneR, a specific bit of genetics software, seems to be under CeCILL
v1 as evidenced by the copying file, which begins with "FREE SOFTWARE
LICENSING AGREEMENT CeCILL" and ends with "Version 1 of 06/21/2004".
Of specific interest here is GPL (v2) compatibility, because R is
GPLv2 and R plugins are linked with both libR and libreadline.
SciLab has changed its licence to CeCILLv2, which claims to be GPLv2+
compatible. I tried reading it and it gave me a headache. It seems
to contain a few dubious passages. Could RH Legal have a look at it
and decide if it's OK to include code licensed under it in Fedora?
Ideally, I'd like to have an answer for all four licences listed on
this page, but CeCILLv2 would suffice for now.
 In particular: second paragraph of Article 5, last paragraph of 6.4
and Article 9.4
RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
Hi, I wanted to bring into attention the recent development in the licensing of the iText. This software was included in Fedora in the past but then removed due to licensing trouble:
According to the second link it was removed from F-7 because of the fact that it contained some Sun-licensed files.
I downloaded the software from its current website:
The website claims a dual MPLv1.1 / LGPL license. Inside the package there is a text file (core/com/lowagie/text/misc_licenses.txt), which I will paste to the bottom of this email.
The most relevant parts of this txt file are in section (3). The original license ended with the sentence: "You acknowledge that Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility." The word "licensed" caused the trouble in the past (see comment#2 in (ii)) as it made the software non-free. But according to the txt file there has been some email traffic between the original developer and iText developer on January 23, 2008 and the word "licensed" has been removed from that sentence in the final license.
I think we can re-consider packaging this software. I want to make sure we are on solid grounds.
Please post your opinions.
The original version of this class was published in an article by Heinz Kabutz.
"This material from The Java(tm) Specialists' Newsletter by Maximum Solutions (South Africa). Please contact Maximum Solutions for more information.
The original version of this class was published in a JavaWorld article by Steven Brandt:
Jennifer Orr (JavaWorld) wrote: "You have permission to use the code appearing in Steven Brandt's JavaWorld article, 'Java Tip 128: Create a quick-and-dirty XML parser.'
We ask that you reference the author as the creator and JavaWorld as the original publisher of the code." Steven Brandt also agreed with the use of this class.
The following files contain material that was copyrighted by SUN:
com/lowagie/text/pdf/LZWDecoder.java (first appearance in iText: 2002-02-08)
com/lowagie/text/pdf/codec/BmpImage.java (first appearance in iText: 2003-06-20)
com/lowagie/text/pdf/codec/PngImage.java (first appearance in iText: 2003-04-25)
com/lowagie/text/pdf/codec/TIFFDirectory.java (first appearance in iText: 2003-04-09)
com/lowagie/text/pdf/codec/TIFFFaxDecoder.java (first appearance in iText: 2003-04-09)
com/lowagie/text/pdf/codec/TIFFField.java (first appearance in iText: 2003-04-09)
com/lowagie/text/pdf/codec/TIFFLZWDecoder.java (first appearance in iText: 2003-04-09)
The original code was released under the BSD license, and contained the following extra restriction: "You acknowledge that Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility."
In a mail sent to Bruno Lowagie on January 23, 2008, Brian Burkhalter (@sun.com) writes: "This code is under a BSD license and supersedes the older codec packages on which your code is based. It also includes numerous fixes among them being the ability to handle a lot of 'broken' TIFFs."
Note that numerous fixes were applied to the code used in iText by Paulo Soares, but apart from the fixes there were no essential changes between the code that was originally adapted and the code that is now available under the following license:
Copyright (c) 2005 Sun Microsystems, Inc. All Rights Reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
- Redistribution of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
- Redistribution in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
Neither the name of Sun Microsystems, Inc. or the names of
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
This software is provided "AS IS," without a warranty of any
kind. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND
WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY
EXCLUDED. SUN MIDROSYSTEMS, INC. ("SUN") AND ITS LICENSORS SHALL
NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF
USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE OR ITS
DERIVATIVES. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR
ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR
INABILITY TO USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
You acknowledge that this software is not designed or intended for
use in the design, construction, operation or maintenance of any
The main difference can be found in the final paragraph: the restriction
that the source code is not "licensed" in this particular situation has
FYI: Brian also added: "A bit of history might be in order.
The codec classes that you used originally were based on some
classes included with JAI but not strictly part of JAI.
As of Java SE 1.4 an official Image I/O framework was
added in javax.imageio.... This frameork supports these formats:
Java 1.4: GIF (read only), JPEG, PNG
Java 1.5: Added support for BMP and WBMP
Java 1.6: Added support for writing GIF
The JAI Image I/O Tools packages (jai-imageio-core) were created
to support formats handled by JAI but not included in Java SE
as well as some new things like JPEG2000."
(4) the file com/lowagie/text/pdf/codec/TIFFConstants
and some other TIFF related code is derived from LIBTIFF:
Copyright (c) 1988-1997 Sam Leffler
Copyright (c) 1991-1997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software and
its documentation for any purpose is hereby granted without fee, provided
that (i) the above copyright notices and this permission notice appear in
all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or
publicity relating to the software without the specific, prior written
permission of Sam Leffler and Silicon Graphics.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND,
EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF
LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
OF THIS SOFTWARE.
As stated in the Javadoc comments, materials from Unicode.org are used in the class com/lowagie/text/pdf/BidiOrder.java
The following license applies to these materials:
UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE
Unicode Data Files include all data files under the directories
and http://www.unicode.org/cldr/data/ . Unicode Software includes any source code published in the Unicode Standard or under the directories http://www.unicode.org/Public/, http://www.unicode.org/reports/, and http://www.unicode.org/cldr/data/.
NOTICE TO USER: Carefully read the following legal agreement. BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING UNICODE INC.'S DATA FILES ("DATA FILES"), AND/OR SOFTWARE ("SOFTWARE"), YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND BY, ALL OF THE TERMS AND CNDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, COP, DISTRIBUTE OR USE THE DATA FILES OR SOFTWARE.
ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE THE DATA FILES OR SOFTWARE.
COPYRIGHT AND PERMISSION NOTICE
Permission is hereby granted, free of charge, to any person obtaining a copy of the Unicode data files and any associated documentation (the "Data Files") or Unicode software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that (a) the above copyright notice(s) and this permission notice appear with all copies of the Data Files or Software, (b) both the above copyright notice(s) and this permission notice appear in associated documentation, and (c) there is clear notice in each modified Data File or in the Software as well as in the documentation associated with the Data File(s) or Software that the data or software has been modified.
THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTAILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE DATA FILES OR SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in these Data Files or Software without prior written authorization of the