categories - Category Theory list
 help / color / mirror / Atom feed
From: ICFP Publicity <icfp.publicity@googlemail.com>
To: agda <agda@lists.chalmers.se>, agents <agents@cs.umbc.edu>,
	 appsem <appsem@lists.tcs.ifi.lmu.de>,
	bigloo <bigloo@sophia.inria.fr>,
	 bx <bx@liste.es.e-technik.tu-darmstadt.de>,
	caml-list <caml-list@inria.fr>,  categories <categories@mta.ca>,
	chicken-scheme <chicken-users@nongnu.org>,
	 clean <clean-announce@science.ru.nl>,
	concurrency <concurrency@cwi.nl>,  coq-club <coq-club@inria.fr>,
	ecoop <ecoop-info@ecoop.org>,
	 erlang-questions <erlang-questions@erlang.org>,
	 "F# Discussions" <fsharp-opensource@googlegroups.com>,
	fp-nl <fp-nl@cs.uu.nl>,  fun <fun@cs.nott.ac.uk>,
	 "functional-programming@st-and"
	<functional-programming@cs.st-and.ac.uk>,
	 gambit-list <gambit-list@iro.umontreal.ca>,
	GPCE-related <GPCE-related@cs.rice.edu>,
	 haskell <haskell@haskell.org>,
	haskell-cafe <haskell-cafe@haskell.org>,
	 infodir_sigplan <infodir_sigplan@acm.org>,
	isabelle-users <isabelle-users@c
Subject: ICFP 2023: Call for Workshop and Co-Located Event
Date: Thu, 1 Dec 2022 16:31:44 +0800	[thread overview]
Message-ID: <CAAmpXihTm4N8fqhVcbsB3ZrvSyq8d+RU4np5X-ZKnq5pdsrDBA@mail.gmail.com> (raw)

        CALL FOR WORKSHOP AND CO-LOCATED EVENT PROPOSALS
                            ICFP 2023
 28th ACM SIGPLAN International Conference on Functional Programming


                      September 4 - 9, 2023
                        Seattle, WA, USA
                    https://icfp23.sigplan.org/

The 28th ACM SIGPLAN International Conference on Functional
Programming will be held in Seattle, WA, USA on September 4 - 9,
2023, with the option of virtual participation. ICFP provides a forum
for researchers and developers to hear about the latest work on the
design, implementations, principles, and uses of functional
programming.

Proposals are invited for workshops (and other co-located events,
such as symposiums) to be affiliated with ICFP 2023 and sponsored by
SIGPLAN. These events should be less formal and more focused than
ICFP itself, include sessions that enable interaction among the
attendees, and foster the exchange of new ideas. The preference is
for one-day events, but other schedules can also be considered.

The workshops are scheduled to occur on September 4th (the day before
ICFP) and September 8-9th (the two days after ICFP).

----------------------------------------------------------------------

Submission details
 Deadline for submission:     December 22, 2022
 Notification of acceptance:  January  13, 2023

Prospective organizers of workshops or other co-located events are
invited to submit a completed workshop proposal form in plain text
format to the ICFP 2023 workshop co-chairs (Arthur Azevedo de Amorim
and Yannick Forster) via email to

   icfp-workshops-2023@googlegroups.com

by December 22, 2022. (For proposals of co-located events other than
workshops, please fill in the workshop proposal form and just leave
blank any sections that do not apply.) Please note that this is a
firm deadline.

Organizers will be notified whether their event proposal is accepted
by January 13, 2023, and if successful, depending on the event, they
will be asked to produce a final report after the event has taken
place that is suitable for publication in SIGPLAN Notices.

The proposal form is available at:

http://www.icfpconference.org/icfp2023-files/icfp23-workshops-form.txt

Further information about SIGPLAN sponsorship is available at:

http://www.sigplan.org/Resources/Proposals/Sponsored/

----------------------------------------------------------------------

Selection committee

The proposals will be evaluated by a committee comprising the
following members of the ICFP 2023 organizing committee, together
with the members of the SIGPLAN executive committee.

 Workshop Co-Chair: Arthur Azevedo de Amorim       (Boston University)
 Workshop Co-Chair: Yannick Forster                     (Inria Nantes)
 General Chair:     Nikhil Swamy                  (Microsoft Research)
 Program Chair:     Sam Lindley              (University of Edinburgh)


----------------------------------------------------------------------

Further information

Any queries should be addressed to the workshop co-chairs (Arthur
Azevedo de Amorim and Yannick Forster), via email to
icfp-workshops-2023@googlegroups.com.


                 reply	other threads:[~2022-12-01  8:31 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=CAAmpXihTm4N8fqhVcbsB3ZrvSyq8d+RU4np5X-ZKnq5pdsrDBA@mail.gmail.com \
    --to=icfp.publicity@googlemail.com \
    --cc=GPCE-related@cs.rice.edu \
    --cc=agda@lists.chalmers.se \
    --cc=agents@cs.umbc.edu \
    --cc=appsem@lists.tcs.ifi.lmu.de \
    --cc=bigloo@sophia.inria.fr \
    --cc=bx@liste.es.e-technik.tu-darmstadt.de \
    --cc=caml-list@inria.fr \
    --cc=categories@mta.ca \
    --cc=chicken-users@nongnu.org \
    --cc=clean-announce@science.ru.nl \
    --cc=concurrency@cwi.nl \
    --cc=coq-club@inria.fr \
    --cc=ecoop-info@ecoop.org \
    --cc=erlang-questions@erlang.org \
    --cc=fp-nl@cs.uu.nl \
    --cc=fsharp-opensource@googlegroups.com \
    --cc=fun@cs.nott.ac.uk \
    --cc=functional-programming@cs.st-and.ac.uk \
    --cc=gambit-list@iro.umontreal.ca \
    --cc=haskell-cafe@haskell.org \
    --cc=haskell@haskell.org \
    --cc=infodir_sigplan@acm.org \
    --cc=isabelle-users@c \
    /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).