caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ashish Agarwal <agarwal1975@gmail.com>
To: "Boutillier, Pierre" <Pierre_Boutillier@hms.harvard.edu>
Cc: "Richard W.M. Jones" <rich@annexia.org>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml reference manual non-free license
Date: Wed, 3 Jan 2018 14:04:53 -0500	[thread overview]
Message-ID: <CAMu2m2Kc5ER_P_AzCusF2Pqs_rtt4LKLHcma32ijCpTXwwj7cQ@mail.gmail.com> (raw)
In-Reply-To: <BB47382D-F948-4AB5-93AA-8ED36B9EC48D@hms.harvard.edu>

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

> The only way a reference manual can be admissible as a (citable)
publication is if, once released, it is not editable.

I don't think so. A good citation is one that is accessible in the exact
form that the published work is based on. For work products that can
evolve, one should thus provide a version. In the case of the OCaml manual,
this is easy enough since it is maintained in git. Additionally, there is
no "requirement" that a citation follow this criteria.

On Wed, Jan 3, 2018 at 11:52 AM, Boutillier, Pierre <
Pierre_Boutillier@hms.harvard.edu> wrote:

> Hi Richard, Hi list,
>
> I am not an authoritative voice, I only share what I'm aware in order to
> save time.
>
> Don't hold your breath expecting a relicensing.
>
> As you've already notice by yourself debian also ships the documentation
> as non-free package and everybody is already aware[1] of the drawback a
> non-free license has on integration in free distributions... (Coq has the
> exact same problem for example)
>
> The rationale is the following:
> Because scientifically research is evaluating through (and therefore sadly
> driven by) citation metrics, things built in academic settings have to be
> citable. The only way to cite a software (found up to now) is to cite its
> reference manual. The only way a reference manual can be admissible as a
> (citable) publication is if, once released, it is not editable.
>
> But, indeed, if it is not editable, it is not free anymore... Here is
> where we are stuck and have been for a long time with no escape (so far).
>
> I am (and I know I'm not the only one) sorry about that.
>
> Pierre B.
>
> [1] I didn't manage to dig out links to former discussion on the subject
> in the time frame I allocated to this reply but they are some and maybe
> someone can find them easier than I do.
>
> > Le 3 janv. 2018 à 16:08, Richard W.M. Jones <rich@annexia.org> a écrit :
> >
> > Hi, this bug was filed:
> >
> >  https://bugzilla.redhat.com/show_bug.cgi?id=1530647
> >
> > I notice that Florian is correct and copies of the reference manual do
> > indeed have a non-free license (specifically restrictions on making
> > derivative works).
> >
> > Is this intended?  If so we'll have to drop this documentation from
> > Fedora which would be a shame.  If not, could the work be relicensed
> > under a suitable free license?
> >
> > Rich.
> >
> > --
> > 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
>
>
> --
> 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: 4180 bytes --]

  parent reply	other threads:[~2018-01-03 19:05 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 [this message]
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
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=CAMu2m2Kc5ER_P_AzCusF2Pqs_rtt4LKLHcma32ijCpTXwwj7cQ@mail.gmail.com \
    --to=agarwal1975@gmail.com \
    --cc=Pierre_Boutillier@hms.harvard.edu \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.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;
as well as URLs for NNTP newsgroup(s).