The Erlang Workshop aims to bring together the open source, academic, and industrial communities of Erlang, other BEAM-related languages, actor model programming, distribution, and concurrency to discuss techniques, technologies, languages and other relevant topics. The Erlang model of concurrent programming has been widely emulated, for example by Akka in Scala. Moreover, several newer programming languages, such as Elixir, have been designed atop Erlang’s VM. The workshop is welcoming contributions related to any and all systems like those mentioned above.

The workshop aims to enable participants to learn about recent developments on techniques and tools, novel applications, draw lessons from users’ experiences and identify research problems and common areas relevant to the practice of Erlang and other Erlang-like languages, functional programming, distribution, concurrency, etc.

Topics

This year we invite three types of submissions:

• Technical papers describing language extensions, critical discussions of the status quo, formal semantics of language constructs, program analysis and transformation, virtual machine extensions and compilation techniques, implementations and interfaces of Erlang in/with other languages, and new tools (profilers, tracers, debuggers, testing frameworks, etc.). Submission related to Erlang, Elixir, Lisp Flavored Erlang, and topics in functional, concurrent, and distributed programming are welcome and encouraged. The maximum length for technical papers is restricted to 12 pages, but short papers (max. 6 pages) are also welcome.
• Practice and application papers describing uses of Erlang and related languages in the “real-world”, libraries for specific tasks, experiences from using Erlang in specific application domains, reusable programming idioms and elegant new ways of using Erlang to approach or solve particular problems, etc. The maximum length for the practice and application papers is restricted to 12 pages, but short papers (max. 6 pages) are also welcome.
• Lightning talks describing topics related to the workshop goals that allow participants to present and demonstrate projects and preliminary work in academia and industry. Presentations in this category will be given at most an hour of shared simultaneous presentation time, will not be part of the peer review process and will not be part of the formal proceedings. Notification of acceptance will be continuous.

Important dates

Deadlines are anywhere on Earth.

Workshop Co-Chairs

• Burcu Kulahcioglu Ozkan, Delft University of Technology, Netherlands
• Kiko Fernandez-Reyes, Ericsson, Sweden

Program Committee

(Note: the Workshop Co-Chairs are also committee members)

• Dino Distefano, Facebook London
• Thomas Arts, Quivq, Sweden
• Laura Bocchi, Kent University, UK
• Emanuele D’Osulado, MPI-SWS, Germany
• Juliana Franco, DeepMind, UK
• Elisa Gonzalez Boix, Vrije Universiteit Brussel, Belgium
• Torben Hoffmann, Erlang Solutions, Denmark
• Marjan Sirjani, Reykjavik University and Malardalen University, Iceland and Sweden
• Silvia Tapia Tarifa, University of Oslo, Norway
• Phil Trinder, University of Glasgow, Scotland
• Peter Van Roy, Université catholique de Louvain, Belgium
• Mirko Viroli, University of Bologna, Italy
• Tobias Wrigstad, Uppsala University, Sweden

Instructions to authors

Submission

Submissions must adhere to SIGPLAN’s republication policy (SIGPLAN Republication Policy), and authors should be aware of ACM’s policies on plagiarism
(ACM Policy on Plagiarism, Misrepresentation, and Falsification). Program Committee members are allowed to submit papers, but their papers will be held to a higher standard.

Papers must be submitted online via HotCRP at:

https://erlang2023.hotcrp.com

Lightning talks can be submitted to the workshop’s co-chairs via e-mail.

Formatting

Submitted papers should be in portable document format (PDF), formatted using the ACM SIGPLAN style guidelines. Authors should use the acmart format, with the sigplan sub-format for ACM proceedings. For details, see:

It is recommended to use the review option when submitting a paper; this option enables line numbers for easy reference in reviews.

Supplementary material

Authors have the option to attach supplementary material to a submission, on the understanding that reviewers may choose not to look at it. This supplementary material should not be submitted as part of the main document; instead, it should be uploaded as a separate PDF document or tarball.

Supplementary material should be uploaded at submission time, not by providing a URL in the paper that points to an external repository.

Artifacts

Authors of accepted papers are encouraged to make auxiliary material (artifacts like source code, test data, etc.) available with their paper. They can opt to have these artifacts published alongside their paper in the ACM Digital Library (copyright of artifacts remains with the authors).

If an accepted paper’s artifacts are made permanently available for retrieval in a publicly accessible archival repository like the ACM Digital Library, that paper qualifies for an Artifacts Available badge (Artifact Review and Badging – Version 1.0 (not current)). Applications for such a badge can be made after paper acceptance and will be reviewed by the PC co-chairs.

Proceedings

As with previous years, the accepted workshop papers will be published by the ACM and will appear in the ACM Digital Library.

AUTHORS TAKE NOTE:
The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work.

For more information, please see ACM Copyright Policy (Publication Rights & Licensing Policy) and ACM Author Rights (ACM Authors Portal Homepage).

Accepted lightning talks will be posted on the workshop’s website but not formally published in the proceedings.