legal February 2018

legal@lists.fedoraproject.org

13 participants
9 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

Nagios Open Software License: free software?
by Robert-André Mauchin 05 Mar '18

05 Mar '18

Hello legal folks, I would like some opinions on a license called Nagios Open Software License, used in nrdp (Review request: https://bugzilla.redhat.com/show_bug.cgi? id=1284132). It has "open" in the name and the preambule look good ("to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software") but some of the conditions are dubious, specifically Point 3: "may not be forked" and Point 6: "The Software may only be used in conjunction with products, projects, and other software distributed by the Company." It it Fedora-compatible? Full text below: Nagios Open Software License Version 1.3 ---------------------------------------- Copyright (c) 2010-2016 Nagios Enterprises, LLC Nagios Enterprises, LLC (the "Company") hereby grants, free of charge, to any person, company, or legal entity (each a "User") obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software (each a "Use"), and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 1. The above copyright notice and this license shall be included in its entirety in all copies or substantial portions of the Software. 2. The copyright notices and attribution information included in the Software may not be altered or removed. 3. The Software may not be Forked. "Forking" and "to Fork" means to create or distribute a product or a derivative work of the object or source code of the Software under a new or different brand. 4. Any Use of the Software is subject to compliance with the terms and conditions of the Nagios Trademark Use Restrictions, which are incorporated herein by reference and can be viewed online at http://www.nagios.com/legal/ trademarks/ 5. Any Contribution of materials to the Software by any User is subject to, and signifies, either explicitly or implicitly, the User's acceptance of the terms and conditions of the Nagios Contributor Agreement, which are incorporated herein by reference and can be viewed online at http:// www.nagios.com/legal/contributoragreement/. "Contribution" means any source code, object code, patch, tool, sample, graphic, specification, manual, documentation, or any other material posted or submitted by a User to the Company, directly or indirectly, via the Company's websites, forums, email lists, or other methods of communication. 6. The Software may only be used in conjunction with products, projects, and other software distributed by the Company. Any standalone use of the Software, or use of the Software in conjunction with products, projects, or other software not authored or distributed by the Company - including third- party software that competes with the offerings of Company - is strictly prohibited and is a direct violation of the terms of the license. 7. This license is not intended to restrict any other rights that may be granted to you by other software and associated documentation files that may be included in the Software. If the Software is considered to be a collective work under U.S. copyright laws, the terms of this license do not apply to other contributions of the collective work unless stated otherwise. 8. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, STRICT LIABILITY, TORT (INCLUDING NEGLIGENCE OR OTHERWISE) OR OTHER ACTION, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 9. The terms of this license are subject to the User's compliance with all terms of this license. In the event that any term or condition is violated by the User, the terms of this license terminate and the User shall not have any rights they otherwise might have been granted under this license.

4 3

CP/M license
by Eric Smith 27 Feb '18

27 Feb '18

As of 2001, CP/M, originally from Digital Research, was released under a license that has been reported as open source: http://www.cpm.z80.de/license.html On the one hand, I'm concerned with the phrase "as part of the 'Unofficial CP/M Web Site", but on the other hand, that is immediately followed by "with its maintainers, developers and community", which seems broadly inclusive. Is this license satisfactory for Fedora? Best regards, Eric

3 4

No activity on bug blocking FE-Legal
by Peter Oliver 26 Feb '18

26 Feb '18

Bug 1433617 (Review Request: python-proselint - A linter for prose) has been blocking FE-Legal since September of last year. Is there anything additional I need to do to get this looked at, or will it naturally work its way to the top of the queue in due course? It's not urgent, I simply wondered whether there was some step that I'd missed. https://bugzilla.redhat.com/show_bug.cgi?id=1433617 -- Peter Oliver

3 2

BSD 2-Clause license
by Fernando Nasser 26 Feb '18

26 Feb '18

Hi, Would it be possible to add: BSD 2-clause to our table of valid licenses? It is already in https://spdx.org/licenses/ BSD 2-Clause "Simplified" License <https://spdx.org/licenses/BSD-2-Clause.html> |BSD-2-Clause| and is OSI-approved. For reference: https://spdx.org/licenses/BSD-2-Clause.html#licenseText Thanks in advance! P.S.: It is used by something called 'fluentd'.

4 6

Last U.S. MPEG-2 Patent Expires on Feb. 13th!
by Sérgio Basto 19 Feb '18

19 Feb '18

someone asked in ask site [1] Can Fedora consider allowing the package "libmpeg2" into the Fedora family for the next release? Best regards, [1] https://ask.fedoraproject.org/en/question/116927/last-us-mpeg-2-patent- expires-on-feb-13th/ -- Sérgio M. B.

4 6

Forbidden_items is not updated ?
by Sérgio Basto 19 Feb '18

19 Feb '18

Hello , [1] could be removed from this wiki page isn't it ? [1] https://fedoraproject.org/wiki/Forbidden_items#S3TC_Texture_Compression -- Sérgio M. B.

2 1

MPEG-LA statement about the last MPEG-2 patent expiration in US (February 13, 2018)
by Peter Lemenkov 14 Feb '18

14 Feb '18

Hello All! MPEG-LA updated their site recently. http://www.mpegla.com/main/programs/M2/Pages/PatentList.aspx "This is the list of patents (Attachment 1) covered by the MPEG-2 Patent Portfolio License as of January 1, 2018. Under the MPEG-2 Patent Portfolio License, royalties are payable for products manufactured or sold in countries with an active MPEG-2 Patent Portfolio Patent at the time of manufacture or sale. Please note that the last US patent expired February 13, 2018, and patents remain active in Philippines and Malaysia after that date." PS I've never heard that software patents are valid anywhere but USA and South Korea, so mentioning Philippines and Malaysia was a surprise to me. -- With best regards, Peter Lemenkov.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

legal February 2018