caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Yotam Barnoy <yotambarnoy@gmail.com>,
	Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Activating wiki on ocaml github
Date: Thu, 3 Apr 2014 11:49:15 +0200	[thread overview]
Message-ID: <D8DA96D05609470DB9A98D8A44897E2A@erratique.ch> (raw)
In-Reply-To: <CAPFanBH9ANLf-oyeUhXMu6cAC=fW4MuXKHUeJ+qh7SMnGM_xHA@mail.gmail.com>

Le jeudi, 3 avril 2014 à 11:16, Gabriel Scherer a écrit :
> Color me unconvinced. My experience with wikis has been mild at best.
> There exist wikis for Camlp4 and Ocamlbuild (
> http://brion.inria.fr/gallium/index.php/Camlp4 ,
> http://brion.inria.fr/gallium/index.php/Ocamlbuild ) that have seen
> little contributions outside the core maintainers, and the content is
> often ignored as it is not part of the official manual.

Yes terrible idea. Though I'd say that's not exactly the same case as we have here. These wiki were created because the creator of these tools refused to write proper/good documentation and said let's "crowd source" the documentation to a wiki, a behaviour that should immediately raise red flags.  
  
> If the documentation need to be synchronized with the compiler's evolution, I
> suspect the best place to put it would be either along the compiler.

The real answer seems to be: literate programming. Maybe more realistically ocamldoc'ing the interfaces and writing cross-referenced [1] additional sections in there at the end of the files could be a good start.

Best,

Daniel

[1] ocamldoc's link syntax combined with its xref syntax allows to author text with very precise references see: http://caml.inria.fr/pub/docs/manual-ocaml-4.01/ocamldoc.html#sss:crossref



  reply	other threads:[~2014-04-03  9:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  2:20 Yotam Barnoy
2014-04-03  9:16 ` Gabriel Scherer
2014-04-03  9:49   ` Daniel Bünzli [this message]
2014-04-03  9:49   ` Jeremy Yallop
2014-04-03 11:07 ` Ashish Agarwal
2014-04-03 14:05   ` Yotam Barnoy
2014-04-03 14:40     ` Adrien Nader
2014-04-03 14:49     ` Leo White
2014-04-03 15:51     ` Ashish Agarwal
2014-04-03 15:52     ` Amir Chaudhry
2014-04-03 16:44       ` Yotam Barnoy
2014-04-03 17:52         ` Amir Chaudhry
2014-04-03 18:10           ` Yotam Barnoy
2014-04-03 18:15         ` Ashish Agarwal

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=D8DA96D05609470DB9A98D8A44897E2A@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    --cc=yotambarnoy@gmail.com \
    /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).