From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] portaudio: add license information
Date: Thu, 23 May 2013 09:33:14 +0200 [thread overview]
Message-ID: <20130523073314.GE3373@free.fr> (raw)
In-Reply-To: <20130523070918.GG25186@sapphire.tkos.co.il>
Baruch, All,
On 2013-05-23 10:09 +0300, Baruch Siach spake thusly:
> On Thu, May 23, 2013 at 08:59:04AM +0200, Yann E. MORIN wrote:
[--SNIP--]
> > This is not really MIT, since there is additional text:
> >
> > ---8<---
> > * The text above constitutes the entire PortAudio license; however,
> > * the PortAudio community also makes the following non-binding
> > * requests:
> > *
> > * Any person wishing to distribute modifications to the Software is
> > * requested to send the modifications to the original developer so that
> > * they can be incorporated into the canonical version. It is also
> > * requested that these non-binding requests be included along with the
> > * license above.
> > ---8<---
> >
> > So I'd say:
> > PORTAUDIO_LICENSE = portaudio license (MIT-like plus special clause)
> >
> > (which by the way makes it non-free software.)
>
> Well, the text you cite says explicitly that these are "non-binding requests".
> Would you still consider this non-free?
Well, I poundered that, yes. But the way it is phrased is dubious.
First, it states that it is a non-binding clause. But then the clause
states "[a]ny person [doing changes] is requested to send modifications
[upstream]." The term "requested" is a bit strong for a non-binding
clause.
So, let me rephrase:
(which by the way *may* make it non-free software.)
But the final word should come from a legal counsel, of course. :-)
Anyway, this is not "MIT" per-se.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-05-23 7:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 0:24 [Buildroot] [PATCH 1/5] dvb-apps utilities: needs threads Gilles Talis
2013-05-23 0:24 ` [Buildroot] [PATCH 2/5] tvheadend: " Gilles Talis
2013-05-23 6:54 ` Yann E. MORIN
2013-05-23 14:44 ` Gilles Talis
2013-05-23 17:42 ` Yann E. MORIN
2013-05-23 20:34 ` Peter Korsgaard
2013-05-23 0:24 ` [Buildroot] [PATCH 3/5] portaudio: " Gilles Talis
2013-05-23 20:37 ` Peter Korsgaard
2013-05-23 0:24 ` [Buildroot] [PATCH 4/5] portaudio: add license information Gilles Talis
2013-05-23 6:59 ` Yann E. MORIN
2013-05-23 7:09 ` Baruch Siach
2013-05-23 7:33 ` Yann E. MORIN [this message]
2013-05-23 14:49 ` Gilles Talis
2013-05-23 17:44 ` Yann E. MORIN
2013-05-23 17:52 ` Gilles Talis
2013-05-23 0:24 ` [Buildroot] [PATCH 5/5] libatomic_ops: fix build failure seen with toolchain without threads support Gilles Talis
2013-05-23 20:48 ` Peter Korsgaard
2013-05-23 6:51 ` [Buildroot] [PATCH 1/5] dvb-apps utilities: needs threads Yann E. MORIN
2013-05-23 20:33 ` Peter Korsgaard
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=20130523073314.GE3373@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox