categories - Category Theory list
 help / color / mirror / Atom feed
From: Sam Staton <sam.staton@cs.ox.ac.uk>
To: "las-lics@lists.tu-berlin.de" <las-lics@lists.tu-berlin.de>,
	"categories@mta.ca" <categories@mta.ca>,
	"GAMES@lists.rwth-aachen.de" <GAMES@lists.rwth-aachen.de>,
	"theorem-provers@ai.mit.edu" <theorem-provers@ai.mit.edu>,
	"concurrency@listserver.tue.nl" <concurrency@listserver.tue.nl>,
	"finite-model-theory@lists.rwth-aachen.de"
	<finite-model-theory@lists.rwth-aachen.de>,
	"asl@vassar.edu" <asl@vassar.edu>,
	"agda@lists.chalmers.se" <agda@lists.chalmers.se>,
	"appsem@lists.tcs.ifi.lmu.de" <appsem@lists.tcs.ifi.lmu.de>,
	"lfcs-interest@inf.ed.ac.uk" <lfcs-interest@inf.ed.ac.uk>,
	"cade@itu.dk" <cade@itu.dk>,
	"prog-lang@diku.dk" <prog-lang@diku.dk>,
	"linear@cs.stanford.edu" <linear@cs.stanford.edu>,
	"DMANET@zpr.uni-koeln.de" <DMANET@zpr.uni-koeln.de>,
	"homotopytypetheory@googlegroups.com"
	<homotopytypetheory@googlegroups.com>,
	"rewriting@ens-lyon.fr" <rewriting@ens-lyon.fr>, "coq-
Subject: [LICS] Call for Workshop Proposals affiliated to LICS at FLOC'22
Date: Fri, 17 Sep 2021 11:09:50 +0000	[thread overview]
Message-ID: <49859862-02F1-4FB8-869C-772E4C6B006B@cs.ox.ac.uk> (raw)

Warning: deadline on September 27, 2021

Call for Workshops - FLoC 2022 — The 2022 Federated Logic Conference
July 31 - August 12, 2022
Haifa, Israel
http://www.floc2022.org/

CALL FOR WORKSHOPS

The Eighth Federated Logic Conference (FLoC 2022) will host ten
conferences including

LICS (37th Annual ACM/IEEE Symposium on Logic in Computer Science) https://lics.siglog.org/
Workshop chair: Frederic Blanqui Frederic.Blanqui@inria.fr

SUBMISSION OF WORKSHOP PROPOSALS

Researchers and practitioners are invited to submit proposals for workshops on
topics in the field of computer science, related to logic in the broad sense.
Each workshop proposal must indicate one affiliated conference of FLoC 2022.

It is strongly suggested that prospective workshop organizers contact the
relevant conference workshop chair before submitting a proposal.

Each proposal should consist of the following two parts.

1) A short scientific justification of the proposed topic, its significance,
and the particular benefits of the workshop to the community, as well as a
list of previous or related workshops (if relevant).

2) An organisational part including:

- contact information for the workshop organizers;
- proposed affiliated conference;
- estimate of the number of workshop participants (please note that small workshops, i.e., of less than ~13 participants, will likely be cancelled or merged);
- proposed format and agenda (e.g. paper presentations, tutorials, demo sessions, etc.);
- potential invited speakers (note that expenses of workshop invited speakers are not covered by FLoC);
- procedures for selecting papers and participants;
- plans for dissemination, if any (e.g. a journal special issue);
- duration (which may vary from one day to two days);
- preferred period (pre or post FLoC);
- virtual/hybrid backup plans (including platform preference).
The FLoC Organizing Committee will determine the final list of accepted
workshops based on the recommendations from the Workshop Chairs of the hosting
conferences and availability of space and facilities.

Proposals should be submitted through EasyChair:
https://easychair.org/conferences/?conf=floc2022workshops

Please see the Workshop Guidelines page: https://floc2022.org/workshops/ for further details and FAQ.

IMPORTANT DATES

Submission of workshop proposals deadline: September 27, 2021 (note extended deadline)
Notification: November 1, 2021
Pre-FLoC workshops: Sunday & Monday, July 31–August 1, 2022 (note corrected dates)
Post-FLoC workshops: Thursday & Friday, August 11-12, 2022

CONTACT INFORMATION

Questions regarding proposals should be sent to the workshop chairs of the
proposed affiliated conference. General questions should be sent to:
shaull@technion.ac.il
GuillermoAlberto.Perez@uantwerpen.be

FLoC 2022 WORKSHOP CHAIRS
Shaull Almagor
Guillermo A. Perez

You are subscribed to the lics mailing list because you have signed up for it in the past.

Submissions to the newsletter:
Send an email to las-lics@lists.tu-berlin.de.

Unsubscribe:
To unsubscribe, please send an email to las-lics-request@lists.tu-berlin.de with
the keyword 'unsubscribe' in the message body (without ').

Subscribe:
To subscribe,  please send an email to las-lics-request@lists.tu-berlin.de with
the keyword 'subscribe' in the message body (without ').

                 reply	other threads:[~2021-09-17 11:09 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=49859862-02F1-4FB8-869C-772E4C6B006B@cs.ox.ac.uk \
    --to=sam.staton@cs.ox.ac.uk \
    --cc=DMANET@zpr.uni-koeln.de \
    --cc=GAMES@lists.rwth-aachen.de \
    --cc=agda@lists.chalmers.se \
    --cc=appsem@lists.tcs.ifi.lmu.de \
    --cc=asl@vassar.edu \
    --cc=cade@itu.dk \
    --cc=categories@mta.ca \
    --cc=concurrency@listserver.tue.nl \
    --cc=finite-model-theory@lists.rwth-aachen.de \
    --cc=homotopytypetheory@googlegroups.com \
    --cc=las-lics@lists.tu-berlin.de \
    --cc=lfcs-interest@inf.ed.ac.uk \
    --cc=linear@cs.stanford.edu \
    --cc=prog-lang@diku.dk \
    --cc=rewriting@ens-lyon.fr \
    --cc=theorem-provers@ai.mit.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).