legal July 2008

legal@lists.fedoraproject.org

20 participants
18 discussions

WOL - wide open license - compatibility with Fedora
by Development discussions related to Fedora 19 Jul '08

19 Jul '08

Couldn't see any discussion of WOL previously, so here goes: A particular source file (smbPitchShift.[Ch]) within the rakarrack [1] sources is licensed under WOL: ===== The Wide Open License (WOL) * * Permission to use, copy, modify, distribute and sell this software and its * documentation for any purpose is hereby granted without fee, provided that * the above copyright notice and this license appear in all source copies. * THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT EXPRESS OR IMPLIED WARRANTY OF * ANY KIND. See http://www.dspguru.com/wol.htm ===== Is this compatible with Fedora ? What would be the License field if the whole package was licensed this way ? In this case, the source archive has: - [GPLv3] COPYING (overall copying file). - [GPLv2] header (no or later version) in most source/header files. - [GPL+] 3x files {GPL, no version mentioned, see COPYING}. - WOL 1x file/header What would be the required license, or will a need to query upstream for their licensing intentions {each module tends to have differing authors} ? DaveT. [1]: http://rakarrack.sourceforge.net/

2 3

Open CASCADE Technology Public License
by Dan Horák 18 Jul '08

18 Jul '08

Hi, can you give me "Fedora acceptability statement" for the Open CASCADE Technology Public License available at http://www.opencascade.org/occ/license/ ? Thanks Dan -- Fedora and Red Hat package maintainer

1 0

license questions for user apps
by John 16 Jul '08

16 Jul '08

Dear All, I am looking at developing an application based on FEDORA - which will run from a bootable USB under FEDORA. The application will probably be written in in C or C++ (gcc) and use gtk libraries or use TCL/TK . I may use REALBASIC which if I buy from them does not include license costs for the applications generated and does not include libraries with any licensing costs on them. I then want to distribute the application with a PC commercially ie to sell multiple PCs all with FEDORA on them and all of them running my application. I do not want to contravene any licensing restrictions - but quite honestly the licensing constraints for FEDORA are beyond my mental capabilities. If a license is needed for every machine sold with my application on it what will the license cost for the FEDORA component and any other component ? Rgds, John Lever

2 1

LGPLv2 and v2.1 for fonts?
by Matt Domsch 15 Jul '08

15 Jul '08

https://bugzilla.redhat.com/show_bug.cgi?id=454128 requests review of a set of 4 fonts. 3 are licensed LGPLv2, one LGPLv2.1. These are not listed at http://fedoraproject.org/wiki/Legal_considerations_for_fonts therefore I request clarification. Thanks, Matt -- Matt Domsch Linux Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux

2 1

Fedora Live! on PC Magazine DVD
by PC Magazine - DVD Staff 15 Jul '08

15 Jul '08

Hello, we would like to include FEDORA Live (CD Iso) on PC Magazine Italia cover mount DVD-ROM (paid circulation of 45,000 copies). Is it possible? We need an explicit written permission (with a simple e-mail) from you in order to distribute your software in our country. Your software will be downloaded from your web site and published as is in our DVD-ROM without any modification. We'll include in the DVD Html interface your web site address and all the files of the original distribution. Please note that our DVD-ROM is a gift for our readers, it include many other freeware, shareware and open source software and it is not sold neither distributed without the magazine. Best regards. ==================== PC Magazine Italia DVD staff www.pcmagazine.it dvd(a)pcmagazine.it ACACIA Edizioni Srl Via Copernico, 3 20082 Binasco (MI) ITALY - EU www.acaciaedizioni.com ==================== LEGAL NOTICE This message may contain confidential and/or privileged information. You may not disclose to any third party any portion of the message (whether paraphrased or not) or any information contained in the message without explicit written permission from the author of the message. Furthermore, unless you are the intended addressee (or authorized to receive for the addressee), you may not use or reproduce any portion of the message.

2 1

Ekushey Bengali fonts
by Paul W. Frields 15 Jul '08

15 Jul '08

https://fedorahosted.org/fedora-infrastructure/ticket/648 I'm not sure who (if anyone) has been alerted about this request for us to host some Bengali fonts which apparently have some uncertain origins, despite their licensing. (See ticket URL above for details.) This situation's probably not critical, because there's nothing being hosted by Fedora yet AFAICT, but it would be nice to respond to the requestor(s) in the ticket. -- Paul W. Frields gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://paul.frields.org/ - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

5 4

Is license of cleanfeed right?
by Roman Rakus 07 Jul '08

07 Jul '08

LICENSE This software may be distributed freely, provided it is intact (including all the files from the original archive). You may modify it, and you may distribute your modified version, provided the original work is credited to the appropriate authors, and your work is credited to you (don't make changes and pass them off as my work), and that you aren't charging for it. Is it ok? "That last sentence may or may not cause this to become non-free :("

2 3

Seeking approval for use of LLGPL license
by Anthony Green 07 Jul '08

07 Jul '08

Many Free Software libraries and programs written in Lisp are licensed under the terms of the "Lisp Library General Public License", or LLGPL. It is essentially the LLGPL with a preamble that modifies it to make it more compatible with Lisp technology. See http://www.cliki.net/LLGPL and http://opensource.franz.com/preamble.html . I've included the text of the preamble below. I am seeking approval to use the LLGPL for Fedora packages. I already have one package that is approved, pending resolution of this question: https://bugzilla.redhat.com/show_bug.cgi?id=427411 Thank you, Anthony Green *Preamble to the Gnu Lesser General Public License * Copyright (c) 2000 Franz Incorporated, Berkeley, CA 94704 The concept of the GNU Lesser General Public License version 2.1 <http://opensource.franz.com/license.html> ("LGPL <http://opensource.franz.com/license.html>") has been adopted to govern the use and distribution of above-mentioned application. However, the LGPL <http://opensource.franz.com/license.html> uses terminology that is more appropriate for a program written in C than one written in Lisp. Nevertheless, the LGPL <http://opensource.franz.com/license.html> can still be applied to a Lisp program if certain clarifications are made. This document details those clarifications. Accordingly, the license for the open-source Lisp applications consists of this document plus the LGPL <http://opensource.franz.com/license.html>. Wherever there is a conflict between this document and the LGPL <http://opensource.franz.com/license.html>, this document takes precedence over the LGPL <http://opensource.franz.com/license.html>. A "Library" in Lisp is a collection of Lisp functions, data and foreign modules. The form of the Library can be Lisp source code (for processing by an interpreter) or object code (usually the result of compilation of source code or built with some other mechanisms). Foreign modules are object code in a form that can be linked into a Lisp executable. When we speak of functions we do so in the most general way to include, in addition, methods and unnamed functions. Lisp "data" is also a general term that includes the data structures resulting from defining Lisp classes. A Lisp application may include the same set of Lisp objects as does a Library, but this does not mean that the application is necessarily a "work based on the Library" it contains. The Library consists of everything in the distribution file set before any modifications are made to the files. If any of the functions or classes in the Library are redefined in other files, then those redefinitions ARE considered a work based on the Library. If additional methods are added to generic functions in the Library, those additional methods are NOT considered a work based on the Library. If Library classes are subclassed, these subclasses are NOT considered a work based on the Library. If the Library is modified to explicitly call other functions that are neither part of Lisp itself nor an available add-on module to Lisp, then the functions called by the modified Library ARE considered a work based on the Library. The goal is to ensure that the Library will compile and run without getting undefined function errors. It is permitted to add proprietary source code to the Library, but it must be done in a way such that the Library will still run without that proprietary code present. Section 5 of the LGPL <http://opensource.franz.com/license.html> distinguishes between the case of a library being dynamically linked at runtime and one being statically linked at build time. Section 5 of the LGPL <http://opensource.franz.com/license.html> states that the former results in an executable that is a "work that uses the Library." Section 5 of the LGPL <http://opensource.franz.com/license.html> states that the latter results in one that is a "derivative of the Library", which is therefore covered by the LGPL <http://opensource.franz.com/license.html>. Since Lisp only offers one choice, which is to link the Library into an executable at build time, we declare that, for the purpose applying the LGPL <http://opensource.franz.com/license.html> to the Library, an executable that results from linking a "work that uses the Library" with the Library is considered a "work that uses the Library" and is therefore NOT covered by the LGPL <http://opensource.franz.com/license.html>. Because of this declaration, section 6 of LGPL <http://opensource.franz.com/license.html> is not applicable to the Library. However, in connection with each distribution of this executable, you must also deliver, in accordance with the terms and conditions of the LGPL <http://opensource.franz.com/license.html>, the source code of Library (or your derivative thereof) that is incorporated into this executable.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

legal July 2008