<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Dear all,<br class="">
<br class="">
The first workshop on "Functional Software Architecture - FP in the Large”<br class="">
will be held in Seattle in Sept 2023, co-located with the ICFP conference.<br class="">
<br class="">
Please submit your best papers, experience reports, and architectural
<div class="">pearls on large-scale functional programming!<br class="">
<br class="">
The submission deadline 1st June 2023.<br class="">
<br class="">
Best wishes,<br class="">
<br class="">
Mike Sperber and Graham Hutton<br class="">
Program Chairs, FUNARCH 2023<br class="">
<br class="">
<br class="">
======================================================================<br class="">
<br class="">
*** FUNARCH 2023 — FINAL CALL FOR PAPERS ***<br class="">
<br class="">
The First ACM SIGPLAN Workshop on<br class="">
Functional Software Architecture - FP in the Large<br class="">
<br class="">
8th September 2023, Seattle, Washington, USA<br class="">
Co-located with ICFP 2023<br class="">
<br class="">
<a href="https://tinyurl.com/FUNARCH-23" class="">https://tinyurl.com/FUNARCH-23</a><br class="">
<br class="">
======================================================================<br class="">
<br class="">
TIMELINE:<br class="">
<br class="">
Paper submission<span class="Apple-tab-span" style="white-space: pre;"> </span>1st June 2023<br class="">
Author notification<span class="Apple-tab-span" style="white-space: pre;"> </span>
28th June 2023<br class="">
Camera ready copy<span class="Apple-tab-span" style="white-space: pre;"> </span>18th July 2023<br class="">
Workshop<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>8th Sept 2023<br class="">
<br class="">
BACKGROUND:<br class="">
<br class="">
"Functional Software Architecture" refers to methods of construction<br class="">
and structure of large and long-lived software projects that are<br class="">
implemented in functional languages and released to real users,<br class="">
typically in industry. The goals for the workshop are:<br class="">
<br class="">
- To assemble a community interested in software architecture<br class="">
techniques and technologies specific to functional programming;<br class="">
<br class="">
- To identify, categorize, and document topics relevant to<br class="">
the field of functional software architecture;<br class="">
<br class="">
- To connect the functional programming community to the software<br class="">
architecture community to cross-pollinate between the two.<br class="">
<br class="">
The workshop follows on from the Functional Software Architecture<br class="">
open space that was held at ICFP 2022 in Slovenia.<br class="">
<br class="">
SCOPE:<br class="">
<br class="">
The workshop seeks submissions in a range of categories:<br class="">
<br class="">
- You're a member of the FP community and have thought about how<br class="">
to support programming in the large, for example by framing<br class="">
functional ideas in architectural terms or vice verse, comparing<br class="">
different languages in terms of their architectural capabilities,<br class="">
clarifying architectural roles played by formal methods, proof<br class="">
assistants and DSLs, or observing how functional concepts are<br class="">
used in other language and architecture communities.<br class="">
<br class="">
Great, submit a research paper!<br class="">
<br class="">
- You're a member of the architecture community, and have thought<br class="">
about how your discipline might help functional programmers, for<br class="">
example by applying domain-driven design, implementing hexagonal<br class="">
architecture, or designing self-contained systems.<br class="">
<br class="">
Excellent, submit a research paper!<br class="">
<br class="">
- You've worked on a large project using functional programming,<br class="">
and it's worked out well, or terribly, or a mix of both; bonus<br class="">
points for deriving architectural principles from your experience.<br class="">
<br class="">
Wonderful, submit an experience report!<br class="">
<br class="">
- You know a neat architectural idiom or pattern that may be useful<br class="">
to others developing large functional software systems.<br class="">
<br class="">
Fabulous, submit an architectural pearl!<br class="">
<br class="">
- You have something that doesn't fit the above categories, but<br class="">
that still relates to functional software architecture, such <br class="">
as something that can be written up, or that could be part of<br class="">
the workshop format like a panel debate or a fishbowl.<br class="">
<br class="">
Superb, submit to the open category!<br class="">
<br class="">
Research papers should explain their research contributions in both<br class="">
general and technical terms, identifying what has been accomplished,<br class="">
explaining why it is significant, and relating it to previous work,<br class="">
and to other languages where appropriate.<br class="">
<br class="">
Experience reports and architectural pearls need not necessarily<br class="">
report original research results. The key criterion for such papers<br class="">
is that they make a contribution from which others can benefit.<br class="">
It is not enough simply to describe a large software system, or<br class="">
to present ideas that are specific to a particular system.<br class="">
<br class="">
Open category submissions that are not intended for publication <br class="">
are not required to follow the formatting guidelines, and can <br class="">
submit in PDF, word or plain text format as preferred.<br class="">
<br class="">
If you are unsure whether your contribution is suitable, or if<br class="">
you need any kind of help with your submission, please email<br class="">
the program chairs at <<a href="mailto:funarch2023@easychair.org" class="">funarch2023@easychair.org</a>>.<br class="">
<br class="">
SUBMISSION:<br class="">
<br class="">
Papers must be submitted by 1st June 2023 using EasyChair, via the<br class="">
following link: <a href="https://tinyurl.com/FUNARCH23-submit" class="">https://tinyurl.com/FUNARCH23-submit</a><br class="">
<br class="">
Formatting: submissions intended for publication must be in PDF<br class="">
format and follow the ACM SIGPLAN style guidelines, using the<br class="">
acmart format and the sigplan sub-format. Please use the review<br class="">
option, as this enables line numbers for easy reference in reviews.<br class="">
For further details, see: <a href="https://tinyurl.com/sigplan-acmart" class="">https://tinyurl.com/sigplan-acmart</a><br class="">
<br class="">
If your submission is not a research paper, please mark this using<br class="">
a subtitle (Experience Report, Architectural Pearl, Open Category).<br class="">
<br class="">
Length: submissions must adhere to the limits specified below.<br class="">
However, there is no requirement or expectation that all pages<br class="">
are used, and authors are encouraged to strive for brevity.<br class="">
<br class="">
Research papers<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>5 to 12+ pages<br class="">
Architectural pearls<span class="Apple-tab-span" style="white-space: pre;"> </span>
5 to 12 pages<br class="">
Experience reports<span class="Apple-tab-span" style="white-space: pre;"> </span>
3 to 6 pages<br class="">
Open category<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>1 to 6 pages<br class="">
<br class="">
Publication: The proceedings of FUNARCH 2023 will be published in<br class="">
the ACM Digital Library, and authors of accepted papers are required<br class="">
to agree to one of the standard ACM licensing options. Accepted<br class="">
papers must be presented at the workshop by one of the authors, but<br class="">
in special cases we may consider remote presentation. <br class="">
<br class="">
The official publication date is the date the papers are made available<br class="">
in the ACM Digital Library. This date may be up to two weeks prior to<br class="">
the first day of the conference. The official publication date affects<br class="">
the deadline for any patent filings related to published work.<br class="">
<br class="">
PROGRAM CHAIRS:<br class="">
<br class="">
Mike Sperber <span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>Active Group, Germany<br class="">
Graham Hutton <span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>University of Nottingham, UK<br class="">
<br class="">
PROGRAM COMMITTEE:<br class="">
<br class="">
Joachim Breitner<span class="Apple-tab-span" style="white-space: pre;"> </span>Germany<br class="">
Manuel Chakravarty<span class="Apple-tab-span" style="white-space: pre;"> </span>
Tweag & IOG, The Netherlands<br class="">
Ron Garcia<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>University of British Columbia, Canada<br class="">
Debasish Ghosh<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>LeadIQ, India<br class="">
Lars Hupel<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>Giesecke+Devrient, Germany<br class="">
Andy Keep<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>Meta, USA<br class="">
Shriram Krishnamurthi<span class="Apple-tab-span" style="white-space: pre;"> </span>
Brown University, USA<br class="">
Andres Löh<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>Well-Typed, Germany<br class="">
Anil Madhavapeddy<span class="Apple-tab-span" style="white-space: pre;"> </span>University of Cambridge, UK<br class="">
José Pedro Magalhães<span class="Apple-tab-span" style="white-space: pre;"> </span>
Standard Chartered, UK<br class="">
Simon Marlow<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>Meta, UK<br class="">
Hannes Mehnert<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>Robur, Germany<br class="">
Erik Meijer<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>USA<br class="">
Ivan Perez<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>KBR / NASA Ames Research Center, USA<br class="">
Stefanie Schirmer<span class="Apple-tab-span" style="white-space: pre;"> </span>DuckDuckGo, Germany<br class="">
Perdita Stevens<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>University of Edinburgh, UK<br class="">
Stefan Wehr<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>Hochschule Offenburg, Germany<br class="">
Scott Wlaschin<span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"></span>FPbridge, UK<br class="">
<br class="">
WORKSHOP VENUE:<br class="">
<br class="">
The workshop will be co-located with the ICFP 2023 conference at<br class="">
The Westin Seattle Hotel, Seattle, Washington, United States.<br class="">
<br class="">
======================================================================</div>
<PRE>
This message and any attachment are intended solely for the addressee
and may contain confidential information. If you have received this
message in error, please contact the sender and delete the email and
attachment.
Any views or opinions expressed by the author of this email do not
necessarily reflect the views of the University of Nottingham. Email
communications with the University of Nottingham may be monitored
where permitted by law.
</PRE></body>
</html>