All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Leopold Palomo-Avellaneda <leo@alaxarxa.net>,
	Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] License Issues
Date: Thu, 18 Jun 2015 08:59:25 +0200	[thread overview]
Message-ID: <55826C4D.4000506@siemens.com> (raw)
In-Reply-To: <11760776.AKg2s0Tc8c@indiana>

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.)?

> 
> 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?

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2015-06-18  6:59 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 [this message]
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

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=55826C4D.4000506@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=leo@alaxarxa.net \
    --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.