From: Allan Wegan <allanwegan@allanwegan.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml reference manual non-free license
Date: Wed, 3 Jan 2018 19:13:14 +0100 [thread overview]
Message-ID: <267e5e21-2598-4ec5-9c42-3087f25fea0d@allanwegan.de> (raw)
In-Reply-To: <BB47382D-F948-4AB5-93AA-8ED36B9EC48D@hms.harvard.edu>
[-- Attachment #1.1: Type: text/plain, Size: 855 bytes --]
> 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).
Not working in science myself - but is it forbidden to cite a specific
version of a manual as published by one specific source?
Just mentioning the repository where one got the manual from and the
commit ID or version ID given by the author should provide enough data
for everyone to be able to verify the cited source.
--
Allan Wegan
<http://www.allanwegan.de/>
Jabber: allanwegan@ffnord.net
OTR-Fingerprint: E4DCAA40 4859428E B3912896 F2498604 8CAA126F
Jabber: allanwegan@jabber.ccc.de
OTR-Fingerprint: A1AAA1B9 C067F988 4A424D33 98343469 29164587
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-03 18:13 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 [this message]
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
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=267e5e21-2598-4ec5-9c42-3087f25fea0d@allanwegan.de \
--to=allanwegan@allanwegan.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).