All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Raj Sarraf <rrs@debian.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Xose Vazquez Perez <xose.vazquez@gmail.com>,
	"christophe.varoqui@opensvc.com" <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: What license is multipath-tools under
Date: Fri, 29 Jul 2016 00:11:00 +0530	[thread overview]
Message-ID: <1469731260.4380.19.camel@debian.org> (raw)
In-Reply-To: <1469726763.2295.20.camel@HansenPartnership.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1891 bytes --]

Hello James,

On Thu, 2016-07-28 at 13:26 -0400, James Bottomley wrote:
> On Thu, 2016-07-28 at 22:23 +0530, Ritesh Raj Sarraf wrote:
> > Thanks Xose, for digging this information. But shouldn't this 
> > information go into respective source files?
> 
> If there's a COPYING file, there's no need for individual files to have
> a copyright.  The licence of the file defaults to whatever COPYING (or
> LICENCE or some recognizable top level file says).  A significant
> number of Linux Kernel files don't have individual file header copyrigh
> ts, if you want an example of this.

Yes. But as I understand, the entire Linux [1] code base is GPLv2 only. Whereas
in case of multipath-tools, as Xose mentioned in the previous email, it is a mix
of:

* GPLv2 (only?)
* GPLv2+
* LGPLv2

Having this information in the source repository (not necessarily as individual
source headers) will speak out much clear.

I think something like Debian's Machine-readable copyright format will be a good
fit in this case.

https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

An example project, with mixed licenses:
http://metadata.ftp-master.debian.org/changelogs/main/libs/libstoragemgmt/unstab
le_copyright

BTW, this topic hit my mind 2 days ago when I looked at the aging (old format)
multipath-tools/debian/copyright in my packaging repo and wanted to fix it.

http://metadata.ftp-master.debian.org/changelogs/main/m/multipath-tools/unstable
_copyright



I have attached a patch for a copyright file, based on what Xose had mentioned
in the email. There still are files, like libmultipath/prioritizers/alua.c,
which mention the license as plain GPL. So, this patch is still not complete.


[1] with some minor exceptions I just noticed.

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

[-- Attachment #1.1.2: 0001-Add-initial-licensing-copyright-file.patch --]
[-- Type: text/x-patch, Size: 2953 bytes --]

From a148c6de8b558858e3210c973574859954ad2e63 Mon Sep 17 00:00:00 2001
From: Ritesh Raj Sarraf <rrs@debian.org>
Date: Fri, 29 Jul 2016 00:03:27 +0530
Subject: [PATCH] Add initial licensing/copyright file

Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>
---
 copyright | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 63 insertions(+)
 create mode 100644 copyright

diff --git a/copyright b/copyright
new file mode 100644
index 0000000..0758ab0
--- /dev/null
+++ b/copyright
@@ -0,0 +1,63 @@
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: multipath-tools
+Upstream-Contact: Multipath Tools Project (dm-devel@redhat.com)
+Source: https://http://git.opensvc.com/?p=multipath-tools/.git;a=summary
+
+Files: *
+License: LGPL-2.1+
+
+Files: kpartx/
+        multipath/main.c
+        libmultipath/checkers/cciss_tur.c
+        libmultipath/memory.c
+        libmultipath/memory.h
+        libmultipath/parser.c
+        libmultipath/parser.h
+        libmultipath/vector.c
+        libmultipath/vector.h
+        libmultipath/version.h
+        libmultipath/file.c
+        libmultipath/alias.c
+License: GPL-2+
+
+Files: libmulitpath/uevent.c
+        libmultipath/sysfs.c
+        libmultipath/prioritizers/ontap.c
+License: GPL-2
+
+
+License: GPL-2+
+ This package is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+ .
+ This package is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>
+ .
+ On Debian systems, the complete text of the GNU General
+ Public License version 2 can be found in "/usr/share/common-licenses/GPL-2".
+
+
+License: LGPL-2.1+
+ This package is free software; you can redistribute it and/or modify
+ it under the terms of the GNU Lesser General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+ .
+ This package is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU Lesser General Public License for more details.
+ .
+ You should have received a copy of the GNU Lesser General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>
+ .
+ On Debian systems, the complete text of the GNU Lesser General
+ Public License version 2 can be found in "/usr/share/common-licenses/LGPL-2.1".
+
-- 
2.8.1


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2016-07-28 18:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 10:42 What license is multipath-tools under Ritesh Raj Sarraf
2016-07-27 22:19 ` Xose Vazquez Perez
2016-07-27 22:41   ` Xose Vazquez Perez
2016-07-28 16:53   ` Ritesh Raj Sarraf
2016-07-28 17:26     ` James Bottomley
2016-07-28 18:41       ` Ritesh Raj Sarraf [this message]
2016-07-28 18:59         ` James Bottomley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1469731260.4380.19.camel@debian.org \
    --to=rrs@debian.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.com \
    --cc=xose.vazquez@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.