caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Siraaj Khandkar <siraaj@khandkar.net>
To: Siraaj Khandkar <siraaj@khandkar.net>
Cc: Ashish Agarwal <agarwal1975@gmail.com>,
	Wojciech Meyer <wojciech.meyer@gmail.com>,
	Anil Madhavapeddy <anil@recoil.org>,
	Benedikt Meurer <benedikt.meurer@googlemail.com>,
	caml-list@inria.fr
Subject: Re: [Caml-list] OCaml wiki
Date: Fri, 21 Dec 2012 12:52:30 -0500	[thread overview]
Message-ID: <28D89228-06D5-4BBF-920F-6233737B8659@khandkar.net> (raw)
In-Reply-To: <FD9A01B9-19E2-4333-8BD1-5C0B1B251A77@khandkar.net>

Or, it seems one can haz cake and eat it too! :)

https://github.com/jgm/gitit


On Dec 21, 2012, at 10:33 AM, Siraaj Khandkar <siraaj@khandkar.net> wrote:

> +1
> 
> Wiki is a fun concept, but is a complete mess in practice.
> 
> It has some versioning capabilities, but not nearly as sophisticated as a DVCS
> such as Git. Obviously, there're editing capabilities, but not nearly as
> productive as your favorite text editor.
> 
> Why force suboptimal tools on people that are interested in an optimal
> programming language? ;)
> 
> Now, what about the maintainers? How do they even begin to keep track of tiny
> edits to 1000's of wiki pages? Queueing theory to the rescue! A pull request
> queue gives them a chance to audit the contributions in a sane manner (without
> wasting their volunteered time).
> 
> 
> On Dec 20, 2012, at 9:49 PM, Ashish Agarwal <agarwal1975@gmail.com> wrote:
> 
>> A wiki could be good but I strongly encourage any such effort to integrate
>> with ocaml.org, and to carefully weigh the pros and cons. Wikis make
>> contributions easier, but you need someone to keep the content organized
>> and do some basic quality control. Also, the structure of the documentation
>> is not very customizable. The question is whether pushing to a git repo
>> (the current contribution method for ocaml.org) is so much harder (given
>> that we're all programmers after all).
>> 
>> The tutorials page is a good candidate for converting to wiki format, but
>> remember that a wiki is where all this content came from, and it eventually
>> got out of date. We could create wiki.ocaml.org, but then the question is
>> how to make it integrate nicely with the rest of the pages that don't fit
>> the wiki model.
>> 
>> Finally, which wiki software to use? None are very good, and who amongst us
>> is keen to hack into php code. My initial goal for ocaml.org was to use
>> ocsigen and ocsimore, but there is a big upfront cost in getting such a
>> site implemented.
>> 
>> Whatever the community decides, we can support and integrate with ocaml.org.
>> My only strong opinion is please don't build a separate unrelated site,
>> with duplication of effort and and fragmentation of content.
>> 
>> 
>> On Thu, Dec 20, 2012 at 6:50 PM, Wojciech Meyer <wojciech.meyer@gmail.com>wrote:
>> 
>>> 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

-- 
Siraaj Khandkar
.o.
..o
ooo


  reply	other threads:[~2012-12-21 17:52 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 [this message]
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=28D89228-06D5-4BBF-920F-6233737B8659@khandkar.net \
    --to=siraaj@khandkar.net \
    --cc=agarwal1975@gmail.com \
    --cc=anil@recoil.org \
    --cc=benedikt.meurer@googlemail.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).