<div dir="ltr"><div><div><div><div>Wow, I wasn't aware of any of this!<br><br></div>That tutorials page is really incredible... just so much material (and in different languages too!). And I'm really happy to see those wiki pages as well. So I guess now there are... too many places to put material? I think there has to be one centralized location for a thorough, wiki-like repository.<br>
<br></div>The tutorials page looks excellent, although I have a feeling people just aren't going to want to fork, edit, and then submit a push request. The thing about wikis is that contributing takes minimal effort. Is it possible to allow anyone with a github account to contribute to parts of the site (as if it were a wiki?) Also, in a wiki, if you want to create a hierarchy (ie. split off into sub-pages) at any point, you can easily do so. Is this doable in the tutorial page? For example, I think it makes more sense to have a page other than 'tutorials' as the topic for discussions such as compiler internals and parallelism.<br>
<br></div>Regarding the existing wikis, how hard would it be to centralize everything? I'm not so fond of the fact that there is one wiki for compiler hacking, and one for ocaml internals. Wikis generally include everything on a wide topic. So to me it would make more sense to have an 'ocaml' wiki, with sub-categories for compiler hacking, internals, parallelism etc. <br>
<br></div><div>Any other opinions?<br></div><div><br></div>-Yotam<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 8, 2014 at 5:57 PM, Ashish Agarwal <span dir="ltr"><<a href="mailto:agarwal1975@gmail.com" target="_blank">agarwal1975@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Regarding the need for a wiki, why not create a new Parallel Programming page under tutorials [1]. A "tutorial" can be as simple as listing the libraries available and a brief description about the high level goal of each.<div>
<br></div><div>Note <a href="http://ocaml.org" target="_blank">ocaml.org</a> is now almost entirely written in Markdown. A new page can be written quite easily, see for example The Basics tutorial [2].</div><div><br></div>
<div>[1] <a href="http://ocaml.org/learn/tutorials/" target="_blank">http://ocaml.org/learn/tutorials/</a></div>
<div>[2] <a href="https://github.com/ocaml/ocaml.org/blob/master/site/learn/tutorials/basics.md" target="_blank">https://github.com/ocaml/ocaml.org/blob/master/site/learn/tutorials/basics.md</a></div><div><br></div><div>
<br></div></div>
<div class="gmail_extra">
<br><br><div class="gmail_quote"><div><div class="h5">On Wed, Jan 8, 2014 at 5:38 PM, Anil Madhavapeddy <span dir="ltr"><<a href="mailto:anil@recoil.org" target="_blank">anil@recoil.org</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div style="word-wrap:break-word"><div><div>On 8 Jan 2014, at 22:13, Yotam Barnoy <<a href="mailto:yotambarnoy@gmail.com" target="_blank">yotambarnoy@gmail.com</a>> wrote:</div><div><br><blockquote type="cite">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Regarding a place to share ideas, it seems like it would be very useful to have an official ocaml wiki. Haskell has this and it's a huge help. In fact, I would say haskell development would be greatly hampered without it. There's so much information that's relevant to more than one library ie. doesn't fit in any particular library's documentation. It wouldn't be too hard to set up a wikimedia instance on<span> </span></span><a href="http://ocaml.org/" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">ocaml.org</a><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">, would it? Alternatively it should be pretty easy to set up something on wikia. This wiki would also be a great place to describe the conceptual implementation of the compiler, which is again what haskell has.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
</blockquote></div><br></div><div>We do have a fledgling service for "domain-specific" conversations, in the form of <a href="http://lists.ocaml.org" target="_blank">lists.ocaml.org</a>. In fact, we set up a "wg-parallel" mailing list last year, but never announced it for various reasons. This seems like a good time to advertise its existence:</div>
<div><br></div><div><a href="http://lists.ocaml.org/pipermail/wg-parallel/" target="_blank">http://lists.ocaml.org/pipermail/wg-parallel/</a></div><div><br></div><div>(note that if anyone else would like an archived list on <a href="http://lists.ocaml.org" target="_blank">lists.ocaml.org</a> for a project or community group, then please do drop a line to <a href="mailto:infrastructure@lists.ocaml.org" target="_blank">infrastructure@lists.ocaml.org</a> to request it)</div>
<div><br></div><div>Regarding other services on <a href="http://ocaml.org" target="_blank">ocaml.org</a>, we (the "infrastructure team") are happy to set them up, but please bear in mind that they all come with a maintenance burden. Dealing with security issues, backups, software updates, outages all take up time, and I confess a preference for sipping martinis and hacking on code instead of sysadmin work. Jeremy and Leo got tired of waiting for me to set up the wiki too, and started:</div>
<div><a href="https://github.com/ocamllabs/compiler-hacking/wiki" target="_blank">https://github.com/ocamllabs/compiler-hacking/wiki</a></div><div><br></div><div>If you follow the links through there, there is a 'compiler internals' page that would be good to contribute to, and you (or anyone else) is extremely welcome to add more information on topics such as parallel programming libraries there. I think we could have a decent stab at a <a href="http://wiki.ocaml.org" target="_blank">wiki.ocaml.org</a> by backing it against a GitHub repository, and not have to do any special hosting for it at all (the OPAM web pages work in a similar fashion at the moment). But for now though, I'd recommend focussing on the problem at hand (parallel programming) and getting some information down somewhere, and less on the lack of a central wiki.</div>
<span><font color="#888888"><div><br></div><div>-anil</div></font></span></div><br></div></div>_______________________________________________<br>
Infrastructure mailing list<br>
<a href="mailto:Infrastructure@lists.ocaml.org" target="_blank">Infrastructure@lists.ocaml.org</a><br>
<a href="http://lists.ocaml.org/listinfo/infrastructure" target="_blank">http://lists.ocaml.org/listinfo/infrastructure</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>