[prev in list] [next in list] [prev in thread] [next in thread]
List: haskell
Subject: [Haskell] Second CFP: Haskell Symposium 2024
From: "J. Garrett Morris via Haskell" <haskell () haskell ! org>
Date: 2024-04-17 19:21:16
Message-ID: CALqZiMxYe-4GThjZhmoNJsGKHA+rqHHLya-DffiXeNsjGzaoRg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Friends,
The obligatory first repetition of the 2024 Haskell Symposium CFP is below.
*New this year, *in addition to full papers, the Haskell Symposium is also
inviting talk proposals. Tell us about your exciting work in progress or
upcoming results!
/g
--
The ACM SIGPLAN Haskell Symposium 2024 will be co-located with the 2024
International Conference on Functional Programming (ICFP).
The Haskell Symposium presents original research on Haskell, discusses
practical experience and future development of the language, and promotes
other forms of declarative programming.
Topics of interest include:
-
*Language design,* with a focus on possible extensions and modifications
of Haskell as well as critical discussions of the status quo;
-
*Theory,* such as formal semantics of the present language or future
extensions, type systems, effects, metatheory, and foundations for program
analysis and transformation;
-
*Implementations,* 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;
-
*Libraries,* that demonstrate new ideas or techniques for functional
programming in Haskell;
-
*Tools,* such as profilers, tracers, debuggers, preprocessors, and
testing tools;
-
*Applications,* to scientific and symbolic computing, databases,
multimedia, telecommunication, the web, and so forth;
-
*Functional Pearls,* being elegant and instructive programming examples;
-
*Experience Reports,* to document general practice and experience in
education, industry, or other contexts;
-
*Tutorials,* to document how to use a particular language feature,
programming technique, tool or library within the Haskell ecosystem;
-
*System Demonstrations,* based on running software rather than novel
research results.
Regular papers 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.
*New this year*, talk proposals need not be full-length, and should report
work in progress relevant to Haskell language design, theory, tools, or
applications. Talk proposals will be evaluated by the PC for novelty and
relevance to the Haskell 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.
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 paper 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 Haskell in the standard way and
achieved the result you were expecting.
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 Haskell
language and/or ecosystem in a way that is generally useful to a Haskell
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.
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 Haskell community
at large, whether on grounds academic or industrial, theoretical or
practical, technical, social or artistic. Please contact the program chair
with any questions about the relevance of a proposal.
If your contribution is not a research paper, 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 Paper, System Demonstration).
Submission Details 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.
Talk proposals, functional pearls, experience reports, tutorials and demo
proposals should be labelled clearly as such.
Lightweight Double-blind Reviewing
Haskell Symposium 2024 will use a lightweight double-blind reviewing
process. To facilitate this, submitted papers must adhere to two rules:
- Author names and institutions must be omitted, and
- 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 ").
The purpose of this process is to help the reviewers come to an initial
judgment about the paper 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 paper 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 paper as they normally
would. For instance, authors may post drafts of their papers on the web or
give talks on their research ideas.
A reviewer will learn the identity of the author(s) of a paper after a
review is submitted.
Page Limits
The length of submissions should not exceed the following limits:
- *Regular paper:* 12 pages
- *Talk proposals:* 6 pages
- *Functional pearl:* 12 pages
- *Tutorial:* 12 pages
- *Experience report:* 6 pages
- *Demo proposal:* 2 pages
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.
Deadlines
- *Paper submission:* 3 June 2024 (Mon)
- *Notification:* 5 July 2024 (Fri)
- *Camera-ready Deadline:* 18 July 2024 (Thu)
Deadlines are end of day Anywhere on Earth (UTC-12)
<https://www.timeanddate.com/time/zones/aoe>.
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.
The paper submission deadline and length limitations are firm. There will
be no extensions, and papers violating the length limitations will be
summarily rejected.
Papers should be submitted through HotCRP at:
https://haskell24.hotcrp.com/
Improved versions of a paper may be submitted at any point before the
submission deadline using the same web interface.
*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. 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 paper and learned the identity of the author(s).
*Resubmitted Papers:* authors who submit a revised version of a paper that
has previously been rejected by another conference 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 conference 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.
Proceedings
Accepted papers will be included in the ACM Digital Library. Their authors
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);
- Author retains copyright of the work and grants ACM an exclusive
permission-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>.
Accepted proposals for system demonstrations will be posted on the
symposium website but not formally published in the proceedings.
*Publication date:* The official publication date of accepted papers 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 conference. The
official publication date affects the deadline for any patent filings
related to published work.
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 chair.
[Attachment #5 (text/html)]
<div dir="ltr">
<div id="gmail-:1lu" class="gmail-Ar gmail-Au gmail-Ao" style="display:block"><div \
id="gmail-:1lq" class="gmail-Am gmail-aiL gmail-Al editable gmail-LW-avf gmail-tS-tW \
gmail-tS-tY" aria-label="Message Body" role="textbox" aria-multiline="true" \
style="direction:ltr;min-height:1333px" tabindex="1" aria-controls=":1ox" \
aria-expanded="false"><div>Friends,</div><div><br></div><div>The obligatory first \
repetition of the 2024 Haskell Symposium CFP is \
below.</div><div><br></div><div><i>New this year, </i>in addition to full papers, the \
Haskell Symposium is also inviting talk proposals. Tell us about your exciting work \
in progress or upcoming results!<br></div><div><br></div><div> \
/g</div><div><br></div><div>--</div><div><br></div><div> <p>The ACM SIGPLAN Haskell \
Symposium 2024 will be co-located with the 2024 International Conference on \
Functional Programming (ICFP).</p> <p>The Haskell Symposium presents original \
research on Haskell, 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 \
Haskell 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 Haskell;</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 Haskell ecosystem;</p> </li><li>
<p><em>System Demonstrations,</em> based on running software rather than novel \
research results.</p> </li></ul>
<p>Regular papers 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 Haskell
language design, theory, tools, or applications. Talk proposals will be
evaluated by the PC for novelty and relevance to the Haskell 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 paper 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 Haskell 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 Haskell language and/or ecosystem in a way that is generally useful
to a Haskell 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 Haskell
community at large, whether on grounds academic or industrial,
theoretical or practical, technical, social or artistic. Please contact
the program chair with any questions about the relevance of a proposal.</p>
<p>If your contribution is not a research paper, 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 Paper, System
Demonstration).</p>
<h1>Submission Details</h1>
<h2>Formatting</h2>
<p>Submitted papers 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 paper; 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>Haskell Symposium 2024 will use a lightweight double-blind reviewing
process. To facilitate this, submitted papers 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 paper 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 paper 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
paper as they normally would. For instance, authors may post drafts of
their papers on the web or give talks on their research ideas.</p>
<p>A reviewer will learn the identity of the author(s) of a paper 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 paper:</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>Paper 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 papers, but their \
papers will be held to a higher standard.</p> <p>The paper submission deadline and \
length limitations are firm. There will be no extensions, and papers violating the \
length limitations will be summarily rejected.</p>
<p>Papers 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 paper \
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 paper 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 paper and
learned the identity of the author(s).</p>
<p><em>Resubmitted Papers:</em> authors who submit a revised version of a
paper that has previously been rejected by another conference 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 conference 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 papers 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 symposium \
website but not formally published in the proceedings.</p> <p><em>Publication \
date:</em> The official publication date of accepted papers 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 conference. The official publication date \
affects the deadline for any patent filings related to published work.</p>
<h1>Artifacts</h1>
<p>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).</p>
<p>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 (<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 paper acceptance and will be reviewed \
by the PC chair.</p>
</div></div></div>
</div>
[Attachment #6 (text/plain)]
_______________________________________________
Haskell mailing list
Haskell@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic