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