From: oliver <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: [Caml-list] Licenses - Confusion
Date: Wed, 22 May 2013 14:34:27 +0200 [thread overview]
Message-ID: <20130522123427.GA1894@siouxsie> (raw)
Hello,
I did publish one of my tools as GPLv3.
It is written in OCaml.
Now I saw at another project, that there is the need
for an "OCaml exception" regarding linking.
If thats true I may have missed a crucial points
when thinking about the license for tools written in OCaml.
I'm not a lwayer, and all that licenses stuff is rather+
annoying and confusing to me.
That OCaml code needs special treatment here, even
OCaml is shipped even with Debian, who surely would not accept
GPL-violating stuff, is annoying.
So, some questions came up now:
- Which licenses can be used together with OCaml
without changes?
- Which licenses can be used together with added exceptions,
and which exceptions are that?
- In case of needed exceptions, where to find "ready-to-use"-versions
of these licenses?
- How to handle a project that already was published under a license
that does not match 1:1 with OCaml licenses?
It's not possible to delete any copy someone did of it already.
Also it's not possible to sed all those people a message, to inform them
that the license must be modified.
Also I'm not sure how this could work, because the license came with the
software at one time, and the correction comes later.
Regarding the third point: it would be a good idea to provide
"ready to use" licenses, which include the exceptions, instead
of lawyer-compatible (but not necessarily programmer-compatible)
explanations with many if-then-else's.
Ciao,
Oliver
next reply other threads:[~2013-05-22 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 12:34 oliver [this message]
2013-05-22 12:39 ` Anil Madhavapeddy
2013-05-22 16:40 ` Marek Kubica
2013-05-22 13:02 ` Török Edwin
2013-05-22 17:19 ` Adrien Nader
2013-05-23 6:36 ` Stéphane Glondu
2013-05-23 8:41 ` Daniel Bünzli
2013-05-23 21:07 ` Marek Kubica
2013-05-23 21:36 ` Stéphane Glondu
2013-05-23 22:28 ` Daniel Bünzli
2013-05-23 21:39 ` Ernesto Posse
2013-05-23 21:45 ` Chet Murthy
2013-05-23 22:11 ` Stefano Zacchiroli
2013-05-23 22:52 ` oliver
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=20130522123427.GA1894@siouxsie \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
/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