From: Wojciech Meyer <wojciech.meyer@gmail.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: Benedikt Meurer <benedikt.meurer@googlemail.com>, caml-list@inria.fr
Subject: Re: [Caml-list] OCaml wiki
Date: Thu, 20 Dec 2012 23:50:08 +0000 [thread overview]
Message-ID: <wfehikgu6n.fsf@gmail.com> (raw)
In-Reply-To: <88F05F0A-10A2-47AF-8285-575E95797E54@recoil.org> (Anil Madhavapeddy's message of "Thu, 20 Dec 2012 23:34:18 +0000")
Anil Madhavapeddy <anil@recoil.org> writes:
> On 20 Dec 2012, at 23:31, Benedikt Meurer <benedikt.meurer@googlemail.com> wrote:
>>
>> On Dec 21, 2012, at 0:22 , Anil Madhavapeddy <anil@recoil.org> wrote:
>>
>>> Personally, I've got mixed feelings about wikis from experience with
>>> previous projects, since they get out of date very rapidly indeed. They
>>> do work well if someone's maintaining it, but if that's the case, why
>>> not just push these tips and guides to the existing ocaml.org site?
>>>
>>> I'm happy to run a wiki on the OCL infrastructure, but would strongly
>>> prefer contributions to the ocaml.org Git repo with all this good stuff
>>> instead! If it really turns out we need a swanky wiki, that can be arranged
>>> later...
>>
>> Why not use the wiki provided by Github for the ocaml.org project?
>
> That works too; Thomas has written a Github Markdown to HTML converter in
> COW [1], and is using that to generate the OPAM website from the Github
> wiki (for the documentation that you see on opam.ocamlpro.com).
Yes, we could use github pages as long as they are searchable, I see no
problem with it. I think the biggest advantage of wiki would be that
everything would be in single place and hyperlinked.
As for protecting the wiki from being up-date emacswiki [1] is always a
great example that it is possible as long as people maintain their
webpages. Also, I feel that ocaml.org pages on github would be a good
entry point.
[1] http://emacswiki.org/
-Wojciech
next prev parent reply other threads:[~2012-12-20 23:49 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 [this message]
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
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=wfehikgu6n.fsf@gmail.com \
--to=wojciech.meyer@gmail.com \
--cc=anil@recoil.org \
--cc=benedikt.meurer@googlemail.com \
--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).