From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: Malcolm Matalka <mmatalka@gmail.com>, caml-list@inria.fr
Subject: AW: [Caml-list] OUD2013 part of CUFP?
Date: Wed, 03 Apr 2013 17:42:53 +0200 [thread overview]
Message-ID: <1365003773.10138.2@samsung> (raw)
In-Reply-To: <1850140A-303F-40BB-87AA-2DA5BAD33C3C@recoil.org> (from anil@recoil.org on Wed Apr 3 15:41:47 2013)
Sorry Anil,
I did meant to criticize people who put a lot of work into organizing
events. On the contrary, this is highly welcome.
My point is rather that you get a certain audience when an event is
organized as an addendum to a large academic conference. You don't get
the average programmer, but people with a strong academic background.
Or more direct: OUD is then just a side program for people who attend
ICFP anyway.
Am 03.04.2013 15:41:47 schrieb(en) Anil Madhavapeddy:
> 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).
This is not meant with "rituals". The ritual is to visit ICFP every
year. The ritual is to publish a paper every year and to bore the
audience, as it happens often enough. This is acceptable as being part
of science, but I just have some doubts whether this is the right
environment for a users' meeting, especially if you also want to
address users outside universities and research institutes.
> 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.
As an "industrial" user I am very interested into spreading out the
word to the masses. We have difficulties finding programmers, which is
no wonder if nobody (on the street) has ever heard of the language.
What we need are not further talks at scientific conferences, but at
events attended by more average people. That could e.g. be open source
conferences, hacker events, etc.
I put "industrial" in quotes because there isn't an industry yet. The
companies using OCaml are doing this for very individual reasons, and
there is not much cooperation (so far I can see that).
As you mention CUFP, this is a different type of thing. It's a
collection of success stories to encourage companies (and more
something for CTOs and chief architects).
> 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.
Don't get me wrong, but a "travelling" conference has also many cons.
E.g. in general it is harder to plan the attendance (reserving time,
planning the costs, etc.), especially if the location is not at a
traffic hub.
> 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.
Thanks for the suggestion, but I think I'm really doing enough for the
success of OCaml.
Gerd
> -anil
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
next prev parent reply other threads:[~2013-04-03 15:43 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
2013-04-03 15:42 ` Gerd Stolpmann [this message]
2013-04-03 16:39 ` AW: " 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=1365003773.10138.2@samsung \
--to=info@gerd-stolpmann.de \
--cc=anil@recoil.org \
--cc=caml-list@inria.fr \
--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