CFP: OOPSLA 2024: Round 1 Call for Papers
Call for Papers: OOPSLA 2024 Round 1
in Conferences by Umar Farooq on September 12, 2023

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

                       PACMPL Issue OOPSLA 2024                          Call for Papers                OOPSLA 2024 will be held as part ofThe ACM Conference on Systems, Programming, Languages, and Applications:                  Software for Humanity (SPLASH'24)              October 20-25, 2024, Pasadena, California, United States           https://2024.splashcon.org/track/splash-2024-oopsla========================================================================### Important dates#### ROUND 1:Submission Deadline:               Fri Oct 20, 2023Author Response:                   Mon Dec 11 - Wed Dec 13, 2023Author Notification:               Fri Dec 22, 2023Artifact Submission:               Fri Jan 5, 2024Artifact kick-tires:               Sat Jan 6 - Fri Jan 19, 2024Submission of Revisions:           Sun Feb 11, 2024Author Notification of Revisions:  Sat Feb 24, 2024Artifact Notification:             Fri Mar 1, 2024Camera Ready:                      Fri Mar 8, 2024#### ROUND 2:Submission Deadline:                Fri Apr 5, 2024Author Response:                    Mon Jun 3 - Wed Jun 5, 2024Author Notification:                Fri Jun 21, 2024Artifact Submission:                Fri Jul 5, 2024Artifact kick-tires:                Sat Jul 6 - Fri Jul 19, 2024Submission of Revisions:            Sun Aug 4, 2024Author Notification of Revisions:   Sun Aug 18, 2024Artifact Notification:              Fri Aug 23, 2024Camera Ready:                       Sun Sep 1, 2024Papers accepted at either of the rounds will be published in the 2024volume of PACMPL(OOPSLA) and invited to be presented at the SPLASHconference in October 2024.### ScopeThe OOPSLA issue of the Proceedings of the ACM on Programming Languages(PACMPL) welcomes papers focusing on all practical and theoreticalinvestigations of programming languages, systems and environments.Papers may target any stage of software development, includingrequirements, modelling, prototyping, design, implementation,generation, analysis, verification, testing, evaluation, maintenance,and reuse of software systems. Contributions may include thedevelopment of new tools, techniques, principles, and evaluations.#### Review ProcessPACMPL(OOPSLA) has two rounds of reviewing with submission deadlinesaround October and April each year. As you submit your paper you willreceive around three reviews and an opportunity to provide an authorresponse that will be read and addressed by the reviewers in the finaldecision outcome summary. There are 5 possible outcomes at the end ofthe round:*Accept*: Your paper will appear in the upcoming volume of PACMPL(OOPSLA).*Conditional Accept*: You will receive a list of required revisionsthat you will need to address. You must submit a revised paper, a clearexplanation of how your revision addresses these comments, and"if possible" a diff of the PDF as supplementary material. Assumingyou meet the listed requirements, after further review by the samereviewers, your paper will very likely  be accepted. This process*has to be completed within two months of the initial decision* for thepaper to be accepted, so we encourage timely turnaround in caserevisions take more than one cycle to be accepted.*Minor Revision*: The reviewers have concerns that go beyond what canbe enumerated in a list. Therefore, while you may receive a list ofrevisions suggested by the reviewers, this will not necessarily becomprehensive. You will have the opportunity to resubmit your revisedpaper and have it re-reviewed by the same reviewers, which may or maynot result in your paper's acceptance. When you resubmit, you shouldclearly explain how the revisions address the comments of thereviewers, by including a document describing the changes and "ifpossible" a diff of the PDF as supplementary material. This process*has to be completed within two months of the initial decision* for thepaper to be accepted in the current round, so we encourage timelyturnaround in case revisions take more than one cycle to be accepted.*Major Revision*: You will receive a list of revisions suggested by thereviewers. Papers in this category are *invited to submit a revisionto the next round of submissions* with a specific set of expectationsto be met. When you resubmit, you should clearly explain how therevisions address the comments of the reviewers, by including adocument describing the changes and "if possible" a diff of the PDF assupplementary material. The revised paper will be re-evaluated in thenext round. Resubmitted papers will retain the same reviewersthroughout the process to the extent possible.*Reject*: Rejected papers will not be included in the upcoming volumeof PACMPL(OOPSLA). Papers in this category are not guaranteed a reviewif resubmitted less than one year from the date of the originalsubmission. A paper will be judged to be a resubmission if it issubstantially similar to the original submission. The Chairs willdecide whether or not a paper is a resubmission of the same work.### SubmissionsSubmitted papers must be at most **23 pages** in 10 point font. Thereis no page limit on references. No appendices are allowed on the mainpaper, instead authors can upload supplementary material with no pageor content restrictions, but reviewers may choose to ignore it.Submissions must adhere to the "ACM Small" template available from[the ACM](http://www.acm.org/publications/authors/submissions). Papersare expected to use author-year citations. Author-year citations may beused as either a noun phrase, such as "The lambda calculus wasoriginally conceived by Church (1932)", or a parenthetic phase, suchas "The lambda calculus (Church 1932) was intended as a foundation formathematics".PACMPL uses double-blind reviewing. Authors' identities are onlyrevealed if a paper is accepted. Papers must1. omit author names and institutions,2. use the third person when referencing your work,3. anonymise supplementary material.Nothing should be done in the name of anonymity that weakens thesubmission; see the DBR FAQ. When in doubt, contact the ReviewCommittee Chairs.Papers must describe unpublished work that is not currently submittedfor publication elsewhere as described by [SIGPLAN's Republication  Policy](http://www.sigplan.org/Resources/Policies/Republication).Submitters should also be aware of [ACM's Policy and Procedures onPlagiarism](http://www.acm.org/publications/policies/plagiarism_policy).Submissions are expected to comply with the [ACM Policies forAuthorship](https://www.acm.org/publications/authors/information-for-authors).#### ArtifactsAuthors should indicate with their initial submission if an artifactexists, describe its nature and limitations, and indicate if it willbe submitted for evaluation. Accepted papers that fail to provide anartifact will be requested to explain the reason they cannot supportreplication. It is understood that some papers have no artifacts.Please note that the artifact submission deadline will be followingclosely the paper submission deadline so make sure you check theArtifact Call as soon as you submit your paper to PACMPL(OOPSLA).##### Data-Availability StatementTo help readers find data and software, OOPSLA recommends adding asection just before the references titled Data-Availability Statement.If the paper has an artifact, cite it here. If there is no artifact,this section can explain how to obtain relevant code. The statementdoes not count toward the OOPSLA 2024 page limit. It may be includedin the submitted paper; in fact we encourage this, even if the DOI isnot ready yet.Example:\section{Conclusion}....\section*{Data-Availability Statement}The software that supports~\cref{s:design,s:evaluation}is available on Software Heritage~\cite{artifact-swh}and Zenodo~\cite{artifact-doi}.\begin{acks}....#### Expert PC MembersDuring the submission, we will ask you to list up to 3 non-conflictedPC members who you think are experts on the topic of this submission,starting with the most expert. This list will not be used as an inputduring the paper assignment and it will not be visible to the PC. Itmay be used by the PC Chair and Associate Chairs for advice onexternal experts if the paper lacks expert reviews.### PublicationPACMPL is a Gold Open Access journal, all papers will be freelyavailable to the public. Authors can voluntarily cover the articleprocessing charge ($400 USD), but payment is not required. Theofficial publication date is the date the journal is made available inthe ACM Digital Library. The journal issue and associated papers maybe published up to two weeks prior to the first day of the conference.The official publication date affects the deadline for any patentfilings related to published work.By submitting your article to an ACM Publication, you areacknowledging that you and your co-authors are subject to all [ACMPublications Policies](https://www.acm.org/publications/policies),including ACM’s [new Publications Policy on Research Involving HumanParticipants and Subjects](https://www.acm.org/publications/policies/research-involving-human-participants-and-subjects).Alleged violations of this policy or an ACM Publications Policy willbe investigated by ACM and may result in a full retraction of yourpaper, in addition to other potential penalties, as per ACMPublications Policy.Please ensure that you and your co-authors obtain [an ORCID ID](https://orcid.org/register),so you can complete the publishing process for your accepted paper.ACM has been involved in ORCID from the start and we have recentlymade a [commitment to collect ORCID IDs from all of our publishedauthors](https://authors.acm.org/author-resources/orcid-faqs).We are committed to improving author discoverability, ensuring properattribution and contributing to ongoing community efforts around namenormalization; your ORCID ID will help in these efforts.The ACM Publications Board has recently updated the ACM AuthorshipPolicy in several ways:- Addressing the use of generative AI systems in the publicationsprocess- Clarifying criteria for authorship and the responsibilities ofauthors- Defining prohibited behaviour, such as gift, ghost, or purchasedauthorship- Providing a linked FAQ explaining the rationale for the policy andproviding additional detailsYou can find the updated policy here:[https://www.acm.org/publications/policies/new-acm-policy-on-authorship](https://www.acm.org/publications/policies/new-acm-policy-on-authorship)##### Review CommitteeReview Committee Chairs:Alex Potanin, Australian National University, AustraliaBor-Yuh Evan Chang, University of Colorado Boulder, USAReview Committee Associate Chairs:Anders Møller, Aahrus University, DenmarkLingming Zhang, UIUC, USAReview Committee:Aleksandar Nanevski, IMDEA Software Institute, SpainAlex Summers, University of British Columbia, CanadaAlexandra Bugariu, ETH Zurich, SwitzerlandAna Milanova, Rensselaer Polytechnic Institute, USAAndreas Zeller, CISPA Helmholtz Center for Information Security, GermanyAnitha Gollamudi, UMass, USAAnkush Desai, AWS, USAAshish Tiwari, Microsoft Research, USABen Hermann, TU Dortmund, GermanyBen Titzer, CMU, USABenjamin Delaware, Purdue University, USABernardo Toninho, Universidade Nova de Lisboa, PortugalBruno C. d. S. Oliveira, U. Hong Kong, Hong KongBurcu Kulahcioglu Ozkan, Delft University of Technology, The NetherlandsCasper Bach Poulsen, Delft University of Technology, NetherlandsColin Gordon, Drexel University, USACorina Pasarenau, NASA, USACyrus Omar, University of Michigan, USADamien Zufferey, Sonar Source, SwitzerlandDana Drachsler Cohen, Technion, IsraelDavid Darais, Galois, USADavid Pearce, ConsenSys, New ZealandDi Wang, Peking University, ChinaEmma Söderberg, Lund University, SwedenEmma Tosch, Northeastern University, USAFabian Muehlboeck, Australian National University, AustraliaFei He, Tsinghua University, ChinaFilip Niksic, Google, USAFredrik Kjolstad, Stanford University, USAGuido Salvaneschi, University of St. Gallen, SwitzerlandHila Peleg, Technion, IsraelJiasi Shen, The Hong Kong University of Science and Technology, China (Hong Kong)Jonathan Bell, Northeastern University, USAJonathan Brachthäuser, University of Tübingen, GermanyJoseph Tassarotti, New York University, USAJustin Hsu, Cornell University, USAKarine Even-Mendoza, King's College London, UKKenji Maillard, Inria Rennes, FranceMatthew Flatt, U. Utah, USAMatthew Parkinson, Microsoft, UKMax Schaefer, GitHub, UKMichael Coblenz, UCSD, USAMilos Gligoric, UT Austin, USAMinseok Jeon, Korea University, KoreaMohamed Faouzi Atig, Uppsala University, SwedenOwolabi Legunsen, Cornell University, USAPamela Zave, AT&T Laboratories, USAPavel Panchekha, University of Utah, USARahul Gopinath, University of Sydney, AustraliaRajiv Gupta, UC Riverside, USASaman Amarasinghe, MIT, USASantosh Pande, Georgia Institute of Technology, USASean Treichler, NVIDIA, USAShachar Itzhaky, Technion, IsraelShaz Qadeer, Facebook, USASheng Chen, University of Louisiana at Lafayette, USAShigeru Chiba, University of Tokyo, JapanShriram Krishnamurthi, Brown University, USASreepathi Pai, University of Rochester, USAStefan Brunthaler, University of the Federal Armed Forces in Munchen, GermanySteve Blackburn, Google, AustraliaSubhajit Roy, IIT Kanpur, IndiaSukyoung Ryu, KAIST, KoreaSwarnendu Biswas, IIT Kanpur, IndiaThanh Vu Nguyen, George Mason University, USATiark Rompf, Purdue, USATien Nguyen, University of Texas at Dallas, USATomas Petricek, Charles University, Czech RepublicUmut Acar, CMU, USAWei Le, Iowa State, USAWei Zhang , Meta, USAXiaokang Qiu, Purdue University, USAYingfei Xiong, Peking University, ChinaYizhou Zhang, University of Waterloo, CanadaYouyou Cong, Tokyo Institute of Technology, JapanYu David Liu, Binghamton, USAYu Feng, UCSB, USAYuepeng Wang, Simon Fraser University, Canada##### Artifact Evaluation CommitteeArtifact Evaluation Committee Chairs:Guillaume Baudart, Inria - École normale supérieure, France

Sankha Narayan Guria, University of Kansas, USA