From: Till Varoquaux <till@pps.jussieu.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Online documentation for Core now available
Date: Thu, 12 Nov 2009 10:07:04 -0500 [thread overview]
Message-ID: <9d3ec8300911120707g3ab296e1sd31eb299459e1323@mail.gmail.com> (raw)
In-Reply-To: <20091112145132.GA25423@usha.takhisis.invalid>
FWIW: It is not recommended to license documentation with the same
kind of license as source code; a lot of restrictions that apply to
source code do not make any sense when it comes to documentation. When
licencing a project it is good to consider a three pronged approach:
1) Licensing the main code of the project. This might be split in:
1.1) The exported library
1.2) The tools (test suites etc.)
2) Licensing the documentation
3) Licensing the included examples
A typical example would be:
1)
1.1) LGPL + linking exception
1.2) GPL
2) FDL
3) Public domain
Of course which licenses you choose is entirely up to you... Creative
commons [1] provides an easy interface to choose licenses...
Till
[1] http://creativecommons.org/choose/
On Thu, Nov 12, 2009 at 9:51 AM, Stefano Zacchiroli <zack@upsilon.cc> wrote:
> On Thu, Nov 12, 2009 at 07:30:42AM -0500, Yaron Minsky wrote:
>> People have been asking for this since our last release, and now we've
>> finally got it done. Here's the link:
>>
>> http://www.janestreet.com/ocaml/janestreet-ocamldocs/
>
> I, thanks a lot for the doc!
> Can you please comment on the licensing problems I've highlighted in
> this mail:
> http://lists.debian.org/debian-ocaml-maint/2009/11/msg00101.html ?
>
> BTW, it would be nice to have a clear(er) contact point for that doc on
> the web.
>
> Thanks again!
> 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
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2009-11-12 15:07 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 [this message]
2009-11-12 16:07 ` Stefano Zacchiroli
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=9d3ec8300911120707g3ab296e1sd31eb299459e1323@mail.gmail.com \
--to=till@pps.jussieu.fr \
--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).