caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Stefano Zacchiroli <zack@upsilon.cc>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Online documentation for Core now available
Date: Thu, 12 Nov 2009 17:07:36 +0100	[thread overview]
Message-ID: <20091112160736.GA14482@usha.takhisis.invalid> (raw)
In-Reply-To: <9d3ec8300911120707g3ab296e1sd31eb299459e1323@mail.gmail.com>

On Thu, Nov 12, 2009 at 10:07:04AM -0500, Till Varoquaux wrote:
> FWIW: It is not recommended to license documentation with the same
> kind of license as source code; a lot of restrictions that apply to

I don't want to drift too much in this discussion (OT here), but notice
that in this specific case the documentation in question is
*generated*. While in general what you say about different concerns
among doc and code is true, in such a case way more concerns of code
apply also to (generated) documentations; of course some still remain
different (e.g. linking concerns).

Whether or not the amount of similarities between generated doc and
source code warrants identical licensing is of course up to the
authors. For distributions, it generally eases several maintenance
aspects.

Cheers.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime


      reply	other threads:[~2009-11-12 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 12:30 Yaron Minsky
2009-11-12 14:51 ` [Caml-list] " Stefano Zacchiroli
2009-11-12 15:06   ` Yaron Minsky
2009-11-12 15:07   ` Till Varoquaux
2009-11-12 16:07     ` Stefano Zacchiroli [this message]

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=20091112160736.GA14482@usha.takhisis.invalid \
    --to=zack@upsilon.cc \
    --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).