From: David Allsopp <dra-news@metastack.com>
To: Roberto Di Cosmo <roberto@dicosmo.org>
Cc: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>,
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: Fri, 6 Mar 2015 09:41:21 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9E9978C4B@Remus.metastack.local> (raw)
In-Reply-To: <20150306093130.GB15242@traveler>
Roberto Di Cosmo wrote:
> David, you are right: one cannot "change" the terms of a licence used on a
> piece of code after releasing this piece of code under this licence.
> But we are talking about "interpretation" of these terms, which is quite a
> different story.
Yes, but the copyright holder does not get to dictate the interpretation.
> If you look at FSF/OSI/<whatever other external entity including me> to
> know whether a git branch is fine as an implementation of "separate", you
> only get an opinion... maybe a well respected opinion, but just an opinion
> that may become the subject of debate later on. And avoiding debate is a
> desirable thing.
Absolutely - and hence why it's sensible to ask!
> If Inria says publicly (e.g. on this mailing list): "for us it's fine to
> see OCaml derivatives developed and published as separate git branches",
> then you get the work owner's explicit statement that this practice is
> acceptable for the only entity entitled to enforce the licence. And
> that's the end of the story: simple, clear, undebatable, no hassle.
Yes, I agree - sorry, I made my point unclearly. The point I was making is that if Inria were to say "no, we don't accept that as satisfying the licence" then that is just their opinion. You can still do it, you just know that you're likely to end up in court testing the licence if you do. The arbiter in a difference of opinion on interpretation is the legal system, not the copyright holder.
David
prev parent reply other threads:[~2015-03-06 9:41 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ć
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 [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=E51C5B015DBD1348A1D85763337FB6D9E9978C4B@Remus.metastack.local \
--to=dra-news@metastack.com \
--cc=Fabrice.Le_fessant@inria.fr \
--cc=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=electreg@list.ru \
--cc=roberto@dicosmo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox