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 9AEAE81792 for ; Thu, 20 Jun 2013 16:03:44 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of thomas.gazagnaire@gmail.com) identity=pra; client-ip=74.125.82.52; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="thomas.gazagnaire@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of thomas.gazagnaire@gmail.com designates 74.125.82.52 as permitted sender) identity=mailfrom; client-ip=74.125.82.52; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="thomas.gazagnaire@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wg0-f52.google.com) identity=helo; client-ip=74.125.82.52; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="postmaster@mail-wg0-f52.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AooBAC0Lw1FKfVI0k2dsb2JhbABVBhaDJAHAbRYOAQEBAQcLCwkUBCSCRyMBJwQOAw0FfwEFASInh2gDDwybHYJ+j0yEcicNiEwBBQyOEIQtYQORL4c7hHiJPj+BXYJa X-IPAS-Result: AooBAC0Lw1FKfVI0k2dsb2JhbABVBhaDJAHAbRYOAQEBAQcLCwkUBCSCRyMBJwQOAw0FfwEFASInh2gDDwybHYJ+j0yEcicNiEwBBQyOEIQtYQORL4c7hHiJPj+BXYJa X-IronPort-AV: E=Sophos;i="4.87,905,1363129200"; d="scan'208";a="18429684" Received: from mail-wg0-f52.google.com ([74.125.82.52]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 20 Jun 2013 16:03:19 +0200 Received: by mail-wg0-f52.google.com with SMTP id b12so5566197wgh.19 for ; Thu, 20 Jun 2013 07:03:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject:date :message-id:to:mime-version:x-mailer; bh=KJs5mUDx81RM8OQT2csAgcTWInBUfP0Y1Z89iamVkrg=; b=VFKY2k181I95OsY+c9URBq+sfrAbNEck51V1OiotdodGoJbfesGABIVh92KeULb+vu NzSuqAgkYo/QC4wN+49PRZ5L+n0Z5p6uvbcBbD+Aa9/3LGkjupbDpi540LuA08aaVCiJ p/jEacTDQ/gKSxcTyP8xsUhif+DZIiNZn2jEPVrdScKpTLWhEH6BE95QhlF7PH2Q9aAA T825VYiyet2V+OTIyUWu5a/4jX7+MiAIU/SsCVV+Y1yDVTSMdtyZOG/c2DWY//bfUoMh KGaL7XFGefiqNFMBBB6H7DzuM8bLwdadZqS/2xoJuSbCh6Ej+wMOQ24A3gst7rM1vziN +X3w== X-Received: by 10.180.81.8 with SMTP id v8mr14441898wix.15.1371736999066; Thu, 20 Jun 2013 07:03:19 -0700 (PDT) Received: from [192.168.1.100] (perens.inria.fr. [128.93.60.79]) by mx.google.com with ESMTPSA id m3sm16415257wij.5.2013.06.20.07.03.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Jun 2013 07:03:18 -0700 (PDT) Sender: Thomas Gazagnaire From: Thomas Gazagnaire Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 20 Jun 2013 16:03:15 +0200 Message-Id: <1B65F6F9-9BCB-4815-BBED-5D6392B4BFDD@ocamlpro.com> To: Caml List Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) Subject: [Caml-list] Commercial Users of Functional Programming (CUFP) 2013 Last call for CUFP, the deadline is at the end of the month! *** Commercial Users of Functional Programming (CUFP) 2013 ICFP 2013; Boston, MA, Sep 22-24. Proposals due June 29. The annual CUFP workshop is a place where people can see how others are usi= ng functional programming to solve real world problems; where practitioners= meet and collaborate; where language designers and users can share ideas a= bout the future of their favorite language; and where one can learn practic= al techniques and approaches for putting functional programming to work. Giving a talk If you have experience using functional languages in a practical setting, w= e invite you to submit a proposal to give a talk at the workshop. We are lo= oking for both experience reports and in-depth technical talks. Experience reports are typically 25 minutes long (but negotiable), and aim = to inform participants about how functional programming plays out in real-w= orld applications, focusing especially on lessons learned and insights gain= ed. Experience reports don't need to be highly technical; reflections on th= e commercial, management, or software engineering aspects are, if anything,= more important. Technical talks are also 25 minutes long (also negotiable), and should focu= s on teaching the audience something about a particular technique or method= ology, from the point of view of someone who has seen it play out in practi= ce. These talks could cover anything from techniques for building functiona= l concurrent applications, to managing dynamic reconfigurations, to design = recipes for using types effectively in large-scale applications. While thes= e talks will often be based on a particular language, they should be access= ible to a broad range of programmers. If you are interested in offering a talk, or nominating someone to do so, p= lease fill in the form at https://www.surveymonkey.com/s/cufp There will be a short scribes report of the presentations and discussions b= ut not of the details of individual talks, as the meeting is intended to be= more a discussion forum than a technical interchange. You do not need to s= ubmit a paper, just a proposal for your talk! Note that we will need all pr= esenters to register for the CUFP workshop and travel to Boston at their ow= n expense. Program committee Marius Eriksen (Twitter, Inc.), co-chair Mike Sperber (Active Group), co-chair Mary Sheeran (Chalmers) Andres L=F6h (Well-Typed) Thomas Gazagnaire (OCamlPro) Steve Vinoski (Basho) Jorge Ortiz (Foursquare, Inc.) Blake Matheny (Tumblr, Inc.) Simon Marlow (Facebook, Inc.) More information For more information on CUFP, including videos of presentations from previo= us years, take a look at the CUFP website at http://cufp.org. Note that pre= senters, like other attendees, will need to register for the event. Present= ations will be video taped and presenters will be expected to sign an ACM c= opyright release form. Acceptance and rejection letters will be sent out by= July 16th. Please contact Marius Eriksen or Mike Sperber for questions or concerns: marius(at)twitter(dot)com sperber(at)deinprogramm(dot)de Guidance on giving a great CUFP talk Focus on the interesting bits: Think about what will distinguish your talk,= and what will engage the audience, and focus there. There are a number of = places to look for those interesting bits. * Setting: FP is pretty well established in some areas, including formal ve= rification, financial processing and server-side web-services. An unusual s= etting can be a source of interest. If you're deploying FP-based mobile UIs= or building servers on oil rigs, then the challenges of that scenario are = worth focusing on. Did FP help or hinder in adapting to the setting? * Technology: The CUFP audience is hungry to learn about how FP techniques = work in practice. What design patterns have you applied, and to what areas?= Did you use functional reactive programming for user interfaces, or DSLs f= or playing chess, or fault-tolerant actors for large scale geological data = processing? Teach us something about the techniques you used, and why we sh= ould consider using them ourselves. * Getting things done: How did you deal with large software development in = the absence of a myriad of pre-existing support that are often expected in = larger commercial environments (IDEs, coverage tools, debuggers, profilers)= and without larger, proven bodies of libraries? Did you hit any brick wall= s that required support from the community? * Don't just be a cheerleader: It's easy to write a rah-rah talk about how = well FP worked for you, but CUFP is more interesting when the talks also sp= end time on what doesn't work. Even when the results were all great, you sh= ould spend more time on the challenges along the way than on the parts that= went smoothly. Important dates Submissions due: June 29, 2013 Acceptance notifications: Mid-late July, 2013 Workshop: September 22-24, 2013 Links http://monkey.org/~marius/cufp.html http://cufp.org/conference/schedule