caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml reference manual non-free license
Date: Sat, 06 Jan 2018 12:38:38 +0100	[thread overview]
Message-ID: <20180106123838.Horde.URMMB2lE0F-9ap2zUOhpW_F@webmail.in-berlin.de> (raw)
In-Reply-To: <20180105215504.14aefb1f@xivilization.net>


Zitat von Marek Kubica <marek@xivilization.net> (Fri, 5 Jan 2018  
21:55:04 +0100)

> On Thu, 4 Jan 2018 14:44:05 +0100
> Xavier Leroy <xavier.leroy@inria.fr> wrote:
>
[...]
>
>> - 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.
[...]

As I understand it: The official, approved version is, what INRIA provides via
*.tar.gz as ocaml release.
Anything before is unapproved stuff, staged to become approved.

Then providing pull-requests is no problem.
And, btw. creating a pull-request does not mean that they are accepted,
which is another step that seperates approved and non-approved.

Regarding the quotation-problem, the official version might come with
hashes and cryptographic igning of a document.
But it seems, such thing is missing in science in general.
For example measurement data can be found on many servers that provide  
data openly
(which is good), but so far no hashsums or signing of the data is done.
So, data corruption might occur, and the validity of data is gone.

This is not only a problem of computer science / OCaml docs.

Ciao,
   Oliver


  parent reply	other threads:[~2018-01-06 11:38 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
2018-01-06 11:38     ` Oliver Bandel [this message]
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=20180106123838.Horde.URMMB2lE0F-9ap2zUOhpW_F@webmail.in-berlin.de \
    --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;
as well as URLs for NNTP newsgroup(s).