caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yann Hamdaoui <yann.hamdaoui@gmail.com>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] CONFLANG21: 1st Workshop on Configuration Languages (CfP)
Date: Thu, 22 Apr 2021 15:31:12 +0200	[thread overview]
Message-ID: <cf7f4d9f-495e-e676-7b90-580184a4b7c2@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2735 bytes --]

Dear OCamlers,

While fairly specialized, the 1st workshop on configuration languages
may be of interest for some of you, in particular the programming
language design aspect of it. Also, some tools of the OCaml ecosystem
(I'm thinking about Dune e.g.) are more directly related to the themes.
Cheers,
Yann

=======================================================================

Call for presentations - Configuration Languages Workshop 2021
(CONFLANG21)
=======================================================================


EVENT DETAILS


Event: CONFLANG21, colocated at SPLASH 2021

Date: Sunday October 17th to Friday 22th, 2021

Submission deadline: Friday 6th August 2021

Location: Chicago, Illinois (subject to change to being held online)

Website: https://2021.splashcon.org/home/conflang-2021


While in-person presentations make sharing and interacting easier,
please note that remote presentations are also considered due to the
current health context.

OVERVIEW


CONFLANG is a new workshop on the design, the usage and the tooling of
configuration programming languages. CONFLANG aims at uniting language
designers, industry practitioners and passionate hobbyists to share
knowledge in any form. Topics of interest include, but are not limited to:


- Infrastructure and configuration code maintenance and evolution

- Specification learning and mining for configurations

- Infrastructure and Configuration testing and verification

- Infrastructure as Code and configuration repair

- New languages for configuration

- The application of language security and type theory to program
configuration


CALL FOR PRESENTATIONS

The committee welcomes proposals for presentations:

- Traditional talks on any theoretical or practical aspect of the usage,
the tooling and the design of configuration languages

- Experience and case study talks on the real world usage and deployment
of configuration languages

- Explorative talks and/or demos on experimenting with configuration
languages and related tools


SUBMISSION GUIDELINES

Please submit an abstract (up to 600 words, excluding title, author
names, and bibliography) of your proposed talk using the submission link
provided below.

- **Format**: 600 words maximum abstract (estimated between 1 and 1,5
pages) as a PDF, excluding title, author names, and bibliography. Any
additional material will be considered at the discretion of the PC.

- **URL** : https://conflang21.hotcrp.com/


PROGRAM CHAIRS

- Eelco Dolstra: Tweag I/O

- Yann Hamdaoui: Tweag I/O

- Jürgen Cito: TU Wien and Facebook

- Mark Santolucito: Columbia University

- Marcel van Lohuizen: Google

- Gabriel Gonzalez: Arista Networks

- Nicolas Jeannerod: IRIF, Paris Diderot University


[-- Attachment #2: Type: text/html, Size: 15733 bytes --]

                 reply	other threads:[~2021-04-22 13:33 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=cf7f4d9f-495e-e676-7b90-580184a4b7c2@gmail.com \
    --to=yann.hamdaoui@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).