legal November 2017

legal@lists.fedoraproject.org

15 participants
13 discussions

Henry Spencer's license
by Petr Šabata 06 Mar '23

06 Mar '23

Dear legal, While checking the contents of our `perl' package, I noticed the following: (...) /* NOTE: this is derived from Henry Spencer's regexp code, and should not * confused with the original package (see point 3 below). Thanks, Henry! */ /* Additional note: this code is very heavily munged from Henry's version * in places. In some spots I've traded clarity for efficiency, so don't * blame Henry for some of the lack of readability. */ /* The names of the functions have been changed from regcomp and * regexec to pregcomp and pregexec in order to avoid conflicts * with the POSIX routines of the same names. */ (...) * pregcomp and pregexec -- regsub and regerror are not used in perl * * Copyright (c) 1986 by University of Toronto. * Written by Henry Spencer. Not derived from licensed software. * * Permission is granted to anyone to use this software for any * purpose on any computer system, and to redistribute it freely, * subject to the following restrictions: * * 1. The author is not responsible for the consequences of use of * this software, no matter how awful, even if they arise * from defects in it. * * 2. The origin of this software must not be misrepresented, either * by explicit claim or by omission. * * 3. Altered versions must be plainly marked as such, and must not * be misrepresented as being the original software. * **** Alterations to Henry's code are... **** **** Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, **** 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 **** by Larry Wall and others **** **** You may distribute under the terms of either the GNU General Public **** License or the Artistic License, as specified in the README file. (...) You can see the whole file here: https://metacpan.org/source/SHAY/perl-5.20.1/regexec.c I looked but couldn't find any common name for this license of Henry's. Is it on our list? Is it free? What name should I use in the License tag? Thank you, Petr

5 9

about openssl we may enable and build all elliptic curves on corp ?
by Sérgio Basto 05 Nov '22

05 Nov '22

Hello, I reopen or start thinking again on this question of enable elliptic curves of openssl [1] So going directly to the point, may I built all source of openssl in copr [2] ? or at least some other curves that fedora package don't ship? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1405843 [2] Version: 1.0.2k %global fips_version 2.0.14 I mean sources: http://ftp.o penssl.org/source/openssl-%{version}.tar.gz and http://ftp.openssl.org/s ource/openssl-fips-%{fips_version}.tar.gz Thanks , -- Sérgio M. B.

4 6

libdvdcss package in COPR
by Michal Novotny 10 Jan '18

10 Jan '18

Hello, is it alright to host libdvdcss package in COPR or should it be deleted? (more info here: https://www.videolan.org/legal.html) The licence is ok (GPL) and it's not listed here: https://fedoraproject.org/wiki/Forbidden_items But I am not sure if it goes well with US regulations. See COPR specific regulations here: https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-… Thank you Michal Novotny

5 5

Perfect DOS VGA 437 - is it okay to package this font?
by Artur Iwicki 30 Nov '17

30 Nov '17

Hello. I'm currently trying to package some games for Fedora; since all of them come from one author, they share a lot of their dependencies. One of the dependencies if the "Perfect DOS VGA 437" font. While there's no licence explicitly stated, I wrote an e-mail to the author and he responded that "the font is free to use for any purpose. No crediting needed either. Feel free to use it." However, there's a different issue I want to ask about. The 2003 blog post where the author describes the process behind creating the font says: >So I fired up QuickBasic (!), created a quick program to display >all 255 characters directly on screen, and captured the screen >using Screen Thief, a classic DOS image grabbing software that >accompanied me for ages (it was mainly created to capture game >screens on DOS, but it did capture text screens on graphic format). As such, I wonder - could this font be seen as infringing copyright, and thus, not suitable for inclusion in Fedora? Full link to aforementioned blog post: http://zehfernando.com/2003/flash-ansi-viewer-and-reflections-on-flash-spee… Thank you for your time, A.I.

2 1

JpGraph and "open source use"
by Randy Barlow 27 Nov '17

27 Nov '17

Hello! It's me again with another question about a weird license wording on a library. tl;dr; JpGraph's download page[0] says: "JpGraph is released under a dual license. QPL 1.0 (Qt Free License) For non-commercial, open-source or educational use and JpGraph Professional License for commercial use." I don't know what "open-source use" means, but does that wording make this licensing unacceptable for Fedora? Longer story You may recall a thread I started earlier this year[1] about c-pchart and the strange license that led to a contradiction. I've filed an issue with Ampache[2] (a project that uses c-pchart) and they are willing to switch to a different graphing library to help resolve this legal issue. They are considering JpGraph as a replacement, and had asked if it would be acceptable to Fedora. I am not sure since it has the "non-commercial" and "commercial" language in there. Does the "or" in the QPL satisfy our legal requirements (since "open-source" was included in a list with "or"), or does the language about "commercial use" supercede that? It does seem pretty ambiguous to me. [0] http://jpgraph.net/download/ [1] https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org… [2] https://github.com/ampache/ampache/issues/1515

2 2

EPL-2.0 license
by Fernando Nasser 27 Nov '17

27 Nov '17

Hi, I've got this request asking to add the EPL 2.0 license to Fedora. (and maybe add a EPL-1.0 alias in addition to our EPL for the 1.0 one). I am wondering how this hasn't come up yet. SPDX also only has "EPL-1.0" atm. Regards, Fernando From the original request: ---------------------- As there is already a newer version of EPL - EPL 2.0, we should probably update Fedora rules for abbreviation of such license (optionally also include this new 2.0 version). For particular versions see: https://www.eclipse.org/org/documents/epl-v10.html https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.html Thanks in advance.

1 0

Licensing wiki page for QPL has dead URL
by Randy Barlow 26 Nov '17

26 Nov '17

Greetings! The licensing page[0] in the Wiki lists a URL to a domain that no longer exists: http://doc.qt.digia.com/3.0/license.html [0] https://fedoraproject.org/wiki/Licensing:Main

2 1

Is OpenSpades content license acceptable for COPR?
by Mihai-Drosi Caju 21 Nov '17

21 Nov '17

Greetings, I would like to distribute OpenSpades on COPR. The license of the code itself is GPLv3. But it depends on content which I am not sure can be distributed on COPR. I have attached a link to the license in question below. Can I distribute the files in question on COPR? https://github.com/yvt/openspades-paks/blob/master/Nonfree/LICENSE.md

6 9

GPLv2+ vs GPLv3+
by Mattia Verga 13 Nov '17

13 Nov '17

I'm reviewing a new package to be included in Fedora repos. [1] As always, I'm making confusion between GPLv2+ and GPLv3+... license in spec file is "GPLv3+ and MIT", but some sources are licensed GPLv2+ and LGPLv2+ also. The COPYING file itself distributed in sources is a GPLv2 license. What license is right to be write in spec file? Mattia [1] https://bugzilla.redhat.com/show_bug.cgi?id=1321081

3 5

CUPS changing from GPLv2 to ASL2.0 -- implications?
by Solomon Peachy 13 Nov '17

13 Nov '17

Folks, CUPS has announced [1] they're going to release all future versions under the Apache 2.0 license, instead of the GPLv2+exceptions they used to use. This appears to have some thorny implications due to license incompatibilities with GPLv2-only stuff, and the ramifications of bumping [L]GPLv2+ stuff to v3 for purposes of linking against CUPS. Rather than several of us prattling on about what we think this might mean for Fedora [2], it seems prudent to ask actual legal folks about how to proceed. (FWIW, I suspect convincing Apple to dual-license CUPS isn't going to happen..) BTW, my personal interest in this has to do with my involvement with Gutenprint. [3] [1] https://lists.cups.org/pipermail/cups-devel/2017-November/017085.html [2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… [3] https://sourceforge.net/p/gimp-print/mailman/message/36108142/ - Solomon -- Solomon Peachy pizza at shaftnet dot org Coconut Creek, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum videtur.

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

legal November 2017