caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vincent Balat <vincent.balat@univ-paris-diderot.fr>
To: Ashish Agarwal <agarwal1975@gmail.com>
Cc: caml-list@inria.fr, Wojciech Meyer <wojciech.meyer@gmail.com>
Subject: Re: [Caml-list] OCaml wiki
Date: Sun, 23 Dec 2012 15:53:39 +0100	[thread overview]
Message-ID: <201212231553.39806.vincent.balat@univ-paris-diderot.fr> (raw)
In-Reply-To: <CAMu2m2J3XnH20+dpx9GOka7P0MKPw89+ZHXEmPutzac+eBqFnw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

> > It is possible for example to keep the current web site and add
> > progressively new pages using the wiki.
> 
> Nice! If we did this, a gradual transition is key.
> 
> > We will release version 1 soon.
> 
> This is even more critical. Currently the ocsimore page says "It is under
> development (not usable for now)." Using a wiki locks us in to a very
> specific model. We need confidence the tool is stable and will continue to
> be maintained and developed.

I can change this sentence if it scares you ;) Actually Ocsimore has been used 
for years at PPS without any problem. Every member of the laboratory has its 
own wiki for his personal pages and people like it. 
The part that is still not really user friendly is the administration 
interface. But a lot of work has been done in the past few months by the new 
maintainer Jacques-Pascal Deplaix and he plans to improve a few more things 
during the next weeks. I just don't want to call 1.0 something that is too 
difficult to install or that is badly documented.

I understand that you would prefer a wiki that is used on more than 2 Web 
sites, and that has commercial suport (or at least a large community) and I 
won't blame you for doing that choice. But Ocsimore is not going to die 
(because it's part of the Ocsigen project). And using Ocsimore on ocaml.org 
would be a good opportunity to support an OCaml project (may be OCaml Labs or 
the consortium could help if you need new features?). It would also be easier 
to find contributors amongst OCaml developers for creating customized 
extensions you may need ...

Why not giving it a try? We can install and configure it if you want.

Vincent

[-- Attachment #2: Type: text/html, Size: 5063 bytes --]

  reply	other threads:[~2012-12-23 14:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 23:15 Wojciech Meyer
2012-12-20 23:19 ` Malcolm Matalka
2012-12-20 23:22 ` Anil Madhavapeddy
2012-12-20 23:31   ` Benedikt Meurer
2012-12-20 23:34     ` Anil Madhavapeddy
2012-12-20 23:38       ` Malcolm Matalka
2012-12-20 23:50       ` Wojciech Meyer
2012-12-21  2:49         ` Ashish Agarwal
2012-12-21  8:37           ` Philippe Veber
2012-12-21  9:13             ` Fermin Reig
2012-12-21  9:39               ` Philippe Veber
2012-12-21 13:05           ` Wojciech Meyer
2012-12-21 13:31             ` Adrien
2012-12-21 16:39             ` Ashish Agarwal
2012-12-21 15:33           ` Siraaj Khandkar
2012-12-21 17:52             ` Siraaj Khandkar
2012-12-21 13:00     ` Hezekiah M. Carty
2012-12-21  1:31 ` [Caml-list] OCaml search into libraries for ocaml.org Francois Berenger
2012-12-21  2:57   ` Ashish Agarwal
2012-12-21  7:34     ` forum
2012-12-21 15:31       ` Leo White
2012-12-21 19:57   ` AW: " Gerd Stolpmann
2012-12-21 20:22     ` Török Edwin
2012-12-21 20:34       ` AW: " Gerd Stolpmann
2012-12-21 20:37         ` Edgar Friendly
2012-12-21 20:41           ` AW: " Gerd Stolpmann
2012-12-21 20:48             ` Library install standards (was: Re: AW: AW: AW: [Caml-list] OCaml search into libraries for ocaml.org) Edgar Friendly
2012-12-21 20:59               ` [Caml-list] Re: Library install standards Török Edwin
2012-12-21 23:47                 ` AW: " Gerd Stolpmann
2012-12-21 16:20 ` [Caml-list] OCaml wiki Vincent Balat
2012-12-21 16:45   ` Ashish Agarwal
2012-12-23 14:53     ` Vincent Balat [this message]
2012-12-25  1:14       ` 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=201212231553.39806.vincent.balat@univ-paris-diderot.fr \
    --to=vincent.balat@univ-paris-diderot.fr \
    --cc=agarwal1975@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=wojciech.meyer@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).