All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] License Issues
Date: Thu, 18 Jun 2015 10:46:11 +0200	[thread overview]
Message-ID: <3797185.22VocOj7TI@soho> (raw)
In-Reply-To: <55826C4D.4000506@siemens.com>

Hi,


I leave my desktop a few minutes and I got this bunch of messages!!!!

El Dijous, 18 de juny de 2015, a les 08:59:25, Jan Kiszka va escriure:
> On 2015-06-17 23:35, Leopold Palomo-Avellaneda wrote:
> > El Dimecres, 17 de juny de 2015, a les 19:25:56, Gilles Chanteperdrix va
> > 
> > escriure:
> >> Leopold Palomo-Avellaneda wrote:
> >>> Hi,
> >>> 
> >>> using a debian tool to check the license of the package I have found
> >>> that
> >>> his
> >> 
> >>> files:
> >> This mail looks very different from the one you sent me privately and I
> >> told you to post on the list. It does not even concern the same version
> >> of
> >> Xenomai.
> > 
> > yes,
> > 
> > it's true. But what I understood from you was that it was better that I
> > sent to the list. That file comes from xenomai-2.6.4. Any problem then?
> > 
> > I just need to clarify this kind of things because ftp-masters are every
> > day more strict (what I think it's better), especially with licenses.
> > Never happens nothing till the day that something happen.
> 
> Out of curiosity: How do these license check work right now? What's the
> tool used and how are the outputs processed (manual or automatic
> decisions etc.)?

I use debmake [1] (debmake -ccc). I normally create a debian package from 
zero, using some templates of similar from packages. The job that makes me 
spend more time is the copyright file and make it almost lintian [2] clean. I 
have attached the files generated. Anyway, debmake makes a good job.

The copyright file, in the format:
http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

has some fields. Basically, you must put, after the header:

Files: (which files)
Copyright: (who holds the copyright. Take note that not the author. Many 
times, you could have an author that work for a company and the copyright 
belongs to the company)
License: (a key of the license) [3]

It helps me to fill the final copyright file. For instance, I know that the 
doc directory is GFDL-1.2 (at least it was on 2.6.3), so all the references to 
doc/* I put then under Files: doc/* manually.

Also, there are cases that for instance the tool show:

Files:     ksrc/drivers/analogy/national_instruments/mio_common.c
Copyright: 1997-2001 David A. Schleef <ds@schleef.org>
           2002-2006 Frank Mori Hess <fmhess@users.sourceforge.net>
License:   __UNKNOWN__
 This code 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.


the tool mark that files as __UNKNOWN__, but in the body of the license you 
can read that it's GPL-2.0+

Obviously, edit all that files and put the same header, format, whatever will 
help. It's a manual, tedious and boring job. 


> 
> > If can check this kind of stuff it would be better, that's all. For
> > instance, I was a bit surprised about the autotools generated files,
> > because I thought they would never had license.
> 
> If something has no license, it cannot be used. IIRC, you can freely
> choose the license of the generated autotools files, but you should
> state at least something somewhere to avoid needless confusion for
> people who validate the licenses of projects (AKA license clearing process).
> 
> Given that tool-based license analysis often looks at individual files
> only, a license header for those that lack a note would be the optimal
> resolution. The minimum - and likely the only option for generated files
> - is to define a default license for Xenomai that covers all files not
> explicitly carrying a note or not being covered by a subdir COPYING file.
> 
> Did you also look at Xenomai 3 already in this regard, Leopold?

Yes, I put both files from xenomai-3 git and xenomai-2.6 git.

I know that is a lot of disgusting work, to check all the files, see the 
header, or whatever, but, at least for xenomai-3 could be good.

Another thing could be write a file explaining every directory license. I 
think that the kernel patches are GPL-2.0 but the library are LGPL2.1, but I 
don't know which directories are from one or other, of if they are mixed. In 
xenomai-2.6 is not done.

In Xenomai-3, the web says:
"For information regarding a particular software component, you should look at 
the COPYING file available in the directory containing the relevant source 
code."

but:

$../xenomai-3.git$ ls
config   demo  include  lib README   testsuite configure.ac debian                     
doc   kernel   Makefile.am  scripts  utils

$../xenomai-3.git$ tree -fia | grep COPYING
./include/COPYING
./kernel/cobalt/COPYING
./kernel/cobalt/posix/COPYING
./kernel/cobalt/rtdm/COPYING
./lib/alchemy/COPYING
./lib/analogy/COPYING
./lib/cobalt/COPYING
./lib/copperplate/COPYING
./lib/psos/COPYING
./lib/vxworks/COPYING

doc, config, utils, scripts, testsuite, debian* and demo directories have not 
COPYING files.

I have admit that I began to work with 2.6.4, but looking this it seems more 
easy (in license terms) to manage this issue with xenomai-3. :-) (And no 
Gilles, it's not a waste of time. A lot of people use 2.6.x, like me for 
instance)

Best regards,

Leopold

[1] http://anonscm.debian.org/cgit/collab-maint/debmake.git
[2] Lintian is a tool used to check the quality of a debian package. It try to 
make it following all the debian policies.
[3] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#stand-alone-license-paragraph


-- 
--
Linux User 152692     GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: copyright-xenomai-2.6-debug.zip
Type: application/zip
Size: 34442 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150618/dbdbc425/attachment.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: copyrights-xenomai3-debug.zip
Type: application/zip
Size: 44039 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150618/dbdbc425/attachment-0001.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150618/dbdbc425/attachment.sig>

      parent reply	other threads:[~2015-06-18  8:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 16:25 [Xenomai] License Issues Leopold Palomo-Avellaneda
2015-06-17 16:48 ` Lennart Sorensen
2015-06-17 21:36   ` Leopold Palomo-Avellaneda
2015-06-17 17:25 ` Gilles Chanteperdrix
2015-06-17 21:35   ` Leopold Palomo-Avellaneda
2015-06-18  6:59     ` Jan Kiszka
2015-06-18  7:05       ` Gilles Chanteperdrix
2015-06-18  7:18         ` Philippe Gerum
2015-06-18  7:19         ` Jan Kiszka
2015-06-18  7:25           ` Gilles Chanteperdrix
2015-06-18  7:41             ` Jan Kiszka
2015-06-18  8:03       ` Gilles Chanteperdrix
2015-06-18  8:05         ` Gilles Chanteperdrix
2015-06-18  8:46       ` Leopold Palomo-Avellaneda [this message]

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=3797185.22VocOj7TI@soho \
    --to=leo@alaxarxa.net \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.org \
    /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.