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
1 year, 1 month
Volatility Software License
by Miro Hrončok
Is this OK for inclusion in Fedora?
https://github.com/volatilityfoundation/volatility3/blob/master/LICENSE.txt
Volatility Software License
Version 1.0 dated October 3, 2019.
This license covers the Volatility software, Copyright 2019 Volatility Foundation.
Software
The software referred to in this license includes the software named above, and
any data (such as operating system profiles or configuration information), and
documentation provided with the software.
Purpose
This license gives you permission to use, share, and build with this software
for free, but requires you to share source code for changes, additions, and
software that you build with it.
Acceptance
In order to receive this license, you must agree to its rules. The rules of this
license are both obligations under that agreement and conditions to your
license. You must not do anything with this software that triggers a rule that
you cannot or will not follow.
Copyright
Each contributor licenses you to do everything with this software that would
otherwise infringe that contributor's copyright in it.
Notices
You must ensure that everyone who gets a copy of any part of this software from
you, with or without changes, also gets the text of this license or a link to
https://www.volatilityfoundation.org/license/vsl-v1.0. You must not remove any
copyright notice in the Software.
Patent
Each contributor licenses you to do everything with this software that would
otherwise infringe any patent claims they can license or become able to license.
Reliability
No contributor can revoke this license.
Copyleft
If you make any Additions available to others, such as by providing copies of
them or providing access to them over the Internet, you must make them publicly
available, according to this paragraph. "Additions" includes changes or
additions to the software, and any content or materials, including any training
materials, you create that contain any portion of the software. "Additions" also
includes any translations or ports of the software. "Additions" also includes
any software designed to execute the software and parse its results, such as a
wrapper written for the software, but does not include shell or execution menu
software designed to execute software generally. When this license requires you
to make Additions available:
- You must publish all source code for software under this license, in the
preferred form for making changes, through a freely accessible distribution
system widely used for similar source code, so the developer and others can find
and copy it.
- You must publish all data or content under this license, in a format
customarily used to make changes to it, through a freely accessible distribution
system, so the developer and others can find and copy it.
- You are responsible to ensure you have rights in Additions necessary to comply
with this section.
Contributing
If you contribute (or offer to contribute) any materials to Volatility
Foundation for the software, such as by submitting a pull request to the
repository for the software or related content run by Volatility Foundation, you
agree to contribute them under the under the BSD 2-Clause Plus Patent License
(in the case of software) or the Creative Commons Zero Public Domain Dedication
(in the case of content), unless you clearly mark them "Not a Contribution."
Trademarks
This license grants you no rights to any trademarks or service marks.
Termination
If you violate any term of this license, your license ends immediately.
No Liability
As far as the law allows, the software comes as is, without any warranty or
condition, and no contributor will be liable to anyone for any damages related
to this software or this license, under any kind of legal claim.
Versions
Volatility Foundation is the steward of this license and may publish new
versions of this license with new version numbers. You may use the software
under the version of this license under which you received the software, or, at
your choice, any later version.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
4 years, 1 month
How to write License field for packages bundling mutliple others
by Igor Gnatenko
In Rust world we package all crates as source code in -devel packages.
Then we use them to build the real applications.
Some time ago, someone noticed that we don't put licenses of those
-devel packages into a resulting RPM with app which is fair.
However, I'm not entirely sure how to properly write the License tag.
What should be there if -devel packages have:
* ASL 2.0
* ASL 2.0 or Boost
* ASL 2.0 or MIT
* ISC
* MIT
* (MIT or ASL 2.0) and BSD
* Unlicense or MIT
Is it correct to put License: ISC and MIT and ASL 2.0 and BSD?
4 years, 2 months
