caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rich@annexia.org>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml reference manual non-free license
Date: Mon, 8 Jan 2018 16:34:10 +0000	[thread overview]
Message-ID: <20180108163410.l2ao2ajkm653fi4n@annexia.org> (raw)
In-Reply-To: <07e8a536-984b-850b-6dec-2c30ea0cfb2d@inria.fr>

On Thu, Jan 04, 2018 at 02:44:05PM +0100, Xavier Leroy wrote:
> On 03/01/2018 16:08, Richard W.M. Jones wrote:
> >  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?
> 
> Debian is happy with putting OCaml's manual in the non-free section.  
> 
> https://fedoraproject.org/wiki/Licensing:Main lists CC-BY-ND as a good
> license for contents, but doesn't list it (neither good nor bad) for
> documentation.  Care to explain the difference between documentation
> and contents?

Thanks Xavier.  Fedora doesn't have a non-free section, although
people use other repositories such as RPMFusion which ship packages
that are legally difficult to ship for all sorts of reasons.

"Content" is stuff like clip art, fonts and things and apparently it's
not suitable for documentation.

We'll drop the documentation for now.

Rich.

-- 
Richard Jones

  parent reply	other threads:[~2018-01-08 16:34 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
2018-01-08 16:34   ` Richard W.M. Jones [this message]
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=20180108163410.l2ao2ajkm653fi4n@annexia.org \
    --to=rich@annexia.org \
    --cc=caml-list@inria.fr \
    --cc=xavier.leroy@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).