caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: Malcolm Matalka <mmatalka@gmail.com>, caml-list@inria.fr
Subject: Re: [Caml-list] OUD2013 part of CUFP?
Date: Wed, 3 Apr 2013 06:41:47 -0700	[thread overview]
Message-ID: <1850140A-303F-40BB-87AA-2DA5BAD33C3C@recoil.org> (raw)
In-Reply-To: <1364994641.10138.1@samsung>

On 3 Apr 2013, at 06:10, Gerd Stolpmann <info@gerd-stolpmann.de> wrote:

> Am 03.04.2013 13:22:07 schrieb(en) Anil Madhavapeddy:
>> On 3 Apr 2013, at 01:24, Malcolm Matalka <mmatalka@gmail.com> wrote:
>> > Last year, OUD was part of CUFP and it worked great.  I'm wondering if
>> > it's the same this year?
>> >
>> Yes, it is part of ICFP 2013 (in Boston this year), and is being chaired by Michel Mauny this year.  The Call for Proposals hasn't gone yet out.
> 
> Too sad. OCaml not leaving the Cathedral. I liked the idea of the first couple of OUD events of keeping some distance to academic rituals.

Nothing stops you from organising your own group, inviting people, reserving a building, sorting out registration, invoicing sponsors, organising local facilities and lunch, recording the talks, and uploading them online.  ICFP's "rituals" take care of all of that for us (Sylvain did a big job before).

Your cathedral analogy also doesn't make any sense to me.  I like attending a few days in one go where I can interact with OCaml, ML, Haskell, Scheme, Erlang, and F# users at the same time, see talks from industrial users at CUFP, and enjoy hearing the excitement and wails of the emerging new languages being developed by the community.

The rotating locations also enables worldwide users to attend, instead of just European ones.  The ICFP/CUFP at Japan a few years ago represented a big jump in attendance from the Asian community.  ICFP moves across Europe, Asia and the USA, which is difficult to arrange with a single user group.

Having said that, having more local meetups is a very positive thing. Ashish and Christophe have been tracking them here: http://ocaml.org/meetings.html
Do get involved and set up your own.

-anil


  reply	other threads:[~2013-04-03 13:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  8:24 Malcolm Matalka
2013-04-03 11:22 ` Anil Madhavapeddy
2013-04-03 13:10   ` AW: " Gerd Stolpmann
2013-04-03 13:41     ` Anil Madhavapeddy [this message]
2013-04-03 15:42       ` Gerd Stolpmann
2013-04-03 16:39         ` Malcolm Matalka
2013-04-03 16:54           ` AW: " Gerd Stolpmann
2013-04-03 17:32             ` Amir Chaudhry
2013-04-03 18:02               ` Martin Jambon
2013-04-03 18:33                 ` Anil Madhavapeddy
2013-04-03 19:16                   ` Malcolm Matalka
2013-04-03 20:01                   ` AW: " Gerd Stolpmann
2013-04-03 21:21                     ` Gabriel Scherer
2013-04-03 21:45                       ` AW: " Gerd Stolpmann
2013-04-04  7:57                         ` Esther Baruk
2013-04-03 17:08           ` Anil Madhavapeddy
2013-04-03 14:18     ` 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=1850140A-303F-40BB-87AA-2DA5BAD33C3C@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    --cc=mmatalka@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).