legal May 2009

legal@lists.fedoraproject.org

20 participants
18 discussions

emc2 license
by Jason L Tibbitts III 14 May '09

14 May '09

Several users here want to use the emc2 mesh generation software so I figured I'd package it up if the license is acceptable. The software page in English is at: http://www-c.inria.fr/gamma/cdrom/www/emc2/eng.htm The COPYRIGHT file, however, is in French: http://www-c.inria.fr/gamma/cdrom/www/emc2/copyright.htm There seems to be some sort of commercial utilization clause, but my French is too limited to comprehend its scope. - J<

3 2

Re: [Fedora-legal-list] Does every file in the upstream tarball need to have a license?
by Tom Callaway 13 May '09

13 May '09

On 05/13/2009 04:56 PM, David Malcolm wrote: > Based on that, it sounds like this is OK for inclusion, and that I was > being overly paranoid. Is this correct? Yes, although, you should still ask upstream to fix the license attribution on the files which do not contain it. ~spot

1 0

Does every file in the upstream tarball need to have a license?
by David Malcolm 13 May '09

13 May '09

I'm reviewing Djblets: https://bugzilla.redhat.com/show_bug.cgi?id=487098 which is a utility library used by ReviewBoard [1] The upstream website: http://code.google.com/p/reviewboard/wiki/Djblets states "Djblets is under the MIT license." However, the upstream tarball does not contain a license file. Only some of the files within the tarball contain license headers. I believe that every file with a "Copyright" also contains an MIT license grant. (There's also an embedded copy of jquery, which is dual licensed MIT and GPL) The setup.py does state "MIT" in the license field, in the usual place for such metadata (although said file is itself GPLv2 licensed). Is this a problem for Fedora inclusion? Thanks Dave [1] https://bugzilla.redhat.com/show_bug.cgi?id=487097

2 1

python openssl/gpl license issue?
by Christoph Höger 12 May '09

12 May '09

Hi, I've just read http://blog.pierlux.com/2009/05/12/pythons-hidden-poissoned-apple-for-gpl-a… and it seems to me that this applys to offlineimap (which i am maintaining), as that tool uses sslsock from python and is licensed under gpl. I contacted upstream already, but first this is a fedora legal issue. So what am I supposed to do? regards christoph

3 2

Question on legal issues
by Panagiotis Galiotos 09 May '09

09 May '09

Dear all I'm trying to get familiar with Fedora Core 9. I would like to ask you if I can use this OS in my work for making profit or if this kind of usage is not permitted under the licence terms of FC 9 ? Please let me know about that, since I'm a little confused with all the talk about licences, GNU etc. Is this licence about copying and redistributing the source code or does it refer to the terms of use ? Regards, Panagiotis Galiotos

2 1

CMSVLIB
by Orion Poplawski 07 May '09

07 May '09

I'm trying to figure out if we can include this in Fedora. Web site is: http://cow.physics.wisc.edu/~craigm/idl/idl.html For the most part it seems like the code is "Copyright Only": ; Copyright (C) 1999-2000,2006 Craig Markwardt ; This software is provided as is without any warranty whatsoever. ; Permission to use, copy, modify, and distribute modified or ; unmodified copies is granted, provided this copyright and disclaimer ; are included unchanged. The tricky part is the code that reads and writes IDL save files. IDL is proprietary software from (currently) ITT (previously Research Systems Inc). There is a LICENSE.RSI file: http://cow.physics.wisc.edu/~craigm/idl/down/LICENSE.RSI That seems to grant permission to use it. Comments? Thanks! -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion(a)cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com

2 5

Linux firmware
by Rahul Sundaram 06 May '09

06 May '09

Hi Planet GNOME points to this bug now which is apparently non-redistributable firmware being included in Ubuntu for quite sometime. Just a heads up to make sure we aren't having the same problem. https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/223212 Rahul

3 22

License check for new library for fedora
by Thomas Janssen 05 May '09

05 May '09

Good day. I try to become a new packager for Fedora and face a license that needs to be checked. The Main package is Newsbeuter MIT/X license and the needed lib is "stfl" with a LGPLv3 license, supplemented by additional permissions. Following the license: GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below. 0. Additional Definitions. As used herein, "this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of the GNU General Public License. "The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below. An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library. A "Combined Work" is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the "Linked Version". The "Minimal Corresponding Source" for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version. The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work. 1. Exception to Section 3 of the GNU GPL. You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL. 2. Conveying Modified Versions. If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version: a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy. 3. Object Code Incorporating Material from Library Header Files. The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following: a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the object code with a copy of the GNU GPL and this license document. 4. Combined Works. You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the Combined Work with a copy of the GNU GPL and this license document. c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. d) Do one of the following: 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source. 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version. e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.) 5. Combined Libraries. You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License. b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 6. Revised Versions of the GNU Lesser General Public License. The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation. If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library. This is obviously my first post to this list. So i will wait until i get an answer. Thanks for your time. Thomas Janssen -- LG Thomas Dubium sapientiae initium

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

legal May 2009