caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Marek Kubica <marek@xivilization.net>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml reference manual non-free license
Date: Fri, 5 Jan 2018 22:34:58 +0100	[thread overview]
Message-ID: <CAPFanBH9bp1tX36UqXNYFO4FO+1_g5B59yB1CYK_TBWbWgoUGQ@mail.gmail.com> (raw)
In-Reply-To: <20180105215504.14aefb1f@xivilization.net>

[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]

> It also creates issues for people wanting to contribute to the OCaml
> manual on e.g. GitHub. It is not possible to create a pull request with
> a change to the manual on any public platform because that would be
> publishing without approval.


I think this view is exaggerated, as I don't think that the people who
wrote this clause would consider hosting (modified) .etex files on a Github
clone of the manual's repository as "distribution". To "distribute" the
documentation or manual, I would at least expect a rendered (compiled)
version of it. It is not necessary to distribute a rendered copy of the
manual to contribute to it.

I'm not particularly fond of custom licenses either, but I don't think that
they should be interpreted as making open-source contributions impossible.


On Fri, Jan 5, 2018 at 9:55 PM, Marek Kubica <marek@xivilization.net> wrote:

> On Thu, 4 Jan 2018 14:44:05 +0100
> Xavier Leroy <xavier.leroy@inria.fr> wrote:
>
> > The restriction on derivative works is very much intended.
> >
> > The license predates Creative Commons, but in CC terms it would be
> > CC-BY-ND.
>
> Non-derivative licenses like the custom one on the OCaml manual and
> also CC-BY-ND create annoying edge cases. We've seen the case of
> Debian and Fedora already. But reading the license:
>
> > - Any translation or derivative work of the OCaml documentation and
> >  user's manual must be approved by the authors in writing before
> >  distribution.
>
> It also creates issues for people wanting to contribute to the OCaml
> manual on e.g. GitHub. It is not possible to create a pull request with
> a change to the manual on any public platform because that would be
> publishing without approval.
>
> Kind regards,
> Marek
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 3032 bytes --]

  reply	other threads:[~2018-01-05 21:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 15:08 Richard W.M. Jones
2018-01-03 16:52 ` Boutillier, Pierre
2018-01-03 18:13   ` Allan Wegan
2018-01-03 19:12     ` Hendrik Boom
2018-01-03 19:04   ` Ashish Agarwal
2018-01-04 13:44 ` Xavier Leroy
2018-01-05 20:55   ` Marek Kubica
2018-01-05 21:34     ` Gabriel Scherer [this message]
2018-01-06 11:38     ` Oliver Bandel
2018-01-08 16:34   ` Richard W.M. Jones
2018-03-11 11:20   ` Maxime Dénès
2018-03-11 11:22     ` Maxime Dénès

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=CAPFanBH9bp1tX36UqXNYFO4FO+1_g5B59yB1CYK_TBWbWgoUGQ@mail.gmail.com \
    --to=gabriel.scherer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=marek@xivilization.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;
as well as URLs for NNTP newsgroup(s).