Henry Spencer's license
by Petr Šabata
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
6 months, 3 weeks
BSD like license with strange wording?
by Robert-André Mauchin
Hi,
The following license is lifted from a code coming from NetBSD
(ftp://ftp.NetBSD.org/pub/NetBSD/misc/sjg/ ) but I cannot find exactly
the text of this license anywhere else:
# This file is provided in the hope that it will
# be of use. There is absolutely NO WARRANTY.
# Permission to copy, redistribute or otherwise
# use this file is hereby granted provided that
# the above copyright notice and this notice are
# left intact.
Is this considered BSD-like?
Best regards,
Robert-André
2 years, 6 months
Quick question about a BSD like license
by Robert-André Mauchin
Hello,
The following license is BSD but with an extra clause regarding binary
distribution, it should be okay I think but I just want confirmation it's not a
problem:
================================================================================
FatFs License
FatFs has being developped as a personal project of the author, ChaN. It is
free from the code anyone else wrote at current release. Following code block
shows a copy of the FatFs license document that heading the source files.
/*----------------------------------------------------------------------------/
/ FatFs - Generic FAT Filesystem Module Rx.xx /
/-----------------------------------------------------------------------------/
/
/ Copyright (C) 20xx, ChaN, all right reserved.
/
/ FatFs module is an open source software. Redistribution and use of FatFs in
/ source and binary forms, with or without modification, are permitted provided
/ that the following condition is met:
/
/ 1. Redistributions of source code must retain the above copyright notice,
/ this condition and the following disclaimer.
/
/ This software is provided by the copyright holder and contributors "AS IS"
/ and any warranties related to this software are DISCLAIMED.
/ The copyright owner or contributors be NOT LIABLE for any damages caused
/ by use of this software.
/----------------------------------------------------------------------------*/
Therefore FatFs license is one of the BSD-style licenses but there is a
significant feature. FatFs is mainly intended for embedded systems. In order to
extend the usability for commercial products, the redistributions of FatFs in
binary form, such as embedded code, binary library and any forms without source
code, does not need to include about FatFs in the documentations. This is
equivalent to the 1-clause BSD license. Of course FatFs is compatible with the
most of open source software licenses including GNU GPL. When you redistribute
the FatFs source code with any changes or create a fork, the license can also
be changed to GNU GPL, BSD-style license or any open source software license
that not conflict with FatFs license.
================================================================================
Best regards,
Robert-André
2 years, 6 months
Adding rnnoise to the repo
by Vascom
Hi all.
I want to add rnnoise (Recurrent neural network for audio noise
reduction) to Fedora repo.
Upstream https://gitlab.xiph.org/xiph/rnnoise
My Review Request https://bugzilla.redhat.com/show_bug.cgi?id=1919606
I have some doubts about patents in this program. But one of the
authors answered me by email.
See forwarded message below.
So сan I get permission from the Legal Team to add this package?
---------- Forwarded message ---------
От: Jean-Marc Valin <jmvalin(a)jmvalin.ca>
Date: сб, 6 мар. 2021 г. в 09:59
Subject: RNNoise in Fedora
To: <vascom2(a)gmail.com>
Hi Vasiliy,
I saw you were inquiring about the legal status of RNNoise. I don't
like making public comments involving patents, but I can say that I do
not have knowledge of any patent that would cover the RNNoise code.
Also, that code was written while I was employed by Mozilla (I am no
longer with them) and we did not file any patent on it. So I hope this
helps.
Jean-Marc
2 years, 6 months
