<div dir="ltr">
<p>Friends,</p><p>The Haskell Symposium submission deadline is less than a week away, the PC is eagerly standing by, the HotCRP instance is open (thanks Mati!),... the only thing missing is you!</p><p>Hope to see you in Milan.<br> /g<br></p><p>----<br></p><p>The ACM SIGPLAN <span class="gmail-il">Haskell</span> <span class="gmail-il">Symposium</span> 2024 will be co-located with the
2024 International <span class="gmail-il">Conference</span> on Functional Programming (ICFP).</p>
<p>The <span class="gmail-il">Haskell</span> <span class="gmail-il">Symposium</span> presents original research on <span class="gmail-il">Haskell</span>,
discusses practical experience and future development of the language,
and promotes other forms of declarative programming.</p>
<p>Topics of interest include:</p>
<ul><li>
<p><em>Language design,</em> with a focus on possible extensions and modifications of <span class="gmail-il">Haskell</span> as well as critical discussions of the status quo;</p>
</li><li>
<p><em>Theory,</em> such as formal semantics of the present language or
future extensions, type systems, effects, metatheory, and foundations
for program analysis and transformation;</p>
</li><li>
<p><em>Implementations,</em> including program analysis and
transformation, static and dynamic compilation for sequential, parallel,
and distributed architectures, memory management, as well as foreign
function and component interfaces;</p>
</li><li>
<p><em>Libraries,</em> that demonstrate new ideas or techniques for functional programming in <span class="gmail-il">Haskell</span>;</p>
</li><li>
<p><em>Tools,</em> such as profilers, tracers, debuggers, preprocessors, and testing tools;</p>
</li><li>
<p><em>Applications,</em> to scientific and symbolic computing, databases, multimedia, telecommunication, the web, and so forth;</p>
</li><li>
<p><em>Functional Pearls,</em> being elegant and instructive programming examples;</p>
</li><li>
<p><em>Experience Reports,</em> to document general practice and experience in education, industry, or other contexts;</p>
</li><li>
<p><em>Tutorials,</em> to document how to use a particular language feature, programming technique, tool or library within the <span class="gmail-il">Haskell</span> ecosystem;</p>
</li><li>
<p><em>System Demonstrations,</em> based on running software rather than novel research results.</p>
</li></ul>
<p>Regular <span class="gmail-il">papers</span> should explain their research contributions in both
general and technical terms, identifying what has been accomplished,
explaining why it is significant, and relating it to previous work, and
to other languages where appropriate.</p>
<p><strong>New this year</strong>, talk proposals need not be
full-length, and should report work in progress relevant to <span class="gmail-il">Haskell</span>
language design, theory, tools, or applications. Talk proposals will be
evaluated by the PC for novelty and relevance to the <span class="gmail-il">Haskell</span> community,
but are not expected to include finished results. Talk proposals will
not be distributed to attendees, but authors of talk proposals may
provide links to materials to be included on the program.</p>
<p>Experience reports and functional pearls need not necessarily report
original academic research results. For example, they may instead report
reusable programming idioms, elegant ways to approach a problem, or
practical experience that will be useful to other users, implementers,
or researchers. The key criterion for such a <span class="gmail-il">paper</span> is that it makes a
contribution from which other Haskellers can benefit. It is not enough
simply to describe a standard solution to a standard programming
problem, or report on experience where you used <span class="gmail-il">Haskell</span> in the standard
way and achieved the result you were expecting.</p>
<p>Like an experience report and a functional pearl, tutorials should
make a contribution from which other Haskellers can benefit. What
distinguishes a tutorial is that its focus is on explaining an aspect of
the <span class="gmail-il">Haskell</span> language and/or ecosystem in a way that is generally useful
to a <span class="gmail-il">Haskell</span> audience. Tutorials for many such topics can be found
online; the distinction here is that by writing it up for formal review
it will be vetted by experts and formally published.</p>
<p>System demonstrations should summarize the system capabilities that
would be demonstrated. The proposals will be judged on whether the
ensuing session is likely to be important and interesting to the <span class="gmail-il">Haskell</span>
community at large, whether on grounds academic or industrial,
theoretical or practical, technical, social or artistic. Please <span class="gmail-il">contact</span>
the program chair with any questions about the relevance of a proposal.</p>
<p>If your contribution is not a research <span class="gmail-il">paper</span>, please mark the title
of your experience report, functional pearl, tutorial or system
demonstration as such, by supplying a subtitle (Talk Proposal,
Experience Report, Functional Pearl, Tutorial <span class="gmail-il">Paper</span>, System
Demonstration).</p>
<h1>Submission Details</h1>
<h2>Formatting</h2>
<p>Submitted <span class="gmail-il">papers</span> should be in portable document format (PDF),
formatted using the ACM SIGPLAN style guidelines. Authors should use the
<code>acmart</code> format, with the <code>sigplan</code> sub-format for ACM proceedings. For details, see:</p>
<p><a href="http://www.sigplan.org/Resources/Author/#acmart-format" target="_blank">http://www.sigplan.org/Resources/Author/#acmart-format</a></p>
<p>It is recommended to use the <code>review</code> option when submitting a <span class="gmail-il">paper</span>; this option enables line numbers for easy reference in reviews.</p>
<p>Talk proposals, functional pearls, experience reports, tutorials and demo proposals should be labelled clearly as such.</p>
<h2>Lightweight Double-blind Reviewing</h2>
<p><span class="gmail-il">Haskell</span> <span class="gmail-il">Symposium</span> 2024 will use a lightweight double-blind reviewing
process. To facilitate this, submitted <span class="gmail-il">papers</span> must adhere to two rules:</p>
<ul><li>Author names and institutions must be omitted, and</li><li>References to authors’ own related work should be in the third
person (e.g., not “We build on our previous work” but rather "We build
on the work of ").</li></ul>
<p>The purpose of this process is to help the reviewers come to an
initial judgment about the <span class="gmail-il">paper</span> without bias, not to make it impossible
for them to discover the authors if they were to try. Nothing should be
done in the name of anonymity that weakens the submission or makes the
job of reviewing the <span class="gmail-il">paper</span> more difficult (e.g., important background
references should not be omitted or anonymized). In addition, authors
should feel free to disseminate their ideas or draft versions of their
<span class="gmail-il">paper</span> as they normally would. For instance, authors may post drafts of
their <span class="gmail-il">papers</span> on the web or give talks on their research ideas.</p>
<p>A reviewer will learn the identity of the author(s) of a <span class="gmail-il">paper</span> after a review is submitted.</p>
<h2>Page Limits</h2>
<p>The length of submissions should not exceed the following limits:</p>
<ul><li><em>Regular <span class="gmail-il">paper</span>:</em> 12 pages</li><li><em>Talk proposals:</em> 6 pages</li><li><em>Functional pearl:</em> 12 pages</li><li><em>Tutorial:</em> 12 pages</li><li><em>Experience report:</em> 6 pages</li><li><em>Demo proposal:</em> 2 pages</li></ul>
<p>There is no requirement that all pages are used. For example, a good
talk proposal might be two pages, and a functional pearl may be much
shorter than 12 pages. In all cases, the list of references is not
counted against these page limits.</p>
<h2>Deadlines</h2>
<ul><li><em><span class="gmail-il">Paper</span> submission:</em> 3 June 2024 (Mon)</li><li><em>Notification:</em> 5 July 2024 (Fri)</li><li><em>Camera-ready Deadline:</em> 18 July 2024 (Thu)</li></ul>
<p>Deadlines are end of day <a href="https://www.timeanddate.com/time/zones/aoe" target="_blank">Anywhere on Earth (UTC-12)</a>.</p>
<h1>Submission</h1>
<p>Submissions must adhere to SIGPLAN’s <a href="http://sigplan.org/Resources/Policies/Republication/" target="_blank">republication policy</a>, and authors should be aware of ACM’s <a href="https://www.acm.org/publications/policies/plagiarism" target="_blank">policies on plagiarism</a>. Program Committee members are allowed to submit <span class="gmail-il">papers</span>, but their <span class="gmail-il">papers</span> will be held to a higher standard.</p>
<p>The <span class="gmail-il">paper</span> submission deadline and length limitations are firm. There
will be no extensions, and <span class="gmail-il">papers</span> violating the length limitations will
be summarily rejected.</p>
<p><span class="gmail-il">Papers</span> should be submitted through HotCRP at:</p>
<p><a href="https://haskell24.hotcrp.com/" target="_blank">https://haskell24.hotcrp.com/</a></p>
<p>Improved versions of a <span class="gmail-il">paper</span> may be submitted at any point before the submission deadline using the same web interface.</p>
<p><em>Supplementary material:</em> 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 <span class="gmail-il">paper</span> that points to an external repository. Authors can
distinguish between anonymized and non-anonymized supplementary
material. Anonymized supplementary material will be visible to reviewers
immediately; non-anonymized supplementary material will be revealed to
reviewers only after they have submitted their review of the <span class="gmail-il">paper</span> and
learned the identity of the author(s).</p>
<p><em>Resubmitted <span class="gmail-il">Papers</span>:</em> authors who submit a revised version of a
<span class="gmail-il">paper</span> that has previously been rejected by another <span class="gmail-il">conference</span> have the
option to attach an annotated copy of the reviews of their previous
submission(s), explaining how they have addressed these previous reviews
in the present submission. If a reviewer identifies him/herself as a
reviewer of this previous submission and wishes to see how his/her
comments have been addressed, the <span class="gmail-il">conference</span> chair will communicate to
this reviewer the annotated copy of his/her previous review. Otherwise,
no reviewer will read the annotated copies of the previous reviews.</p>
<h1>Proceedings</h1>
<p>Accepted <span class="gmail-il">papers</span> will be included in the ACM Digital Library. Their
authors will be required to choose one of the following options:</p>
<ul><li>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);</li><li>Author retains copyright of the work and grants ACM an exclusive permission-to-publish license;</li><li>Author transfers copyright of the work to ACM.</li></ul>
<p>For more information, please see ACM <a href="http://www.acm.org/publications/policies/copyright-policy" target="_blank">Copyright Policy</a> and ACM <a href="http://authors.acm.org/main.html" target="_blank">Author Rights</a>.</p>
<p>Accepted proposals for system demonstrations will be posted on the
<span class="gmail-il">symposium</span> website but not formally published in the proceedings.</p>
<p><em>Publication date:</em> The official publication date of accepted
<span class="gmail-il">papers</span> 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 the
<span class="gmail-il">conference</span>. The official publication date affects the deadline for any
patent filings related to published work.</p>
<h1>Artifacts</h1>
<p>Authors of accepted <span class="gmail-il">papers</span> are encouraged to make auxiliary material
(artifacts like source code, test data, etc.) available with their
<span class="gmail-il">paper</span>. They can opt to have these artifacts published alongside their
<span class="gmail-il">paper</span> in the ACM Digital Library (copyright of artifacts remains with
the authors).</p>
<p>If an accepted <span class="gmail-il">paper</span>’s artifacts are made permanently available for
retrieval in a publicly accessible archival repository like the ACM
Digital Library, that <span class="gmail-il">paper</span> qualifies for an Artifacts Available badge (<a href="https://www.acm.org/publications/policies/artifact-review-badging#available" target="_blank">https://www.acm.org/publications/policies/artifact-review-badging#available</a>). Applications for such a badge can be made after <span class="gmail-il">paper</span> acceptance and will be reviewed by the PC chair.</p>
</div>