|
| 1 | +--- |
| 2 | +title: "Call for Papers, Erlang Workshop 2026" |
| 3 | +timestamp: "4/1/2026 5:34:20" |
| 4 | +deadline: "5/14/2026" |
| 5 | +--- |
| 6 | +# Erlang Workshop 2026 - Call for Papers |
| 7 | + |
| 8 | +25th Edition of the Erlang Workshop |
| 9 | +Friday 28 August 2026, Indianapolis, Indiana, USA |
| 10 | +A satellite workshop of ICFP 2026 |
| 11 | + |
| 12 | +https://icfp26.sigplan.org/home/erlang-2026 |
| 13 | + |
| 14 | + ** Deadline: 14 May 2026 ** |
| 15 | + |
| 16 | + |
| 17 | +## Overview |
| 18 | + |
| 19 | +The Erlang Workshop aims to bring together the open source, academic, |
| 20 | +and industrial communities of BEAM languages (Erlang, Elixir, Gleam, LFE, etc.), |
| 21 | +along with other actor-model systems such as Akka and Clojure, |
| 22 | +including the concurrent, distributed systems, and fault-tolerant communities. |
| 23 | + |
| 24 | +The workshop will give participants the opportunity to learn about recent |
| 25 | +developments in techniques and tools, explore novel applications, |
| 26 | +draw lessons from users' experiences, and identify research problems |
| 27 | +and common ground across BEAM languages, related actor-model systems, |
| 28 | +functional programming, distribution, and concurrency. |
| 29 | + |
| 30 | +This year the workshop will be hybrid: we encourage authors and |
| 31 | +participants to attend in person, but remote talks and participation |
| 32 | +will be fully supported. We also plan to provide financial support to |
| 33 | +individuals who might not otherwise be able to attend. |
| 34 | + |
| 35 | +## Topics |
| 36 | + |
| 37 | +This year we invite four types of submissions: |
| 38 | + |
| 39 | +* Technical papers describing language extensions, critical |
| 40 | + discussions of the status quo, formal semantics of language |
| 41 | + constructs, program analysis and transformation, virtual machine |
| 42 | + extensions and compilation techniques, implementations and |
| 43 | + interfaces of BEAM languages in/with other languages, and new tools |
| 44 | + (profilers, tracers, debuggers, testing frameworks, etc.). |
| 45 | + Submissions related to BEAM languages (Erlang, Elixir, Gleam, LFE, etc.) and |
| 46 | + topics in functional, concurrent, and distributed programming |
| 47 | + are welcome and encouraged. |
| 48 | + |
| 49 | +* Practice and application papers describing uses of BEAM languages and |
| 50 | + related actor-model systems in real-world settings, libraries for specific tasks, |
| 51 | + experiences from using BEAM languages in specific application domains, |
| 52 | + reusable programming idioms and elegant new ways of using BEAM languages to |
| 53 | + approach or solve particular problems, etc. |
| 54 | + |
| 55 | +* Educational papers describing traditional or novel approaches to |
| 56 | + teaching and learning BEAM languages and BEAM-related technologies |
| 57 | + (curriculum design, courseware, workshops, tutorials, tooling for |
| 58 | + pedagogy, online materials, assessments, etc.). |
| 59 | + |
| 60 | +For all paper categories, both full papers (up to 12 pages) and short |
| 61 | +papers (up to 6 pages) are welcome. |
| 62 | + |
| 63 | +* Lightning talks describing topics related to the workshop goals that |
| 64 | + allow participants to present and demonstrate projects and |
| 65 | + preliminary work in academia and industry. Presentations in this |
| 66 | + category will be given at most an hour of shared simultaneous |
| 67 | + presentation time, will not be part of the peer review process and |
| 68 | + will not be part of the formal proceedings. Notification of |
| 69 | + acceptance will be continuous. |
| 70 | + |
| 71 | +## Important dates |
| 72 | + |
| 73 | +Submission deadline: 14 May 2026 |
| 74 | +Notification: 17 June 2026 |
| 75 | +Camera ready: 07 July 2026 |
| 76 | +Lightning talk registration: 07 July 2026 |
| 77 | +Workshop: 28 Aug 2026 |
| 78 | + |
| 79 | +Deadlines are anywhere on Earth. |
| 80 | + |
| 81 | + |
| 82 | +## Workshop Co-Chairs |
| 83 | + |
| 84 | +* Lee Barney, Brigham Young University-Idaho, USA |
| 85 | +* Akos Hajdu, Meta, UK |
| 86 | +* Laura Voinea, University of Glasgow, UK |
| 87 | + |
| 88 | + |
| 89 | +## Program Committee |
| 90 | + |
| 91 | +(Note: the Workshop Co-Chairs are also committee members) |
| 92 | + |
| 93 | +* Viktória Fördős (Cisco Systems, Sweden) |
| 94 | +* Jonatan Männchen (Erlang Ecosystem Foundation, Switzerland) |
| 95 | +* Radu Grigore (Meta, UK) |
| 96 | + |
| 97 | + |
| 98 | + |
| 99 | +## Instructions to authors |
| 100 | + |
| 101 | +### Submission |
| 102 | + |
| 103 | +Submissions must adhere to SIGPLAN’s republication policy |
| 104 | +(http://sigplan.org/Resources/Policies/Republication/), and authors |
| 105 | +should be aware of ACM’s policies on plagiarism |
| 106 | +(https://www.acm.org/publications/policies/plagiarism). Program |
| 107 | +Committee members are allowed to submit papers, but their papers will |
| 108 | +be held to a higher standard. |
| 109 | + |
| 110 | +Papers must be submitted online via HotCRP at: |
| 111 | +https://erlang2026.hotcrp.com |
| 112 | + |
| 113 | +Lightning talks can be submitted via the workshop form: |
| 114 | +https://forms.gle/DHcVwEYVkusxfCA19 |
| 115 | + |
| 116 | +### Formatting |
| 117 | + |
| 118 | +Submitted papers should be in portable document format (PDF), |
| 119 | +formatted using the ACM SIGPLAN style guidelines. Authors should use |
| 120 | +the `acmart` format, with the `sigplan` sub-format for ACM |
| 121 | +proceedings. For details, see: |
| 122 | + |
| 123 | +http://www.sigplan.org/Resources/Author/#acmart-format |
| 124 | + |
| 125 | +It is recommended to use the `review` option when submitting a paper; |
| 126 | +this option enables line numbers for easy reference in reviews. |
| 127 | + |
| 128 | +### Supplementary material |
| 129 | + |
| 130 | +Authors have the option to attach supplementary material to a |
| 131 | +submission, on the understanding that reviewers may choose not to look |
| 132 | +at it. This supplementary material should not be submitted as part of |
| 133 | +the main document; instead, it should be uploaded as a separate PDF |
| 134 | +document or tarball. |
| 135 | + |
| 136 | +Supplementary material should be uploaded at submission time, not by |
| 137 | +providing a URL in the paper that points to an external repository. |
| 138 | + |
| 139 | +### Artifacts |
| 140 | + |
| 141 | +Authors of accepted papers are encouraged to make auxiliary material |
| 142 | +(artifacts like source code, test data, etc.) available with their |
| 143 | +paper. They can opt to have these artifacts published alongside their |
| 144 | +paper in the ACM Digital Library (copyright of artifacts remains with |
| 145 | +the authors). |
| 146 | + |
| 147 | +If an accepted paper’s artifacts are made permanently available for |
| 148 | +retrieval in a publicly accessible archival repository like the ACM |
| 149 | +Digital Library, that paper qualifies for an Artifacts Available badge |
| 150 | +(https://www.acm.org/publications/policies/artifact-review-badging#available). |
| 151 | +Applications for such a badge can be made after paper acceptance and |
| 152 | +will be reviewed by the PC co-chairs. |
| 153 | + |
| 154 | +## Proceedings |
| 155 | + |
| 156 | +As with previous years, the accepted workshop papers will be published |
| 157 | +by the ACM and will appear in the ACM Digital Library. |
| 158 | + |
| 159 | + |
| 160 | +AUTHORS TAKE NOTE: |
| 161 | +The official publication date is the date the proceedings are made available |
| 162 | +in the ACM Digital Library. This date may be up to two weeks prior to the first |
| 163 | +day of your conference. The official publication date affects the deadline for |
| 164 | +any patent filings related to published work. |
| 165 | + |
| 166 | +For more information, please see ACM Copyright Policy |
| 167 | +(http://www.acm.org/publications/policies/copyright-policy) and ACM |
| 168 | +Author Rights (http://authors.acm.org/main.html). |
| 169 | + |
| 170 | +Accepted lightning talks will be posted on the workshop's website but |
| 171 | +not formally published in the proceedings. |
0 commit comments