From: "Milan Stanojević" <milanst@gmail.com>
To: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
Cc: David Allsopp <dra-news@metastack.com>,
Alexey Egorov <electreg@list.ru>, Adrien Nader <adrien@notk.org>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml compiler license
Date: Thu, 5 Mar 2015 18:54:46 -0500 [thread overview]
Message-ID: <CAKR7PS_F-By9xU_83pPfNOT4fwOCJ3X=uiDsbiNcB76T_bV1tw@mail.gmail.com> (raw)
In-Reply-To: <CAHvkLrMKK4xJL58mKGT_u+MSmfFFefyMXsuVyr0DvDRU2vryFw@mail.gmail.com>
On Thu, Mar 5, 2015 at 6:28 PM, Fabrice Le Fessant
<Fabrice.Le_fessant@inria.fr> wrote:
> From the QPL 1.0 license in OCaml sources:
>
> "... distribute your modifications, in a form that is separate from
> the Software, such as patches."
>
> In GIT, the software itself is a set of patches, so it's not so clear
> for me that if the modifications are another set of patches, there are
> in a "separate form".
I thought that the intent was to make sure that modified software
can't be mistaken for original one, hence "separate form".
But, reading here
https://www.gnu.org/philosophy/license-list.html
"Q Public License (QPL), Version 1.0 (#QPL)
This is a non-copyleft free software license which is incompatible
with the GNU GPL. It also causes major practical inconvenience,
because modified sources can only be distributed as patches."
This seems like a much stronger reading.
Maybe INRIA is willing to amend the license to explicitly allow any
form of redistribution, not only patches.
next prev parent reply other threads:[~2015-03-05 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 17:38 Alexey Egorov
2015-03-05 19:41 ` Adrien Nader
2015-03-05 19:50 ` Alexey Egorov
2015-03-05 23:07 ` David Allsopp
2015-03-05 23:28 ` Fabrice Le Fessant
2015-03-05 23:54 ` Milan Stanojević [this message]
2015-03-06 7:41 ` Adrien Nader
2015-03-06 8:45 ` David Allsopp
2015-03-06 9:01 ` Roberto Di Cosmo
2015-03-06 9:08 ` David Allsopp
2015-03-06 9:31 ` Roberto Di Cosmo
2015-03-06 9:41 ` David Allsopp
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='CAKR7PS_F-By9xU_83pPfNOT4fwOCJ3X=uiDsbiNcB76T_bV1tw@mail.gmail.com' \
--to=milanst@gmail.com \
--cc=Fabrice.Le_fessant@inria.fr \
--cc=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
--cc=electreg@list.ru \
/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