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
>