From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id D3E067EE99 for ; Thu, 9 Jan 2014 03:52:45 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of yotambarnoy@gmail.com) identity=pra; client-ip=209.85.216.179; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="yotambarnoy@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of yotambarnoy@gmail.com designates 209.85.216.179 as permitted sender) identity=mailfrom; client-ip=209.85.216.179; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="yotambarnoy@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-qc0-f179.google.com) identity=helo; client-ip=209.85.216.179; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="postmaster@mail-qc0-f179.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiwEAGYOzlLRVdizlWdsb2JhbABZgkd8VrBriFWBCAgWDgEBAQEHDQkJEiqCJQEBAQMBAQEBPQEbEgsBAwELBgULDRUZIQEBBAEMAQUBHAYTFIdbAQMJCA2dZoxcgwmREQoZJw1khC4RAQUMjGaCDwQHCoIlgggEiUOMBGSBbIEwiyqDThgphHce X-IPAS-Result: AiwEAGYOzlLRVdizlWdsb2JhbABZgkd8VrBriFWBCAgWDgEBAQEHDQkJEiqCJQEBAQMBAQEBPQEbEgsBAwELBgULDRUZIQEBBAEMAQUBHAYTFIdbAQMJCA2dZoxcgwmREQoZJw1khC4RAQUMjGaCDwQHCoIlgggEiUOMBGSBbIEwiyqDThgphHce X-IronPort-AV: E=Sophos;i="4.95,627,1384297200"; d="scan'208";a="52362749" Received: from mail-qc0-f179.google.com ([209.85.216.179]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 09 Jan 2014 03:52:44 +0100 Received: by mail-qc0-f179.google.com with SMTP id i8so2195545qcq.24 for ; Wed, 08 Jan 2014 18:52:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=q73NdMXkeutCq9dWjbFftdRA5HWce7LFWUW7gbfDjhw=; b=0G3T4lQ5TnofAu4kuirUBzErcuzePw3w4Qog9XIoDtlMuzNls7FiG8h2hCCDfVowxn iZvaMsyUmFq8m5X5P6Zalv1lUaQqbJVQqTyQotBwLDQte4qjotePfLJRHXGKAAERkQhD PlsH+PhNJPHrhJMJaAtfgr7I1Z11dqsivjMFyaXIqjKewEYysIFziilZSLKX7zREDQTG Y8pvDmzaBt2pUMCevJtjPeecOGeZHVby7wk8SnvOiTUsY/DNL+0s6dxqlkhdeUPU486E bZAW/68gb3uqL0BBLPkIwQ2wjUsH3egVr+eLaToCqkxAKF2vPj6c5OEDjroHIpYY+YJg nOjg== X-Received: by 10.49.98.35 with SMTP id ef3mr1798237qeb.30.1389235963720; Wed, 08 Jan 2014 18:52:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.224.95.8 with HTTP; Wed, 8 Jan 2014 18:52:23 -0800 (PST) In-Reply-To: References: <20140108202952.GA3669@voyager> <17C64E48-1AC4-4C4E-94E1-4170A39111C7@recoil.org> From: Yotam Barnoy Date: Wed, 8 Jan 2014 21:52:23 -0500 Message-ID: To: Ashish Agarwal Cc: Anil Madhavapeddy , Roberto Di Cosmo , Ocaml Mailing List , infrastructure Content-Type: multipart/alternative; boundary=047d7bea3cb62079b704ef80b425 Subject: Re: [Caml-list] [ocaml-infra] Concurrent/parallel programming --047d7bea3cb62079b704ef80b425 Content-Type: text/plain; charset=ISO-8859-1 Wow, I wasn't aware of any of this! 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. 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. 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. Any other opinions? -Yotam On Wed, Jan 8, 2014 at 5:57 PM, Ashish Agarwal wrote: > 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. > > Note ocaml.org is now almost entirely written in Markdown. A new page can > be written quite easily, see for example The Basics tutorial [2]. > > [1] http://ocaml.org/learn/tutorials/ > [2] > https://github.com/ocaml/ocaml.org/blob/master/site/learn/tutorials/basics.md > > > > > On Wed, Jan 8, 2014 at 5:38 PM, Anil Madhavapeddy wrote: > >> On 8 Jan 2014, at 22:13, Yotam Barnoy wrote: >> >> 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 ocaml.org, 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. >> >> >> We do have a fledgling service for "domain-specific" conversations, in >> the form of lists.ocaml.org. 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: >> >> http://lists.ocaml.org/pipermail/wg-parallel/ >> >> (note that if anyone else would like an archived list on lists.ocaml.orgfor a project or community group, then please do drop a line to >> infrastructure@lists.ocaml.org to request it) >> >> Regarding other services on ocaml.org, 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: >> https://github.com/ocamllabs/compiler-hacking/wiki >> >> 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 >> wiki.ocaml.org 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. >> >> -anil >> >> _______________________________________________ >> Infrastructure mailing list >> Infrastructure@lists.ocaml.org >> http://lists.ocaml.org/listinfo/infrastructure >> >> > --047d7bea3cb62079b704ef80b425 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Wow, I wasn't aware of any of this= !

That tutorials page is really incredible... just so much mat= erial (and in different languages too!). And I'm really happy to see th= ose 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.

The tutorials page looks excellent, although I have a feeling peo= ple just aren't going to want to fork, edit, and then submit a push req= uest. The thing about wikis is that contributing takes minimal effort. Is i= t 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 h= ierarchy (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 se= nse to have a page other than 'tutorials' as the topic for discussi= ons such as compiler internals and parallelism.

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 comp= iler hacking, and one for ocaml internals. Wikis generally include everythi= ng on a wide topic. So to me it would make more sense to have an 'ocaml= ' wiki, with sub-categories for compiler hacking, internals, parallelis= m etc.

Any other opinions?

-Yotam
=


On Wed, Jan 8= , 2014 at 5:57 PM, Ashish Agarwal <agarwal1975@gmail.com> wrote:
Regarding the need for a wi= ki, why not create a new Parallel Programming page under tutorials [1]. A &= quot;tutorial" can be as simple as listing the libraries available and= a brief description about the high level goal of each.

Note ocaml.or= g is now almost entirely written in Markdown. A new page can be written= quite easily, see for example The Basics tutorial [2].





On Wed, Jan 8, 20= 14 at 5:38 PM, Anil Madhavapeddy <anil@recoil.org> wrote:
<= /div>
On 8 Jan 2014, at 22:13, Yota= m Barnoy <yot= ambarnoy@gmail.com> wrote:

Regarding a place to sha= re ideas, it seems like it would be very useful to have an official ocaml w= iki. Haskell has this and it's a huge help. In fact, I would say haskel= l development would be greatly hampered without it. There's so much inf= ormation that's relevant to more than one library ie. doesn't fit i= n any particular library's documentation. It wouldn't be too hard t= o set up a wikimedia instance on=A0ocaml.org, would it? Alternatively it should be pretty eas= y to set up something on wikia. This wiki would also be a great place to de= scribe the conceptual implementation of the compiler, which is again what h= askell has.

We do have a fledgling service for "= domain-specific" conversations, in the form of lists.ocaml.org. =A0In fact, we set up a = "wg-parallel" mailing list last year, but never announced it for = various reasons. =A0This seems like a good time to advertise its existence:=

http://lists.ocaml.org/pipermail/wg-parallel/

(note that if anyone else would like an archived list = on lists.ocaml.org= for a project or community group, then please do drop a line to infrastructure@li= sts.ocaml.org to request it)

Regarding other services on ocaml.org, we (the "infrastructure team")= are happy to set them up, but please bear in mind that they all come with = a maintenance burden. =A0Dealing with security issues, backups, software up= dates, outages all take up time, and I confess a preference for sipping mar= tinis and hacking on code instead of sysadmin work. Jeremy and Leo got tire= d of waiting for me to set up the wiki too, and started:

If you follow the links through there, there is a 'com= piler 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. =A0I think we could have a decent st= ab at a wiki.ocaml.org<= /a> by backing it against a GitHub repository, and not have to do any speci= al hosting for it at all (the OPAM web pages work in a similar fashion at t= he moment). =A0But for now though, I'd recommend focussing on the probl= em at hand (parallel programming) and getting some information down somewhe= re, and less on the lack of a central wiki.

-anil
=

_______________________________________________
Infrastructure mailing list
Infrast= ructure@lists.ocaml.org
http://lists.ocaml.org/listinfo/infrastructure



--047d7bea3cb62079b704ef80b425--