[Momonga-devel.en:00021] Momonga Linux licence expression unification policy
- From: Shigeru Yamazaki <yamazaki@xxxxxxxxxxxxx>
- Date: Tue, 8 Jul 2003 02:28:04 +1000
This is muradaikan from the Momonga Project.
For the following policy draft, any suggestions and comments are welcome.
Cheers, mate.
muradaikan
Queensland, Australia
------------------------------------------------------------------------
Momonga Linux licence expression unification policy (draft) by hl2o
Coverage
"License:" preamble entry in spec file for packages included, and
packages that are going to be included, in the Momonga Linux distribution
(main, zoo, and non-free).
Policy
A preamble value to be put in the License entry is the parameter to
identify a license type. On this assumption, it is not restricted to
stipulate the official name or title of a particular license or lisensor.
For the reasons above, the following issues can be raised:
It is deemed adequate to keep the license description short for
"rpm -qi" command to display package information.
Since speclint checks the preamble value, it is better not
to risk chances for a typographical error to happen in the sincere
effort to spelling the proper title or name of the license.
Meanwhile, a chart to show relationships between preamble values
(parameters) and proper linense titiles would be prepared.
(Note: Perhaps including the chart in some package is preferable,
but for the time being, no particluar package is chosen for it.
License identifier
Characters for license idetifier
Upper and lower case alphabets
Numerals
Following characters: -, _, (space)
Recognized license identifier
As identifier, the following license expressions will be used.
Examples are"
Use "Apache" for the following
Apache
Apache License
Apache Software License
Apache like
Apacheish
The PHP License」(as of 3.0, see http://www.php.net/license/);
Use "Artistic" for the following
Artistic
artistic
Use "BSD" or "Modified BSD" for the following
BSD
Modified BSD
BSD License
BSD Style
BSD like
BSD style license
BSD-like
BSD-style
BSDish
BSDlike
The modified BSD license
W3C
W3C (see: http://www.w3.org/Consortium/Legal/
copyright-software.html)
W3C Copyright (BSD like).
distributable and BSD Style
modified BSD
UCB
dump relicesed to BSD
Use "GFDL" for the following
GFDL」
Use "GPL" for the following
GNU
GNU GPL Version 2
GNU GPL Version 2 or any later version.
GNU General Public License
GPL version 2, (C) 1994-1999 The DOSEMU-Development-Team
GPL2
distributable GPL
Use "LGPL" for the following
LGPL
GNU LGPL
LGPL2
WINEL
Use "MIT" for the following
MIT
X
MIT/X Consortium
MIT/X Consortium License
X Consortium-like
X, distributable
XFree86
Use "MPL" for the following
MPL
Use "OPL" for the following
OPL?
Use "Public Domain" for the following
Public domain
public domain
suite yourself
Momonga ([momonga-release])
None ([termcap] indicated as public domain inside file)
Use "QPL" for the following
QPL
Use "Ruby" for the following
(Note: Ruby license contains GPL license elements in its
license condition.)
Ruby
Ruby License
Ruby's
Other individual license
Use "" to quote an individual license.
(Note: Speclint currently puts a ":" before license name but this will
be changed to use double quotation marks for cosmetic appearance.)
Division For cases of selective license names or titles
Use "or" for when selection from 2 licenses is available.
Use "," and "or" for when selecting from 3 or more licenses are
available. Written in the proper expression, it is /(?:,|\s+or)\s+/.
Do not use "and", "&", or "/" as seen in the following:
License: Modified BSD or MIT
License: "Foobar", "Barbaz" or MIT
(Note: Unifying is recommended since various expressions such as
"and", "or", "/", and "," are all used.)
----------------------------------------------------------------