From: geoff@cs.miami.edu
To: <caml-list@inria.fr>
Subject: [Caml-list] LPAR-23 - Call for Workshops and Tutorials
Date: Tue, 18 Feb 2020 09:49:32 -0500 (EST) [thread overview]
Message-ID: <20200218144932.9CD9E17003B2@cs.miami.edu> (raw)
CALL FOR WORKSHOPS AND TUTORIALS
LPAR-23: 23rd International Conference on Logic for Programming,
Artificial Intelligence and Reasoning
22-27 May, 2020, Alicante, Spain
https://easychair.org/smart-program/LPAR23/
Workshop and tutorial proposals for LPAR-23 are solicited.
These events will take place on May 22 2020, before the main conference.
To apply for a workshop or a tutorial, please contact the workshop chair via
martin.suda@cvut.cz and specify:
* A title of the event.
* Names and affiliations of organisers.
* Proposed duration (half day or full).
* Brief description of the goals and the scope/the topics to be covered.
Why is the tutorial/workshop relevant for LPAR?
* Whether or not the tutorial/workshop has been organised previously.
* For previously organized workshops, information on previous meetings should
be given (e.g., links to the program, number of submissions, number of
participants).
* For workshops: What are the plans for publication?
The deadline for submitting workshop/tutorial proposals: March 1, 2020.
reply other threads:[~2020-02-18 14:55 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=20200218144932.9CD9E17003B2@cs.miami.edu \
--to=geoff@cs.miami.edu \
--cc=caml-list@inria.fr \
/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