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 mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id BEA0D7EE99 for ; Wed, 8 Jan 2014 23:39:04 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of anil@recoil.org) identity=pra; client-ip=89.16.177.154; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="anil@recoil.org"; x-sender="anil@recoil.org"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of anil@recoil.org) identity=mailfrom; client-ip=89.16.177.154; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="anil@recoil.org"; x-sender="anil@recoil.org"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@dark.recoil.org) identity=helo; client-ip=89.16.177.154; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="anil@recoil.org"; x-sender="postmaster@dark.recoil.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuMCACDTzVJZELGanGdsb2JhbABZgkd8hjWgDIp/iFWBKg4BAQEBAQgUCTyCJQEBAQMBAQJrCwULC0YhBy8GExSHXAMJDAm/Hg2FEheMcoIPBAeDJIETBJVHZIFsgTCLKgKGeYFtPA X-IPAS-Result: AuMCACDTzVJZELGanGdsb2JhbABZgkd8hjWgDIp/iFWBKg4BAQEBAQgUCTyCJQEBAQMBAQJrCwULC0YhBy8GExSHXAMJDAm/Hg2FEheMcoIPBAeDJIETBJVHZIFsgTCLKgKGeYFtPA X-IronPort-AV: E=Sophos;i="4.95,626,1384297200"; d="scan'208,217";a="44041444" Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) ([89.16.177.154]) by mail3-smtp-sop.national.inria.fr with SMTP; 08 Jan 2014 23:39:03 +0100 Received: (qmail 28661 invoked by uid 634); 8 Jan 2014 22:39:01 -0000 X-Spam-Level: * X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 08 Jan 2014 22:39:01 +0000 Content-Type: multipart/alternative; boundary="Apple-Mail=_9FADB2E4-05CE-4DAB-8416-DB568DD19568" Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 8 Jan 2014 22:38:58 +0000 Cc: Roberto Di Cosmo , Ocaml Mailing List , infrastructure Message-Id: <17C64E48-1AC4-4C4E-94E1-4170A39111C7@recoil.org> References: <20140108202952.GA3669@voyager> To: Yotam Barnoy X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: Re: [Caml-list] Concurrent/parallel programming --Apple-Mail=_9FADB2E4-05CE-4DAB-8416-DB568DD19568 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 8 Jan 2014, at 22:13, Yotam Barnoy wrote: > Regarding a place to share ideas, it seems like it would be very useful t= o have an official ocaml wiki. Haskell has this and it's a huge help. In fa= ct, I would say haskell development would be greatly hampered without it. T= here's so much information that's relevant to more than one library ie. doe= sn'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 sh= ould 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, whi= ch 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 l= ast year, but never announced it for various reasons. This seems like a go= od 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 fo= r a project or community group, then please do drop a line to infrastructur= e@lists.ocaml.org to request it) Regarding other services on ocaml.org, we (the "infrastructure team") are h= appy to set them up, but please bear in mind that they all come with a main= tenance burden. Dealing with security issues, backups, software updates, o= utages all take up time, and I confess a preference for sipping martinis an= d hacking on code instead of sysadmin work. Jeremy and Leo got tired of wai= ting 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 lib= raries there. I think we could have a decent stab at a wiki.ocaml.org by b= acking it against a GitHub repository, and not have to do any special hosti= ng for it at all (the OPAM web pages work in a similar fashion at the momen= t). But for now though, I'd recommend focussing on the problem at hand (pa= rallel programming) and getting some information down somewhere, and less o= n the lack of a central wiki. -anil= --Apple-Mail=_9FADB2E4-05CE-4DAB-8416-DB568DD19568 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
On 8 Jan= 2014, at 22:13, Yotam Barnoy <= yotambarnoy@gmail.com> wrote:

Regarding a place to share ideas, i= t seems like it would be very useful to have an official ocaml wiki. Haskel= l has this and it's a huge help. In fact, I would say haskell development w= ould be greatly hampered without it. There's so much information that's rel= evant 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? Alternat= ively it should be pretty easy to set up something on wikia. This wiki woul= d also be a great place to describe the conceptual implementation of the co= mpiler, which is again what haskell has.

We do have a fledgl= ing 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 reaso= ns.  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.org for a project or community group, then please do= drop a line to infrastru= cture@lists.ocaml.org to request it)

Regarding other services on ocaml= .org, we (the "infrastructure team") are happy to set them up, but plea= se 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 instea= d of sysadmin work. Jeremy and Leo got tired of waiting for me to set up th= e wiki too, and started:
https://github.com/ocamllabs/compiler-hac= king/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 ad= d 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 fo= cussing on the problem at hand (parallel programming) and getting some info= rmation down somewhere, and less on the lack of a central wiki.

-anil
= --Apple-Mail=_9FADB2E4-05CE-4DAB-8416-DB568DD19568--