diff --git a/Cares/index.md b/Cares/index.md
index 9340cdd8..6ed2a1c6 100644
--- a/Cares/index.md
+++ b/Cares/index.md
@@ -242,8 +242,8 @@ We have received open, public feedback from a number of members of the community
Member, jeffrey.foster@tufts.edu, Tufts University, Jul 2025- |
-  Nate Foster (he/him) |
- Member, jnfoster@cs.cornell.edu, Cornell University, Oct 2024- |
+  Nate Foster (he/him) |
+ Member, nate.foster@epfl.ch, EPFL, Oct 2024- |
 Atsushi Igarashi (he/him) |
diff --git a/Conferences.md b/Conferences.md
index fe05da5f..00188506 100644
--- a/Conferences.md
+++ b/Conferences.md
@@ -1,6 +1,6 @@
---
layout: default
-title: "SIGPLAN Conferences"
+title: "SIGPLAN Conferences & Workshops"
---
SIGPLAN organizes the
premier conferences and workshops in the area of programming language
@@ -27,6 +27,12 @@ The conferences listed below are regularly sponsored by
SIGPLAN.
{% for conf in site.data.Conferences %}
-**[{{conf.name}}]({{conf.link}})**
+**[{{conf.name}}]({{conf.link}})**
+{%- if conf.inactive %}
+ (inactive)
+{%- endif -%}
+{%- if conf.cooperation %}
+ (in-cooperation)
+{%- endif %}
{{conf.description}}
{% endfor %}
diff --git a/Conferences/DLS.md b/Conferences/DLS.md
index d5c5bfc3..ec4c6b42 100644
--- a/Conferences/DLS.md
+++ b/Conferences/DLS.md
@@ -30,6 +30,28 @@ For questions or suggestions, please contact the [Steering Committee Chair](#scc
Awards
------
+- Most Notable Paper Award 2026 for 2016
+ - Recipients: Stefan Marr, Benoit Daloze, Hanspeter Mössenböck
+ - Title: Cross-Language Compiler Benchmarking—Are We Fast Yet?
+ - Conference: DLS 2016
+ - Paper: [https://doi.org/10.1145/2989225.298923](10.1145/2989225.298923)
+ - Citation: Comparing the performance of different language implementations is a hard task,
+ given the many features and requirements that complicate optimizations. This paper addresses
+ this challenge by proposing a set of cross-language benchmarks that has become a key reference
+ for the research community. By using an abstract language with core features, the approach ensures
+ that an identical workload is exposed to each language, thus enabling fair comparisons.
+
+- Most Notable Paper Award 2025 for 2015
+ - Recipient: Marc Feeley
+ - Title: Compiling for Multi-language Task Migration
+ - Conference: DLS 2015
+ - Paper: [https://dl.acm.org/doi/10.1145/2816707.2816713](10.1145/2816707.2816713)
+ - Citation: Recent years have seen a resurgent interest in the use and implementation of first-class control,
+ especially in the form of delimited continuations via effect handlers. This paper is motivated by the
+ challenges of implementing continuations for an uncooperative environment and the opportunities for
+ code migration that the implementation affords. The paper recaps the design of the Gambit Virtual Machine
+ for efficient continuations, and it provides evidence for the ongoing effectiveness of the design.
+
- Most Notable Paper Award 2024 for 2014
- Recipients: Vanessa Freudenberg, Dan Ingalls, Tim Felgentreff, Tobias Pape, Robert Hirschfeld
- Title: SqueakJS: A Modern and Practical Smalltalk that Runs in Any Browser
@@ -44,7 +66,6 @@ Awards
Today, SqueakJS continues to be used in education, for web applications,
and as environments to preserve important parts of Smalltalk’s history, and with it, computing history.
-
- Most Notable Paper Award 2023 for 2013
- Recipients: Esteban Allende, Johan Fabry, Éric Tanter
- Title: Cast Insertion Strategies for Gradually-Typed Objects
@@ -60,7 +81,6 @@ Awards
In particular, the proposed hybrid approach has been adapted time and
time again by many systems, giving this work a lasting impact beyond its original scope.
-
- Most Notable Paper Award 2022 for 2012
- Recipients: Thomas Würthinger, Andreas Wöß, Lukas Stadler, Gilles Duboscq, Doug Simon, and Christian Wimmer
- Title: Self-optimizing AST interpreters
@@ -111,8 +131,7 @@ Awards
- Recipients: Jeremy G. Siek and Manish Vachharajani
- Title: Gradual Typing With Unification-based Inference
- Conference: DLS 2008
- - Paper:
- [https://dl.acm.org/citation.cfm?doid=1408681.1408688](https://dl.acm.org/citation.cfm?doid=1408681.1408688)
+ - Paper: [https://dl.acm.org/citation.cfm?doid=1408681.1408688](https://dl.acm.org/citation.cfm?doid=1408681.1408688)
- Citation: The 2008 DLS paper "Gradual Typing With
Unification-based Inference" showed that one can increase the
static guarantees made in a program through an ingenious
diff --git a/Conferences/GPCE.md b/Conferences/GPCE.md
index fb408ca2..d573fe5f 100644
--- a/Conferences/GPCE.md
+++ b/Conferences/GPCE.md
@@ -2,7 +2,7 @@
layout: default
title: "Generative Programming: Concepts and Experiences (GPCE)"
---
-As the commercial production of software systems moves towards being a traditional industry, automation will necessarily play a more substantial role in this industry, just as it plays a key role in the production of traditional commodities such as garments, automobiles, chemicals, and electronics. GPCE is a conference promoting the application and innovation of foundational techniques for supporting automatic program generation.
+As the commercial production of software systems moves towards being a traditional industry, automation will necessarily play a more substantial role in this industry, just as it plays a key role in the production of traditional commodities such as garments, automobiles, chemicals, and electronics. [GPCE](https://conf.researchr.org/series/gpce) is a conference promoting the application and innovation of foundational techniques for supporting automatic program generation.
**Steering Committee:**
@@ -10,7 +10,11 @@ As the commercial production of software systems moves towards being a tradition
**Conference Web Pages**
-- [GPCE 2022](https://2022.splashcon.org/home/gpce-2022)
+- [GPCE 2026](https://conf.researchr.org/home/gpce-2026) (Brussels, Belgium)
+- [GPCE 2025](https://conf.researchr.org/home/gpce-2025) (Bergen, Norway)
+- [GPCE 2024](https://conf.researchr.org/home/gpce-2024) (Pasadena, California, U.S.A.)
+- [GPCE 2023](https://conf.researchr.org/home/gpce-2023) (Cascais, Portugal)
+- [GPCE 2022](https://2022.splashcon.org/home/gpce-2022) (Auckland, New Zealand)
- [GPCE 2021](https://conf.researchr.org/home/gpce-2021)
- [GPCE 2020](https://conf.researchr.org/home/gpce-2020)
- [GPCE 2019](https://conf.researchr.org/home/gpce-2019)
diff --git a/Conferences/MPLR.md b/Conferences/MPLR.md
index ab0ebcc1..425602fd 100644
--- a/Conferences/MPLR.md
+++ b/Conferences/MPLR.md
@@ -16,6 +16,7 @@ MPLR commenced in 2002 as a Java-focused conference (Principles and Practice of
**Web Pages of Previous Conferences**
+* [MPLR 2027](https://2027.splashcon.org/home/mplr-2027) (Prague, Czechia)
* [MPLR 2026](https://2026.ecoop.org/home/mplr-2026) (Brussels, Belgium)
* [MPLR 2025](https://conf.researchr.org/home/icfp-splash-2025/mplr-2025) (Singapore)
* [MPLR 2024](https://conf.researchr.org/home/issta-ecoop-2024/mplr-2024) (Vienna, Austria)
diff --git a/Conferences/OOPSLA.md b/Conferences/OOPSLA.md
index bd9bdd82..5f196f39 100644
--- a/Conferences/OOPSLA.md
+++ b/Conferences/OOPSLA.md
@@ -4,7 +4,21 @@ title: "Object-oriented Programming, Systems, Languages, and Applications (OOPSL
---
OOPSLA (Object-oriented Programming, Systems, Languages, and Applications) is now part of SPLASH (Systems, Programming, Languages, and Applications: Software for Humanity).
-The OOPSLA Steering Committee is a strict subset of the [SPLASH Steering Committee](/Conferences/SPLASH) and consists of the past three OOPSLA RC (co-)chairs and present and future RC (co-)chairs and has its own mailing list for discussing OOPSLA specific issues. The SPLASH SC Chair is also a member of this committee and is the committee chair by default but can choose to delegate the chair position if desired.
+**OOPSLA Steering Committee**
+
+The OOPSLA Steering Committee is a *strict subset* of the [SPLASH Steering Committee](/Conferences/SPLASH) and is constituted by the following members:
+
+- future, current, and *past three* SPLASH General Chairs,
+- future, current, and *past three* OOPSLA RC (co-)chairs,
+- the SPLASH Steering Committee Chair, who is the chair of the OOPSLA Steering Committee by default but can choose to delegate the chair position if desired.
+
+*NB!* In 2027 the past three years are 2026, 2025, and 2024.
+
+The OOPSLA Steering Committee has its own mailing list for discussing OOPSLA specific issues.
+
+The current OOPSLA steering committee is:
+
+{% include committee.liquid name="OOPSLA Steering Committee" %}
The scope of OOPSLA includes all aspects of programming languages and software engineering, broadly construed. Papers that address any aspect of software development are welcome, including requirements, modeling, prototyping, design, implementation, generation, analysis, verification, testing, evaluation, maintenance, reuse, replacement, and retirement of software systems. Papers may address these topics in a variety of ways, including new tools (such as languages, program analyses, and runtime systems), new techniques (such as methodologies, design processes, code organization approaches, and management techniques), and new evaluations (such as formalisms and proofs, corpora analyses, user studies, and surveys).
diff --git a/Conferences/Onward.md b/Conferences/Onward.md
index bea20806..85efb7da 100644
--- a/Conferences/Onward.md
+++ b/Conferences/Onward.md
@@ -8,42 +8,68 @@ aspect of programming. Welcomed are papers that propose and argue for
new approaches to the creation of software as well as reflections on
technology and ideas bearing on programming broadly construed.
+The current SPLASH steering committee is:
+
+{% include committee.liquid name="Onward! Steering Committee" %}
+
[A Table of Contents](./Onward_legacy.md) for the years 2002–2010.
-Onward! 2024
+Onward! 2026
------------
-- Pasadena, California, USA, October 23-25, 2024
-- Co-located with SPLASH 2024
-- Papers chair: Jonathan Edwards (unaffiliated)
-- Essays chair: Marcel Taeumel (HPI and University of Potsdam)
-- [https://2024.splashcon.org](https://2024.splashcon.org)
-- [https://2024.splashcon.org/track/splash-2024-Onward-papers](https://2024.splashcon.org/track/splash-2024-Onward-papers)
-- [https://2024.splashcon.org/track/splash-2024-Onward-Essays](https://2024.splashcon.org/track/splash-2024-Onward-Essays)
+- Oakland, California, USA, October 3-9, 2026
+- Co-located with SPLASH/ISSTA 2026 at the Oakland Marriott City Center
+- Papers chair: Sverrir Thorgeirsson (ETH Zurich)
+- Essays chair: Felienne Hermans (Vrije Universiteit Amsterdam)
+- [https://2026.splashcon.org](https://2026.splashcon.org)
+- [https://2026.splashcon.org/track/splash-2026-onward--papers](https://2026.splashcon.org/track/splash-2026-onward--papers)
+- [https://2026.splashcon.org/track/splash-2026-onward--essays](https://2026.splashcon.org/track/splash-2026-onward--essays)
Awards
------
-- Most Notable Paper Award 2024 (1) for 2011
+- Most Notable Paper Award 2026 for 2016
+ - Recipients: Johannes Emerich
+ - Title:
+ - Conference: Onward! 2016
+ - Paper: [https://dl.acm.org/doi/abs/10.1145/2986012.2986030](https://dl.acm.org/doi/abs/10.1145/2986012.2986030)
+ - Citation: In this essay, Johannes Emerich revisits age-old questions of language design in a still-new and surprising way, with strong direct analogies to the history of mathematics and the role of intuition. His articulate and unmistakably personal essay manages to be critical of modernist formal-methods approaches while fully embracing the mathematical tradition. Read today, it finds new relevance around the recent application of large language models to both mathematics and programming. With its creative spirit and challenge to established viewpoints, it is a uniquely Onward! contribution.
+
+- Most Notable Paper Award 2025 for 2015 (Dual Award)
+ - First Award:
+ - Recipients: Andrei Chiş, Oscar Nierstrasz, Aliaksei Syrel, Tudor Gîrba
+ - Title: The Moldable Inspector
+ - Conference: Onward! 2015
+ - Paper: [https://dl.acm.org/doi/abs/10.1145/2814228.2814234](https://dl.acm.org/doi/abs/10.1145/2814228.2814234)
+ - Citation: This paper is a beautiful blend of identifying an aspect of programming environments that was stale and not serving the needs of programmers and building something to meet those needs that was new and insightful. It is an exemplar of the Onward! spirit: exploring different ways of thinking about, approaching and reporting on programming language and software engineering research.
+ - Second Award:
+ - Recipients: Daniel Jackson
+ - Title: Towards a Theory of Conceptual Design for Softwar
+ - Conference: Onward! 2015
+ - Paper: [https://dl.acm.org/doi/abs/10.1145/2814228.2814248](https://dl.acm.org/doi/abs/10.1145/2814228.2814248)
+ - Citation: This essay deftly argues the need to consider concepts as first-class entities during software design, providing nice examples to show where a lack of coherent concepts leads to software that is more difficult to use for a human.
+It has had a substantial influence not only the field of Software Design, but also subsequent submissions to Onward.
+
+- Most Notable Paper Award 2023 for 2013
- Recipients: Sean McDirmid
- - Title: Coding at the Speed of Touch
- - Conference: Onward! 2011
- - Paper: [https://dl.acm.org/doi/10.1145/2048237.2048246](https://dl.acm.org/doi/10.1145/2048237.2048246)
- - Citation: This 2011 Onward! paper describes the design and implementation of YinYang, a graphical system providing a proficient programming experience for tablet devices with constrained screen space. YingYang's tile-based approach sidestepped these devices' limited text-editing capabilities and enabled an intuitive and effective form of direct manipulation. The work stands out as an emblematic Onward! contribution. It is notable for championing programmability on a class of traditionally "closed" devices, exploring many subtle design points of graphical and visual languages, and as a call to action for moving "beyond typewriters" and inspiring the next generation of programmers.
+ - Title: Usable Live Programming
+ - Conference: Onward! 2013
+ - Paper: [https://dl.acm.org/doi/10.1145/2509578.2509585](https://dl.acm.org/doi/10.1145/2509578.2509585)
+ - Citation: This paper revitalized the study of live programming, introducing mechanisms that are now standard techniques in the field. The paper epitomizes the spirit of Onward!, asking risky questions outside the current discourse. In its form the paper was a breath of fresh air, enlivened by the use of comic strips. The work marked the beginning of a rich seam of research that has been productively mined at the ongoing LIVE workshop series at SPLASH.
-- Most Notable Paper Award 2024 (2) for 2012
+- Most Notable Paper Award 2022 for 2012
- Recipients: Andrew P. Black, Kim B. Bruce, Michael Homer and James Noble
- Title: Grace: the Absence of (Inessential) Difficulty
- Conference: Onward! 2012
- Paper: [https://dl.acm.org/doi/pdf/10.1145/2384592.2384601](https://dl.acm.org/doi/pdf/10.1145/2384592.2384601)
- Citation: In this Onward! 2012 paper, the authors distilled a tremendous effort to accommodate the needs of programming pedagogy in a new language design. The paper is a model of clarity, deftly justifying its choices while also situating Grace within the rich history of programming languages past and present. It has supported and inspired considerable follow-on work, not only on pedagogy but also in programming language research topics such as gradual typing and the semantics of object-orientation.
-- Most Notable Paper Award 2023 for 2013
+- Most Notable Paper Award 2021 for 2011
- Recipients: Sean McDirmid
- - Title: Usable Live Programming
- - Conference: Onward! 2013
- - Paper: [https://dl.acm.org/doi/10.1145/2509578.2509585](https://dl.acm.org/doi/10.1145/2509578.2509585)
- - Citation: This paper revitalized the study of live programming, introducing mechanisms that are now standard techniques in the field. The paper epitomizes the spirit of Onward!, asking risky questions outside the current discourse. In its form the paper was a breath of fresh air, enlivened by the use of comic strips. The work marked the beginning of a rich seam of research that has been productively mined at the ongoing LIVE workshop series at SPLASH.
+ - Title: Coding at the Speed of Touch
+ - Conference: Onward! 2011
+ - Paper: [https://dl.acm.org/doi/10.1145/2048237.2048246](https://dl.acm.org/doi/10.1145/2048237.2048246)
+ - Citation: This 2011 Onward! paper describes the design and implementation of YinYang, a graphical system providing a proficient programming experience for tablet devices with constrained screen space. YingYang's tile-based approach sidestepped these devices' limited text-editing capabilities and enabled an intuitive and effective form of direct manipulation. The work stands out as an emblematic Onward! contribution. It is notable for championing programmability on a class of traditionally "closed" devices, exploring many subtle design points of graphical and visual languages, and as a call to action for moving "beyond typewriters" and inspiring the next generation of programmers.
- Most Notable Paper Award 2020 for 2010
- Recipients: Lennart C. L. Kats, Eelco Visser, and Guido Wachsmuth
@@ -172,6 +198,24 @@ Awards
Past Events
-----------
+- Onward! 2025
+ - Singapore, October 16-18, 2025
+ - Co-located with SPLASH 2025
+ - Papers chair: Shigeru Chiba (University of Tokyo) and Clemens Nylandsted Klokmose (Aarhus University)
+ - Essays chair: Colin S. Gordon (Drexel University)
+ - [https://2025.splashcon.org](https://2025.splashcon.org)
+ - [https://2025.splashcon.org/track/splash-2025-Onward-papers](https://2025.splashcon.org/track/splash-2025-Onward-papers)
+ - [https://2025.splashcon.org/track/splash-2025-Onward-Essays](https://2025.splashcon.org/track/splash-2025-Onward-Essays)
+
+- Onward! 2024
+ - Pasadena, California, USA, October 23-25, 2024
+ - Co-located with SPLASH 2024
+ - Papers chair: Jonathan Edwards (unaffiliated)
+ - Essays chair: Marcel Taeumel (HPI and University of Potsdam)
+ - [https://2024.splashcon.org](https://2024.splashcon.org)
+ - [https://2024.splashcon.org/track/splash-2024-Onward-papers](https://2024.splashcon.org/track/splash-2024-Onward-papers)
+ - [https://2024.splashcon.org/track/splash-2024-Onward-Essays](https://2024.splashcon.org/track/splash-2024-Onward-Essays)
+
- Onward! 2023
- Cascais, Portugal, October 25-27, 2023
- Co-located with SPLASH 2023
diff --git a/Conferences/SLE.md b/Conferences/SLE.md
index 4396f343..57f8bac1 100644
--- a/Conferences/SLE.md
+++ b/Conferences/SLE.md
@@ -14,6 +14,12 @@ algebraic specification, etc.
**Web Pages of Previous Conferences**
+- [SLE 2026](http://www.sleconf.org/2026) (Rennes, France)
+- [SLE 2025](http://www.sleconf.org/2025) (Koblenz, Germany)
+- [SLE 2024](http://www.sleconf.org/2024) (Pasadena, California, U.S.A.)
+- [SLE 2023](http://www.sleconf.org/2023) (Cascais, Portugal)
+- [SLE 2022](http://www.sleconf.org/2022) (Auckland, New Zealand)
+- [SLE 2021](http://www.sleconf.org/2021) (virtual)
- [SLE 2020](http://www.sleconf.org/2020) (virtual)
- [SLE 2019](http://www.sleconf.org/2019) (Athens, Greece)
- [SLE 2018](http://www.sleconf.org/2018) (Boston, Massachusetts, U.S.A.)
diff --git a/Conferences/SPLASH.md b/Conferences/SPLASH.md
index 442309b1..81ec7a24 100644
--- a/Conferences/SPLASH.md
+++ b/Conferences/SPLASH.md
@@ -17,9 +17,9 @@ The SPLASH Steering Committee is constituted by the following members:
- Steering Committee Chair for *any conference that co-located with SPLASH for the past three years*
- the outgoing Chair of the Steering Committee, for one year past the end of their term as Chair.
-*NB!* In 2026 the past three years are 2025, 2024, and 2023 and the co-located conferences include: SAS (while GPCE and SLE last co-located in 2023).
+*NB!* In 2027 the past three years are 2026, 2025, and 2024 and the co-located conferences include: SAS and GPCE (while SLE last co-located in 2024).
-The Chair of the Steering Committee is elected by the Steering Committee from among the members of the committee to serve a two-year term. The Chair of the Steering Committee would normally also serve as the chair of the OOPSLA Steering Committee which is a subcommittee of the SPLASH SC. The outgoing chair serves an additional year on the committee past his or her term as chair to provide institutional memory.
+The Chair of the Steering Committee is elected by the Steering Committee from among the members of the committee to serve a two-year term. The Chair of the Steering Committee would normally also serve as the chair of the [OOPSLA Steering Committee](/Conferences/OOPSLA) which is a subcommittee of the SPLASH SC (see below). The outgoing chair serves an additional year on the committee past his or her term as chair to provide institutional memory.
Steering Committee membership was expanded by adding members-at-large in 2020, with the intention of adding one member-at-large each subsequent year. Members-at-large serve 4 year terms and are selected by the Steering Committee.
@@ -29,6 +29,10 @@ The current SPLASH steering committee is:
{% include committee.liquid name="SPLASH Steering Committee" %}
+**OOPSLA Steering Committee: a strict subset of the SPLASH Steering Committee**
+
+The [OOPSLA Steering Committee](/Conferences/OOPSLA) is a *strict subset* of the SPLASH Steering Committee listed above. It consists of the future, current, and *past three* SPLASH General Chairs together with the future, current, and *past three* OOPSLA RC (co-)chairs, and is chaired by the SPLASH Steering Committee Chair by default. It has its own mailing list for OOPSLA specific issues, and its current membership is listed on the [OOPSLA page](/Conferences/OOPSLA).
+
**Documents on How to Run SPLASH/OOPSLA Conferences**
* [OOPSLA](/Conferences/SPLASH/ObjectivesOfOOPSLA)
@@ -46,6 +50,7 @@ The current SPLASH steering committee is:
Web Pages of Previous Conferences
---------------------------------
+* [SPLASH 2027](https://2027.splashcon.org/) (Prague, Czechia)
* [SPLASH 2026](https://2026.splashcon.org/) (Oakland, CA, USA)
* [SPLASH 2025](https://2025.splashcon.org/) (Singapore, Singapore)
* [SPLASH 2024](https://2024.splashcon.org/) (Pasadena, CA, USA)
diff --git a/Conferences/SPLASH/HowToSPLASH.md b/Conferences/SPLASH/HowToSPLASH.md
index 1c22295c..10816ee5 100644
--- a/Conferences/SPLASH/HowToSPLASH.md
+++ b/Conferences/SPLASH/HowToSPLASH.md
@@ -3,6 +3,337 @@ layout: default
title: "How to Run SPLASH"
---
-The information on this public page is slowly being migrated from the private notes [stored here](https://docs.google.com/document/d/1wyVhwfp4TXm9_EeIDAZ5SS7YyvR0WedsFxeCynAAEt4).
+This page contains guidance for current and future SPLASH General Chairs, compiled from the experiences of previous chairs.
-Private files accessible by the Steering Committee members only are on the special [SPLASH Google Drive](https://drive.google.com/drive/folders/0APXWu4PPnVzBUk9PVA) provided by SIGPLAN.
+**Also See:**
+
+- [Practices of PLDI](http://www.sigplan.org/sites/default/files/PracticesofPLDI.pdf)
+- [Principles of POPL](/Conferences/POPL/Principles)
+- [The Functioning of ICFP](https://www.icfpconference.org/TheFunctioningofICFP.pdf)
+- [Objectives of OOPSLA](/Conferences/SPLASH/ObjectivesOfOOPSLA)
+
+*Originally documented by Annabelle Satin (SIGPLAN PCO in the 2010's) and then amended during and after COVID by the SPLASH General Chairs, including [Alex Potanin](https://potanin.github.io/) (2022), [Manu Sridharan](https://manu.sridharan.net/) (2024), and [Ilya Sergey](https://ilyasergey.net/) (2025). Future General Chairs are expected to keep these notes up to date.*
+
+**Important:** All documents related to SPLASH must be stored on the [SPLASH Google Drive](https://drive.google.com/drive/folders/0APXWu4PPnVzBUk9PVA) provided by SIGPLAN, which is the central repository for all essential documents. This ensures continuity across years and that future chairs can access prior materials.
+
+The current SIGPLAN PCO (Professional Conference Organiser) is [Neringa Young](https://conf.researchr.org/profile/conf/neringayoung), who supports the GC across budgeting, logistics, and communications throughout the conference cycle.
+
+* TOC
+{:toc}
+
+## General ACM Guidance
+
+ACM's [conference planning guide](https://www.acm.org/special-interest-groups/volunteer-resources/conference-planning) is the authoritative reference for running an ACM conference. It is worth at least scanning the [table of contents](https://www.acm.org/special-interest-groups/volunteer-resources/conference-planning/table-of-contents) to know which topics it covers (reimbursing speakers, taxes, etc.) so you can refer back later.
+
+## What is SPLASH?
+
+[SPLASH](https://sigplan.org/Conferences/SPLASH/) typically consists of the following events.
+
+### Conferences
+
+- **Essential:** OOPSLA, Onward!, and SPLASH-E.
+- **Regularly co-locating** (but may vary from year to year): REBASE, SAS, SLE, GPCE, DLS. Currently, DLS has retired and SLE and GPCE are exploring other co-location alternatives.
+- **One-off:** e.g., in 2023, LOPSTR, PPDP, and MPLR also co-located, in 2025 ICFP co-located, and in 2026 ISSTA co-located.
+
+The essential conferences can be assumed to be occurring at every SPLASH. For regularly co-locating conferences, the GC should confirm whether the conference will co-locate that year. Note that some of the co-located communities tend to stay to themselves and value their independence.
+
+### Workshops
+
+Workshops vary from year to year based on a call for proposals. It is worthwhile for the workshop chairs to reach out to organizers of the previous year's workshops to solicit repeat proposals where sensible. Numbers have ranged from around 7 to 15+; 15 is typically the maximum accommodated over 3 days.
+
+Co-located workshops must adhere to the [SIGPLAN Workshop Guidelines](https://www.sigplan.org/Resources/Guidelines/Workshops/). In particular, any proceedings must be published in the ACM Digital Library (or not at all).
+
+### Student-Focused Events
+
+- PLMW
+- Doctoral Symposium
+- Student Research Competition / Poster Session
+
+## Organizing Committee
+
+Form the organizing committee **at least 12 months prior** to the conference. For nearly all positions invited by the GC, each chair serves for **two years** --- one as the "junior" chair and then one as the "senior" chair --- for continuity and knowledge preservation. It is common to ask the senior chair (from the previous year) for suggestions on who to invite as the junior chair for the current year.
+
+### Chairs from Co-Located Events (GC does not need to invite)
+
+- OOPSLA Associate Editors
+- PLMW Chairs
+- SPLASH-E Chairs
+- Artifact Evaluation Chairs
+- Onward! Papers and Essays Chairs
+- REBASE Chairs
+
+### Chairs Invited by the GC
+
+- Workshops Chairs
+- Publicity / Web Chairs
+- Sponsorship Chair
+- Student Volunteer Chairs
+- Video Chairs (they typically self-organize; there is a group of students that overlaps across SIGPLAN conferences)
+- DEI Chair
+- SIGPLAN Track Chair
+- Publications Chair
+- Student Research Competition Chairs
+- Doctoral Symposium Chair
+
+A Finance Chair is not required as SIGPLAN PCO (currently Neringa) can handle this.
+
+Beyond the organizing committee, the GC is the direct contact for the chairs of any other co-located conferences (SLE, GPCE, etc.). Typically, workshop organizers raise queries with the workshop chairs, though they may also contact the GC directly.
+
+See the [SPLASH 2022 Organizing Committee](https://2022.splashcon.org/committee/splash-2022-organizing-committee) as an example.
+
+## Venue and Timing
+
+### Site Selection
+
+- Pick the city and venue **approximately two years in advance**.
+- University venues are cheaper but only available during breaks, which does not work well for the Northern Hemisphere academic calendar.
+- Consider actively coordinating location with other SIGPLAN conferences; there is ongoing discussion about rotating continents for SIGPLAN conferences.
+
+### Rough Process
+
+1. Pick a city; find candidate venues.
+2. Get ACM to obtain formal quotes via John Otero.
+3. Pick the venue.
+4. Get the budget and TMRF approved and sign with the venue.
+5. Everything else follows in the 12 months prior to the conference.
+
+### Timing
+
+- SPLASH is normally in **October** --- avoid Thanksgiving. Historically it has been as early as the first week of October and as late as the first week of December.
+- Plenary keynotes are traditionally held on the 3 main days of OOPSLA and Onward!.
+- Three days of workshops are typically held prior to OOPSLA.
+
+### Attendance Expectations
+
+- East Coast USA: typically 600--700 attendees.
+- West Coast USA: typically 400--500 (2024 on the west coast broke 550).
+- EU and Asia-Pacific: hard to predict.
+- Target registration fee: **around $300 USD per day** where feasible.
+
+## Email Aliases
+
+Various `@splashcon.org` email aliases must be updated every year. Ask the previous General Chair for the CSV file listing all the `splashcon.org` email aliases. Update the addresses for the current year, then email [technicalsupport@acm.org](mailto:technicalsupport@acm.org) and [ishelpdesk@hq.acm.org](mailto:ishelpdesk@hq.acm.org), attaching the updated CSV, and ask them to update the aliases.
+
+## Keynotes
+
+SPLASH typically has **3 keynote plenary talks**. Traditionally:
+
+- One is chosen by the GC.
+- One by the OOPSLA chairs.
+- One by the Onward! chairs.
+
+Coordinate together to ensure a diverse set of speakers.
+
+As of 2024, SPLASH keynote speakers receive **free conference registration** and up to **$2k reimbursement** for travel expenses. For other co-located events, there has not been a standard budget line for keynote reimbursement. If the budget allows, consider giving at least a one-day complimentary registration to keynote speakers at co-located events for the day they are speaking. See also the [SIGPLAN Conference Complimentary Registrations Policy](/Resources/Policies/ComplimentaryRegistrations).
+
+## Paper Deadlines
+
+For all SPLASH-related proceedings (and the OOPSLA PACMPL issues), camera-ready deadlines must be coordinated with Conference Publishing ([info@conference-publishing.com](mailto:info@conference-publishing.com)) to ensure sufficient time for the papers to be available on the ACM DL before the conference. Submission and notification deadlines should be set appropriately. For workshops, guidelines should be given on these dates and communicated to co-located conferences. The Publications Chair can help with this.
+
+## SIGPLAN Track and TOPLAS
+
+### SIGPLAN Track
+
+SPLASH since 2022 has included a **SIGPLAN track**, inviting talks for papers that appeared in the previous year's SIGPLAN conferences (PLDI / POPL / ICFP / SPLASH) but whose speaker was unable to give an in-person talk. The number of slots allocated to SIGPLAN track papers is at the discretion of the GC. Typically, only a small number of authors ask for such a talk (there was 1 at SPLASH 2024). **Please keep this option available every year** --- it offers a second chance to present for those who could not attend the previous year due to travel, visa, or other constraints, and is extra registration revenue.
+
+### TOPLAS
+
+TOPLAS has an agreement with OOPSLA where papers published at TOPLAS may request a talk slot. Acceptance of such talks is at the discretion of the OOPSLA chairs and the GC.
+
+## DEI Events
+
+The following DEI events are typically held during SPLASH:
+
+- SIGPLAN-M lunch (pre-registration required)
+- Women@SPLASH dinner
+- LGBTQ+ lunch
+- URM lunch
+
+The DEI Chair may also organize additional events; e.g., at SPLASH 2024 there was a Newcomer's Coffee. Work with Neringa and the DEI Chair to schedule these events. Announce at the conference that attendees who did not pre-register are welcome at the Women@SPLASH dinner, LGBTQ+ lunch, and URM lunch.
+
+Aim to **not schedule important events in conflict with DEI events**. For example, at SPLASH 2024, the URM lunch was re-scheduled to be an URM coffee to avoid a conflict with an Awards Lunch.
+
+## Online Schedule
+
+All event co-organizers should be encouraged (or required) to have the schedule of their event up to date on the main `splashcon.org` page for the conference. Some events have their own websites, which is fine, but it is important that schedule info also appears on the `splashcon.org` page so attendees can see a consolidated schedule. Try to have this populated a few days before the early registration deadline.
+
+The researchr web interface for creating and modifying the schedule can be counter-intuitive. The Web Chairs typically retain institutional knowledge on how things work and can help out.
+
+## Chairs' Talks and Reports During the Conference
+
+SPLASH does not have a formal business meeting during the conference.
+
+- **Opening:** The GC may say a few welcome words, including information on the number of attendees, venue, etc. Ask the previous GC for their slides.
+- **OOPSLA report:** The OOPSLA chairs typically give a brief report on the OOPSLA review process during the conference (around 5 minutes, 10 max). This can occur, e.g., before the final day's keynote.
+- **Next year's announcement:** Before the final day's keynote, budget time for the announcement of the following year's SPLASH; hopefully one of the next year's chairs will be present to do it.
+
+## Awards
+
+The following awards are typically presented at SPLASH:
+
+- Student Research Competition winners
+- [SIGPLAN John Vlissides Award](/Awards/Vlissides) from the Doctoral Symposium
+- OOPSLA Distinguished Papers and Reviewers
+- OOPSLA Distinguished Artifacts and Artifact Reviewers
+- [OOPSLA Most Influential Paper](/Awards/Conferences/OOPSLA) from 10 years prior
+- Onward! Most Notable Paper from 10 years prior
+
+The GC coordinates these award presentations, arranges printing of certificates (with Neringa's help), and schedules the announcements. It is nice if at least the OOPSLA Most Influential Paper winners can say a few words when accepting.
+
+## Organizing Committee and Review Committee Dinner
+
+Plan a dinner for anyone on the OC or the RC. Invite the next year's GC if they are attending, and also the Student Volunteer and Video Chairs if at all possible. The RC is large, but a significant number do not attend the conference.
+
+## Student Volunteers
+
+Student volunteers typically serve for **2 days** in exchange for free registration (3 days if the schedule is tight). Budget accordingly. Recently there has been significant last-minute "melt" of accepted student volunteers due to inability to travel; depending on the difficulty of recruiting local volunteers, this may need to be factored into how many student volunteers are accepted initially.
+
+The Student Volunteer Chairs are **essential** to the smooth running of the conference --- they deal with many of the logistical issues during the event. Choose carefully, and make them feel appreciated.
+
+Beyond student volunteers, avoid giving free registrations if at all possible --- it can easily get out of control. (Yannis once suggested, when SPLASH was in Athens, giving each sub-conference a small allocation of free regos based on its size and letting the sub-conference decide how to use them.)
+
+## Video Chairs and Virtual Platform
+
+The Video Chairs both organize the video recording and streaming during the conference and help facilitate remote talks and participation. They also manage and set up the virtual platform (Discord, recently). There is typically no need for a separate virtual chair. Help them by forwarding their announcements and requests to the various event organizers.
+
+See also the [SIGPLAN Video Recording Policy](/Resources/Policies/VideoRecording).
+
+## Talk Scheduling
+
+- Past surveys on talk length (10, 15, 20, 25, 30 minutes) have produced mixed results. In 2021 (COVID), 15 minutes was most popular; in 2022 (in-person), people loved 30-minute slots.
+- With ~150 accepted papers and 3 days, options are roughly:
+ - 15-minute slots with 10-minute talks and 2 parallel sessions, or
+ - 3 parallel sessions with 20-minute slots and 15-minute talks.
+- FSE uses 9-minute talks; ICSE can be 5--7 minutes; NeurIPS uses posters. Going into workshop days is unpopular.
+- **Run a post-conference survey every year** to inform future decisions.
+
+Past survey results can be found on the SPLASH Google Drive.
+
+## Ice Cream Social
+
+Traditionally, OOPSLA / SPLASH ends with **ice cream for attendees**. At SPLASH 2024, due to the lengthy OOPSLA schedule on the final day, ice cream was served at the final coffee break before the last session.
+
+## Post-Conference Survey
+
+Send a post-conference survey to gather attendee feedback. A Google Forms template based on previous years exists; contact the most recent GC for editor access and any updates. Sharing results from Google Forms can be painful; one approach is to take screenshots of the charts and put them in a Google Doc.
+
+## OOPSLA-Specific Guidance
+
+The primary OOPSLA-specific guidance lives in [Objectives of OOPSLA](/Conferences/SPLASH/ObjectivesOfOOPSLA) and the [SIGPLAN PC Chair Resources](/Resources/Guidelines/ProChair). The notes below cover items that surface at the GC level.
+
+### OOPSLA Timeline (approximate)
+
+- **October, Year X-2:** General Chair selection.
+- **February, Year X-2:** PC Chair selection.
+- **August, Year X-2:** Submit candidate PC and ERC to SIGPLAN Vice-Chair and SPLASH SC.
+- **October, Year X-1:** Finalize PC and ERC.
+- **October, Year X-1:** Publish PC+ERC and CFP.
+- **March, Year X-1:** Submission deadline.
+- **May, Year X-1:** PC meeting.
+- **May, Year X-1:** First-phase notification.
+- **July, Year X-1:** Second-phase notification.
+- **August, Year X-1:** Camera-ready deadline.
+
+Note: OOPSLA has operated a two-round model with different dates in recent years. See [Objectives of OOPSLA](/Conferences/SPLASH/ObjectivesOfOOPSLA) for the current scheduling guidance.
+
+### PC / RC Composition
+
+The PC (now RC) is selected by the PC/RC Chairs, subject to the [SIGPLAN Diversity Policy](/Resources/Policies/Diversity). Composition must be approved by the EC Vice-Chair **before** invitations are issued. The PC Chair should also work closely with the SPLASH SC Chair to avoid surprises.
+
+The SIGPLAN diversity policy is intentionally vague. Historical prescriptions for OOPSLA's committees have included:
+
+- No more than 2 people from the same institution. An "institution" is an independent administrative organization (e.g., the 10 campuses of the University of California count as different institutions; different departments of the same campus do not). When in doubt, consult the SC Chair.
+- No more than 20% overlap with the previous year's committee.
+- At least 10% of members should be women, ideally 15%.
+- Strive for relative balance between academia and industry.
+- Strive for relative balance in seniority (ideally 1/3 junior, 1/3 mid-career, 1/3 senior).
+- Strive for geographic representativeness.
+
+Suggestions for identifying members:
+
+- Look at previous years' authors to find strong OOPSLA contributors.
+- Pay attention to OOPSLA contributors who are not yet well known.
+
+### External Review Committee (historical)
+
+Historically, OOPSLA's ERC was primarily used to review submissions from members of the Program Committee. This had several advantages: fewer conflicts of interest during the PC meeting, less imbalance in PC-meeting attendance, and consistent treatment for reviews of PC papers. Historically, PC papers received 4 reviews and non-PC papers received 3. ERC composition followed the same policies as the PC. See [Objectives of OOPSLA](/Conferences/SPLASH/ObjectivesOfOOPSLA) for the current model.
+
+### Reserve Reviewer Policy
+
+Introduced in 2025 and continued in the [2026 CfP](https://2026.splashcon.org/track/oopsla-2026), the **Reserve Reviewer policy** requires that at least one senior author (PhD completed 5+ years ago) per submission register as a reserve reviewer, unless exempt. Exemptions apply when: the paper has no senior authors; a senior author is already an RC member; or all senior authors are new to SIGPLAN/SIGSOFT (fewer than 3 major conference publications), chairing a 2025--2027 conference, or have documented exceptional circumstances. Reserve reviewers must upload 5--10 prior papers to TPMS for expertise matching. This has been a reliable load-balancer for OOPSLA's growing submission volume and future chairs are encouraged to continue refining it. See [Objectives of OOPSLA](/Conferences/SPLASH/ObjectivesOfOOPSLA#reserve-reviewers) for further details.
+
+### TPMS Budget
+
+OOPSLA relies on the [Toronto Paper Matching System (TPMS)](https://torontopapermatching.org/) for reviewer--paper matching and bidding. TPMS is partly funded by the conferences that use it and **charges participating conferences a fee**. The GC should make sure this fee is included in the SPLASH budget (and TMRF) from the outset, and paid from the conference rather than out of pocket by the OOPSLA RC chairs. Confirm the arrangement with the RC chairs early: they are responsible for contacting the TPMS team ([reviewer-paper-matching@cs.toronto.edu](mailto:reviewer-paper-matching@cs.toronto.edu)) to organise a new instance for their OOPSLA, and that instance needs to exist before RC invitations go out. See [Objectives of OOPSLA](/Conferences/SPLASH/ObjectivesOfOOPSLA#using-tpms) for the RC-chair side of this.
+
+## Open Policy Questions
+
+The following items are under ongoing discussion and would benefit from a SPLASH- or OOPSLA-specific policy page:
+
+- The SPLASH GC is allowed to submit to OOPSLA in their year, provided they were not directly involved in picking the OOPSLA RC chairs but only as part of the normal SPLASH-SC-wide selection process.
+- Having a SIGPLAN track at every SPLASH.
+- Rotating continents for SIGPLAN conferences, with SPLASH actively coordinating locations.
+
+## Historical Timeline (Annabelle, pre-Neringa)
+
+The following timeline was originally maintained by Annabelle Satin. Months are relative to the conference date; dates in the original were anchored to a specific year and are omitted here.
+
+### Pre-Conference
+
+| Months Before | Task | Comments / Who |
+| ---: | :--- | :--- |
+| 18 | Submit PAF | Needs city, date, PC Chair, and GC |
+| 14 | Site selection | PCO checks possible venues / ACM requests formal quotes / GC visits and requests formal contract from ACM / GC + PCO review and approve |
+| 14 | Appoint committee members | PCO updates list of previous committee; GC picks committee |
+| 13 | Create logo | GC picks designer, or PCO connects GC with regular supplier |
+| 12 | Create website | Elmer creates link; Web or Publications Chair populates; individual workshops populate their own pages (Workshop Chair sets up pages) |
+| 12 | Submit TMRF | PCO provides copies from previous years for Part I; PCO creates budget for Part II (discussed with GC) |
+| 12 | Approve hotel / venue contract for submission | GC with PCO |
+| 12 | Schedule fortnightly calls with Conference Manager | |
+| 12 | Call for workshops | Workshops Chair posts |
+| 10 | Prepare the Call for Papers (CFP) | |
+| 10 | Contract CPC | GC reviews current contract |
+| 9 | Solicit corporate support | PCO provides contact list from previous sponsors, full list of previous attendees, and committee (no direct contacts by default, but can be provided on request) |
+| 9 | Select food & beverage provider(s) | Banquet vs. daily social? PCO gathers quotes |
+| 9 | Select A/V equipment and Wi-Fi provider | PCO gathers quotes from suppliers |
+| 9 | Select registration provider | RSL |
+| 9 | Select banquet venue & caterer | Daily social vs. banquet? GPCE / SLE may find their own venue |
+| 9 | Update the budget with variable costs | PCO updates; GC approves |
+| 9 | Contact tourist office, local authorities, etc., for accommodation arrangements | PCO provides list of nearby (alt) hotels |
+| 9 | Apply for potential grants for students, speakers, etc. | PLMW applies for NSF |
+| 6 | Start student page / application | PCO updates and works with captains |
+| 6 | Submit schedule of events to the conference venue | PCO updates post workshop acceptance |
+| 6 | Schedule calls with Conference Manager (fortnightly or weekly) | |
+| 5 | Send acceptance and copyright forms to authors | CPC sends |
+| 5 | Prepare advance program (print or electronic) | GC if full booklet; PCO if 2-page schedule |
+| 5 | Decide on registration fees and models; communicate with registration provider | PCO revises budget and works with RSL |
+| 5 | Invite keynotes | PC + Onward! + GC pick and invite |
+| 4 | Obtain camera-ready papers from authors | CPC sends |
+| 4 | Set up the registration system | RSL |
+| 4 | Select sites for PC and SC dinners | Usually lunch on-site for SPLASH |
+| 3 | Notify the venue of exact A/V needs | PCO reviews and finalizes |
+| 3 | Notify the caterers of menus (numbers TBC) | PCO revises |
+| 3 | Open early registration | RSL brings live |
+| 3 | Call for participation | Publications Chair sends |
+| 3 | Publish the advance program | PC provides program; Workshops Chair follows up with workshops |
+| 3 | Schedule calls with Conference Manager every 7--10 days | |
+| 2 | Prepare print-ready proceedings | |
+| 2 | Prepare plaques or certificates | Define awards and responsibilities |
+| 2 | Establish signage needs and arrange for printing | PCO works with hotel |
+| 2 | Source and contract supplier of registration bags, etc. | PCO finds supplier |
+| 2 | Book venue for PC and SC dinners | Usually N/A for SPLASH |
+| 2 | Liaise with speakers for travel and accommodation needs | PCO |
+| 1 | Print final program | SLE keynote title; poster session location |
+| 1 | Determine social activities | |
+| 1 | Liaise with sponsors on comps and print material | |
+| 15 days | Establish needs for badges (special diet, social events, etc.) | |
+| 7 days | Deliver final printed program to venue | |
+| 7 days | Liaise with registration and caterers on special dietary needs | |
+| 7 days | Print badges | |
+
+### Post-Conference
+
+| Months After | Task |
+| ---: | :--- |
+| 1 | Liaise with Conference Manager to ensure all bills have been added to the budget |
+| 3 | Submit the final financial report to ACM |
diff --git a/Conferences/SPLASH/ObjectivesOfOOPSLA.md b/Conferences/SPLASH/ObjectivesOfOOPSLA.md
index b94ca23e..235ddb7c 100644
--- a/Conferences/SPLASH/ObjectivesOfOOPSLA.md
+++ b/Conferences/SPLASH/ObjectivesOfOOPSLA.md
@@ -5,6 +5,13 @@ title: "Objectives of OOPSLA"
This page contains guidance for current and future OOPSLA RC chairs, compiled from the experiences of previous chairs.
+**Also See:**
+
+- [Practices of PLDI](http://www.sigplan.org/sites/default/files/PracticesofPLDI.pdf)
+- [Principles of POPL](/Conferences/POPL/Principles)
+- [The Functioning of ICFP](https://www.icfpconference.org/TheFunctioningofICFP.pdf)
+- [How to Run SPLASH](/Conferences/SPLASH/HowToSPLASH)
+
*Started by [Alex Potanin](https://potanin.github.io/) and [Bor-Yuh Evan Chang](https://plv.colorado.edu/bec/) (OOPSLA 2024 RC co-chairs). Revised by [Shriram Krishnamurthi](https://cs.brown.edu/~sk/) and [Sukyoung Ryu](https://plrg.kaist.ac.kr/ryu) (OOPSLA 2025 RC co-chairs). We expect further input from [Anders Møller](https://cs.au.dk/~amoeller/) and [Işıl Dillig](https://www.cs.utexas.edu/~isil/) (OOPSLA 2026 RC co-chairs) and [Ilya Sergey](https://ilyasergey.net/) and [Nadia Polikarpova](https://cseweb.ucsd.edu/~npolikarpova/) (OOPSLA 2027 RC co-chairs).*
**Important:** All documents related to OOPSLA must be stored on the [SPLASH Google Drive](https://drive.google.com/drive/folders/0APXWu4PPnVzBUk9PVA) provided by SIGPLAN, in the folder for the relevant year. This ensures continuity across years and that future chairs can access prior materials. Do not use personal storage or other shared drives for official OOPSLA documents.
@@ -38,6 +45,25 @@ There is a **SPLASH SC** (splash-sc@googlegroups.com) and, created in the afterm
- OOPSLA is in intense competition with other conferences for RC members. **Get your RC invites out early.**
- A very private document restricted to RC chairs only is maintained with notes on the selection of Associate Editors (AEs) as potential future RC candidates. Consult this internal document on the SPLASH Google Drive (or via the SPLASH/OOPSLA SC) when forming your RC.
+## Reviewer Policies and Attestations
+
+The RC signup form should require every invited reviewer to read and attest, as a **forced-choice question**, to two rules. This applies to all reviewers, including [Reserve Reviewers](#reserve-reviewers) --- capture the attestation at registration time.
+
+> Serving on the OOPSLA Review Committee means following the two rules below. Please confirm you have read them and will follow them.
+>
+> 1. **Confidentiality of submissions.** Submitted papers, and the reviews on them, are confidential. Do not share a submission with anyone outside the review process; the one exception is light, well-attributed use of a sub-reviewer with the RC Chairs' approval. Furthermore, do not upload or paste a submission, or any part of its content, into any external or hosted AI/LLM service.
+>
+> 2. **Integrity of reviews.** Your review must be your own work: your understanding, your analysis, and your judgment, written in your own words. You may use LLMs to correct spelling or grammar in text you have written yourself, but you may NOT use a language model, whether a hosted service or one running locally on your own hardware, to read a submission for you, to summarise or critique it, or to draft any part of a review. The assessment, the arguments, and the verdict must be yours.
+>
+> ○ I have read both rules and I agree to follow them.
+> ○ I have a question or concern about one of these. Please contact me before my appointment is finalised.
+
+The two rules are kept separate so that local LLMs --- which raise no confidentiality concern --- are still ruled out for drafting reviews under Rule 2.
+
+### Joint Reviews with Students or Postdocs
+
+> For training and educational purposes, RC members may jointly write a review with a student or postdoc, but this **must** be cleared with the RC chair first to ensure no conflicts. The RC member must still take full responsibility for the final review and for online discussion of the submission.
+
## Choosing Associate Editors
Think of an AE as **the chair of a mini-conference**. You are subdividing OOPSLA into a bunch of mini-venues, each headed by an AE. Ultimately the buck stops with you, but this mental model helps in choosing AEs.
@@ -55,20 +81,21 @@ Think of an AE as **the chair of a mini-conference**. You are subdividing OOPSLA
### Avoiding Date Conflicts
- Check competing conferences: primarily **POPL, PLDI, and ICFP**, but also SE events like **ICSE, FSE, ASE, and ISSTA**. You cannot avoid all clashes, but avoid egregious ones (e.g., OOPSLA papers due during the week of POPL). In many cases, other conferences only settle their dates after yours are published.
+- **Keep the OOPSLA R1 notification deadline well clear of the PLDI submission deadline.** A tight gap puts authors of OOPSLA R1 rejections under pressure to rework for PLDI in a few days, and overlaps the OOPSLA R1 discussion/decision crunch with PLDI submission for the many RC members who also submit to PLDI. Aim for at least a 2--3 week buffer.
- Be aware of major holidays: Christmas, New Year, Thanksgiving in the US (nearly a week lost). Europeans have also complained about review duties during August, the traditional vacation month, but it is hard to have two rounds and skip August entirely.
### Review Period Duration
- Since R2 gets about **twice as many papers as R1**, the initial reviewing period for R2 should be roughly **twice that of R1** if following the 1-review-per-week policy. Other parts (discussion time, response time, etc.) are constant across rounds.
- Aim for **6 weeks of review time** for each round, especially R2 with roughly 10 papers per reviewer.
-- Authors strongly prefer **4 days for the response period** (the 2026 CfP uses 4 days: e.g., Tuesday--Friday for R1, Tuesday--Friday for R2).
+- Give authors **at least 4 full days for the response period**, not 3. A 3-day window is painful for authors with large time-zone differences, and the response phase otherwise consumes their entire week. The 2026 CfP uses 4 days (Tue--Fri for both R1 and R2); a Tue--Sat window is also reasonable as it gives authors the option to use weekend time without forcing it.
- There is one hard deadline above all: **the publisher's deadline**. Understand it and work everything else backward from there.
### Practical Scheduling Tips
-- Make reviews due on **Friday AoE**, start author response on Monday (after Sunday AoE), giving you the weekend to chase late reviewers.
-- Make public-facing deadlines fall during the week. **Friday** was used for the R1 2026 submission deadline and **Tuesday** for R2. Thursday and Friday are good choices (if due Monday, people effectively lose the weekend; mid-to-late week also respects that different countries have different weekend days).
-- Give yourself **slack days**. People will always be late. For instance, make things due on a Friday, but assign the next step (at least internally) to Monday.
+- **Public-facing deadlines (submission, author response) should fall on Tue, Wed, or Thu.** Avoid Friday --- it is a weekend day or holiday in parts of the Middle East and some Asian countries, and it pushes the next step into the weekend for everyone. Avoid Monday --- it forces authors and reviewers to work through the previous weekend. Mid-week deadlines also respect that different countries observe different weekend days.
+- For **internal, reviewer-facing** deadlines, **Friday AoE** is still a useful choice: it gives chairs the weekend to chase late reviewers before the next public-facing step starts on Monday or Tuesday.
+- Give yourself **slack days**. People will always be late. For instance, make an internal review deadline on a Friday, but assign the next step to Tuesday rather than Monday.
- Make CLEAR the **mid-cycle 3-week deadline** for half of reviews being due. Many reviewers miss this.
### Suggested Discussion Period Timeline (Minimum)
@@ -102,7 +129,12 @@ Note: you can re-allocate Major Revision papers to past reviewers concurrently w
### Using TPMS
-[TPMS](https://torontopapermatching.org/webapp/profileBrowser/about_us/) is very important. Get all RC members to upload or update their PDFs inside TPMS as soon as they accept their invites, so everything is ready when the submission deadline comes. Use the TPMS report to see who is missing papers or accounts.
+The [Toronto Paper Matching System (TPMS)](https://torontopapermatching.org/) is very important. It is run out of the University of Toronto by Laurent Charlin and Richard Zemel and is partly funded by the conferences that use it (see the [TPMS about page](https://torontopapermatching.org/webapp/profileBrowser/about_us/)).
+
+- **Organise your TPMS instance early.** A conference instance is not created automatically. Contact the TPMS team at [reviewer-paper-matching@cs.toronto.edu](mailto:reviewer-paper-matching@cs.toronto.edu) (the "contact us" link on the [TPMS website](https://torontopapermatching.org/)) to organise a new instance for your OOPSLA. Do this well before RC invitations go out, so RC members can upload their papers as soon as they accept.
+- **Budget for the TPMS fee.** TPMS charges participating conferences a fee. Check with the SPLASH General Chair (GC) early to ensure this fee is included in the conference budget and paid from the conference, not out of pocket by the RC chairs. See also the [SPLASH GC Notes](/Conferences/SPLASH/HowToSPLASH).
+
+Get all RC members to upload or update their PDFs inside TPMS as soon as they accept their invites, so everything is ready when the submission deadline comes. Use the TPMS report to see who is missing papers or accounts.
- Use TPMS rankings **multiplied by 100** so everyone gets scores between 0 and 100.
- Ask reviewers to add rankings **above 100 only** for their personal preferences, so you can distinguish TPMS scores from reviewer preferences.
@@ -120,6 +152,8 @@ The 2024 chairs found TPMS indispensable. In 2025, the experience was more mixed
In 2025, the Reserve Reviewer policy was initiated (see the SIGPLAN blog post). This was a life-saver and has been continued in the [2026 CfP](https://2026.splashcon.org/track/oopsla-2026). Under this policy, at least one senior author (PhD completed 5+ years ago) must register as a reserve reviewer unless exempt. Exemptions apply when: the paper has no senior authors; a senior author is already an RC member; or all senior authors are new to SIGPLAN/SIGSOFT (fewer than 3 major conference publications), chairing a 2025--2027 conference, or have documented exceptional circumstances. Reserve reviewers must upload 5--10 prior papers to TPMS for expertise matching. Future chairs should continue to refine this approach.
+Reserve reviewers must complete the same [Reviewer Policies and Attestations](#reviewer-policies-and-attestations) as full RC members, at registration time.
+
### Expertise and Review Allocation
- Ask reviewers for an expertise check and to prioritise papers where they have strong expertise.
diff --git a/LongTermMentoring.md b/LongTermMentoring.md
index f6e156e0..4d521047 100644
--- a/LongTermMentoring.md
+++ b/LongTermMentoring.md
@@ -37,13 +37,14 @@ Check out our [Twitter](https://twitter.com/SigplanM) for the latest news! You c
## Committee Members
-- **Operations Team**: [Jai Arora](https://jaiarora0011.github.io/), [Carolina Carreira](https://carolinacarreira.github.io/), [Ronak Chauhan](https://in.linkedin.com/in/ronchauhan), [Kiran Gopinathan](https://gopiandcode.uk/), [Jacqueline Mitchell](https://jlmitche23.github.io/), [Reshabh Sharma](https://www.linkedin.com/in/reshabh/)
+- **Operations Team**: [Jai Arora](https://jaiarora0011.github.io/), [Carolina Carreira](https://carolinacarreira.github.io/), [Ronak Chauhan](https://in.linkedin.com/in/ronchauhan), [Kiran Gopinathan](https://gopiandcode.uk/), [Brian Hyeongseok Kim](https://briankim113.github.io/), [Jacqueline Mitchell](https://jlmitche23.github.io/)
- **Rematching Coordinators**: [Houda Boukham](https://www.linkedin.com/in/houda-boukham-821198142/), [Jocelyn Chen](https://www.cs.utexas.edu/~qchen/)
- **Advisory Board**: [Brigitte Pientka](https://www.cs.mcgill.ca/~bpientka/), [Amal Ahmed](https://www.khoury.northeastern.edu/home/amal/), [Sam Westrick](https://www.cs.cmu.edu/~swestric/), [Santosh Nagarakatte](https://people.cs.rutgers.edu/~santosh.nagarakatte/), [Vasco Vasconcelos](https://www.di.fc.ul.pt/~vv/)
- **Chair**: [Stephen Chong](https://people.seas.harvard.edu/~chong/)
- **Previous Chairs**: [Nadia Polikarpova](https://cseweb.ucsd.edu/~npolikarpova/), [Talia Ringer](https://dependenttyp.es/)
- **Previous Advisory Board Members**: [Alexandra Silva](https://alexandrasilva.org/), [David Van Horn](https://www.cs.umd.edu/~dvanhorn/), [Dimitrios Vytiniotis](https://dimitriv.github.io/), [Sebastian Erdweg](https://www.pl.informatik.uni-mainz.de/), [Steve Blackburn](http://users.cecs.anu.edu.au/~steveb/), [Sukyoung Ryu](https://plrg.kaist.ac.kr/ryu)
+- **Previous Team Members** [Reshabh Sharma](https://www.linkedin.com/in/reshabh/), Alexa VanHattum, Jialu Bao, Kimaya Bedarkar, Sabree Blackmon, Shraddha Barke, Umang Mathur, Yanze Li, Yunjeong Lee
## Getting Involved
@@ -73,6 +74,9 @@ Examples of urgent needs for mentoring include but are not limited to
mental health struggles, advisor-advisee conflicts, ongoing job or graduate school applications, and abusive situations at work or in the community.
If any of these apply, and if you are comfortable doing so, please feel free to contact us so that we match you in a timely fashion.
+Please note that SIGPLAN-M is a mentoring program, not a research advising or collaboration program.
+Mentors may be able to offer their perspective on research, graduate school, career development, the programming languages community, and more, but mentees should not expect their SIGPLAN-M mentor to serve as a research advisor, provide a research project, or collaborate on research.
+
## Thank You, Mentors!
We really appreciate all of our mentors for the amazing work they do---and we want the world to know how much we appreciate it!
diff --git a/Resources/Guidelines/ConferenceOrganizers.md b/Resources/Guidelines/ConferenceOrganizers.md
index dd495ca2..313afb65 100644
--- a/Resources/Guidelines/ConferenceOrganizers.md
+++ b/Resources/Guidelines/ConferenceOrganizers.md
@@ -18,4 +18,4 @@ Policies:
- [Republication Policy](/Resources/Policies/Republication)
- [Code of Conduct Policy](/Resources/Policies/CodeOfConduct)
- [Conference Complimentary Registrations Policy](/Resources/Policies/ComplimentaryRegistrations)
-- [Video Recording Policy (DRAFT)](/Resources/Policies/VideoRecording)
+- [Video Recording Policy](/Resources/Policies/VideoRecording)
diff --git a/Resources/Guidelines/ProChair.md b/Resources/Guidelines/ProChair.md
index f6f42f69..e8f3c8ee 100644
--- a/Resources/Guidelines/ProChair.md
+++ b/Resources/Guidelines/ProChair.md
@@ -3,13 +3,14 @@ layout: default
title: "Guidelines for the Program Chair of a SIGPLAN Event"
---
-
+These guidelines are primarily intended for Program Chairs of SIGPLAN-sponsored conferences.
+For organizers of workshops and similar events, see [this page](/Resources/Guidelines/Workshops).
-[N.b.: SIGPLAN rules are highlighted like
-this to distinguish them from general recommendations and
-discussion.]
+This document uses "Program Committee (PC)" and "Program Chair (PCC)"
+as generic terms. For PACMPL conferences, "Program Committee"
+corresponds to "Review Committee," and the current Program Chair
+normally serves as an Associate Editor, as described in the
+[PACMPL procedures](https://sigplan.org/PACMPL/pacmpl_procedures.pdf).
Executive Summary
-----------------
@@ -24,67 +25,26 @@ skim the rest of this page and the following others:
- SIGPLAN's [diversity policy](/Resources/Policies/Diversity)
- SIGPLAN's [republication policy](/Resources/Policies/Republication)
- SIGPLAN's [code of conduct policy](/Resources/Policies/CodeOfConduct/)
-- SIGACCESS's [Guide to Creating a Conference Accessibility FAQ Page](http://www.sigaccess.org/welcome-to-sigaccess/resources/creating-a-conference-accessibility-faq-page/)
+
+Most importantly:
+
- For a SIGPLAN-sponsored event, seek approval for the Program Committee
from the SIGPLAN Vice-Chair, *before* sending invitations
- Consult with the conference Steering Committee before diverging from any
existing conventions
-- Make sure the Call for Papers makes potential authors aware of SIGPLAN's
- [Copyright policies](https://authors.acm.org/main.html).
-- Some special considerations for organizers of workshops and similar events
- can be found on [this page](/Resources/Guidelines/Workshops).
+- Make sure the Call for Papers makes potential authors aware of ACM's
+ [policy on authorship](https://www.acm.org/publications/policies/new-acm-policy-on-authorship).
_Please help us keep this document (and the rest of this site) up to date:_ If you notice any errors, duplications, inconsistencies, etc., please inform the [SIGPLAN vice chair](mailto:vc_sigplan@acm.org).
-Submission and Reviewing Policies
----------------------------------
-
-
-
-The Program Chair (PCC) may not submit papers to the conference; SIGPLAN's
-Executive Committee recommends that the General Chair also not be
-allowed to submit papers. If Program Committee members are allowed to
-submit papers, either their papers should be held to a higher standard
-or other EC-approved measures should be taken, to avoid the appearance
-of impropriety.
-
-Conferences that use full double blind reviewing and have program committees with at least fifty members need not hold PC papers to a higher standard, as the EC has judged that these are sufficient conditions to avoid the appearance of impropriety. Here full double blind means submissions are anonymous, references to prior work are in the third person, authors' identities are not revealed until a paper is conditionally or fully accepted, and author identities for rejected papers (that were not conditionally accepted) are never revealed.
-
-The PC Chair should make all program committee members and reviewers aware
-of SIGPLAN's policies on
-[reviewing of conference paper submissions](/Resources/Policies/Review) and
-on [plagiarism](http://www.acm.org/publications/policies/plagiarism_policy).
-
-The conference steering committee should be consulted for any changes to the
-accepted way of organizing and running the conference.
-
-You, the Program Chair, in consultation with the General Chair, should
-decide on general policies relating to the program committee, such as:
-
-- Will you have a physical PC meeting? If so, when and where will it be
- held? If not, will the PC discussion be a "synchronous" teleconference or
- an extended discussion over email or moderated by some conference
- management platform? (Whichever you choose, SIGPLAN expects all PC
- members to participate fully in the PC meeting, except in unusual
- circumstances.)
-- Who pays for the travel expenses of the PC members?
-- Who pays for the conference registration of the PC members? Typically,
- the PC member is responsible for all of his/her expenses, including
- registration. If a decision is made to provide funding for some/all of the
- members, these expenses must of course be included in the budget.
-
-The previous year's Program Chair for the same conference is a good
-resource.
-
Program Committee Selection
---------------------------
-In consultation with the General Chair,
+In consultation with the General Chair (and the rest of the Steering Committee),
develop a list of potential Program Committee members. In formulating this
list, be mindful of [SIGPLAN's diversity
policy](/Resources/Policies/Diversity). Also, some people will decline the
-invitation, so your list should includes sufficient alternates. The list
+invitation, so your list should include sufficient alternates. The list
should be finalized at least one year prior to the meeting.
Download the [PC proposal
@@ -93,415 +53,430 @@ template and enter the requested information for your proposed PC members
and alternates. Send the completed spreadsheet to the SIGPLAN Vice Chair
([vc\_sigplan@acm.org](mailto:vc_sigplan@acm.org)) for comments and approval
by the SIGPLAN Executive Committee. The approval process normally takes
-less than two weeks. The same approval process applies to all other
-reviewing committees for conferences such as ERC and EPC.
-
-
+less than two weeks. If the conference has other reviewing committees
+(for example, an External Review Committee),
+the same approval process applies.
-At the same time, make plans for the Program Committee meeting, so that
+At the same time, make plans for the review-discussion and decision process so that
these can be communicated to potential PC members when you invite them:
-choose the location (if physical) and finalize the date(s).
+finalize key dates for online discussion periods and any virtual or in-person meetings.
After SIGPLAN approval is confirmed, invite the people on the list to serve.
Explain what is expected of them and any relevant
-[policy decisions](/Resources/Policies/Review), and give them the date(s) for
-the PC meeting. If more people than expected decline and you run out of
+[policy decisions](/Resources/Policies/Review), and give them relevant dates.
+If more people than expected decline and you run out of
alternates, send the SIGPLAN Vice Chair another set of candidates for
approval.
-Recommendations:
+Recommendations:
-- The PCC should strive to avoid the appearance of favoring current and former students, postdocs, colleagues, or collaborators for membership on the PC or ERC.
-- The size of the PC should be such that, given the expected number of submissions, will yield a reasonable reviewing load per PC member. Exceeding 25 papers per PC members is strongly discouraged.
-- If there is an ERC, the same diversity criteria listed above should apply
+- The PCC should strive to avoid the appearance of favoring current and former students, postdocs, colleagues, or collaborators for membership on the PC.
+- The PC should be large enough to keep the expected reviewing load reasonable. Assigning more than 15 papers to a PC member is discouraged.
+- If there are other reviewing committees, the same diversity criteria listed above should apply
to them, scaled to the size of each committee.
-
-
-- PC members should generally not serve on the PC more often than every four years. Exceptions may be made to enable a small overlap (<10%) from year to year to provide continuity. It is advisable that no one should serve on the PC for more than two years in a row.
-- The PCC of year X+1 can be invited to serve on the PC (with a lighter reviewing load) for year X as soon as he or she is selected.
-- The PCC should strive to avoid selecting PC members that collaborate regularly with each other or with the PCC, or PC members from the same institution in the exact same area.
-- For conferences, all PC members should have PhDs (or other appropriate qualifications) by the submission deadline of the conference. For affiliated workshops, the PC can include PhD students in their final year, as long as the total number does not exceed 10% (rounded up) the PC.
+- PC members should generally not serve on the PC for the same conference more often than once every three years. A small overlap of less than 15% from one year to the next may be used to provide continuity, but no one should ordinarily serve for more than two consecutive years.
+- The PCC of year X+1 can be invited to serve on the PC (possibly with a lighter reviewing load) for year X as soon as they are selected.
+- The PCC should avoid selecting a committee that is overly concentrated
+ among frequent collaborators, close colleagues, or researchers from
+ the same institution or research group. Applicable conflict-of-interest
+ rules should be followed when determining institutional or
+ organizational conflicts.
+- PC members should have appropriate research experience and qualifications for evaluating submissions in the conference's area. For affiliated workshops, suitably qualified senior PhD students may serve where appropriate.
+PC Member Responsibilities
+--------------------------
+When inviting PC members, clearly communicate the expected reviewing
+load, deadlines, discussion responsibilities, and applicable policies.
+A person who cannot make that commitment should decline the invitation
+or promptly inform the PCC if circumstances change.
+
+PC members should personally read their assigned submissions, provide
+constructive and sufficiently detailed reviews, declare their expertise
+accurately, read the other reviews and any author response, and
+participate actively in discussion and decision making.
+
+The PCC should monitor timely completion, review quality, participation
+in discussion, and compliance with SIGPLAN's
+[Conference Submission Review Policy](/Resources/Policies/Review/).
+Questions about related publications, conflicts, reviewer conduct, or
+the integrity of the review process should be referred to the PCC.
Call for Papers
---------------
Develop a call for papers.
Note that you can produce a preliminary call without listing the
-PC members. Make sure to put the call on the web site for the
-conference (established by the General Chair). The web page
-should refer prospective authors to SIGPLAN's
-[Republication Policy](/Resources/Policies/Republication)
-and to ACM's
-[Policy and Procedures on Plagiarism](http://www.acm.org/publications/policies/plagiarism_policy).
-Once the conference web page is in place, establish a link to the page
+PC members. Make sure to put the call on the website for the
+conference (established by the General Chair). The web page should refer
+prospective authors to SIGPLAN's
+[Republication Policy](/Resources/Policies/Republication),
+[Conference Submission Review Policy](/Resources/Policies/Review/),
+ACM's
+[Policy on Authorship](https://www.acm.org/publications/policies/new-acm-policy-on-authorship),
+and ACM's
+[Publications Policies](https://www.acm.org/publications/policies).
+Once the conference web page is in place, establish a link to it
from the SIGPLAN conference page by contacting the SIGPLAN
[Information Director](mailto:infodir_sigplan@acm.org?subject=Conference%20Information).
-If the proceedings will be published by ACM, declare explicitly in the call for
-papers that authors of accepted submissions will be required to choose one of
-the following options: Author retains copyright of the work and grants ACM a
-non-exclusive permission-to-publish license (and, optionally, licenses the work
-with a [Creative Commons license](https://creativecommons.org)); Author retains
-copyright of the work and grants ACM an exclusive permssion-to-publish license;
-Author transfers copyright of the work to ACM. For more information, please see
-[ACM Copyright
-Policy](http://www.acm.org/publications/policies/copyright-policy) and [ACM
-Author Rights](http://authors.acm.org/main.html).
-
-Proceedings published by ACM as an issue of PACMPL are Gold Open Access, and
-the PACMPL editorial board recommends the first option (author retains
-copyright of the work, licenses the work with a [Creative Commons
-license](https://creativecommons.org), and grants
-ACM a non-exclusive permission-to-publish license).
-The PACM Steering Committee also requires conferences to collect statistics
-about the review process---see [here](https://www.acm.org/publications/pacm/title-assessment) for details.
-
-If presentations are to be recorded, mention that presenters must sign a
-permission form in order for the video to be released online.
-
-Mention that publication of auxiliary material is encouraged, and note the
-associated copyright policy (see 'Auxiliary material', below).
+For proceedings published by ACM, the call for papers should
+explain ACM's open-access publication model and refer authors to ACM's
+current
+[Open Access information](https://authors.acm.org/open-access),
+[Publication Rights and Licensing Policy](https://www.acm.org/publications/policies/publication-rights-and-licensing-policy),
+and
+[Author Rights and Responsibilities](https://authors.acm.org/author-resources/author-rights).
+The call should make clear that publication charges may apply unless the
+corresponding author is covered by an ACM Open institutional agreement or an applicable
+waiver or discount. Because the rates and arrangements may change, link
+to ACM's current information rather than stating specific charges.
+
+For proceedings published as an issue of a *Proceedings of the ACM*
+journal, consult the journal's Editor-in-Chief regarding any additional
+journal-specific requirements, including the collection of
+review-process statistics required by the PACM Steering Committee. See
+[PACM Title Assessment and EiC-Provided Statistics](https://www.acm.org/publications/pacm/title-assessment)
+for details.
+
+If presentations are to be recorded or streamed, inform presenters of
+the applicable consent or release requirements.
+
+Explain whether authors may submit supplementary material for reviewers
+to consult (see the [Review policy](/Resources/Policies/Review)),
+whether reviewers are expected or merely permitted to consider it, and
+any applicable anonymity requirements. Such material may later be
+published alongside the accepted paper; see "Published Supplementary
+Material" below. If the conference has a separate
+artifact-evaluation process, the call or conference web page should
+clearly distinguish that process from the submission of supplementary
+material with the paper.
The conference web page should include information about the various
-benefits offered by the [SIGPLAN Professional Activities
-Committee](/PAC) to SIGPLAN members attending SIGPLAN-sponsored
-conferences. These benefits include travel and lodging assistance for
-student authors and assistance for members who need a companion
-care-provider in order to attend.
-
-Author Response
----------------
-
-Many SIGPLAN conferences have included author response mechanisms as part of
-the paper review process, and the general feedback concerning author
-response has been positive (see
-[Experiences with Author Response at PLDI and ICFP 2004](http://portalparts.acm.org/1060000/1052883/fm/frontmatter.pdf),
-Kathleen Fisher and Craig Chambers, *SIGPLAN Notices*, Dec. 2004).
-Program Chairs and Steering Committees are encouraged to consider
-allowing author response or rebuttals as part of the paper review
-process.
+benefits offered by the
+[SIGPLAN Professional Activities Committee](/PAC)
+to participants in SIGPLAN-sponsored conferences. These include travel
+support for eligible students and other participants, child-care travel
+support, and companion travel grants.
Submission and Review
---------------------
-Set up the paper submission web site. Many services are available for this
-purpose; most SIGPLAN conferences these days use
-[HotCRP](https://hotcrp.com) (which is free for us because ACM has a bulk
-deal). If you choose a different one, look for support for the [ABCD rating
-scale][Nier00], author feedback, and double-blind reviewing.
-
-[Nier00]: http://www.iam.unibe.ch/~oscar/Champion/champion.pdf "Oscar Nierstrasz, _Identify the Champion_"
-
-Some advice: Many systems make it easy to include ratings on a
-large number of different scales, but please don't do this. Most
-PC chairs use only two scales: an overall rating and an
-expertise rating. It also works best to have just two or three text
-fields: one for a summary of the paper (this is optional), one for
-comments for both the PC and the authors, and one for comments to
-be seen by the PC only. The ABCD scale avoids ranking papers by
-average: instead you can group papers by highest and lowest rating
-(not a linear scale, since AD neither precedes nor follows BC).
-For more details see:
-[Conferences with improved management and style](http://portalparts.acm.org/1140000/1137933/fm/frontmatter.pdf),
-Philip Wadler, _SIGPLAN Notices_, Feb. 2006.
-
-
-
-Before papers are received, develop an evaluation procedure. After the
-submission deadline, send submitted papers and a description of the
-evaluation procedure to the PC members.
-
-The PCC should identify another PC member (a “COI-PCC”) to handle papers for
-which the Chair is in conflict.
-
-
-PC Meeting
-----------
-
-Some SIGPLAN conferences have in-person PC meetings; others have moved to
-virtual meetings (to reduce carbon footprint, wear and tear on PC members,
-or both).
-
-For both kinds of meetings, PC members should be allowed to participate in
-the discussion (both online and in-person) of papers that they didn't
-review, and with which they have no conflicts. The PCC should strive to
-ensure, prior to the PC meeting, that every competitive paper has at least
-two PC reviews at least one, and preferably two expert reviews
-
-During the online discussion period (whether or not followed by an in-person
-meeting), the PC should be allowed to see all papers with which they have no
-conflicts, and participate in the discussion. Online discussion must be
-actively facilitated by the PCC, and (if applicable) paper guardians.
-
-Before the PC meeting, decide on any policies that should be in effect, such as:
-- What defines a conflict of interest?
-- What happens if a PC member has a conflict of interest?
-- What are the rules of confidentiality?
-- Do you want to have a best paper award?
-
-### In-Person PC Meetings
-
-A physical PC meeting should be preceded by an extensive online discussion
-period. The online discussion period should be a minimum of one week, but
-two (or more) is strongly preferred.
-
-The designated COI-PCC (see COI policies) should handle papers the PCC is
-conflicted with during the meeting.
-
-At the end of the PC meeting, the PCC may want to take a bit of time to plan the
-sessions and the session chairs.
-
-It is strongly recommended that the PCC have an assistant during
-the physical PC meeting, to take on certain administrative and logistical
-tasks during the meeting and allow the PCC to concentrate on
-leading the discussions of papers. Typical duties of the assistant would be
-to keep track of the disposition of papers for the PC, interface with the
-on-line review system, and record any relevant information about a
-particular paper (e.g., paper Y paper is being shepherded by committee
-member X, committee member X agrees to revise their on-line review,
-etc.). Past PCCs have used graduate students or post-docs as
-assistants, with good results.
-
-Any PC meeting expenses that are to be reimbursed by the conference should
-be put in the conference budget. Send receipts to the ACM Representative to
-SIGPLAN for reimbursement (the [SIGPLAN Vice
-Chair](mailto:vc_sigplan@acm.org) can tell you who this is at the moment).
-
-Additional suggestions:
-- Experience has shown that a two day PC meeting provides adequate time for deliberation while avoiding PC burnout.
-- The GC may play the role of "COI-PCC".
-- The PCC is encouraged to have one or two dedicated assistants to deal with timekeeping and bookkeeping in order to allow the PCC to focus entirely on the discussion rather than logistical concerns. A senior non-PC member such as the GC or next PCC can fulfill this role.
-- Instead of considering the papers in order from highest-ranked to lowest, consider the papers in a quasi-random order (see article by Kathleen Fisher in SIGPLAN Notices, 46(4):17, April 2011).
-- If the most positive reviewer for a paper is external, the chair may wish to ensure that the paper is discussed on day one of the PC meeting and the outcome summarized by the PCC so that the external reviewer can provide additional feedback prior to a final decision.
-- The PCC is encouraged to use a multi-round discussion process for papers where an initial consensus is not apparent.
-- The PCC can distinguish between contentious and marginal papers and table all marginal papers until the end of the meeting to allow them to be systematically considered in the context of the emergent acceptance standard.
-
-After the PC Meeting
---------------------
+Set up the submission and review site sufficiently early to test the
+submission form, review form, conflict declarations, anonymity settings,
+reviewer assignments, author response, discussion, and decision
+notifications. Most SIGPLAN conferences use
+[HotCRP](https://hotcrp.com/), but the PCC may use another system that
+supports the conference's reviewing model and applicable SIGPLAN
+policies.
+
+Before submissions open, determine and publish the main elements of the
+review process, including:
+
+* the reviewing model and anonymity requirements;
+* the evaluation criteria;
+* the treatment of supplementary material;
+* whether and when author response will be permitted;
+* whether papers may be conditionally accepted or invited for revision;
+* the applicable conflict-of-interest rules; and
+* any rules concerning the use of external reviewers.
+
+The review form should be kept reasonably simple, reflect the published
+evaluation criteria, and explain its questions and rating scales clearly.
+The PCC should avoid treating numerical scores or averages as substitutes
+for substantive judgment and discussion.
+
+### Managing the Review Process
+
+Keeping the review form reasonably stable across editions can help
+authors and reviewers calibrate and interpret its ratings.
+One possible model is Nierstrasz's Identify the Champion scoring process,
+which has stood the test of time. The essence of the process is to ask
+each reviewer whether they would champion the paper during discussion,
+without prescribing a specific scale. One example review form in this
+spirit has (at least) the following fields:
+- Paper score:
+ - A: Good paper. I will champion it during the discussion.
+ - B: OK paper, but I will not champion it.
+ - C: Weak paper, though I will not fight strongly against it.
+ - D: Serious problems. I will argue to reject this paper.
+
+ Reviewers sometimes gravitate toward middle scores; the PCC should
+ remind the PC that the scale is meant to be used across its full
+ range, and that a paper's score should reflect the reviewer's honest
+ willingness (or reluctance) to champion it.
+- Reviewer expertise:
+ - X: I am an expert in the subject area of this paper.
+ - Y: I am knowledgeable in the area, though not an expert.
+ - Z: I am not an expert. My evaluation is that of an informed outsider.
+- Paper summary (reviewer’s synopsis provides a useful sanity check)
+- Points in favor (encourage positive reviewing)
+- Points against (be clear about principal objections)
+- Detailed comments for authors (body of review)
-
-
-
-Send acceptance and rejection letters as soon as possible after the PC
-meeting. Authors using LaTeX should be directed to the [template
-developed by SIGPLAN](/Resources/Author). This template was designed to
-allow more material in a paper while remaining easy on the eyes
-(typically, a paper that requires 12 pages with the standard ACM
-format requires 11 with the SIGPLAN format, and most readers find the
-SIGPLAN style easier to read).
+Additionally:
+- The PCC should become familiar with the conference management system
+ and its facilities well before submissions open.
+- A two-phase reviewing process may be used to reduce reviewing load,
+ provided that the early phase gives each submission an adequate expert
+ assessment and follows the review process described to authors.
+- PC members should be strongly encouraged to submit reviews as they are completed;
+ this makes it easier for the PCC to monitor progress and identify problems early.
+- The PCC should allow all reviewers to see the decisions for the papers
+ they reviewed before those decisions are communicated to authors.
+
+The PCC should ensure that each submission receives reviews of sufficient
+quality and breadth. In particular, the PCC should identify papers for
+which the assigned reviewers lack sufficient expertise, reviews are
+incomplete or inadequate, or reviewers substantially disagree, and seek
+additional reviews where appropriate.
+External reviewers should be selected and managed in accordance with SIGPLAN's
+[Conference Submission Review Policy](/Resources/Policies/Review/).
+
+### Associate Chairs and Guardians
+
+Some large conferences divide the Program Committee into groups, each
+led by an Associate Chair who chairs that group much as the PCC chairs
+the PC as a whole. Associate Chairs are sometimes called "Area Chairs"
+when the groups are organized by topic of expertise.
+
+The PCC may also assign a PC member as guardian for a submission. A
+guardian is responsible for helping ensure that the paper is assessed
+carefully and fairly. Depending on the conference's review process, the
+guardian's role may include:
+
+* identifying gaps in reviewer expertise;
+* checking that the reviews are sufficiently complete and constructive;
+* facilitating discussion among the reviewers; and
+* drafting or coordinating the author-visible decision rationale.
+
+The guardian does not replace the assigned reviewers and does not make
+the acceptance decision. The PCC retains responsibility for ensuring
+that the review process is fair and that the final decision is properly
+supported.
+
+### Author Response
+
+Configure and announce the author-response process in accordance with
+SIGPLAN's
+[Conference Submission Review Policy](/Resources/Policies/Review/).
+The PCC should make every effort to complete the initial reviews before
+the response period, ensure that reviewers read and consider the
+responses, and incorporate them into subsequent discussion and
+decisions.
+
+### Discussion and Decisions
+
+The PCC should organize an active discussion period after the initial
+reviews and any author response. Discussion may take place
+asynchronously in the conference management system, in synchronous
+online meetings, or through a combination of these.
+
+The PCC, and any designated discussion leads, should ensure that
+reviewers read the other reviews and the author response, discuss
+significant disagreements and outstanding questions, and assess papers
+according to the published criteria. Concerns raised late in the process
+should be communicated to the other reviewers and considered fairly.
+
+The PCC should make acceptance decisions based on the reviews,
+discussion, author response, and published evaluation criteria.
+Numerical scores and votes may inform a decision but should not determine
+it mechanically. Before decisions are communicated to authors, each
+decision should be supported by a clear author-visible rationale that
+accurately reflects the main points of the discussion.
+
+### Conflicts
+
+The PCC should designate another qualified committee member, commonly
+called the COI-PCC, to manage submissions for which the PCC has a
+conflict of interest. The COI-PCC should have the authority and access
+needed to manage reviewing, discussion, and decisions for those
+submissions independently of the PCC.
+
+### Shepherding
+
+A conference may use shepherding or another conditional-acceptance
+process when a paper can be accepted subject to clearly identified
+revisions. The PCC should appoint a qualified reviewer or committee
+member to oversee the revision. In consultation with the other
+reviewers, the shepherd should provide the authors with a concise list
+that clearly distinguishes changes required for acceptance from
+optional suggestions.
+
+The shepherd should assess whether the revised paper adequately
+addresses the required changes and report this assessment to the PCC.
+The shepherd should not impose substantial new requirements that were
+not part of the acceptance decision without consulting the PCC and the
+other reviewers. The PCC retains responsibility for the final
+acceptance decision.
Managing the Proceedings
------------------------
-The proceedings service by Conference Publishing Consulting (ConfPub)
-can be initiated once you decide
-that you want formal proceedings. Please contact the
-[ACM Publications Coordinator](mailto:griscti@acm.org), Adrienne Griscti,
-to begin the process. ACM will provide ConfPub with pertinent
-conference information. ConfPub will forward you a schedule and
-instructions on how to proceed.
-
-
-Draft a "Letter from the Program Chair," which should
-include a description of the paper selection process (number of
-papers submitted and accepted, etc.). Forward the letter to
-ConfPub along with any other front matter (perhaps a "Letter from the
-Conference Chair," a List of Reviewers, etc.) for inclusion
-in the proceedings. ConfPub will format all front matter; their
-schedule will include a deadline for front matter submission. They
-will also compile the table of contents/author index, using the
-schedule of talks/advanced program that you provide to determine
-paper order.
-
-Accepted authors will submit their papers directly to the ConfPub
-web site. Once ConfPub have collected all of the papers/copyright
-forms and front matter, compiled the table of contents/author index
-and paginated the volume, they will provide camera-ready copy for
-your review. The proceedings will not be printed until this
-has been approved. It is a good idea to send
-the table of contents to the contributing authors to confirm the
-spelling of their names and affiliations. You then will be asked to
-provide conference shipping information and the number of proceedings
-needed for the conference.
-
-At the Conference
------------------
-
-At the meeting, give a short summary of the paper evaluation
-process. Include the number of submissions, in what topical areas,
-and the number of accepted papers. You might want to compare the
-number of submissions and acceptances with the previous year (these
-numbers should also be in the proceedings and the final report).
-You should also explain the review process, e.g, how many PC
-members reviewed each paper and the organization of the PC meeting.
-You might want to talk about the geographic distribution of
-submissions and any unusual trends. The summary should take about
-15 minutes.
-
-After the Conference
---------------------
-
-Help the Conference Chair prepare the post-event report for SIGPLAN EC.
-
-
-As former Program Chair, you may be invited to serve on the
-conference's Steering Committee. For the formal
-rules for your particular conference's steering committee, consult the relevant SIGPLAN
-conference web page. Links to these pages can be be found
-[here](/Conferences).
-
-The program chairs of the major SIGPLAN conferences (POPL, PLDI,
-OOPSLA, and ICFP) are automatically on the selection committee for
-the following year's
-[SIGPLAN Programming Languages Achievement Award](/Awards/Achievement).
-
-
-Artifacts
----------
-
-ACM treats artifacts as "first-class" objects in the digital library,
-that is, each artifact has its own DOI, meta data, and landing page.
-AEC chairs should send a list of papers with accepted artifacts
-and their badge assignment to ConfPub.
-They will print the badges on the papers at a uniform position.
-ConfPub also collects the meta data from the authors and provides
-the data to ACM.
-
-
-Auxiliary Material
-------------------
-
-The ACM Digital Library and ConfPub, who prepare many
-ACM proceedings, are both set up to accept auxiliary material. The
-SIGPLAN EC encourages SIGPLAN-sponsored conferences to accept such
-material as part of the publication process. (Some conferences also
-accept auxiliary material with submissions; this is an independent
-issue.)
-
-Auxiliary material may include
-
-- a technical report with additional details
-- source code for software
-- proof scripts for automated theorem provers
-- test data
-
-or anything else relevant. It is SIGPLAN policy to encourage authors to
-publish adequate auxiliary material to enable others to reproduce their
-work. Authors retain copyright of their auxiliary material, while copyright
-of the paper can be either assigned to ACM or held by the authors. Referees
-may examine auxiliary material, if it accompanies the submission, but this
-should not be considered part of the review process. For an example of
-auxiliary material in the Digital Library, see
-[here](https://doi.org/10.1145/1462173.1462178) and click on
-"Supplemental Material".
-
-
-
-Shepherding
------------
-
-
-Papers may be accepted conditionally, in which case, such papers require shepherds. The role of the shepherd is to compile a list of required changes to the paper that are required for the paper to be accepted, in consultation with all reviewers, and subject to the approval of the PCC. Authors are expected to modify their papers appropriately; in the event that the reviewers and the shepherds do not come to an agreement that a paper has been revised satisfactorily, the PCC should have the ultimate decision as to whether the paper will be accepted.
-
-
-Additionally, the shepherds can ensure that outstanding work is not rejected on the basis of a problem that can easily be fixed with minor modifications to the paper.
-
+Most SIGPLAN-sponsored conferences use
+[Conference Publishing Consulting](https://www.confpub.com/)
+to manage the proceedings-production process. Contact ConfPub early and
+agree on the production schedule, author instructions, required
+metadata, and division of responsibilities. For proceedings published
+as an issue of a Proceedings of the ACM journal, also coordinate with
+the journal's Editor-in-Chief and follow any journal-specific
+requirements.
+
+After acceptance decisions have been finalized, provide ConfPub with
+complete and accurate metadata for all accepted contributions,
+including titles, author names and affiliations, contact information,
+submission identifiers, and contribution types. ConfPub will normally
+use this information to initiate ACM's publication-rights process and
+the production workflow.
+
+Authors must complete ACM's publication-rights process and provide their
+final source material in accordance with the instructions supplied by
+ConfPub. ACM currently uses
+[The ACM Publishing System (TAPS)](https://authors.acm.org/proceedings/production-information/taps-for-conference-organizers)
+to produce and validate the PDF and HTML versions of published
+articles. Depending on the production workflow, authors or ConfPub may
+submit and correct the source files in TAPS. ConfPub coordinates the
+process, communicates instructions and deadlines to authors, monitors
+progress, and helps resolve production problems.
+
+The PCC should provide authors with clear deadlines and instructions
+for preparing their final versions, including the applicable ACM
+template, page limits, citation style, accessibility requirements,
+supplementary material, and treatment of third-party
+material. Allow sufficient time for authors to address formatting,
+metadata, rights, and TAPS validation problems.
+
+Before the proceedings are finalized, the PCC or a designated
+proceedings chair should verify that all accepted contributions are
+included and that their titles, author lists, ordering, and other
+metadata are correct. Also check the front matter, table of contents,
+and any required review-process statistics or journal-specific
+information. Coordinate corrections with ConfPub rather than making
+changes directly in ACM's production systems.
+
+### Artifacts
+
+ACM supports the evaluation and publication of research artifacts and
+displays applicable artifact badges with the associated papers in the
+ACM Digital Library.
+
+The Artifact Evaluation Committee chairs should provide ConfPub with the
+final list of papers whose artifacts have received badges and the badge
+assignments. ConfPub coordinates the inclusion of the badges in the
+published papers and the collection of any required artifact metadata.
+
+The conference should give authors clear instructions concerning artifact
+submission, evaluation, archival availability, licensing, and any
+requirements for persistent identifiers or external repositories.
+
+### Published Supplementary Material
+
+ACM proceedings may include supplementary material associated with a
+published paper, such as:
+
+- technical reports containing additional details;
+- source code or software;
+- proof scripts;
+- data sets; and
+- other material relevant to understanding, reproducing, or building on
+ the work.
+
+SIGPLAN encourages authors to make appropriate supplementary material
+available when it supports reproducibility and future research. The
+conference should provide authors with clear instructions for submitting
+such material through the applicable proceedings-production process.
+
+This published, post-acceptance supplementary material may be distinct
+from material that authors may submit alongside a paper at submission time
+for reviewers to consult, which has its own anonymity and consideration
+rules; see the [Review policy](/Resources/Policies/Review) for that.
Distinguished Papers
--------------------
-Up to 10% of the accepted papers may be designated for ACM SIGPLAN Distinguished Paper Awards.
-- Nominations may be solicited from the PC and ERC, and will also include the top 10% papers in terms of numeric scores. PC/ERC members should not nominate papers by authors they are conflicted with.
-- PC papers may be nominated.
-- The PC/ERC (excluding the authors of any nominated papers) should vote on this set of nominated papers. Each PC member may cast as many votes as the target number of Distinguished Papers. The usual conflict-of-interest rules will apply (e.g., PC/ERC members cannot vote on papers with which they have a conflict of interest).
-- The PCC and GC should decide which papers will receive the award. While the number of votes received by nominated papers is an important factor, the PCC and GC may exercise their judgment in making their decision.
-PC Member Responsibilities
---------------------------
+Up to 10% of the accepted papers may be selected for ACM SIGPLAN
+Distinguished Paper Awards. The selection process should consider
+relevance, originality, significance, and clarity, and should not rely
+mechanically on numerical review scores.
-PC members must commit to reading all of their assigned papers and writing their own reviews. PC members may also suggest additional reviewers, but they should not subcontract reading or review writing duties to others. The PCC should be consulted before additional reviewers are contacted to avoid conflicts and to ensure topical balance.
+The PCC should establish a fair process for identifying and assessing
+candidate papers. Nominations may be solicited from the PC and any
+other reviewing committees, and the PCC may appoint a suitably qualified
+subset of the committee to assess the candidates. Papers with PC members
+among the authors remain eligible.
-If there is an in-person PC meeting, then PC members must attend the PC meeting in-person. If the meeting is virtual, PC members must participate in the manner described in the invitation to join the PC. Invited members who cannot commit to attending or participating in the meeting in person in the way the PC chair has specified should decline the invitation.
+The usual conflict-of-interest rules apply throughout the process.
+Conflicted committee members must not nominate, assess, discuss, or vote
+on the relevant papers. The PCC and General Chair have final
+responsibility for the selection, unless the conference has an approved
+alternative procedure.
-_Recommendations:_
+At the Conference
+-----------------
-The PCC should consider whether to explicitly allow PC members to share and discuss papers with their own students (subject to the usual confidentiality and COI provisions), and to incorporate information from such discussions into their review. If this is permitted, the PC member should still be responsible for writing the review. When a student is involved in this capacity, the PCC should be informed so that the student receives appropriate credit.
+Coordinate with the General Chair and other organizers on the PCC's
+responsibilities during the conference. These may include introducing
+the technical program, presenting paper or artifact awards, assisting
+session chairs, and handling program changes or problems involving
+presenters.
+
+Provide attendees with a brief summary of the submission and review
+process, either during the conference or in the proceedings or
+conference website. This will typically include the numbers of
+submissions and accepted papers, the reviewing model, the number and
+types of reviews obtained, and any other information useful for
+understanding how the program was selected. Relevant comparisons with
+previous years or aggregate statistics about submissions may also be
+included.
+
+Ensure that session chairs have the information they need and know whom
+to contact if a presenter is absent, a session runs late, or another
+problem arises. Coordinate any changes to the published program with
+the General Chair and web or publicity chairs.
+
+Be familiar with the conference's code-of-conduct and incident-response
+arrangements, and promptly refer any incident to the appropriate
+conference organizer.
-PC members should consult the SIGPLAN Republication Policy. If a related version of the paper appeared in a workshop, PC members should take into account whether its call for papers stated that publication in the workshop is not intended to preclude later publication.
+After the Conference
+--------------------
+Prepare a post-event report for the conference Steering Committee, if
+the conference has one, and otherwise for the
+[SIGPLAN Executive Committee](/ContactUs).
+The report should summarize the submission, review,
+acceptance, and technical-program statistics, note any significant
+issues that arose, and record recommendations for future editions of
+the conference.
-Recommendations for Reviewing Process Management
-------------------------------------------------
+Prepare a brief handover for the next PCC, including the review-process
+timeline, committee organization, relevant statistics, useful
+procedures, and lessons learned.
-Keeping the same reviewing form has benefit for authors and reviewers as they can more easily calibrate and interpret scores if the ratings are well understood. Nierstrasz' Identify the Champion scoring process has stood the test of time. A typical review form in the spirit of this process has (at least) the following fields:
-- Paper score:
- --A: Good paper. I will champion it at the PC meeting.
- --B: OK paper, but I will not champion it.
- --C: Weak paper, though I will not fight strongly against it.
- --D: Serious problems. I will argue to reject this paper.
-- Reviewer expertise:
- --X: I am an expert in the subject area of this paper.
- --Y: I am knowledgeable in the area, though not an expert.
- --Z: I am not an expert. My evaluation is that of an informed outsider.
-- Paper summary (reviewer’s synopsis provides a useful sanity check)
-- Points in favor (encourage positive reviewing)
-- Points against (be clear about principal objections)
-- Detailed comments for authors (body of review)
-
-Additionally:
-- It is useful for the PCC to acquaint themselves ahead of time with the conference management system (currently HotCRP), and the facilities it offers.
-- A two-phase reviewing process can be used, in order to avoid PC overload, by identifying weaker papers earlier.
-- PC members should be strongly encouraged to submit reviews as they are completed; this makes it easier for the PCC to monitor progress and identify problems early.
-- The PCC may wish to identify major reviewer disagreements and papers without sufficient expertise and seek second opinions where necessary to help resolve the disagreements.
-- The PCC should allow all reviewers to see decisions for the papers they have reviewed before decisions are publicly announced.
+Complete any remaining proceedings, award, artifact-evaluation, or
+journal-specific tasks, and ensure that outstanding author or reviewer
+communications have been handled.
+Former PCCs may also be invited to serve on the conference Steering
+Committee or otherwise advise future organizers.
Important Email Addresses
-------------------------
_SIGPLAN Chair_:
[chair\_sigplan@acm.org](mailto:chair_sigplan@acm.org)
+
_SIGPLAN Vice Chair_:
[vc\_sigplan@acm.org](mailto:vc_sigplan@acm.org)
+
_SIGPLAN Information Director_:
[infodir\_sigplan@acm.org](mailto:infodir_sigplan@acm.org?subject=Conference%20Information)
See Also
--------
-- ACM's *[How to Organize a Conference](http://www.acm.org/sigs/volunteer_resources/conference_manual/conference_manual-toc)* manual
-- [ACM's How to Organize a Conference](http://www.acm.org/sigs/volunteer_resources/conference_manual/manual_read_me)
-- SIGPLAN conference style [LaTeX class file](http://www.sigplan.org/sites/default/files/sigplanconf.cls),
- [article template](http://www.sigplan.org/sites/default/files/sigplanconf-template.tex), and
- [user guide](http://www.sigplan.org/sites/default/files/sigplanconf-guide.pdf)
+- ACM's *[SIG Conference Planning Guide](https://www.acm.org/special-interest-groups/volunteer-resources/conference-planning)*
+- ACM's [Primary Article Templates](https://www.acm.org/publications/proceedings-template)
+ and [LaTeX best practices for TAPS](https://www.acm.org/publications/taps/latex-best-practices)
- [Author Information for SIGPLAN Conferences](/Resources/Author)
- [Guidelines for Referees](/Resources/Guidelines/Referees)
-
-Some columns containing useful advice for conference organizers have
-been published in _SIGPLAN Notices_ and elsewhere over the years:
-
-
-
-- [Experiences with Author Response at PLDI and ICFP 2004](http://portalparts.acm.org/1060000/1052883/fm/frontmatter.pdf), Kathleen Fisher and Craig Chambers, (*SIGPLAN Notices*, Dec. 2004)
-- [Conferences with improved management and style](http://portalparts.acm.org/1140000/1137933/fm/frontmatter.pdf), Philip Wadler (*SIGPLAN Notices*, Feb. 2006)
-- [SIGPLAN EC Activities: Vice Chair Report](http://portalparts.acm.org/1150000/1149982/fm/frontmatter.pdf), Kathleen Fisher (*SIGPLAN Notices*, May 2006)
-- [A Report from the POPL 2007 Chairman](http://portalparts.acm.org/1230000/1229493/fm/frontmatter.pdf), Matthias Felleisen (*SIGPLAN Notices*, December 2006)
-- [How to chair a conference](http://portalparts.acm.org/1990000/1988042/fm/frontmatter.pdf), Alex Aiken (*SIGPLAN Notices*, April 2011)
-- [POPL'12 program chair's report: (or, how to run a medium-sized conference)](http://dl.acm.org/citation.cfm?id=2442779), Michael Hicks (*SIGPLAN Notices*, April 2012)
-- [Artifact evaluation for software conferences](http://dl.acm.org/citation.cfm?id=2502518), Shriram Krishnamurthi (*SIGPLAN Notices*, April 2013)
-- [The OOPSLA two-phase review process](http://dl.acm.org/citation.cfm?id=2641648), Cristina V. Lopes (*SIGPLAN Notices*, April 2014)
-- [A Handbook for [ECOOP] PC Chairs](http://www.pps.univ-paris-diderot.fr/~gc/papers/pc-handbook.pdf), Giuseppe Castagna
-- [Refreshing ATC – USENIX ATC 2019 Program Co-Chairs Message](https://www.usenix.org/sites/default/files/atc19_message.pdf), Dan
- Tsafrir and Dahlia Malkhi
diff --git a/Resources/Policies/Diversity.md b/Resources/Policies/Diversity.md
index 47718261..e56d5a3d 100644
--- a/Resources/Policies/Diversity.md
+++ b/Resources/Policies/Diversity.md
@@ -2,54 +2,84 @@
layout: default
title: "SIGPLAN Diversity Policy"
---
-SIGPLAN values diversity in the composition of the program and
-organizing committees for its meetings, recognizing that there is a
-large pool of people qualified to serve on the committees. Each
-year, meeting organizers must choose a subset of these qualified
-people to serve on program committees. People chosen to serve on
-such committees are seen as leaders in the community, and hence we
-must take pains to ensure that they are chosen fairly and represent
-the breadth of the community. Diversity should also be considered
-with respect to the composition of previous program committees to
-ensure fair representation over time.
-
-Factors that organizers should consider when forming program
-committees from the pool of qualified candidates include:
-
-
-
-
-
-1. Coverage of meeting topics
-2. Turnover: each year's committee should be substantially
- distinct from previous years'. Some overlap to promote continuity
- is permissible.
-3. Diversity of institution: there should be no more than
- two people from a given institution.
- (Multiple sites for the same organization count as the same
- "institution". For large PCs, this may be relaxed to "no more than 10%,
- rounded to the nearest integer, from a given institution".)
-4. Type of institution: Industry, Academia, Government Laboratory,
- etc.
-5. Years of experience: committees should be a mix of junior,
- mid-level, and senior members of the community. (Workshop PCs may
- include at most one PhD student in their final year; please include a
- comment detailing their qualifications. Conference PC members should
- all have PhDs, or other appropriate qualifications, by the submission deadline.)
-6. Geographic distribution: members should come from all parts of
- the world active in the given research area.
-7. Gender.
-8. Ethnic background.
-
-In addition, the PC Chair should strive to avoid the appearance of favoring
-current and former students, postdocs, colleagues, or collaborators for
-membership on the PC or ERC.
-
-Meeting organizers are required to submit their organizing and program
-committees to the
+
+SIGPLAN values diversity in the composition of the organizing and
+reviewing committees for its events. There is a broad pool of people
+qualified to serve on these committees, but each year organizers must
+select only a subset of them. Committee membership is a form of
+professional recognition and leadership, so organizers must take care
+to select members fairly and to represent the breadth of the relevant
+community.
+
+Diversity should be considered both within the current committee and
+across successive editions of an event, so that opportunities to serve
+are distributed fairly over time.
+
+This policy applies to Program Committees and other reviewing
+committees, including External Review Committees. The principles should
+also be considered when forming organizing committees. Their
+application may be scaled to the size, purpose, and expertise
+requirements of each committee.
+
+When forming a reviewing committee, organizers should consider:
+
+1. **Coverage of the event's topics.** The committee should collectively
+ have the expertise needed to evaluate submissions across the scope of
+ the event.
+
+2. **Rotation and continuity.** Each year's committee should be
+ substantially distinct from those of previous years, while allowing
+ limited overlap to provide continuity. Members should generally not
+ serve on the same conference's Program Committee more often than once
+ every three years. Ordinarily, overlap from one year to the next
+ should be less than 15%, and no one should serve for more than two
+ consecutive years.
+
+3. **Institutional diversity.** Ordinarily, no more than two members
+ should come from the same institution. For large committees, this
+ limit may instead be interpreted as no more than 10% of the committee.
+ For the purpose of applying this limit and determining institutional
+ conflicts, a large organization with multiple campuses or
+ organizational units may be treated as comprising separate
+ institutions where those units are comparable in size and
+ organizational independence to typical academic institutions.
+
+4. **Type of institution.** The committee should, where relevant,
+ include members from academia, industry, government laboratories,
+ and other research organizations active in the area.
+
+5. **Career stage and experience.** The committee should include an
+ appropriate mix of junior, mid-career, and senior members of the
+ community. Conference Program Committee members should normally hold
+ a PhD or have comparable research qualifications by the submission
+ deadline. For affiliated workshops and similar events, suitably
+ qualified senior PhD students may serve where appropriate.
+
+6. **Geographic distribution.** Members should be drawn from the
+ regions of the world active in the relevant research area.
+
+7. **Diversity of backgrounds.** The committee should reflect diversity
+ in gender and in ethnic, cultural, and other backgrounds relevant to
+ representation in the community.
+
+These considerations should be applied holistically rather than as
+independent quotas. Organizers should be prepared to explain
+significant departures from them, particularly where a committee is
+large enough that broader representation could reasonably have been
+achieved.
+
+The Program Chair should also avoid selecting a committee that appears
+to favor current or former students, postdoctoral researchers,
+colleagues, or collaborators. The committee should not be overly
+concentrated among frequent collaborators, close colleagues, or
+members of the same institution or research group.
+
+Proposed reviewing committees for SIGPLAN-sponsored conferences and
+SIGPLAN-approved workshops must be submitted to the
[SIGPLAN Vice Chair](mailto:vc_sigplan@acm.org?subject=Program%20Committee%20Approval)
-for approval by the Executive Committee, in the form of a
+for approval by the SIGPLAN Executive Committee, using the
[PC proposal spreadsheet](/Resources/Guidelines/sigplan-pc-proposal-template.xlsx).
+
+Further guidance on committee selection, approval, invitations, and
+committee management is available in the
+[Guidelines for Program Chairs](/Resources/Guidelines/ProChair/).
diff --git a/Resources/Policies/Review.md b/Resources/Policies/Review.md
index 244e7f79..2b58ce4e 100644
--- a/Resources/Policies/Review.md
+++ b/Resources/Policies/Review.md
@@ -1,38 +1,28 @@
---
layout: default
-title: "Policies Regarding Review of Conference Papers"
+title: "Conference Submission Review Policy"
---
-
-
-
**Confidentiality**
-
-
-Papers under consideration for publication should not be distributed
-or disclosed to any individual, except with the explicit authorization
-of the program chair for purpose of review. Accepted papers are
-considered unpublished until the day of the conference, and should not
-be discussed outside the program committee without explicit permission
-from the authors. All reviewers must be made aware that submissions
-are unpublished works, and in no case should they duplicate them, pass
-them on to other people, or discuss them with people other than the
-members of the program committee. The program chair should keep a
-record of the external reviewers used to review submissions.
+Submissions must be treated as confidential and must not be distributed
+or disclosed except to people explicitly authorized by the PCC for the
+purpose of review. Reviewers must not copy submissions, pass them to
+other people, or discuss them with anyone who is not authorized to
+participate in the review process. Confidentiality continues until the
+work has been publicly released by the authors or publisher. The PCC
+must keep a record of all external reviewers.
Reviewers grant paper authors permission to use the reviews however
they wish. Reviews can also be analyzed under the auspices of SIGPLAN
for research purposes such as evaluation of bias.
-The title, authors, acceptance status, and other metadata (including
-discussion summaries, if they exist) can be shared under the
-discretion of the program chair, when there is an expectation of
-legitimate benefit for other SIGPLAN processes (such as a related
-review committee, or an artifact evaluation process).
+Submission metadata, acceptance status, and decision summaries may be
+shared with another authorized SIGPLAN process, such as a related review
+committee or artifact-evaluation committee, when necessary for that
+process. Only the information needed for the stated purpose should be
+shared, and all recipients must observe the applicable confidentiality
+requirements.
**Conflicts**
@@ -42,10 +32,7 @@ A conflict of interest is defined as a situation in which the reviewer
can be viewed as being able to benefit personally from the outcome of
a review, or in which the reviewer is not able to remain objective for
personal reasons. If a conflict of interest exists, then the reviewer
-should decline to review a paper. During the program committee
-meeting, any committee member who has a conflict of interest regarding
-a paper may be asked to leave the room for the duration of the
-discussion.
+should decline to review a paper.
Among the situations in which conflicts are typically considered to
exist are between an advisor and an advisee (Ph.D. and post-doc;
@@ -55,9 +42,22 @@ companies or different locations of research institutes are considered
to be the same institution; for two years after leaving an
institution), between people with financial conflicts of interest, and
between friends or relatives. If a reviewer feels unable to render an
-objective judgement for any reason, he or she should notify the
+objective judgment for any reason, they should notify the
program chair.
+If the PCC has a conflict of interest with a submission, the PCC must
+not have access to or participate in its reviewing, discussion, or
+decision. Another qualified committee member must manage the submission
+independently.
+
+
+**Use of generative AI or LLM systems**
+
+Please see the [FAQ for the general ACM policy](https://www.acm.org/publications/policies/peer-review-faq).
+In particular:
+
+1. *Confidentiality of submissions*. Reviewers may not upload or paste a submission, or any parts of its content, into any generative AI or LLM system, or any other third-party service, that does not guarantee the confidentiality of the submitted material.
+2. *Integrity of reviews*. Reviewers are expected to personally read, evaluate, and form judgments about submissions. AI tools should not be used as substitutes for the reviewer's expertise or judgment. AI may be used to correct spelling, grammar, and presentation, and to improve the clarity of reviewer-written text (provided that confidentiality is ensured). Reviewers remain fully responsible for the contents of their reviews, including any text that has been edited or generated with AI assistance.
**Contacts**
@@ -67,7 +67,6 @@ papers. Any interaction should go through the program chair.
Review Process
--------------
-
**Author Anonymity**
SIGPLAN conferences should implement double-blind reviewing. The primary goal of DBR
@@ -77,85 +76,70 @@ learning their identity:
1. Submissions should not have author names, and references to previous work must be in the third person.
2. Authors are not required to "hide" their submissions: they can put them on web pages and give talks about them.
-3. Reviewers should notify the PCC if anonymity is an obstacle to sound and objective reviewing of a paper.
-
-Given the use of DBR, the PCC must vet any external reviewers suggested by a PC member.
-
-_Recommendations:_
+3. Reviewers should notify the PCC if anonymity is an obstacle to sound and objective reviewing of a paper.
Provision (2) above is intended to prevent DBR from inhibiting normal dissemination of scientific ideas. Authors should not, however, take it as a license to explicitly lobby the PC or likely reviewers on behalf of their work. While SIGPLAN will not attempt to codify or police such behavior, PC chairs may wish to remind authors of their obligation to live up to the spirit as well as to the letter of DBR. A major point of contention concerns posting research results in social media or wide-reach mailing lists. PC Chairs should carefully consider to what extent such publicity conforms to their implementation of DBR and inform authors accordingly.
The two variants of DBR in current SIGPLAN use are “lightweight DBR” and “full DBR”. Under lightweight DBR, author names are revealed to reviewers after the initial review is submitted and before paper deliberations. In full DBR, author names are not revealed until the end of deliberations, and possibly only for accepted papers. These variants (and their many variations in implementation) reflect different models of the threat of reviewing bias and the benefit of knowing author identity. Lightweight DBR is based on the belief that authorship information should not bias “first impressions” of the paper’s quality, but the reviewers’ informed technical opinion will be unaffected, and even improved in depth, if author identities are later revealed. Full DBR rejects all authorship information as a bias factor.
-
-**Guardians**
-
-Guardians may be used at the discretion of the program chair. A guardian is a PC member assigned responsibility for ensuring that a paper is carefully and fairly assessed. Concretely, a guardian’s role may include:
-Assisting the PCC in identifying gaps in reviewer expertise.
-Ensuring that all reviews are of an appropriate standard.
-Facilitating online discussions.
-Writing the author-visible summary of the decision rationale.
-
-
**Expert and External Reviews**
-SIGPLAN conferences should strive to identify expert reviewers for every submission, insofar as possible. An "expert" is a reviewer who is very well versed and current in related work in the field. Authors gain confidence in the outcome of review decisions when expert reviewers are involved. That said, well-informed, but non-expert reviews also play a significant role in acceptance decisions: they represent the majority of the future readership of a paper, and involving them mitigates against topical balkanization.
-
-_Recommendation:_
-
-Several successful formulas for obtaining expert reviews have been used in the past:
+SIGPLAN conferences should strive to ensure that every submission is
+reviewed by people with sufficient relevant expertise. Review teams may
+combine complementary areas of expertise, and well-informed non-expert
+reviews can also provide a valuable perspective representative of the
+paper's broader readership.
-- The PCC designates and announces an External Review Committee (ERC) in the CFP.
-- The chair (sometimes in consultation with the PC) identifies a roster of external reviewers after submissions have closed.
-- The paper’s "guardian" PC member (if applicable) identifies external reviewers, in consultation with the PCC.
+The PCC should exercise judgment when interpreting reviewers'
+self-reported expertise ratings, since PC members calibrate these
+ratings differently: some consider themselves experts on most topics,
+while others rarely do.
-The PCC should exercise some judgment in assessing expertise ratings. Some PC members consider themselves experts on most topics, while other, more modest, PC members almost never declare themselves an expert. In the end, the PCC should use his/her judgment in deciding whether the expertise on a given paper is sufficient.
+External reviewers must be vetted, authorized, and recorded by the PCC.
+They should be encouraged to participate in discussion of the papers
+assigned to them, but must not have access to unrelated submissions or
+discussions.
-External reviewers should be encouraged to participate in online discussion of the papers they've been assigned; however, they should not see unrelated online PC discussions.
+**Submission of Supplementary Material**
-**Recommendations for Submission of Supplementary Material**
-
-Authors can be allowed to submit supplementary material (examples, proofs, software, datasets, etc.) at the time of submission. The PC is allowed, but not required, to consult this material. Supplementary material should be made anonymous if possible and reasonable. For example, proofs and datasets should always be anonymized, while source code may be too difficult to reasonably anonymize.
+Conferences may allow authors to submit supplementary material (examples, proofs, software, datasets, etc.) at the time of submission.
+The PC may, but is not required to, consider this material.
+Supplementary material should be anonymized for double-blind reviewing.
**Evaluation Criteria and Acceptance Ratio**
Conferences should strive to accept all high-quality submissions, and avoid numerical limits on acceptable papers.
-S
-_Recommendation:_
- The PC should focus its deliberations on:
--- whether there is a genuine research contribution which may include a new insightful evaluation of previous work
--- whether the approach is fundamentally sound
--- whether the community will benefit from reading the paper
--- whether the paper (and supporting material) contain sufficient information for others to reproduce and build on the results
+ - whether there is a genuine research contribution which may include a new insightful evaluation of previous work
+ - whether the approach is fundamentally sound
+ - whether the results are likely to be of interest to a sufficiently broad part of the community
+ - whether the paper (and supporting material) contain sufficient information for others to reproduce and build on the results
- The committee should lean toward accepting papers that are controversial, that is, ones that, after discussion, still have both a strong advocate and a strong detractor.
- The committee should lean toward accepting papers that explicate their results clearly.
-
**PC Submissions**
-PC submissions can be problematic to manage, but, on balance, the benefits of allowing PC submissions exceed the costs. Conferences should allow PC submissions, but disallow submissions by the GC and PCC.
+PC submissions can be problematic to manage, but, on balance, the benefits of allowing PC submissions exceed the costs, so conferences should allow PC submissions.
-
-
-PC members should not be allowed to review or discuss other PC papers; hence all reviews of PC submissions must be external. The PCC will designate the roster of external reviewers for PC papers, manage the review process, and make the final acceptance decision, in consultation with the reviewers. SIGPLAN requires that PC papers be held to a higher standard than other papers.
-
-Acceptance decisions for PC papers will be announced at the same time as other author decisions are announced; i.e., the PC will not be aware of any PC paper decisions until the PC meeting is complete.
-
-_Recommendation:_
+If Program Committee members are allowed to submit papers, either their papers should be held to a higher standard or other EC-approved measures should be taken, to avoid the appearance of impropriety.
+Conferences that use full double-blind reviewing and have program committees with at least fifty members need not hold PC papers to a higher standard, as the EC has judged that these are sufficient conditions to avoid the appearance of impropriety.
The policy on PC submission should be clearly explained to candidate PC members when their participation on the PC is solicited.
-An External Program Committee (EPC) can be used to evaluate PC submissions. The EPC can be a subset of the ERC, or a separate, non-overlapping committee, or “EPC” can be used as a replacement term (or synonym) for the ERC.
+Acceptance decisions for PC papers should be communicated at the same time as decisions for other submissions.
-**Author Response Recommendations**
+The Program Chair (PCC) may not submit papers to the conference; SIGPLAN’s Executive Committee recommends that the General Chair (GC) also not be allowed to submit papers.
-Recent SIGPLAN conferences typically allow author responses to reviewers. Authors should be allowed to read all reviews that are available at the time of the author response period. The PCC should make every effort to complete all initial reviews before the author-response period. Additional reviews may be solicited after the author response period and it may not be possible for the authors to see these reviews before final decisions are made by the PC. Ideally, authors should be allowed at least four days to respond.
+**Author Response**
+
+SIGPLAN conferences typically allow author responses to reviewers. Authors should be allowed to read all reviews that are available at the time of the author response period. The PCC should make every effort to complete all initial reviews before the author-response period. Additional reviews may be solicited after the author response period and it may not be possible for the authors to see these reviews before final decisions are made by the PC. Ideally, authors should be allowed at least four days to respond.
Additionally:
-- Authors strongly prefer seeing the scores at author response time. The PCC should consider making the scores available as well as the reviews.
-- Authors should be strongly encouraged to be brief.
+
+- Authors strongly prefer seeing the overall merit score at author response time. The PCC should consider making the scores available as well as the reviews.
+- The PCC may choose whether to make reviewer expertise scores visible to authors. The main purpose of these scores is to help the PCC assess whether the reviewers have sufficient expertise, and keeping them internal may help focus author responses on the substance of the reviews.
+- Authors should be strongly encouraged to be brief.
- PC chairs may choose to state that the PC is not obliged to read or respond to rebuttals beyond a certain designated length.
- The PCC may choose to allow authors to provide feedback on review quality, e.g., via a simple rating scale, in addition to rebutting the content of the review.
diff --git a/Resources/Policies/VideoRecording.md b/Resources/Policies/VideoRecording.md
index 8b3ec279..5640898f 100644
--- a/Resources/Policies/VideoRecording.md
+++ b/Resources/Policies/VideoRecording.md
@@ -1,6 +1,6 @@
---
layout: default
-title: "DRAFT: SIGPLAN Video Recording Policy"
+title: "SIGPLAN Video Recording Policy"
---
SIGPLAN expects every plenary keynote and every talk in the main technical program of POPL, PLDI, ICFP, OOPSLA, and Onward! (Papers and Essays) to be recorded and published on the [ACM SIGPLAN YouTube channel](https://www.youtube.com/@acmsigplan).
@@ -10,9 +10,11 @@ This policy covers recording for later publication, not live streaming. General
Co-located workshops, tutorials, and other events are not covered by this policy, though their organizers are welcome to arrange recording independently.
+We try to work closely with our [ACM SIGPLAN AV Team](https://www.sigplan.org/AV/) and the major conference organisers for this to happen.
+
## Responsibility
-The General Chair of each conference is responsible for ensuring that recordings are produced and delivered for upload to the SIGPLAN YouTube channel. SIGPLAN does not mandate a particular recording method; the General Chair has discretion to choose an approach suited to the venue, budget, and local circumstances. Options include, but are not limited to:
+The General Chair of each conference is responsible for ensuring that recordings are produced and delivered for upload to the [ACM SIGPLAN YouTube channel](https://www.youtube.com/@acmsigplan). SIGPLAN does not mandate a particular recording method; the General Chair has discretion to choose an approach suited to the venue, budget, and local circumstances. Options include, but are not limited to:
- Simple Zoom screen recording on the speaker's laptop, managed by a volunteer or session chair.
- Existing lecture-capture or AV recording equipment at a campus or venue.
@@ -24,4 +26,4 @@ General Chairs should include recording costs in their conference budget.
## Speaker notification
-Speakers should be informed in advance, and their consent should be sought in accordance with ACM requirements. This information and consent request should appear in both the call for papers and the acceptance notification, stating that their talks will be recorded and published on the SIGPLAN YouTube channel. Speakers with concerns should contact the General Chair to discuss accommodations.
+Speakers should be informed in advance, and their consent should be sought in accordance with ACM requirements. This information and consent request should appear in both the call for papers and the acceptance notification, stating that their talks will be recorded and published on the [ACM SIGPLAN YouTube channel](https://www.youtube.com/@acmsigplan). Speakers with concerns should contact the General Chair to discuss accommodations.
diff --git a/_announce/2026-03-17-sas_2026.txt b/_announce/2026-03-17-sas_2026.txt
new file mode 100644
index 00000000..7b547ca6
--- /dev/null
+++ b/_announce/2026-03-17-sas_2026.txt
@@ -0,0 +1,19 @@
+---
+title: "Call for Papers: 33rd Static Analysis Symposium (SAS 2026)"
+timestamp: "3/17/2026 12:26:47"
+deadline: "5/1/2026"
+---
+The 33rd Static analysis Symposium on Static Analysis (SAS 2026) will be held from October 6th to 8th at the Oakland Marriott City Centre hotel (California, USA), as part of SPLASH 2026.
+
+Contributions are welcomed on all aspects of program analysis, including for example abstract interpretation, automated deduction, debugging techniques, program synthesis, machine-learning verification, etc. This year, we specially welcome submissions in two **special topics**: (i) Static Analysis and AI and (ii) Static Analysis and Education.
+
+As in previous years, SAS features regular and NEAT (New questions/areas, Experience, Announcement, Tool) paper categories.
+
+**Important Dates**
+Paper Submission Deadline: May 1, 2026 (AoE)
+Paper Notification: Jun 16, 2026 (AoE)
+Conference Dates: Oct 6-8, 2026
+
+Website: https://conf.researchr.org/home/splash-issta-2026/sas-2026
+Submission link: https://sas26.hotcrp.com/
+
diff --git a/_announce/2026-03-20-mit_plr_2026.txt b/_announce/2026-03-20-mit_plr_2026.txt
new file mode 100644
index 00000000..8857db5c
--- /dev/null
+++ b/_announce/2026-03-20-mit_plr_2026.txt
@@ -0,0 +1,15 @@
+---
+title: "MIT Programming Languages Review Workshop 2026"
+timestamp: "3/20/2026 12:23:47"
+start: "5/8/2026"
+end: "5/8/2026"
+---
+# MIT Programming Languages Review Workshop 2026!
+
+Join us for this year’s annual MIT PLR workshop 2026 on **May 8**! Attendance can be virtually or in-person on MIT campus in Grier (34-401).
+
+This year, we’re excited to present a fresh lineup of talks from authors of what the PLR committee expects to be high-impact, significant works published in recent years at venues including: **OOPLSA, ASPLOS, PLDI, ICFP, VLDB, and more**! We will also be featuring an exciting **“PLR All Stars” Panel**, featuring past authors selected by PLR discussing the impact of their past work and the evolution of their views on their fields since.
+
+The MIT PLR is a student-run committee, launched in 2023, that hopes to highlight recent developments that we believe have significant potential to shape the future direction of PL research and/or industry practice. We aim to select papers that may substantially transform the PL community and beyond, with a focus on emerging trends rather than established lines of research.
+
+You can check out our full program on our [website](plr.csail.mit.edu) and register [here](https://forms.gle/kbDrMCRXUeX2STgXA)! We hope to see you there!
diff --git a/_announce/2026-03-26-gcasr_2026.txt b/_announce/2026-03-26-gcasr_2026.txt
new file mode 100644
index 00000000..29843a49
--- /dev/null
+++ b/_announce/2026-03-26-gcasr_2026.txt
@@ -0,0 +1,62 @@
+---
+title: "GCASR 2026 Announcement and Call for Posters"
+timestamp: "3/26/2026 13:08:50"
+start: "5/11/2026"
+end: "5/12/2026"
+---
+Announcement and Call for Posters: 13th Greater Chicago Area Systems Research Workshop (GCASR 2026)
+May 11, 2026
+Northwestern University, Evanston, Illinois
+
+https://gcasr.org/2026
+
+
+
+The GCASR Workshop, now in its 13th iteration, is a premier venue that promotes awareness, collaboration, and synergy among academic and industry systems researchers in Chicagoland and the greater Midwest region. Its participants span a variety of systems sub-disciplines—including (but not limited to) operating systems, distributed and decentralized computing, machine learning systems, high performance computing, computer architecture, networks, databases, programming languages and compilers, quantum computing, and security.
+
+GCASR 2026 will be held on Monday, May 11th on the campus of Northwestern University, which is located just north of Chicago in Evanston, IL (about 30-45 minutes from downtown via subway). Participation in the workshop is open to all (see the web site for more information).
+
+GCASR 2026 will consist of a keynote, a range of invited talks, and a robust poster session, all highlighting systems research in Chicagoland and the greater Midwest region.
+
+Faculty members, researchers, postdocs, students, industry professionals, and others with an interest in the workshop topics are invited to submit a poster for presentation at GCASR 2026. We welcome posters that highlight theoretical and experimental work in computing systems—including benchmarking, theoretical results, applications, software design, and algorithm/protocol design.
+
+
+
+Important Dates
+
+ Friday, April 10th, 2026 — Abstract Deadline
+ Friday, April 17th, 2026 — Poster Notification
+ Monday, May 11, 2026 — Workshop (Northwestern University, Evanston, Illinois)
+
+
+
+Submission Requirements
+
+ Please submit an abstract of no more than 250 words.
+ Posters may cover already-published work.
+ Please submit your poster abstract at: https://forms.gle/UtroSXguurTJGrvZ9.
+
+
+
+Topics of Interest
+
+Topics of interest include, but are not limited to:
+
+ Operating Systems
+ Computer Architecture
+ Networking
+ Distributed Systems
+ Grids/Clouds/Supercomputing (including HPC/MTC/HTC)
+ Edge Computing
+ Internet-of-Things
+ Energy Efficient Computing
+ Reconfigurable, Real-time, Cyber-Physical, and Embedded Systems
+ Programming Languages, Runtime Systems, and Compilers
+ File and Storage Systems
+ Parallelism and Multi/Many-core Systems
+ Secure and Reliable Systems
+ Databases
+ Artificial Intelligence and Machine Learning
+ Quantum Computing
+
+
diff --git a/_announce/2026-03-29-array_2026.txt b/_announce/2026-03-29-array_2026.txt
new file mode 100644
index 00000000..15e6d3b6
--- /dev/null
+++ b/_announce/2026-03-29-array_2026.txt
@@ -0,0 +1,24 @@
+---
+title: "[ARRAY 2026] Deadline Extension and Keynote Speakers Announced"
+timestamp: "3/29/2026 12:53:19"
+deadline: "4/6/2026"
+---
+**ARRAY 2026 Deadline Extension and Keynote Speakers Announced**
+
+Array programming is at home in many communities, including language design, library development, optimization, scientific computing, and across many existing language communities. The ARRAY Workshop series is intended to bring together researchers from many different practical and theoretical communities, including language designers, library developers, type theorists, compiler researchers, and practitioners. These communities can exchange ideas on the construction of computational tools for manipulating arrays and fundamental principles of array programming.
+
+This year ARRAY has two fantastic keynote speakers!
+* Mary Hall from the University of Utah who is speaking on “Compiler Technologies for Array Programming,” and
+* Jared Roesch from NVIDIA who is speaking on “Tile Programming Abstractions.”
+
+Submissions are welcome in two categories: full research papers (up to 12 pages) and extended abstracts (up to 2 pages) on work in progress. All submissions should be formatted in conformance with the ACM SIGPLAN proceedings style. Accepted submissions in either category will be presented at the workshop; and accepted full papers will also be published in the ACM Digital Library.
+
+**Important Dates:**
+Submission deadline: April 6, 2026 (updated)
+Author notification: April 19, 2026
+Final version: May 3, 2026
+
+Workshop website (CFP + relevant topics + updates): https://pldi26.sigplan.org/home/ARRAY-2026
+Submission link: https://array26.hotcrp.com/
+
+Distributed by the PLDI'26 Publicity Chairs on behalf of the ARRAY'26 Organizers.
diff --git a/_announce/2026-04-01-erlang_2026.txt b/_announce/2026-04-01-erlang_2026.txt
new file mode 100644
index 00000000..297dd90c
--- /dev/null
+++ b/_announce/2026-04-01-erlang_2026.txt
@@ -0,0 +1,171 @@
+---
+title: "Call for Papers, Erlang Workshop 2026"
+timestamp: "4/1/2026 5:34:20"
+deadline: "5/14/2026"
+---
+# Erlang Workshop 2026 - Call for Papers
+
+25th Edition of the Erlang Workshop
+Friday 28 August 2026, Indianapolis, Indiana, USA
+A satellite workshop of ICFP 2026
+
+https://icfp26.sigplan.org/home/erlang-2026
+
+ ** Deadline: 14 May 2026 **
+
+
+## Overview
+
+The Erlang Workshop aims to bring together the open source, academic,
+and industrial communities of BEAM languages (Erlang, Elixir, Gleam, LFE, etc.),
+along with other actor-model systems such as Akka and Clojure,
+including the concurrent, distributed systems, and fault-tolerant communities.
+
+The workshop will give participants the opportunity to learn about recent
+developments in techniques and tools, explore novel applications,
+draw lessons from users' experiences, and identify research problems
+and common ground across BEAM languages, related actor-model systems,
+functional programming, distribution, and concurrency.
+
+This year the workshop will be hybrid: we encourage authors and
+participants to attend in person, but remote talks and participation
+will be fully supported. We also plan to provide financial support to
+individuals who might not otherwise be able to attend.
+
+## Topics
+
+This year we invite four 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 BEAM languages in/with other languages, and new tools
+ (profilers, tracers, debuggers, testing frameworks, etc.).
+ Submissions related to BEAM languages (Erlang, Elixir, Gleam, LFE, etc.) and
+ topics in functional, concurrent, and distributed programming
+ are welcome and encouraged.
+
+* Practice and application papers describing uses of BEAM languages and
+ related actor-model systems in real-world settings, libraries for specific tasks,
+ experiences from using BEAM languages in specific application domains,
+ reusable programming idioms and elegant new ways of using BEAM languages to
+ approach or solve particular problems, etc.
+
+* Educational papers describing traditional or novel approaches to
+ teaching and learning BEAM languages and BEAM-related technologies
+ (curriculum design, courseware, workshops, tutorials, tooling for
+ pedagogy, online materials, assessments, etc.).
+
+For all paper categories, both full papers (up to 12 pages) and short
+papers (up to 6 pages) are 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
+
+Submission deadline: 14 May 2026
+Notification: 17 June 2026
+Camera ready: 07 July 2026
+Lightning talk registration: 07 July 2026
+Workshop: 28 Aug 2026
+
+Deadlines are anywhere on Earth.
+
+
+## Workshop Co-Chairs
+
+* Lee Barney, Brigham Young University-Idaho, USA
+* Akos Hajdu, Meta, UK
+* Laura Voinea, University of Glasgow, UK
+
+
+## Program Committee
+
+(Note: the Workshop Co-Chairs are also committee members)
+
+* Viktória Fördős (Cisco Systems, Sweden)
+* Jonatan Männchen (Erlang Ecosystem Foundation, Switzerland)
+* Radu Grigore (Meta, UK)
+
+
+
+## Instructions to authors
+
+### Submission
+
+Submissions must adhere to SIGPLAN’s republication policy
+(http://sigplan.org/Resources/Policies/Republication/), and authors
+should be aware of ACM’s policies on plagiarism
+(https://www.acm.org/publications/policies/plagiarism). 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://erlang2026.hotcrp.com
+
+Lightning talks can be submitted via the workshop form:
+https://forms.gle/DHcVwEYVkusxfCA19
+
+### 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:
+
+http://www.sigplan.org/Resources/Author/#acmart-format
+
+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
+(https://www.acm.org/publications/policies/artifact-review-badging#available).
+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
+(http://www.acm.org/publications/policies/copyright-policy) and ACM
+Author Rights (http://authors.acm.org/main.html).
+
+Accepted lightning talks will be posted on the workshop's website but
+not formally published in the proceedings.
diff --git a/_announce/2026-04-08-propl_2026.txt b/_announce/2026-04-08-propl_2026.txt
new file mode 100644
index 00000000..0100c58f
--- /dev/null
+++ b/_announce/2026-04-08-propl_2026.txt
@@ -0,0 +1,25 @@
+---
+title: "[PROPL'26] Call for Participation and Papers"
+timestamp: "4/8/2026 15:51:40"
+deadline: "4/24/2026"
+---
+**Call for Participation and Papers: Programming for the Planet (PROPL) 2026**
+
+There are simultaneous interlinked crises across the planet due to human actions: climate change, biodiversity loss, and desertification (collectively, a crisis in climate health). Assessing progress on these complex and interlocking issues requires a global view on the effectiveness of our adaptations and mitigations. To succeed in the coming decades, we need a wealth of new data about our natural environment that we rapidly process into accurate indicators, with sufficient trust in the resulting insights to support interventions that affect the lives of billions of people worldwide.
+
+Previous editions of PROPL (PROPL 2024: https://popl24.sigplan.org/home/propl-2024, PROPL 2025: https://conf.researchr.org/home/icfp-splash-2025/propl-2025) have investigated the state of practice in this area while also eliciting ambitious visions for future computational systems designed to support collaborative climate analysis, modeling, forecasting, policy, and diplomacy. Inspired by the lively discussions around these future visions in previous years, PROPL 2026 will be more focused, operating as an open working meeting where we elicit requirements and propose a coherent set of technical approaches for a next-generation planetary compute engine, i.e. a large-scale “live computational commons” where all sorts of humans, working together when appropriate with safely sandboxed AI systems:
+* collect and process billions of observations about the state of the planet, with new data being ingested continuously
+* feed this data into live computations, including data analyses and simulations
+* present the results of these computations in formats that are comprehensible and actionable in the real world
+
+**Participation**
+This 3rd “Action PROPL” now invites anyone with an interest in helping research, design and implement a next-generation planetary compute engine to attend and actively participate in the workshop, including climate science and biodiversity practitioners and researchers and engineers with expertise in programming systems. In each topical session, the organizers will begin with a brief orienting presentation, then ask audience members to contribute notes and ideas to a “living document” before engaging in an active discussion. If you’re interested in the topic of planetary health, but feel like your research doesn’t fit, then we encourage you to come along and we will try to figure it out with you!
+
+**Submissions**
+ We are soliciting 1-page position papers, or even shorter notes, to help seed and steer the discussion on any of the topics listed on the PROPL’26 webpage (https://pldi26.sigplan.org/home/propl-2026) or any other topics that you think it would be important to discuss. If you have a position paper to contribute, please email it to propl2026-organizers@googlegroups.com. Position papers will be lightly reviewed and posted publicly on the workshop webpage in advance of the event. If you cannot attend, but would like to participate asynchronously, then we encourage you to submit a note to make us aware of your interest. Novelty is not a requirement in either case!
+
+Submission deadline: April 24, 2026 (updated)
+
+Workshop website (CFP + relevant topics + updates): https://pldi26.sigplan.org/home/propl-2026
+
+Distributed by the PLDI'26 Publicity Chairs on behalf of the PROPL’26 Organizers.
diff --git a/_announce/2026-04-13-dramsec_2026.txt b/_announce/2026-04-13-dramsec_2026.txt
new file mode 100644
index 00000000..e68d56fd
--- /dev/null
+++ b/_announce/2026-04-13-dramsec_2026.txt
@@ -0,0 +1,13 @@
+---
+title: "Call for Papers: The Sixth Workshop on DRAM Security (DRAMSec) co-located with ISCA 2026 in Raleigh, USA, June 28, 2026"
+timestamp: "4/13/2026 10:03:59"
+deadline: "5/5/2026"
+---
+We’re soliciting papers on attacks and defenses on current and future DRAM technologies. We also welcome experimental papers describing tools and methodologies for testing DRAM security. We’ll favor papers that bring new insights, debunk previously held beliefs, revisit assumptions, present new attacks and defenses, replicate prior art, or put forward controversial points of view. We will also consider position papers, especially from the industry, that outline design and process challenges affecting DRAM security or describe state-of-the-art DRAM defenses.
+
+>> Submission deadline: May 5, 2026 (AOE): https://dramsec.ethz.ch/cfp.html
+DRAMSec 2026 website: https://dramsec.ethz.ch/
+
+Workshop chairs: Yuval Yarom (Ruhr University Bochum), Steven Woo (Rambus Inc.)
+Submissions and Web Chairs: Nisa Bostancı (ETH Zurich)
+
diff --git a/_announce/2026-04-13-plsss_2026.txt b/_announce/2026-04-13-plsss_2026.txt
new file mode 100644
index 00000000..071bdce2
--- /dev/null
+++ b/_announce/2026-04-13-plsss_2026.txt
@@ -0,0 +1,32 @@
+---
+title: "Call for applications for the first Summer School on Programming Languages, Logic, and Software Security"
+timestamp: "4/13/2026 0:58:18"
+start: "8/10/2026"
+end: "8/14/2026"
+---
+Applications are now open for the first Summer School on Programming Languages, Logic, and Software Security, to be held August 10–14, 2026 in Aarhus, Denmark.
+
+The summer school offers intensive courses by leading researchers covering foundational and applied topics at the intersection of programming languages, formal methods, and software security. It is aimed at PhD students and advanced B.Sc./M.Sc. students active in the areas of programming languages, logic, semantics, and software security.
+
+Dates: August 10–14, 2026
+Venue: Aarhus University (INCUBA Katrinebjerg), Aarhus, Denmark
+Webpage: [https://conferences.au.dk/pls](https://conferences.au.dk/pls)
+
+Application deadline: May 15, 2026
+
+Courses and Speakers:
+
+Bas Spitters: The Rocq proof assistant and Gen-AI Tools for Formalization of Mathematics
+Lars Birkedal and Amin Timany: Higher-Order Concurrent Separation Logic
+Daniel Gratzer: Introduction to Type Theory
+Aslan Askarov: Language-Based Security
+Anders Møller: Static Program Analysis
+
+
+To apply, please visit [https://conferences.au.dk/pls/application](https://conferences.au.dk/pls/application). Applicants should submit a CV and a motivation letter. A reference letter is additionally required for students. Applicants wishing to be considered for financial support should indicate this in their application and include a short text explaining their need.
+
+Decisions will be communicated in late May.
+
+For questions, please contact: timany@cs.au.dk
+
+We look forward to welcoming everyone to Aarhus!
diff --git a/_announce/2026-04-19-acm_elections.txt b/_announce/2026-04-19-acm_elections.txt
new file mode 100644
index 00000000..efb9a26b
--- /dev/null
+++ b/_announce/2026-04-19-acm_elections.txt
@@ -0,0 +1,7 @@
+---
+title: "ACM Elections"
+deadline: "5/22/2026"
+---
+The ACM election has started and former SIGPLAN Chair Jens Palsberg is running
+for ACM President. To vote, go to https://acm.org and find the election link.
+Voting ends on May 22.
diff --git a/_announce/2026-04-23-page_2026.txt b/_announce/2026-04-23-page_2026.txt
new file mode 100644
index 00000000..c5e491fb
--- /dev/null
+++ b/_announce/2026-04-23-page_2026.txt
@@ -0,0 +1,21 @@
+---
+title: "[PAgE 2026] Call for Papers"
+timestamp: "4/23/2026 10:52:31"
+deadline: "4/30/2026"
+---
+**Call for Papers: PAgE 2026**
+
+AI-powered agents are increasingly being deployed in production settings. Yet the formal foundations needed to make these systems safe, reliable, and trustworthy remain underdeveloped. Ensuring correctness in these settings demands a new discipline, which we term agentic engineering: a research agenda that brings together ideas from programming languages, formal verification, software engineering, and neuro-symbolic reasoning to specify, analyze, test, monitor, and repair agents at scale.
+
+The PAgE workshop aims to bring together researchers and practitioners interested in the foundations and practice of safe agentic systems. Our goal is to foster a community around principled approaches for building agents with precise specifications, verifiable behaviors, and runtime safeguards that hold up in real-world deployments. More broadly, the workshop seeks to strengthen connections across the programming languages, formal methods, software engineering, and machine learning communities in order to advance the principles of safe and reliable agentic engineering. The workshop will feature invited talks and peer-reviewed papers spanning theory, systems, tools, and practical experience.
+
+**Submissions are welcome:** We welcome submissions describing research results, artifacts, datasets, case studies, and experience reports. Full papers may be up to 10 pages, excluding bibliography, and should present completed research on topics related to the focus of the workshop. Accepted full papers will be published in the ACM Digital Library. For additional submission instructions see the PAgE website linked below.
+
+**Important Dates:**
+Submission deadline: April 30, 2026 (extended)
+Workshop date: June 15, 2026
+
+Workshop website (CFP + topics of interest + updates): https://pldi26.sigplan.org/home/page-2026
+Submission link: https://page2026.hotcrp.com/u/1/
+
+Distributed by the PLDI'26 Publicity Chairs on behalf of the PAgE’26 Organizers.
diff --git a/_announce/2026-04-27-aeic_2026.txt b/_announce/2026-04-27-aeic_2026.txt
new file mode 100644
index 00000000..ca017168
--- /dev/null
+++ b/_announce/2026-04-27-aeic_2026.txt
@@ -0,0 +1,349 @@
+---
+title: "Ada-Europe Int. Conf. Reliable Software Technologies, AEiC 2026"
+timestamp: "4/27/2026 7:40:50"
+start: "6/9/2026"
+end: "6/12/2026"
+---
+-----------------------------------------------------------------------
+
+Call for Participation
+
+30th Ada-Europe International Conference on
+Reliable Software Technologies (AEiC 2026)
+
+9-12 June 2026, Västerås, Sweden
+
+www.ada-europe.org/conference2026
+
+*** Early registration DEADLINE May 20 ***
+*** Extensive info and registration online ***
+*** Add tutorials and/or a workshop to your conference registration ***
+
+Organized by Ada-Europe and Mälardalen University,
+in cooperation with ACM SIGPLAN
+
+#AEiC2026 #AdaEurope #AdaProgramming
+
+-----------------------------------------------------------------------
+
+Preparations for AEiC 2026, the 30th Ada-Europe International
+Conference on Reliable Software Technologies, are well underway!
+
+Come to the Ada-Europe conference in Västerås, experience a packed
+program in an exciting town, benefit from tutorials on Tuesday, join
+a workshop on Friday, enjoy the social events and some sightseeing!
+
+Register now: discounted fees until May 20!
+
+
+Extra conference sponsorship allows for an extremely low 20 EUR fee for
+the Ada Developers Workshop on Friday!
+
+See below for an overview, and visit our website for more details about
+the conference program, registration fees, social events and much more.
+
+*** General Information
+
+The 30th Ada-Europe International Conference on Reliable Software
+Technologies (AEiC 2026) returns after 14 years to Sweden.
+The conference schedule comprises keynote and invited talks,
+a journal track, a regular paper track, an industrial track, a
+work-in-progress track, a vendor exhibition, parallel tutorials,
+and satellite workshops. There will be time for networking during
+breaks and lunches, as well as various social events.
+
+AEiC 2026 is the latest in a series of annual international conferences
+started in the early 80's, under the auspices of Ada-Europe, the
+international organization that promotes knowledge and use of the Ada
+programming language and reliable software in general, into academic
+education and research, and industrial practice.
+
+The Ada-Europe series of conferences has over the years become
+a leading international forum for providers, practitioners and
+researchers in reliable software technologies. These events
+highlight the increased relevance of Ada in general and in safety-
+and security-critical systems in particular, and provide a unique
+opportunity for interaction and collaboration between academics and
+industrial practitioners.
+
+The conference presentations illustrate current work in the theory and
+practice of the design, development, and maintenance of long-lived,
+high-quality software systems for a challenging variety of application
+domains. The topics of interest for the conference include but are
+not limited to: formal methods, testing, and model-based engineering
+of critical systems; high-integrity systems and reliability; AI for
+safety-critical and high-integrity systems engineering; real-time
+and embedded systems; Ada language and technologies; applications and
+experimental evaluations in relevant domains. More specific topics
+are described on the conference website.
+
+The 2026 edition of the conference continues a number of important
+innovations started in previous years:
+- reduced conference registration fee for one author per presentation;
+- extra low registration fee for Ada Developers workshop;
+- journal-based open-access publication model for peer-reviewed papers;
+- tutorials on Tuesday, followed by welcome event for all participants;
+- compact program with two core days (Wednesday & Thursday);
+- workshops on Friday, optional chill event on Thursday evening.
+
+*** Overview of the Week
+
+- Tue 09: 5 half-day tutorials, welcome reception;
+- Wed 10: core technical program, conference banquet;
+- Thu 11: core technical program, post conference chill-out;
+- Fri 12: 3 full-day workshops.
+
+You will find extensive information about AEiC 2026 on the conference
+website, such as an overview of the program, the list of accepted
+papers and presentations, and descriptions of workshops, tutorials,
+keynote and invited presentations, and social events. Also check the
+conference site for registration, accommodation and travel information.
+The Final Program brochure will be available there as well.
+
+*** Venue
+
+
+The conference is in-person, and will take place at Mälardalen
+University, Västerås, Sweden. Mälardalen University (MDU), one
+of Sweden's youngest and most dynamic universities, is a leading
+institution for applied research and innovation in collaboration
+with industry and the public sector. Established in 1977 and granted
+full university status in 2022, MDU is home to over 17,000 students
+and 1,000 staff members, with strong international ties and research
+excellence in areas such as embedded systems, future energy, health
+and welfare, and sustainable development. The university houses
+several internationally recognized research environments, out of
+which Embedded Systems, Innovation and Product Realization, and Future
+Energy are among the most prominent ones. MDU's campuses (Västerås
+and Eskilstuna) are modern, centrally located, and purpose-built to
+foster interdisciplinary collaboration and innovation.
+
+Västerås is one of Sweden's oldest cities and now a hub for
+advanced technology, energy innovation, and digital transformation.
+Strategically located just an hour west of Stockholm and easily
+accessible by train, bus or car, Västerås is home to global tech
+companies such as ABB, Alstom, Westinghouse. The city sits on the
+shores of Lake Mälaren and combines scenic beauty, a vibrant cultural
+life, and excellent infrastructure. Västerås Airport offers direct
+flights to several European destinations, and Stockholm Arlanda
+International Airport is reachable within 90 minutes. With its
+blend of historical charm, green parks, and cutting-edge industry,
+Västerås offers the perfect setting for an inspiring and high-impact
+academic and industrial gathering.
+
+*** Invited Speakers
+
+
+This year the conference will once more feature keynotes and invited
+talks. All will address topics of relevance in the conference scope,
+with time for questions and answers.
+
+- Mark van den Brand, from Eindhoven University of Technology (TU/e),
+ Eindhoven, the Netherlands, will present a keynote talk.
+
+- More details on this and other keynotes and invited presentations
+ will be made available shortly.
+
+*** Conference Core Composition
+
+
+The core conference program features seven distinct types of technical
+presentations, with different duration, all followed by various
+manners of discussion time: journal track talk, regular track talk,
+industrial track presentation, work-in-progress track talk, vendor
+presentation, keynote, invited talk.
+
+All papers presented in the journal, regular, industrial and
+work-in-progress tracks have undergone peer review. Presentations
+are combined into by-theme and not by-track sessions, in order that
+authors and participants alike enjoy all flavors of the program in
+a mixed as opposed to segregated combination.
+
+The list of accepted papers and presentations is on the conference
+website. The detailed schedule will be announced later.
+
+Papers and Presentations:
+- 1 keynote presentation;
+- sessions with a mix of presentations on specific topics;
+- 9 journal track talks;
+- 7 regular track talks;
+- 3 work-in-progress reports;
+- 4 industrial presentations and experience reports;
+- submissions from around the world;
+- additional presentations and information to be added shortly.
+
+*** Tutorials
+
+
+Improve the benefits of coming to the conference further by attending
+our tutorials, all given by well-known experts.
+
+Five half-day tutorials are scheduled on Tuesday 9th:
+
+- "Get Started with Formal Methods for Safety and Security using SPARK"
+ by Olivier Henley, AdaCore, Canada.
+
+ Ada SPARK is a language that enables formal deductive verification,
+ allowing developers to statically prove the absence of runtime errors
+ as well as functional correctness. Join us in this half day tutorial
+ where we start from scratch to install our toolchain, integrate with
+ VS Code and then use AI to generate a first version of our program.
+ We then incrementally use formal verification to prove the absence
+ of runtime errors and lastly functional correctness and optionally
+ run our program on a Raspberry Pi Pico.
+
+- "Introduction to Ada"
+ by Jean-Pierre Rosen, Adalog, France.
+
+ This tutorial is an overview of the Ada programming language, from
+ basic syntax to its most sophisticated features. It focuses on what
+ makes Ada different from other languages, and on the benefits that
+ it provides for safety, reliability, maintainability, reusability,
+ and efficiency. The tutorial covers all the main components of the
+ language, accompanied with many examples, and is structured in two
+ parts, that can be taken seperately (morning/afternoon).
+
+- "Advanced Ada"
+ by Jean-Pierre Rosen, Adalog, France.
+
+ Both tutorial parts illustrate the benefits of strong typing,
+ the accurate model of numerical computations, the Ada approach to
+ object oriented programming, its unique features for programming
+ by contract, and its support for the concurrency and low level
+ embedded systems programming. It concludes with an overview of
+ the standard libraries (including the annexes), an introduction to
+ SPARK, the high-reliability provable subset of Ada, an overview of
+ the tools available, and examples of industrial users.
+
+- "From Cloud to Bareboard Separating Application and Infrastructure
+ with WebAssembly"
+ by Edoardo Tinto, University of Padua, Italy.
+
+ This hands-on tutorial presents and discusses the traits
+ that make WebAssembly practical in critical embedded systems,
+ starting from the design choices behind its bytecode specification.
+ This tutorial also reviews the state of the current Wasm ecosystem,
+ for compilation toolchains and execution environments. Most of all,
+ this tutorial illustrates hands-on how to use WebAssembly, paired
+ with a memory-safe programming language, to develop applications
+ made of isolated and live-migratable components.
+
+- "Writing Desktop Graphical User Interfaces in Ada"
+ by Gautier de Montmollin, Ada-Switzerland, Switzerland.
+
+ With all the focus on embedded systems, safety-critical systems,
+ and large systems as "the" deployment area for the Ada language,
+ we tend too often to forget its general-purpose nature and
+ the availability of usable open-source libraries for creating
+ "normal" applications such as Graphical User Interfaces (GUIs).
+ In this tutorial, we show some examples of desktop applications of
+ various sizes deployed in the real world and explain the underlying
+ programming techniques for mastering Graphical User Interfaces,
+ with specific subtleties of Ada regarding Object-Orientation.
+
+*** Satellite Events
+
+Three workshops are held on Friday 12th:
+
+- 3rd Ada Developers Workshop.
+
+ An informal yet dynamic gathering for developers in the Ada community
+ to meet, share insights, and present their latest projects or project
+ updates. A full "Ada day" with various technical presentations on
+ Ada-related topics is being scheduled. Even though the submission
+ deadline is already past, a few late submissions might still be
+ accepted, but don't delay sending in a proposal!
+
+
+- 22th Workshop on Advances in Model Based Testing (A-MOST 2026).
+
+ The goal of the workshop is to bring researchers and practitioners
+ together to discuss state of the art, practice and future prospects
+ in Model Based Testing. Submission deadline is 7 May 2026.
+
+
+- Workshop on Digital Twin Experiences (DTE).
+
+ The workshop brings together researchers and practitioners from
+ diverse backgrounds, including software engineering, data science,
+ systems engineering, and industry applications. The aim is to
+ foster dialogue across disciplines and better understand both
+ the opportunities and challenges of digital twin technologies.
+ Submission deadline is 3 May 2026.
+
+
+*** Social Program
+
+The conference provides several opportunities to socialize:
+
+- Each day: coffee breaks and lunches offer ample time for interaction
+ and networking with participants and vendors.
+
+- Tuesday early evening: Welcome Reception (details to be announced).
+
+- Wednesday evening: bus trip to, and Conference Dinner at, Petterssons
+ Matservice I Utvreta.
+
+- Thursday evening: Chill Event (details to be announced).
+
+*** Sponsorship and Exhibition
+
+
+The conference is a leading international gathering of users and
+developers of reliable software technologies that offers companies
+the opportunity to get in contact with the AEiC community and to
+advertise their products. Special interests, although not limited
+to, include high-integrity software, verification tools, Ada-related
+technologies and AI solutions for high-integrity systems engineering.
+
+With previous conferences attracting nearly 100 participants, there
+will be representatives from the industrial Ada community attending
+providing an excellent opportunity to liaise and discuss your products
+and offers.
+
+Conference sponsors enjoy a whole range of benefits, including
+exhibition space and vendor sessions as part of the conference program.
+
+*** Further Information
+
+Registration:
+- registration information is provided at
+
+- early registration discount until Wednesday May 20, 2026
+- payment possible by credit card or bank transfer
+- special low conference fee for authors
+- discount for Ada-Europe and ACM SIGPLAN members
+- registration includes coffee breaks, lunches and social events
+- strong discount on conference fees for students
+- minimal fee for Ada Developers Workshop
+- see registration page for all details
+
+Promotion:
+- recommended hashtags: #AEiC2026 #AdaEurope #AdaProgramming
+
+The conference is organized by:
+- Ada-Europe
+- Mälardalen University
+
+in cooperation with:
+- ACM SIGPLAN
+
+Please make sure you book accommodation as soon as possible.
+
+
+For more info and latest updates see the conference website at
+.
+
+We look forward to seeing you in Västerås in June 2026!
+
+-----------------------------------------------------------------------
+
+Our apologies if you receive multiple copies of this announcement.
+Please circulate widely.
+
+Dirk Craeynest, AEiC 2026 Publicity Chair
+Dirk.Craeynest@cs.kuleuven.be Dirk.Craeynest@kuleuven.be
+
+* 30th Ada-Europe Int.Conf. Reliable Software Technologies (AEiC 2026)
+* June 9-12, 2026, Västerås, Sweden, www.ada-europe.org/conference2026
+
diff --git a/_announce/2026-05-18-splv_2026.txt b/_announce/2026-05-18-splv_2026.txt
new file mode 100644
index 00000000..2be49651
--- /dev/null
+++ b/_announce/2026-05-18-splv_2026.txt
@@ -0,0 +1,45 @@
+---
+title: "Call for Participation, Scottish Programming Languages and Verification Summer School (SPLV 2026)"
+timestamp: "5/18/2026 18:50:05"
+start: "8/3/2026"
+end: "8/7/2026"
+---
+The Scottish Programming Languages and Verification Summer School is a collaborative effort between the Universities of Edinburgh, Glasgow, Heriot-Watt, Strathclyde and St Andrews. This summer school provides core and advanced classes that cover foundational as well as state of the art knowledge on the underlying principles needed to use or design new languages and verifying program correctness.
+
+This school aims to:
+
+ * Facilitate rapid knowledge exchange, in addition to providing essential research training and networking for postgraduate students.
+ * Give postgraduate students the opportunity to network with fellow students in the field as well as many established researchers.
+ * Provide essential postgraduate training in theoretical underpinnings of computer science and in programming languages.
+
+The 2026 edition of the Scottish Programming Languages and Verification Summer School will be held in Glasgow, 3rd -- 7th August 2026 [website](https://spli.scot/splv/2026-glasgow/).
+
+# Confirmed speakers:
+
+## Core Courses
+ * Introduction to Types and Lambdas by Nachi Valliappan (University of Edinburgh)
+ * Introduction to Model Checking by Oana Andrei (University of Glasgow)
+ * Introduction to Category Theory by Bob Atkey (University of Strathclyde)
+
+## Contributed Courses
+ * Formal Modelling with Bigraphs by Blair Archibald (University of Glasgow)
+ * Distributed Systems: A Logical Approach by Jamie Gabbay (Heriot-Watt University)
+ * Modal Fixpoint Logics by Clemens Kupke (University of Strathclyde)
+ * Algebra and Normalisation by Ohad Kammar (University of Edinburgh)
+ * Resource-constrained compiler construction for functional languages by Wim Vanderbauwhede (University of Glasgow)
+ * Building Highly-Assured Compilers using Dependent Types by Jan de Muijnck-Hughes (University of Strathclyde)
+
+# Registration
+
+Registration is via [Eventbrite](https://www.eventbrite.co.uk/e/splv-2026-summer-school-tickets-1989312724911)
+
+ * Academic (early, registration deadline 30th June 2026): £260 / (late) £360
+ * Standard (early, registration deadline 30th June 2026): £760 / (late) £860
+
+This includes access to all sessions, catered lunch, social events, and a catered reception at Glasgow City Chambers.
+We also have a limited amount of subsidised accommodation remaining at £195 for an en-suite room in Queen Margaret Residences, checking in on Sunday 2nd August and checking out on Friday 7th August. You can book this from the registration page.
+
+If you have any questions, please don’t hesitate to contact the organisers: glasgow-splv-organisers@lists.cent.gla.ac.uk.
+
+Best wishes,
+Jeremy
diff --git a/_announce/2026-05-29-plmw_icfp_2026.txt b/_announce/2026-05-29-plmw_icfp_2026.txt
new file mode 100644
index 00000000..bd358f3e
--- /dev/null
+++ b/_announce/2026-05-29-plmw_icfp_2026.txt
@@ -0,0 +1,22 @@
+---
+title: "PLMW @ ICFP 2026: Funding Call"
+timestamp: "5/29/2026 10:31:02"
+start: "8/24/2026"
+end: "8/24/2026"
+---
+APPLICATION FOR PLMW TRAVEL FUNDING
+
+Applications for travel funding to PLMW @ ICFP are now open - we will begin awarding funding starting from June 1 AOE until all funding is committed. So long as funding remains, we will continue to consider applications submitted before June 30th AOE.
+
+We advise all interested to apply as soon as possible, especially if a visa is required.
+
+https://icfp26.sigplan.org/home/PLMW-ICFP-2026#Call-for-Participation
+
+The application can be accessed directly at the following URL:
+https://forms.gle/adtuWjLAbBtGTcCNA
+
+PLMW is a workshop co-located with ICFP 2026 (the International Conference on Functional Programming) in Indanapolis, US, from August 24-29.
+
+The purpose of this mentoring workshop is to encourage graduate students and senior undergraduate students to pursue careers in programming language research. This workshop will bring together world leaders in programming languages research and teaching from academia and industry to help students imagine how they might contribute to our research community. Topics will range from the abstract (e.g., what is PL research and how does one become involved in it) to the concrete (e.g., how to navigate an academic conference, how to pick a research area) as well as technical talks on cutting-edge topics. See the link below for more details:
+
+https://icfp26.sigplan.org/home/PLMW-ICFP-2026
diff --git a/_announce/2026-06-03-from_2026.txt b/_announce/2026-06-03-from_2026.txt
new file mode 100644
index 00000000..b6e4538e
--- /dev/null
+++ b/_announce/2026-06-03-from_2026.txt
@@ -0,0 +1,152 @@
+---
+title: "Tenth Working Formal Methods Symposium (FROM 2026)"
+timestamp: "6/3/2026 9:24:34"
+deadline: "6/30/2026"
+---
+FROM 2026 - Final Call for Papers
+
+ Tenth Working Formal Methods Symposium
+
+ September 15-17, 2026, Timisoara, Romania
+ https://from2026.uvt.ro
+ co-located with SYNASC 2026
+ https://synasc.ro/2026/
+
+
+DESCRIPTION
+-----------
+The Working Formal Methods Symposium (FROM) aims to bring together
+researchers and practitioners who work on formal methods by contributing
+new theoretical results, methods, techniques, and frameworks, and/or by
+creating or using software tools that apply theoretical contributions.
+
+The program of the symposium includes invited lectures and regular contributions.
+Submissions on the general topics of formal methods, theoretical computer
+science, logic and applications are welcome.
+
+This event is co-located with the 28th International Symposium on Symbolic and
+Numeric Algorithms for Scientific Computing (SYNASC 2026).
+
+ORGANIZERS
+----------
+Faculty of Informatics of West University of Timisoara (https://info.uvt.ro/en/)
+Institute for Logic and Data Science (ILDS, https://ilds.ro/)
+
+IMPORTANT DATES
+---------------
+Deadline for paper/abstract submission: June 30, 2026 (AoE)
+Deadline for author notification: July 25, 2026 (AoE)
+Deadline for revised paper/abstract submission: August 23, 2026 (AoE)
+Deadline for registration: September 4, 2026 (AoE)
+Symposium: September 15-17, 2026
+
+SUBMISSIONS
+-----------
+Papers of up to 16 pages prepared according to the EPTCS template
+(see http://style.eptcs.org/) must be submitted electronically
+using the EasyChair submission system at:
+
+https://easychair.org/my/conference?conf=synasc2026
+
+and choosing the track "FROM Symposium"
+
+Research papers must contain original research results not submitted and not
+published elsewhere. They will be considered for inclusion in the EPTCS proceedings
+of the symposium, which will be indexed in the Web of Science. Authors who want to
+present work in progress or discuss new aspects or a survey of their older research
+results at the workshop are welcome to submit an extended abstract (up to 8 pages).
+Papers will be refereed and accepted on the basis of their scientific merit and relevance
+to the topics of the symposium.
+
+Authors of selected papers will be invited to submit an extended version to a journal, most
+probably the Journal of Logical and Algebraic Methods in Programming
+(https://www.sciencedirect.com/journal/journal-of-logical-and-algebraic-methods-in-programming),
+subject to formal approval by Elsevier.
+
+TOPICS OF INTEREST
+------------------
+The topics of interest for FROM 2026 include, but are not limited to:
+
+Areas and formalisms:
++ Category theory in computer science
++ Distributed systems and concurrency
++ Domain science and engineering
++ Formal languages and automata theory
++ Formal modelling, verification and testing
++ Logic in computer science
++ Logical frameworks
++ Mathematical structures in computer science
++ Models of computation
++ Semantics of programming languages
++ Type systems
+
+Methods:
++ Automated reasoning and model generation
++ Automated induction
++ Certified programs
++ Data-flow and control-flow analysis
++ Deductive verification
++ Mechanized proofs
++ Model checking
++ Proof mining
++ Symbolic computation
++ Term rewriting
+
+Applications:
++ Computational logic
++ Computer mathematics
++ Knowledge representation, ontology reasoning, deductive databases
++ Program analysis
++ Verification and synthesis of software and hardware
++ Uncertainty reasoning and soft computing
+
+Submissions on any other related topics are welcome.
+
+INVITED SPEAKERS
+-------------------
+Cătălin Dima (Université Paris-Est Créteil)
+Dániel Horpácsi (Eötvös Loránd University)
+Radu Iosif (CNRS/VERIMAG)
+Temur Kutsia (Johannes Kepler University of Linz)
+Grigore Roșu (University of Illinois at Urbana-Champaign)
+Gheorghe Ștefănescu (University of Bucharest)
+
+PROGRAMME COMMITTEE
+-------------------
+Andrei Arusoaie (Alexandru Ioan Cuza University of Iași)
+Georgiana Caltais (University of Twente)
+Ștefan Ciobâcă (Alexandru Ioan Cuza University of Iași)
+Florin Crăciun (Babeș-Bolyai University of Cluj-Napoca)
+Mădălina Erașcu (West University of Timișoara)
+Dániel Horpácsi (Eötvös Loránd University, Budapest)
+Temur Kutsia (Johannes Kepler University Linz)
+Ioana Leuștean (University of Bucharest)
+Mircea Marin (West University of Timișoara) - chair
+David Nowak (CNRS & University of Lille)
+Corina Păsăreanu (NASA & Carnegie Mellon University)
+Andrei Popescu (University of Sheffield)
+Thomas Powell (University of Bath)
+Grigore Roșu (University of Illinois at Urbana-Champaign)
+Vlad Rusu (INRIA Lille)
+Andrei Sipoș (University of Bucharest & IMAR)
+Viorica Sofronie-Stokkermans (University of Koblenz and Landau)
+Sorin Stratulat (University of Lorraine, Metz)
+Alicia Villanueva (VRAIN, Polytechnic University of Valencia)
+Tomas Vojnar (Masaryk University)
+
+ORGANISING COMMITTEE
+-------------------
+Adrian Crăciun (West University of Timișoara)
+Mădălina Erașcu (West University of Timișoara)
+
+REGISTRATION
+------------
+The registration fee is 300 EUR, and covers: conference kit, refreshments
+during breaks, lunches, and welcome cocktail.
+It does not cover participation at the conference dinner.
+The additional fee for the conference dinner is 60 €.
+***************
+
+Further information is available on our website,
+http://from2026.uvt.ro
+
diff --git a/_announce/2026-06-14-vstte_2026.txt b/_announce/2026-06-14-vstte_2026.txt
new file mode 100644
index 00000000..6d4cfede
--- /dev/null
+++ b/_announce/2026-06-14-vstte_2026.txt
@@ -0,0 +1,61 @@
+---
+title: "VSTTE 2026: Second Call for Papers and WIP Presentations"
+timestamp: "6/14/2026 21:35:52"
+deadline: "7/24/2026"
+---
+18th International Conference on Verified Software: Theories, Tools, and Experiments
+
+14 September, 2026, Graz, Austria
+
+Co-located with Formal Methods in Computer-Aided Design 2026 (FMCAD 2026)
+
+===
+
+Key Information
+
+Conference Website: https://fmcad.org/FMCAD26/vstte/
+
+Important Dates:
+
+Abstract submission: July 10th, 2026 AoE July 17th, 2026 AoE
+Paper submission: July 17th, 2026 AoE July 24th, 2026 AoE (firm, no further extensions)
+Notification of acceptance: August 22nd, 2026 AoE (tentative)*
+Final pre-conference paper submission (optional): September 2nd, 2026 AoE (tentative)
+Camera-ready for papers included in post-conference proceedings: October 23, 2026 (tentative)
+
+* Authors of accepted papers at VSTTE 2026 will be able to register at early-bird rates for FMCAD/VSTTE.
+
+===
+
+Paper Submissions:
+
+VSTTE 2026 accepts both long (limited to 16 pages, excluding references) and
+short (limited to 10 pages, excluding references) paper submissions. Short
+submissions also cover “verification pearls” describing an elegant proof or
+proof technique. Submitted research papers and system descriptions must be
+original and not submitted for publication elsewhere.
+
+Papers must be submitted via EasyChair at the VSTTE 2026 conference submission
+page: https://easychair.org/conferences/?conf=vstte2026.
+
+The use of LaTeX and the Springer LNCS class files is strongly encouraged.
+
+Submissions that are not in the proper format or are too long will not be considered.
+
+Accepted regular-track papers will be included in the post-conference
+proceedings of VSTTE 2026, which will be published as a LNCS volume by
+Springer Verlag. Authors of those papers will have to transfer copyright of
+their contribution to Springer Verlag.
+
+===
+
+Invited speakers
+
+Roderick Bloem (Graz University of Technology)
+Martin Jonáš (Masaryk University, Brno)
+
+Invited tutorial
+
+Daniela Kaufmann (TU Wien)
+Omri Isac (Hebrew University of Jerusalem)
+
diff --git a/_announce/2026-07-29-cgo_2027_ae.txt b/_announce/2026-07-29-cgo_2027_ae.txt
new file mode 100644
index 00000000..ecc21203
--- /dev/null
+++ b/_announce/2026-07-29-cgo_2027_ae.txt
@@ -0,0 +1,21 @@
+---
+title: "CGO'27 Artifact Evaluation Committee: Call for nominations"
+timestamp: "7/29/2026 9:26:09"
+---
+We are looking for motivated researchers and students to serve on the CGO 2027 Artifact Evaluation Committee (AEC) (https://conf.researchr.org/home/cgo-2027).
+
+The artifact evaluation process promotes openness and reproducibility by validating, sharing, and cataloging the research artifacts accompanying papers accepted to CGO 2027.
+
+This year, we are accepting self-nominations for the AEC. The self-nomination form is available at: https://forms.gle/7JDiZTFbXhbr4MnC8
+
+Round 1 self-nominations close on August 27, 2026.
+
+CGO 2027 will follow a two-deadline structure, similar to previous years, with separate artifact evaluation phases for each submission round. We are seeking reviewers for Round 1, Round 2, or both. We anticipate a workload of 1–2 artifacts per round for each AEC member. Most artifact decisions will be made through HotCRP with asynchronous discussion. Additional details, including the evaluation timeline, are available in the self-nomination form.
+
+As an AEC member, your primary responsibility will be to evaluate artifacts associated with accepted conference papers. This may include building and running software, reproducing the experimental results reported in the paper, and inspecting the accompanying datasets and documentation.
+
+We hope you'll consider joining us in helping improve the openness, reproducibility, and quality of research in the compiler community.
+
+Best regards,
+
+Olivia Hsu and Jackson Woodruff
diff --git a/_announce/2026-08-12-planqc_2027.txt b/_announce/2026-08-12-planqc_2027.txt
new file mode 100644
index 00000000..9f62071c
--- /dev/null
+++ b/_announce/2026-08-12-planqc_2027.txt
@@ -0,0 +1,29 @@
+---
+title: "Call for Submissions - PLanQC 2027 - Programming Languages and Quantum Computing"
+timestamp: "8/12/2026 18:06:17"
+deadline: "10/30/2026"
+---
+We invite members of the programming languages and quantum computing communities to submit talk proposals for the 7th International Workshop on Programming Languages for Quantum Computing (PLanQC 2027), co-located in January 2027 with POPL in Mexico City, Mexico. The workshop will be held on January 12, 2027.
+
+Workshop website: https://popl27.sigplan.org/home/planqc-2027
+
+PLanQC aims to bring together researchers from the fields of programming languages and quantum information, exposing the programming languages community to the unique challenges of programming quantum computers. It will promote the development of tools to assist in the process of programming quantum computers, as they exist today and as they are likely to exist in the near to distant future.
+
+Submissions to PLanQC should take the form of 2–5 page abstracts (single-column, 11pt `acmsmall` style, not including references), with links to larger preprints when appropriate. Work in progress is welcome. We hope to make PLanQC maximally accessible to the programming languages community. Thus, abstracts should cover cutting-edge ideas and results, but not be opaque to new, potential entrants to quantum computing coming from programming languages. Abstracts will be reviewed for quality and relevance to the workshop, and accepted authors will be invited to give talks or poster presentations. We will not be publishing formal proceedings, but the extended abstracts, along with links (where available) to full papers will be posted to the website of the workshop.
+
+Submission link: https://planqc27.hotcrp.com/
+
+### Workshop Topics
+- High-level quantum programming languages
+- Verification tools for quantum programs
+- Novel quantum programming abstractions
+- Quantum circuit and program optimization
+- Hardware-aware circuit compilation and routing
+- Error handling, mitigation, and correction
+- Instruction sets for quantum hardware
+- Other techniques from traditional programming languages (e.g., types, compilation/optimization, foreign function interfaces) applied to the domain of quantum computation.
+
+### Important Dates
+- Submission deadline: October 30, 2026 (end of day, AoE)
+- Notification deadline: November 27, 2026 (end of day, AoE)
+- Workshop: January 12, 2027
diff --git a/_announce/2026-08-12-tum_jobs.txt b/_announce/2026-08-12-tum_jobs.txt
new file mode 100644
index 00000000..92594262
--- /dev/null
+++ b/_announce/2026-08-12-tum_jobs.txt
@@ -0,0 +1,20 @@
+---
+title: "PhD and Postdoctoral Positions at TUM - Fundamentals of Programming"
+timestamp: "8/12/2026 16:16:33"
+---
+The newly established Fundamentals of Programming Group at the Technical University of Munich (TUM) invites applications for
+
+- PhD students
+- Postdoctoral researchers
+
+Our group investigates the mathematical foundations of programming and automated reasoning about software. Our research spans programming languages and type systems, program analysis and verification, logic and automata, and the interaction between formal methods and artificial intelligence.
+
+We welcome candidates interested in topics ranging from foundational theory to the development and evaluation of algorithms and research tools.
+
+Applications will be reviewed starting September 1, 2026, and will continue to be considered until the positions are filled.
+
+Further information and application instructions are available here:
+
+https://www.cs.cit.tum.de/en/prog/open-positions/
+
+Informal inquiries are welcome at f.zuleger@tum.de.
diff --git a/_announce/2026-08-18-popl_2027_aec.txt b/_announce/2026-08-18-popl_2027_aec.txt
new file mode 100644
index 00000000..ab807e29
--- /dev/null
+++ b/_announce/2026-08-18-popl_2027_aec.txt
@@ -0,0 +1,31 @@
+---
+title: "POPL 2027 Artifact Evaluation Committee: Call for Nominations"
+timestamp: "8/18/2026 14:12:46"
+start: "8/18/2026"
+end: "9/7/2026"
+---
+TLDR: Nominate students, postdocs, and researchers for the POPL 2027 Artifact Evaluation Committee by Monday, September 7, 2026 at the following link:
+
+https://forms.gle/7uhZuQen2vxCf2ci6
+
+Please forward to your own students and institutions!
+
+—
+
+For the thirteenth year, POPL (https://popl27.sigplan.org/) is establishing an Artifact Evaluation Committee (AEC) to promote repeatable experiments in the POPL community. Last year, we received 49 submitted artifacts, resulting in 2-3 artifacts assigned to each reviewer.
+
+We are proud to announce an open call for nominations of senior graduate students, postdocs, or research community members to serve on the POPL 2027 AEC. We also encourage self-nominations. Participants will gain insight into the value of artifacts in academic publications, and a deeper understanding of the evaluation process – all while helping the community to establish and maintain norms for artifact evaluation.
+
+We strongly encourage graduate students to serve on the AEC – the artifacts provided use a wide range of systems and languages, and graduate students can be particularly well equipped to handle the diversity. Furthermore, the insight and suggestions from upcoming researchers is invaluable to improving the artifact evaluation process.
+
+The work of the AEC will be done approximately between the middle of October and the middle of November (roughly four weeks), so we are looking for people who are available during that time.
+
+Please fill out this nomination form for each nominee by Monday, September 7, 2026:
+https://forms.gle/7uhZuQen2vxCf2ci6
+
+We look forward to your nominations! Please let us know if you have any questions. Thank you for your help!
+
+Calvin Beck and Emmanuel Anaya Gonzalez
+POPL 2027 AEC Chairs
+
+
diff --git a/_announce/2026-09-14-irif_job.txt b/_announce/2026-09-14-irif_job.txt
new file mode 100644
index 00000000..c8d8a864
--- /dev/null
+++ b/_announce/2026-09-14-irif_job.txt
@@ -0,0 +1,20 @@
+---
+title: "Postdoctoral Position: Type Systems for Elixir (IRIF, Paris)"
+timestamp: "9/14/2026 5:30:54"
+---
+Dear colleagues,
+
+IRIF (Paris) is opening a postdoctoral position on gradual and semantic typing for Elixir's module system, working directly with José Valim (creator of Elixir) and the Elixir core team. The goal: extend the semantic-subtyping-based type system already shipping in the official Elixir compiler to cover its module system, treating modules and values within a single, unified type-theoretic framework.
+
+Two intertwined challenges are on the table — bringing gradual typing to modules, and reconciling existential types with the semantic subtyping framework — with a direct path from theory to a compiler used by tens of thousands of developers at companies like Apple, Discord, PepsiCo, BBC, Adobe, and Spotify.
+
+12 months (extendable), starting 1 November 2026 (negotiable, though only to a later date). CNRS salary scale. PhD in Computer Science required; strong background in functional languages and type systems expected.
+
+Full description, scientific context, and how to apply:
+https://www.irif.fr/~gc/postdocElixirModules.en.html
+
+Contact: Giuseppe Castagna (Giuseppe.Castagna@irif.fr)
+
+Best regards,
+Giuseppe Castagna
+CNRS, IRIF, Université Paris Cité
diff --git a/_announce/2026-09-19-oopsla_2027.txt b/_announce/2026-09-19-oopsla_2027.txt
new file mode 100644
index 00000000..d46af867
--- /dev/null
+++ b/_announce/2026-09-19-oopsla_2027.txt
@@ -0,0 +1,140 @@
+---
+title: "Call for Papers: OOPSLA 2027 (PACMPL) - Round 1 deadline Oct 14, 2026"
+timestamp: "9/19/2026 13:04:27"
+deadline: "10/14/2026"
+---
+========================================================================
+ PACMPL Issue OOPSLA 2027
+
+ Call for Papers
+
+ OOPSLA 2027 will be held as part of
+ The ACM SIGPLAN Conference on Systems, Programming, Languages,
+ and Applications: Software for Humanity (SPLASH 2027)
+
+ Sun 10 - Fri 15 October 2027, Prague, Czechia
+
+ https://2027.splashcon.org/track/splashoopsla2027
+========================================================================
+
+### Important dates [AoE (UTC-12h)]
+
+Submission (Round 1): Wed 14 Oct 2026
+Author Response (Round 1): Tue 1 - Sat 5 Dec 2026
+Author Notification (Round 1): Fri 18 Dec 2026
+Revision submission (Round 1): Fri 22 Jan 2027
+Author Notification (Round 1): Fri 12 Feb 2027
+Camera Ready (Round 1): Fri 5 Mar 2027
+
+Submission (Round 2): Wed 7 Apr 2027
+Author Response (Round 2): Tue 15 - Sat 19 Jun 2027
+Author Notification (Round 2): Fri 2 Jul 2027
+Revision submission (Round 2): Fri 30 Jul 2027
+Author Notification (Round 2): Fri 13 Aug 2027
+Camera Ready (Round 2): Fri 27 Aug 2027
+
+NEW THIS YEAR: No individual may be an author of more than 5 submissions
+in a given round, including no more than 2 submissions that have no
+senior authors (as defined in the Reserve Reviewer Policy).
+
+Papers accepted in either round will be published in the 2027 volume of
+PACMPL(OOPSLA) and invited to present in-person at the SPLASH conference
+in 2027. (Remote presentations will not be possible.)
+
+### Scope
+
+The OOPSLA issue of the Proceedings of the ACM on Programming Languages
+(PACMPL) welcomes papers focusing on all practical and theoretical
+investigations of programming systems, languages, and environments.
+Papers may target any stage of software development, including
+requirements, modeling, prototyping, design, implementation, generation,
+analysis, verification, testing, evaluation, maintenance, and reuse of
+software systems. Contributions may include the development of new
+tools, techniques, principles, and evaluations.
+
+### Review Process
+
+PACMPL(OOPSLA) has two rounds of reviewing. Each paper that proceeds to
+full review receives at least three reviews and an author response.
+
+*Accept*: Your paper will appear in the upcoming volume of
+PACMPL(OOPSLA).
+
+*Minor Revision*: While the Review Committee likes the work, it has some
+specific concerns that it would like to see revised. Thus, you will
+receive specific suggestions for your revised manuscript. The committee
+expects the revisions to be doable within the revision phase. You have
+the option to submit a revision by the revision deadline of the current
+round (see deadlines above), or you can wait until the next round.
+
+*Major Revision*: While the Review Committee thinks the direction of the
+work has promise, it has significant concerns that it would like to see
+revised. You may receive some specific required revisions, but will also
+receive broader comments that may take significantly longer to execute.
+For this reason, you cannot submit a revision by the revision deadline
+of the current round, but you have to wait until the next round.
+
+*Reject*: Your paper will not appear in the upcoming volume of
+PACMPL(OOPSLA). In addition, a paper that is rejected in Round 1 is not
+allowed to be resubmitted in Round 2. A paper is considered a
+resubmission if, in the judgment of the Chairs, it is substantially
+similar to the original submission. This restriction applies only within
+OOPSLA 2027: a paper that is rejected in Round 2 is allowed to resubmit
+to Round 1 of OOPSLA 2028, and papers rejected from OOPSLA 2026 (in
+either round) are welcome at OOPSLA 2027.
+
+The Chairs may desk-reject a submission without full review if it
+violates the policies in this call, or if the Chairs, in consultation
+with an Associate Chair or reviewer, judge it clearly below the bar for
+OOPSLA. Desk-rejected papers receive a brief notification and count as
+rejected for the no-resubmission rule.
+
+At least one author of a paper submission must be registered as a
+Reserve Reviewer as per the Reserve Reviewer Policy.
+
+### Submissions
+
+Initial submissions must be at most 23 pages using the template. This
+page limit does not include required statements, references, or
+supplementary material (such as appendices). However, papers must be
+self-contained; reviewers are under no obligation to read the
+supplementary material. Revisions can correspondingly go up to a maximum
+of 25 pages.
+
+PACMPL uses double-blind reviewing. Authors’ identities are only
+revealed if a paper is accepted. Your papers must
+
+- omit author names and institutions,
+- use the third person when referencing your work,
+- anonymize supplementary material.
+
+Papers must describe unpublished work that is not currently submitted
+for publication elsewhere as described by SIGPLAN’s Re-Publication
+Policy.
+
+### Artifacts
+
+To help readers understand the state of the intended artifact, we ask
+you to add a section just before references titled Data-Availability
+Statement in the initial submission. In it, indicate whether an artifact
+exists, its nature and limitations, and whether it will be submitted for
+Artifact Evaluation.
+
+It is understood that some papers have no artifacts but, given the broad
+range of what constitutes an artifact, it would be helpful to readers to
+explain why the paper has none.
+
+### Publication
+
+The official publication date is the date the journal is made available
+in the ACM Digital Library. The journal issue and associated papers
+accepted in Round 1 (OOPSLA1) will be published no earlier than April 1,
+2027, while those accepted in Round 2 (OOPSLA2) will be published no
+earlier than October 1, 2027.
+
+### Additional Information
+
+Please submit using HotCRP: https://oopsla27.hotcrp.com/
+
+Contact: oopsla-2027-rc-chairs@googlegroups.com
+
diff --git a/_announce/2026-09-24-tfpie_2027.txt b/_announce/2026-09-24-tfpie_2027.txt
new file mode 100644
index 00000000..438c1cc5
--- /dev/null
+++ b/_announce/2026-09-24-tfpie_2027.txt
@@ -0,0 +1,71 @@
+---
+title: "Call for Papers, Trends in Functional Programming in Education (TFPIE 2027)"
+timestamp: "9/24/2026 9:48:51"
+deadline: "11/19/2026"
+---
+-------------------------------------------------------
+Call for Papers
+TFPIE 2027: The 16th International Workshop on
+Trends in Functional Programming in Education
+March 12th 2027, Kyoto, Japan, co-located with TFP 2027
+https://wiki.tfpie.science.ru.nl/TFPIE2027
+-------------------------------------------------------
+
+## Topics
+
+TFPIE welcomes submissions describing classroom techniques, classroom tools, and creative uses of functional programming (FP) to aid education in or outside computer science. Topics of interest include, but are not limited to:
+
+* FP at different levels (high school, first-year and advanced undergraduate, graduate)
+* FP and the arts (incl. music, animation, games, philosophy and other liberal arts)
+* FP and applications (in computer science, robotics, artificial intelligence, etc.)
+* FP and pedagogy (incl., e.g., computational thinking, e-learning, automated assessment)
+* FP for building student engagement in research
+
+In addition to papers, we invite best-lecture presentations. These are an opportunity to share your favorite classroom moments. Show us your favorite material or favorite way of presenting it. For best-lecture presentations, please submit a short abstract describing the lecture and its interest to TFPIE attendees.
+
+## Submission Instructions
+
+Submission is via EasyChair:
+
+https://easychair.org/my/conference?conf=tfpie2027
+
+Authors of papers have the choice of having their contributions formally reviewed either before or after the workshop. Further, pre-workshop submissions may either be full (earlier deadline) or draft papers (later deadline). See below for more details.
+
+Accepted papers from the pre-workshop and post-workshop formal review will appear in a formal proceedings, published in the Electronic Proceedings in Theoretical Computer Science (EPTCS).
+
+Reviewing is single-blind.
+
+### Pre-workshop formal review
+
+Papers to be formally reviewed before the workshop should be submitted before the early deadline and will receive their reviews and notification of acceptance for both presentation and publication before the workshop. A paper that has been rejected for publication but accepted for presentation may be revised and resubmitted for the post-workshop formal review. A paper that has been rejected for presentation will not be formally reviewed by the PC.
+
+### Post-workshop formal review
+
+Draft papers will receive minimal reviews and notification of acceptance for presentation at the workshop. Authors of draft papers will be invited to submit revised papers based on the feedback received at the workshop. A post-workshop refereeing process will then select a subset of these papers for formal publication.
+
+### Formatting requirements
+
+Papers must be written in English, and formatted using the EPTCS style (https://style.eptcs.org/). Papers submitted for formal review must be submitted as full papers (7-20 pages). Draft papers may be submitted as extended abstracts (4-6 pages) or full papers (7-20 pages). The page limits do not include bibliography. For best-lecture presentations, we also accept short abstracts.
+
+If you wish to make a submission outside the above formats, please contact the PC chair to discuss. Because TFPIE aims to encourage creative and experimental research ideas, we may be able to accommodate some non-traditional submissions on a case-by-case basis.
+
+## Important Dates
+
+All deadlines are Anywhere-on-Earth.
+
+* Submission deadline (pre-workshop full papers): November 19, 2026
+* Notification (pre-workshop full papers): December 17, 2026
+* Submission deadline (pre-workshop draft papers): February 4, 2027
+* Notification (pre-workshop draft papers): February 11, 2027
+* Submission deadline (post-workshop review): April 8, 2027
+* Notification (post-workshop review): May 12, 2027
+
+## Program Committee
+
+* Youyou Cong (chair) - Institute of Science Tokyo, Japan
+* Hsiang-Shang 'Josh' Ko - Academia Sinica, Taiwan
+* Jens Mönig - SAP, Germany
+* Paige Randall North - Utrecht University, Netherlands
+* Liam O'Connor - Australian National University, Australia
+* Joe Gibbs Politz - University of California at San Diego, USA
+* Katsuhiro Ueno - Niigata University, Japan
diff --git a/_announce/2026-10-07-aeic_2027.txt b/_announce/2026-10-07-aeic_2027.txt
new file mode 100644
index 00000000..36e7f024
--- /dev/null
+++ b/_announce/2026-10-07-aeic_2027.txt
@@ -0,0 +1,284 @@
+---
+title: "CfC 31st Ada-Europe Int. Conf. Reliable Software Technologies, AEiC 2027"
+timestamp: "10/7/2026 5:17:22"
+deadline: "1/25/2027"
+---
+-----------------------------------------------------------------------
+
+Call for Contributions
+
+31st Ada-Europe International Conference on
+Reliable Software Technologies (AEiC 2027)
+
+8-11 June 2027, Berlin, Germany
+
+www.ada-europe.org/conference2027
+
+*** Journal track submissions by 25 January 2027 ***
+*** Work-in-progress papers by 22 March 2027 ***
+*** All other submissions by 8 February 2027 ***
+
+Organized by Ada-Europe, Ada-Germany, and GI FG Ada,
+in cooperation with ACM SIGPLAN
+
+#AEiC2027 #AdaEurope #AdaProgramming
+
+-----------------------------------------------------------------------
+
+*** General Information
+
+The 31st Ada-Europe International Conference on Reliable Software
+Technologies (AEiC 2027) will take place in Berlin, Germany.
+The conference schedule comprises keynote talks, a journal track, an
+industrial track, a regular papers track, a work-in-progress track,
+a vendor exhibition, parallel tutorials, and satellite workshops.
+
+- Journal track papers present journal-level research advances supported
+ by solid theoretical foundation and thorough evaluation.
+- Regular track papers present conference-level (full paper) research
+ advances.
+- Industrial track contributions highlight industrial open challenges
+ and/or the practitioners' side of a challenging case study or
+ industrial project.
+- Work-in-progress track papers illustrate novel research ideas that are
+ still at an initial stage, between conception and first prototype.
+- Tutorials guide attenders through a hands-on familiarization with
+ innovative developments or with useful features related to reliable
+ software.
+- Workshops provide discussion forums on the conference topics.
+- Company presentations and exhibitions to showcase products & services.
+
+*** Schedule
+
+- 25 January 2027: Deadline for submission of journal track papers
+- 8 February 2027: Deadline for submission of industrial track
+ abstracts, regular track papers, tutorial and workshop proposals
+- 15 March 2027: First round notification for journal track papers,
+ and notification of acceptance for all other types of submissions
+- 22 March 2027: Deadline for submission of work-in-progress papers
+- 5 April 2027: Notification for work-in-progress papers
+
+*** Scope and Topics
+
+The conference is a leading international forum for providers,
+practitioners, and researchers in reliable software technologies.
+The conference presentations will illustrate current work in the theory
+and practice of the design, development, and maintenance of long-lived,
+high-quality software systems for a challenging variety of application
+domains. The program will allow ample time for keynotes, Q&A sessions,
+discussions, and social events. Participants include practitioners and
+researchers from industry, academia, and government organizations active
+in the promotion and development of reliable software technologies.
+
+The topics of interest for the conference include but are not
+limited to:
+- Cyber Security;
+- Safe and secure software for critical systems and infrastructures;
+- High-integrity systems and reliability;
+- Software and AI for space missions, e.g. Artemis;
+- AI for safety-critical and high-integrity systems engineering and
+ applications;
+- Automated coding for real-time and embedded systems;
+- Ada language and technologies;
+- SPARK, Rust and formally verified systems;
+- Formal methods, testing, and model-based engineering of critical
+ systems;
+- Applications and experimental evaluations in relevant domains.
+
+More specific topics and submission methods are described on the
+conference web page.
+
+*** Call for Journal Track Submissions
+
+The conference includes a journal track, which seeks original and
+high-quality papers, not submitted elsewhere, which describe mature
+research work on the conference topics. Accepted journal track papers
+will be published in a Special Issue of Elsevier's JSA
+(www.sciencedirect.com/special-issue/335680/reliable-software-technologies-aeic2027)
+- the Journal of Systems Architecture (Q1 ranked, CiteScore 10.5, impact
+factor 4.1). Contributions should not exceed 25 pages (in case the
+authors need more pages the journal track chairs need to be contacted).
+
+JSA has adopted the Virtual Special Issue model to speed up the
+publication process, where Special Issue (SI) papers are published in
+regular issues but marked as SI papers. Acceptance decisions are made
+on a rolling basis. Therefore, authors are encouraged to submit papers
+early and need not wait until the submission deadline. Authors who
+have successfully passed the first round of review (including major
+revisions) will be invited (and required) to present their work at
+the conference.
+
+*** Call for Regular Track Submissions
+
+The conference includes a regular track, which seeks proceedings-level,
+original and high-quality submissions, not submitted elsewhere, which
+describe mature research work on the conference topics. Accepted papers
+presented at the conference will be published in the Open Access Series
+in Informatics (OASICS series: drops.dagstuhl.de/entities/series/OASIcs)
+and should be formatted according to the one-column format, not
+exceeding 16 pages, excluding references.
+
+*** Call for Industrial Track Submissions
+
+The conference seeks industrial-practitioner presentations that
+deliver insight into the challenges of developing reliable software.
+Especially welcome kinds of submissions are listed on the conference
+web site. Given their applied nature, such contributions will be
+subject to a peer-review process by practitioners. Interested authors
+shall submit a 2-page abstract. Authors will also be invited to expand
+their contributions into full-fledged articles for publication in the
+Ada User Journal (www.ada-europe.org/auj/scope/), which will form the
+proceedings of the industrial track of the Conference.
+
+*** Call for Work-in-progress Track Submissions
+
+The work-in-progress (WiP) track seeks two kinds of submissions:
+(a) ongoing research and (b) early-stage ideas. Ongoing research
+submissions are 4-page papers describing research results that are
+not mature enough to be submitted to the journal or regular tracks.
+Early-stage ideas are 1-page summaries that pitch new research
+directions within the scope of the conference. Both kinds of
+submissions must be original and shall undergo anonymous peer review.
+Submissions by recent M.Sc. graduates and Ph.D. students are especially
+sought. Accepted contributions will be presented in the WiP track
+and their authors will be offered the opportunity to publish their
+contribution as an expanded 4-page article in the Ada User Journal
+(www.ada-europe.org/auj/scope/), which will form the proceedings of
+the WiP track of the conference.
+
+*** Academic Listing
+The Journal of Systems Architecture, publication venue of the
+journal-track proceedings of the conference, is Q1 ranked, with
+CiteScore 10.5 and Impact Factor 4.1. The OASIcs series, venue for
+regular track proceedings, provides Open Access online publications,
+and is indexed by Scopus and DBPL. The Ada User Journal, venue of the
+other technical proceedings of the conference, is indexed by Scopus
+and by EBSCOhost in the Academic Search Ultimate database.
+
+*** Conference Booklet
+The abstract of the accepted contributions (journal, regular,
+industrial, work in progress) will be included in the conference
+booklet, which will be distributed to all participants, and made
+available online.
+
+*** Award
+The Ada-Europe organization will offer an honorary award for the best
+technical presentation, to be announced in the closing session of
+the conference.
+
+*** Call for Tutorials
+
+The conference seeks tutorials in the form of educational seminars on
+themes falling within the conference scope. Tutorial proposals shall
+include a title, an abstract, a description of the topic, an outline
+of the presentation, the proposed duration (half-day or full-day),
+the intended level of the contents (introductory, intermediate, or
+advanced), and a statement motivating attendance. If the tutorial
+has been presented elsewhere attendance numbers should be given.
+Tutorial proposals can be submitted at any time but no later than the
+deadline. The authors of accepted full-day tutorials will receive a
+complimentary conference registration, halved for half-day tutorials.
+The Ada User Journal will offer space for the publication of summaries
+of the accepted tutorials.
+
+*** Call for Workshops
+
+The conference welcomes satellite workshops on themes that fall
+within the conference scope. Proposals may be submitted for half-
+or full-day events, to be scheduled on Tuesday or Friday of the AEiC
+conference. Workshop organizers shall also commit to producing the
+proceedings of the event, for publication in the Ada User Journal.
+Workshop proposals can be submitted at any time but no later than the
+deadline. Once submitted, each workshop proposal will be evaluated
+by the conference organizers as soon as possible.
+
+*** Call for Exhibitors and Sponsors
+
+The conference seeks vendor and technology exhibits as well as event
+sponsors. Exhibitors and sponsors will be given the opportunity for
+presentation; details are available on request.
+
+*** Venue
+
+The conference is in-person, and will take place at the Holiday Inn
+Berlin City-West, Rohrdamm 80, 13629 Berlin. Rooms have been set
+aside at the hotel. Attendees are urged to stay at the hotel.
+
+Berlin is the capital of Germany. Thriving in the past, bombed,
+divided, reunited and reborn - Berlin's turbulent past gives it
+a unique energy. With famous museums, a vibrant cultural scene,
+and diverse neighborhoods, German's capital feels both historic and
+forward-looking. And as the birthplace of Konrad Zuse and the first
+modern computer, Berlin is the perfect backdrop for bringing Europe's
+reliable software community together.
+
+Berlin is easily reachable by train or national and international
+flights to one of its airports. The Berlin of today is a young and
+vibrant city and yet offers plenty of famous museums and historic
+landmarks like the Charlottenburg castle nearby.
+
+*** Organizing Committee
+
+- General chairs
+ Hubert B. Keller, ci-tec GmbH
+ Erhard Plödereder, Universität Stuttgart
+ Detlef Streitferdt, TU Ilmenau
+ Christina Unger, OKAPI:Orbits GmbH
+
+- Journal track co-chairs
+ Georg Jäger, TU Bergakademie Freiberg
+ Luis Miguel Pinho, Technical University of Porto
+
+- Paper track chair
+ Erhard Plödereder
+
+- Industrial track chair
+ Peter Dencker, HS Karlsruhe
+
+- Exhibition & sponsorship co-chairs
+ Detlef Streitferdt,
+ Peter Dencker
+
+- Finance chair
+ Ahlan Marriott, White Elephant GmbH
+
+- Publicity chair
+ Dirk Craeynest, Ada-Belgium & KU Leuven
+
+- Webmaster
+ Christina Unger
+
+- Local chair
+ Dirk C. Pinnow, datensicherheit.de Berlin
+
+Contact for any questions to the chairs: AEiC2027@ada-deutschland.de
+
+*** Previous Editions
+
+Ada-Europe organizes annual international conferences since the early
+80's. This is the 31st event in the Reliable Software Technologies
+series, previous ones being held at Montreux, Switzerland ('96),
+London, UK ('97), Uppsala, Sweden ('98), Santander, Spain ('99),
+Potsdam, Germany ('00), Leuven, Belgium ('01), Vienna, Austria
+('02), Toulouse, France ('03), Palma de Mallorca, Spain ('04), York,
+UK ('05), Porto, Portugal ('06), Geneva, Switzerland ('07), Venice,
+Italy ('08), Brest, France ('09), Valencia, Spain ('10), Edinburgh, UK
+('11), Stockholm, Sweden ('12), Berlin, Germany ('13), Paris, France
+('14), Madrid, Spain ('15), Pisa, Italy ('16), Vienna, Austria ('17),
+Lisbon, Portugal ('18), Warsaw, Poland ('19), online from Santander,
+Spain ('21), Ghent, Belgium ('22), Lisbon, Portugal ('23), Barcelona,
+Spain ('24), Paris, France ('25), and Västerås, Sweden ('26).
+
+Information on previous editions of the conference can be found at
+www.ada-europe.org/confs/ae.
+
+-----------------------------------------------------------------------
+
+Our apologies if you receive multiple copies of this announcement.
+Please circulate widely.
+
+Dirk Craeynest, AEiC 2027 Publicity Chair
+Dirk.Craeynest@cs.kuleuven.be Dirk.Craeynest@kuleuven.be
+
+* 31st Ada-Europe Int.Conf. Reliable Software Technologies (AEiC 2027)
+* June 8-11, 2027, Berlin, Germany * www.ada-europe.org/conference2027
diff --git a/_announce/2026-10-08-ohio_state_job.txt b/_announce/2026-10-08-ohio_state_job.txt
new file mode 100644
index 00000000..4b7232bc
--- /dev/null
+++ b/_announce/2026-10-08-ohio_state_job.txt
@@ -0,0 +1,5 @@
+---
+title: "Tenure-track faculty PL position at Ohio State University"
+timestamp: "10/8/2026 15:20:59"
+---
+The Department of Computer Science and Engineering (CSE) in the College of Engineering at The Ohio State University invites applications for a tenured/tenure-track faculty position at the Assistant/Associate/Full Professor level to advance innovative research and development in the Programming Languages & Software Engineering (PLSE) areas. The successful candidate for this endowed position will also be named the Timashev (Assistant/Associate/Full) Professor. This position is located on the main Columbus campus of The Ohio State University and starts as early as Fall 2027.
diff --git a/_data/AVCommittee.yaml b/_data/AVCommittee.yaml
index df0bc023..2f4c29d5 100644
--- a/_data/AVCommittee.yaml
+++ b/_data/AVCommittee.yaml
@@ -1,41 +1,43 @@
active:
+ - name: One An
+ image: https://conf.researchr.org/getProfileImage/onean/d9b1b2a0-8472-4cc8-b62c-4d45f8ecd688/small
- name: Samar Rahmouni
- image: https://conf.researchr.org/getProfileImage/samarrahmouni/6f645dc0-d11c-40c9-a5a3-fb13c5253bab/small.jpg?1752740414000
+ image: https://conf.researchr.org/getProfileImage/samarrahmouni/6f645dc0-d11c-40c9-a5a3-fb13c5253bab/small
- name: Eloise Christian
- image: https://conf.researchr.org/getProfileImage/eloisechristian/d57f17a2-1fe5-44bb-b62e-748f84eaddeb/small.jpg?1737203033000
+ image: https://conf.researchr.org/getProfileImage/eloisechristian/d57f17a2-1fe5-44bb-b62e-748f84eaddeb/small
- name: Angel Pavlov Angelov
- image: https://conf.researchr.org/getProfileImage/angelpavlovangelov/15eb4cf1-1dda-4974-a86e-fe29eb709fe7/small.jpg?1733760295000
- - name: Nicole Heinimann
- image: https://conf.researchr.org/getProfileImage/nicoleheinimann/05e5f59c-af9b-43d6-a4dc-0edac3ab80ba/avatar.jpg
- - name: Nicola Assolini
- image: https://conf.researchr.org/getProfileImage/nicolaassolini/98016cbe-ba0a-4352-9297-31fc38c63b75/avatar.jpg
+ image: https://conf.researchr.org/getProfileImage/angelpavlovangelov/15eb4cf1-1dda-4974-a86e-fe29eb709fe7/small
- name: Eduardo Madeira
- image: https://conf.researchr.org/getProfileImage/eduardomadeira/42073539-cbf3-4609-b04b-0a63287afd82/small.jpg
+ image: https://conf.researchr.org/getProfileImage/eduardomadeira/42073539-cbf3-4609-b04b-0a63287afd82/small
- name: Alexander Bai
- image: https://conf.researchr.org/getProfileImage/alexanderbai/dc1a164a-690d-4c08-926d-de8f9ab476d5/small.jpg
+ image: https://conf.researchr.org/getProfileImage/alexanderbai/dc1a164a-690d-4c08-926d-de8f9ab476d5/small
- name: Chris Lam
- image: https://conf.researchr.org/getProfileImage/christopherlam1/00386a60-bf17-48da-8942-0d2815d7fa08/small.jpg
+ image: https://conf.researchr.org/getProfileImage/christopherlam1/00386a60-bf17-48da-8942-0d2815d7fa08/small
- name: Jan-Paul Ramos
- image: https://conf.researchr.org/getProfileImage/janpaulramosdavila/156687da-3cdb-4157-b31e-636bb71b31dc/small.jpg
+ image: https://conf.researchr.org/getProfileImage/janpaulramosdavila/156687da-3cdb-4157-b31e-636bb71b31dc/small
emeritus:
+ - name: Nicole Heinimann
+ image: https://conf.researchr.org/getProfileImage/nicoleheinimann/05e5f59c-af9b-43d6-a4dc-0edac3ab80ba/small
+ - name: Nicola Assolini
+ image: https://conf.researchr.org/getProfileImage/nicolaassolini/98016cbe-ba0a-4352-9297-31fc38c63b75/small
- name: Ethan Range
- image: https://conf.researchr.org/getProfileImage/ethanrange/a82e09a2-116a-4794-a499-13496f915d0a/small.jpg
+ image: https://conf.researchr.org/getProfileImage/ethanrange/a82e09a2-116a-4794-a499-13496f915d0a/small
- name: Guilherme Espada
- image: https://conf.researchr.org/getProfileImage/guilhermeespada/221aa9ee-6215-4712-b6df-a5a09d269e04/small.jpg
+ image: https://conf.researchr.org/getProfileImage/guilhermeespada/221aa9ee-6215-4712-b6df-a5a09d269e04/small
- name: Apoorv Ingle
- image: https://conf.researchr.org/getProfileImage/apoorvingle/76632b78-6d6b-4f2e-9c36-af0a9e1a5fdb/small.jpg
+ image: https://conf.researchr.org/getProfileImage/apoorvingle/76632b78-6d6b-4f2e-9c36-af0a9e1a5fdb/small
- name: Max Sun
- image: https://conf.researchr.org/getProfileImage/maxsun/7f927b55-626c-4c5c-9ac8-e10beb3d0b76/small.jpg
+ image: https://conf.researchr.org/getProfileImage/maxsun/7f927b55-626c-4c5c-9ac8-e10beb3d0b76/small
- name: John Hui
- image: https://conf.researchr.org/getProfileImage/johnhui/54a9a819-59d8-4b2c-96f8-76f813666876/small.jpg
+ image: https://conf.researchr.org/getProfileImage/johnhui/54a9a819-59d8-4b2c-96f8-76f813666876/small
- name: Zixian Cai
- image: https://conf.researchr.org/getProfileImage/zixiancai/22d210bf-85c3-49e6-8278-4ea50f3290dd/small.jpg
+ image: https://conf.researchr.org/getProfileImage/zixiancai/22d210bf-85c3-49e6-8278-4ea50f3290dd/small
- name: Jessica Foster
- image: https://icfp24.sigplan.org/getProfileImage/jessicafoster/447e864c-9571-4c54-9f51-0e78d5d07ea4/small.jpg
+ image: https://icfp24.sigplan.org/getProfileImage/jessicafoster/447e864c-9571-4c54-9f51-0e78d5d07ea4/small
- name: Bhakti Shah
- image: https://conf.researchr.org/getProfileImage/bhaktishah/624a5a4c-260a-43c9-b37a-eff79a3654f5/small.jpg
+ image: https://conf.researchr.org/getProfileImage/bhaktishah/624a5a4c-260a-43c9-b37a-eff79a3654f5/small
- name: Leif Andersen
- image: https://conf.researchr.org/getProfileImage/leifandersen/022e7f05-2a9a-4e3d-8be9-418b798e00c0/small.jpg
+ image: https://conf.researchr.org/getProfileImage/leifandersen/022e7f05-2a9a-4e3d-8be9-418b798e00c0/small
- name: Benjamin Chung
- image: https://conf.researchr.org/getProfileImage/benjaminchung/30978af0-bcee-4c1e-9dd1-f2588ea14f38/small.jpg
+ image: https://conf.researchr.org/getProfileImage/benjaminchung/30978af0-bcee-4c1e-9dd1-f2588ea14f38/small
diff --git a/_data/Committees.yaml b/_data/Committees.yaml
index e877dad0..430aae50 100644
--- a/_data/Committees.yaml
+++ b/_data/Committees.yaml
@@ -34,7 +34,7 @@ Information Director:
- ACM Program Director: "[Abigail Sumandal](mailto:sumandal@hq.acm.org)"
- SIGPLAN Information Director: "[Adrian Sampson](https://www.cs.cornell.edu/~asampson/) (Cornell University)"
- Editor of FORTRAN Forum: "[Ian Chivers](mailto:ian.chivers@chiversandbryan.co.uk)"
- - ACM TOPLAS Editors: "[Jan Vitek](https://janvitek.org/)"
+ - ACM TOPLAS Editors: "[Alastair F Donaldson](https://www.doc.ic.ac.uk/~afd/)"
- Steering Committee Chairs:
# leave these blank to autolookup from the Steering Committees
- ASPLOS:
@@ -80,7 +80,7 @@ CGO Steering Committee:
- Jingling Xue, UNSW
DLS Steering Committee:
- - Chair: "[Stefan Marr](https://www.kent.ac.uk/computing/people/3167/marr-stefan)"
+ - Chair: "[Stefan Marr](https://ssw.jku.at/General/Staff/Marr/)"
- Davide Ancona
- Wolfgang De Meuter
- Matthew Flatt
@@ -129,7 +129,7 @@ LCTES Steering Committee:
- Zheng Zhang, Rutgers University
MPLR Steering Committee:
- - Chair: "[Stefan Marr](https://www.kent.ac.uk/computing/people/3167/marr-stefan)"
+ - Chair: "[Stefan Marr](https://ssw.jku.at/General/Staff/Marr/)"
- "[Elisa Gonzalez Boix](https://soft.vub.ac.be/disco/elisa/)"
- "[Tobias Wrigstad](https://www.it.uu.se/katalog/writo649)"
- "[J. Eliot Moss](https://www.cics.umass.edu/about/directory/j-eliot-moss)"
@@ -141,18 +141,39 @@ MPLR Steering Committee:
- "[Christophe Scholliers](https://users.ugent.be/~chscholl/)"
Onward! Steering Committee:
- - Chair: Stephen Kell
- - Robert Biddle
- - Richard P. Gabriel
- - Elisa Gonzalez Boix
- - Robert Hirschfeld
- - Hidehiko Masuhara
- - Gail Murphy
- - Tomas Petricek
- - Benjamin C. Pierce
- - Yannis Smaragdakis
- - Emina Torlak
- - Jan Vitek
+ - Chair: Colin S. Gordon
+ - Shigeru Chiba
+ - Jonathan Edwards
+ - Felienne Hermans
+ - Robert Hirschfeld
+ - Stephen Kell
+ - Clemens Nylandsted Klokmose
+ - Marcel Taeumel
+ - Sverrir Thorgeirsson
+ - Tijs van der Storm
+
+OOPSLA Steering Committee:
+# A strict subset of the SPLASH Steering Committee below: future, current, and past three
+# SPLASH General Chairs, and future, current, and past three OOPSLA RC (Program) Co-Chairs.
+# Chaired by the SPLASH Steering Committee Chair by default.
+# In 2027 the past three years are 2026, 2025, and 2024.
+ - Chair: Frank Tip (Northeastern University), SPLASH Steering Committee Chair, SPLASH 2026 General Chair
+
+ - Jeremy Singer (University of Glasgow), SPLASH 2029 General Chair
+ - Michael Pradel (CISPA Helmholtz Center for Information Security/University of Stuttgart), OOPSLA 2028 Review Committee Co-Chair
+ - Alexandra Silva (Cornell University), OOPSLA 2028 Review Committee Co-Chair
+ - Vivek Sarkar (Georgia Institute of Technology), SPLASH 2028 General Chair
+ - Filip Křikava (Czech Technical University), SPLASH 2027 General Chair
+ - Nadia Polikarpova (University of California San Diego), OOPSLA 2027 Review Committee Co-Chair
+ - Ilya Sergey (National University of Singapore), OOPSLA 2027 Review Committee Co-Chair
+ - Anders Møller (Aarhus University), OOPSLA 2026 Review Committee Co-Chair
+ - Işil Dillig (University of Texas at Austin), OOPSLA 2026 Review Committee Co-Chair
+ - Charles Zhang (Hong Kong University of Science and Technology), SPLASH 2025 General Chair
+ - Shriram Krishnamurthi (Brown University), OOPSLA 2025 Review Committee Co-Chair
+ - Sukyoung Ryu (Korea Advanced Institute of Science and Technology), OOPSLA 2025 Review Committee Co-Chair
+ - Manu Sridharan (UC Riverside), SPLASH 2024 General Chair
+ - Alex Potanin (Australian National University), OOPSLA 2024 Review Committee Co-Chair
+ - Bor-Yuh Evan Chang (University of Colorado Boulder), OOPSLA 2024 Review Committee Co-Chair
PLDI Steering Committee:
- SIGPLAN Chair: #
@@ -207,32 +228,34 @@ SIGAPL Steering Committee:
SPLASH Steering Committee:
- SIGPLAN Chair: #
- SIGPLAN Vice Chair: #
- - Chair: Alex Potanin (Australian National University), OOPSLA 2024 Program Co-Chair, SC Chair for 2025 - 2026 2-year term
+ - Chair: Frank Tip (Northeastern University), SPLASH 2026 General Chair, SC Chair for 2027 - 2028
+ - Jeremy Singer (University of Glasgow), SPLASH 2029 General Chair
+ - Vivek Sarkar (Georgia Institute of Technology), SPLASH 2028 General Chair
+ - Michael Pradel (CISPA Helmholtz Center for Information Security/University of Stuttgart), OOPSLA 2028 Review Committee Co-Chair
+ - Alexandra Silva (Cornell University), OOPSLA 2028 Review Committee Co-Chair
- Filip Křikava (Czech Technical University), SPLASH 2027 General Chair
- - Frank Tip (Northeastern University), SPLASH 2026 General Chair
- - Charles Zhang (Hong Kong University of Science and Technology), SPLASH 2025 General Chair
- - Manu Sridharan (UC Riverside), SPLASH 2024 General Chair
- - Vasco T. Vasconcelos (University of Lisbon), SPLASH 2023 General Chair
- - Nadia Polikarpova (University of California San Diego), OOPSLA 2027 Program Co-Chair
- - Ilya Sergey (National University of Singapore), OOPSLA 2027 Program Co-Chair
- - Anders Møller (Aarhus University), OOPSLA 2026 Program Co-Chair
- - Işil Dillig (University of Texas at Austin), OOPSLA 2026 Program Co-Chair
- - Shriram Krishnamurthi (Brown University), OOPSLA 2025 Program Co-Chair
- - Sukyoung Ryu (Korea Advanced Institute of Science and Technology), OOPSLA 2025 Program Co-Chair
- - Bor-Yuh Evan Chang (University of Colorado Boulder), OOPSLA 2024 Program Co-Chair
- - Mira Mezini (TU Darmstadt), OOPSLA 2023 Program Chair
+ - Nadia Polikarpova (University of California San Diego), OOPSLA 2027 Review Committee Co-Chair
+ - Ilya Sergey (National University of Singapore), OOPSLA 2027 Review Committee Co-Chair
+ - Işil Dillig (University of Texas at Austin), OOPSLA 2026 Review Committee Co-Chair
+ - Anders Møller (Aarhus University), OOPSLA 2026 Review Committee Co-Chair
- Sverrir Thorgeirsson (ETH Zurich), Onward! 2026 Papers Chair
- Felienne Hermans (Vrije Universiteit Amsterdam), Onward! 2026 Essays Chair
+ - Charles Zhang (Hong Kong University of Science and Technology), SPLASH 2025 General Chair
+ - Shriram Krishnamurthi (Brown University), OOPSLA 2025 Review Committee Co-Chair
+ - Sukyoung Ryu (Korea Advanced Institute of Science and Technology), OOPSLA 2025 Review Committee Co-Chair
+ - Colin Gordon (Drexel University), Onward! 2025 Essays Chair, Onward! Steering Committee Chair
- Shigeru Chiba (University of Tokyo), Onward! 2025 Papers Co-Chair
- Clemens Nylandsted Klokmose (Aarhus University), Onward! 2025 Papers Co-Chair
- - Colin Gordon (Drexel University), Onward! 2025 Essays Chair
- - Stephen Kell (Kings College London), Onward! Steering Committee Chair
- - Kedar Namjoshi (Nokia), SAS Steering Committee Co-Chair
- - Cezara Dragoi (INRIA), SAS Steering Committee Co-Chair
- - Coen de Roover (Vrije Universiteit Brussel), GPCE Steering Committee Chair
- - Eric van Wyk (University of Minnesota), SLE Steering Committee Chair
+ - Manu Sridharan (UC Riverside), SPLASH 2024 General Chair
+ - Alex Potanin (Australian National University), OOPSLA 2024 Review Committee Co-Chair
+ - Bor-Yuh Evan Chang (University of Colorado Boulder), OOPSLA 2024 Review Committee Co-Chair
+ - Caterina Urban (INRIA, École Normale Supérieure), SAS Steering Committee Co-Chair in 2027
+ - Gagandeep Singh (University of Illinois Urbana-Champaign), SAS Steering Committee Co-Chair in 2027
+ - Coen de Roover (Vrije Universiteit Brussel), GPCE Steering Committee Chair in 2026
+ - Eric van Wyk (University of Minnesota), SLE Steering Committee Chair in 2026
- Amal Ahmed (Northeastern University), Member at Large 2026 - 2029
+ - Robert Hirschfeld (Hasso Plattner Institute), Member at Large 2027 - 2030
VEE Steering Committee:
- Andrew Baumann, Microsoft Research
diff --git a/_data/Conferences.yaml b/_data/Conferences.yaml
index 7b99a222..44c4e674 100644
--- a/_data/Conferences.yaml
+++ b/_data/Conferences.yaml
@@ -5,10 +5,14 @@
# (E.g., should CGO be included? Should CC?) How should the list be
# sorted? -->
#
-#
+#
+#
-
name: Principles of Programming Languages (POPL)
@@ -70,9 +74,6 @@
several SIGPLAN conferences and symposium, including:
- [OOPSLA](/Conferences/OOPSLA)
- [Onward](/Conferences/Onward)
- - [DLS](/Conferences/DLS)
- - [GPCE](/Conferences/GPCE)
- - [SLE](/Conferences/SLE)
-
name: Compiler Construction (CC)
@@ -95,6 +96,7 @@
static to fully dynamic approaches, including techniques ranging
from pure software-based methods to architectural features and
support.
+ CGO is co-sponsored with [SIGMICRO](https://www.sigmicro.org).
-
name: Dynamic Languages Symposium (DLS)
@@ -102,10 +104,11 @@
description: |
The Dynamic Languages Symposium (DLS) is a forum for discussion of
dynamic languages, their implementation, and application.
+ inactive: true
-
name: 'Generative Programming: Concepts and Experiences (GPCE)'
- link: 'http://program-transformation.org/Gpce'
+ link: '/Conferences/GPCE'
description: |
Generative Programming: Concepts & Experiences is a conference
promoting the application and innovation of foundational techniques
@@ -132,6 +135,7 @@
expose researchers and developers from either area to relevant work
and interesting problems in the other area and provide a forum
where they can interact.
+ LCTES is co-sponsored with [SIGBED](https://sigbed.org).
-
name: Haskell Symposium (HS)
@@ -174,7 +178,7 @@
-
name: Software Language Engineering (SLE)
- link: 'http://www.sleconf.org/'
+ link: 'https://www.sleconf.org/'
description: |
The International Conference on Software Language Engineering (SLE) is
devoted to the engineering principles of software languages: their
@@ -204,6 +208,7 @@
among a number of different venues in the languages (VM, PLDI,
OOPSLA, IVME), operating systems (SOSP, OSDI, USENIX), and
architecture (ASPLOS, CGO, PACT) communities.
+ inactive: true
-
name: The Programming Languages Mentoring Workshop (PLMW)
@@ -227,3 +232,26 @@
practical and theoretical topics in all areas that consider formal
verification and certification as an essential paradigm for their work.
CPP spans areas of computer science, mathematics, logic, and education.
+ cooperation: true
+
+-
+ name: International Conference on the Art, Science, and Engineering of Programming (‹Programming›)
+ link: https://programming-conference.org
+ description: |
+ ‹Programming› is a new conference focused on everything to do with
+ programming including the experience of programming. Papers are welcome
+ from any part of the programming research lifecycle, as are papers on
+ programming practice and experience.
+ cooperation: true
+
+-
+ name: Ada-Europe International Conference on Reliable Software Technologies (AEiC)
+ link: https://www.ada-europe.org/confs/ae
+ description: |
+ Leading international forum for providers, practitioners, and researchers
+ in reliable software technologies, focusing on the theory and practice of
+ the design, development, and maintenance of long-lived, high-quality
+ software systems. Participants include practitioners and researchers from
+ industry, academia, and government organizations active in the promotion
+ and development of reliable software technologies.
+ cooperation: true
diff --git a/_data/Educator.yaml b/_data/Educator.yaml
index 4f7d2990..395c9b69 100644
--- a/_data/Educator.yaml
+++ b/_data/Educator.yaml
@@ -1,3 +1,13 @@
+2026:
+- Awardee: Graham Hutton
+ Citation: |
+
+ Professor Graham Hutton has made significant contributions to the teaching of functional programming and Haskell. Graham has distilled twenty years of teaching experience into his book *Programming in Haskell*, widely considered a world-class introduction to the language and used at more than 100 universities worldwide. Graham's curriculum deftly interweaves the practice of writing functional code with the theory of equational reasoning. Graham has further popularized these concepts to a general audience through his many YouTube videos, particularly his collaboration with the Computerphile channel. His videos on the lambda calculus, monads, and other such topics have accumulated over three million views to date.
+
+ At the heart of Graham's work is a desire to show how one can express important mathematical and computational concepts in simple and elegant functional programs. Graham and his collaborators are a mainstay at ICFP and JFP, where they have published numerous papers which embody this spirit. Graham's educational efforts have reached programming language enthusiasts the world over, from the masses of YouTube to the halls of SIGPLAN events, making him more than deserving of this award.
+
+ * Selection committee: Niki Vazou, Will Crichton, John Wickerson, Michael Greenberg, Johan Jeuring
+
2025:
- Awardee: Simon Peyton Jones
Citation: |
diff --git a/_data/OOPSLA.yaml b/_data/OOPSLA.yaml
index ac200a2e..b311a50c 100644
--- a/_data/OOPSLA.yaml
+++ b/_data/OOPSLA.yaml
@@ -1,3 +1,10 @@
+2026:
+- Awardee: Tiark Rompf and Nada Amin
+ Other: |
+ (for 2016) _[Type Soundness for Dependent Object Types (DOT)](https://dl.acm.org/doi/10.1145/3022671.2984008)_
+ Citation: |
+ The PL community has long maintained two different visions for type genericity: "functional" or "parametric" types (e.g., generics, templates, type functions) and "modular" or "virtual" types (e.g., virtual classes, family polymorphism, ThisType). The latter direction has consistently seen lower adoption in major languages, largely because of static type checking challenges. Dependent Object types, a central part of the design of the Scala programming language, made a major step forward in addressing this. Despite being in the language for many years, Dependent Object Types lacked a rigorous formalism and proof of soundness for more than restricted subsets. Earlier work on the DOT calculus proposed a formalism, but still lacked the essential soundness theorem. This work, at OOPSLA 2016, showed how subtle soundness is, but also described conditions necessary for soundness, and used them to establish it. The work directly influenced Scala, being explicitly credited in the Scala 3 release for addressing the very first goal of this major language update: strengthening Scala's foundations.
+
2025:
- Awardee: Vu Le, Chengnian Sun, and Zhendong Su
Other: |
diff --git a/_data/PLDI.yaml b/_data/PLDI.yaml
index 154d67a3..c8ca856b 100644
--- a/_data/PLDI.yaml
+++ b/_data/PLDI.yaml
@@ -1,3 +1,11 @@
+2026:
+- Awardee: |
+ Oded Padon, Kenneth Lauchlin McMillan, Aurojit Panda, Mooly Sagiv, Sharon Shoham
+ Other: |
+ (for 2016) _[Ivy: Safety Verification by Interactive Generalization.](https://dl.acm.org/doi/10.1145/2908080.2908118)_
+ Citation: |
+ Proving the safety of distributed protocols for any number of nodes requires discovering quantified inductive invariants, a task that has historically demanded deep theorem-proving expertise or navigating the unpredictable behavior of SMT solvers within undecidable logics. This paper introduced Ivy, which showed that restricting verification conditions to the decidable Effectively Propositional (EPR) fragment of first-order logic, combined with an interactive counterexample-guided generalization workflow, could make protocol verification accessible to system designers rather than only verification experts. The resulting methodology proved remarkably productive. Ivy and its descendants enabled the first formal proofs of multiple Paxos variants, formal testing of QUIC implementations that uncovered dozens of bugs including an information leak comparable to Heartbleed, and the first mechanized safety and liveness proof of the deployed Stellar blockchain consensus protocol. A decade later, this decidable verification paradigm continues to grow in influence, shaping tools including Verus, mypyvy, and Veil, and finding application in industrial hardware verification.
+
2025:
- Awardee: |
Brandon Lucia and Benjamin Ransford
diff --git a/_data/Redirections.yaml b/_data/Redirections.yaml
index 743ffd86..23dbebc0 100644
--- a/_data/Redirections.yaml
+++ b/_data/Redirections.yaml
@@ -50,7 +50,5 @@
"calendar": "Calendar/"
-"Awards/Vlissides/": "Awards/Other/"
-
# Old acmart pages.
"sites/default/files/acmart/(.*)": "Resources/Author/"
diff --git a/_data/Service.yaml b/_data/Service.yaml
index ab348d75..776684d2 100644
--- a/_data/Service.yaml
+++ b/_data/Service.yaml
@@ -1,3 +1,11 @@
+2026:
+- Awardee: Derek Dreyer
+ Citation: |
+
+ Derek Dreyer has set an exemplary standard of service within the PL community. Throughout the years, Derek has served in almost every possible role in our community, including General Chair of ICFP’19, Program Chair of POPL’24, and Associate Chair of OOPSLA’23 and PLDI'26. Since 2017, he is an Associate Editor of TOPLAS; since 2023, he is on the PACMPL advisory board; and since 2022, he is co-editor-in-chief of the Journal of Functional Programming, presently overseeing the transfer of the journal to Diamond Open Access. But Derek's service work began much earlier. While still an assistant professor, he was moderator of the TYPES mailing list and volunteered to serve on the SIGPLAN Executive Committee (2012-15) as Awards Chair. In 2020, he helped safeguard the perception of programming languages research outside the field, when the CORE ranking committee threatened to demote the rankings of several major PL conferences. Derek has also been a prominent mentor for students, postdocs, and junior faculty. He chaired early editions of PLMW and co-founded the RTFM workshop on faculty mentoring (at PLDI’24 and POPL’26). He frequently speaks at such events, and is known for his widely-cited talks on speaking and writing skills: "How to Write Papers and Give Talks That People Can Follow”. Last but not least, Derek has written popular blog posts touching on the more “human" aspects of a career in research such as: accepting criticism, handling rejection, struggling to maintain a work-life balance, and impostor syndrome. In summary, Derek has served the community in many ways, always striving to promote the value and the quality of PL research, to help maintain cohesion in our community, and to empower junior researchers to conduct outstanding PL research.
+
+ * Selection committee: Alexandra Silva, Jeff Foster, Michael Greenberg, Dan Grossman, Talia Ringer
+
2025:
- Awardee: Stephanie Weirich
Citation: |
diff --git a/_layouts/home.html b/_layouts/home.html
index 9957fb42..81f8ce65 100644
--- a/_layouts/home.html
+++ b/_layouts/home.html
@@ -92,10 +92,16 @@
{% endfor %}
-
+
{% for conf in site.data.Conferences %}
- - {{conf.name}}
+ {% if conf.inactive != true %}
+ - {{conf.name}}
+ {% if conf.cooperation %}
+ (in-cooperation)
+ {% endif %}
+
+ {% endif %}
{% endfor %}
diff --git a/sites/default/files/PracticesofPLDI.pdf b/sites/default/files/PracticesofPLDI.pdf
index a1d57233..0216de7c 100644
Binary files a/sites/default/files/PracticesofPLDI.pdf and b/sites/default/files/PracticesofPLDI.pdf differ