caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Simon Peyton-Jones <simonpj@microsoft.com>
To: "haskell@haskell.org" <haskell@haskell.org>,
	"caml-list@inria.fr" <caml-list@inria.fr>,
	"erlang-questions@erlang.org" <erlang-questions@erlang.org>,
	"plt-scheme@fast.flux.utah.edu" <plt-scheme@fast.flux.utah.edu>,
	"MLton-user@mlton.org" <MLton-user@mlton.org>,
	"EAPLS@JISCMAIL.AC.UK" <EAPLS@JISCMAIL.AC.UK>
Subject: Commercial Users of Functional Programming: call for speaker nominations
Date: Tue, 13 Mar 2007 10:39:41 +0000	[thread overview]
Message-ID: <DCA83D5F3861C941808187D4D38787500FFBEE8377@EA-EXMSG-C312.europe.corp.microsoft.com> (raw)

Commercial Users of Functional Programming (CUFP) 2007
                Oct 4 2007, Freiburg, Germany

=== Call for speaker nominations and talk proposals ===

Functional languages have been under academic development for
over 25 years, and remain fertile ground for programming language
research. Recently, however, developers in industrial,
government, and open source projects have begun to use functional
languages very successfully in practical applications. In these
settings, functional programming has often provided dramatic
leverage, including whole new ways of thinking about the original
problem.

The goal of the CUFP workshop is to act as a voice for these
users of functional languages. The workshop supports the
increasing viability of functional programming in the commercial,
governmental, and open-source space by providing a forum for FP
professionals to share their experiences and ideas, whether those
ideas are related to business, management, or engineering. The
workshop is also designed to enable the formation and
reinforcement of relationships that further the commercial use of
functional languages.


                 Speaking at CUFP

If you use functional programming as a means, rather than as an
end, this message is an invitation for you to offer to give a
talk at the workshop. Alternatively, you may know someone else
who would give a good talk: please nominate them.

Talks are typically about 30-45 minutes long, but can be shorter.
They aim to inform participants about how functional programming
played out in real-world applications, focusing especially on the
re-usable lessons learned, or insights gained.

Your talk does not need to be highly technical; for this
audience, reflections on the commercial, management, or software
engineering aspects are, if anything, more important. You do not
need to submit a paper!

If you are interested in offering a talk, or nominating someone
to do so, send an e-mail to kfisher at research.att.com or
simonpj at microsoft.com by June 1, 2007 with a short description
of what you'd like to talk about or what you think your nominee
should give a talk about. Such descriptions should be roughly a
page in length.




                 reply	other threads:[~2007-03-13 10:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DCA83D5F3861C941808187D4D38787500FFBEE8377@EA-EXMSG-C312.europe.corp.microsoft.com \
    --to=simonpj@microsoft.com \
    --cc=EAPLS@JISCMAIL.AC.UK \
    --cc=MLton-user@mlton.org \
    --cc=caml-list@inria.fr \
    --cc=erlang-questions@erlang.org \
    --cc=haskell@haskell.org \
    --cc=plt-scheme@fast.flux.utah.edu \
    /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).