|
| 1 | +--- |
| 2 | +title: "Call for Papers, Functional Software Architecture (Deadline June 16)" |
| 3 | +timestamp: "3/25/2025 15:30:32" |
| 4 | +deadline: "6/16/2025" |
| 5 | +--- |
| 6 | +====================================================================== |
| 7 | + |
| 8 | + *** FUNARCH 2025 -- CALL FOR PAPERS *** |
| 9 | + |
| 10 | + Third ACM SIGPLAN Workshop on |
| 11 | + Functional Software Architecture - FP in the Large |
| 12 | + |
| 13 | + 17th October 2025, Singapore |
| 14 | + Co-located with ICFP 2025 |
| 15 | + |
| 16 | + https://functional-architecture.org/events/funarch-2025/ |
| 17 | + |
| 18 | +====================================================================== |
| 19 | + |
| 20 | +TIMELINE: |
| 21 | + |
| 22 | +Paper submission 16th June 2025 |
| 23 | +Author notification 21st July 2025 |
| 24 | +Camera ready copy 25th August 2025 |
| 25 | +Workshop 17th October 2025 |
| 26 | + |
| 27 | +BACKGROUND: |
| 28 | + |
| 29 | +"Functional Software Architecture" refers to methods of construction |
| 30 | +and structure of large and long-lived software projects that are |
| 31 | +implemented in functional languages and released to real users, |
| 32 | +typically in industry. The goals for the workshop are: |
| 33 | + |
| 34 | +- To assemble a community interested in software architecture |
| 35 | + techniques and technologies specific to functional programming; |
| 36 | + |
| 37 | +- To identify, categorize, and document topics relevant to |
| 38 | + the field of functional software architecture; |
| 39 | + |
| 40 | +- To connect the functional programming community to the software |
| 41 | + architecture community to cross-pollinate between the two. |
| 42 | + |
| 43 | +The workshop follows on from the Functional Software Architecture |
| 44 | +open space that was held at ICFP 2022 in Slovenia. |
| 45 | + |
| 46 | +SCOPE: |
| 47 | + |
| 48 | +The workshop seeks submissions in a range of categories: |
| 49 | + |
| 50 | +- You're a member of the FP community and have thought about how |
| 51 | + to support programming in the large, for example by framing |
| 52 | + functional ideas in architectural terms or vice verse, comparing |
| 53 | + different languages in terms of their architectural capabilities, |
| 54 | + clarifying architectural roles played by formal methods, proof |
| 55 | + assistants and DSLs, or observing how functional concepts are |
| 56 | + used in other language and architecture communities. |
| 57 | + |
| 58 | + Great, submit a research paper! |
| 59 | + |
| 60 | +- You're a member of the architecture community, and have thought |
| 61 | + about how your discipline might help functional programmers, for |
| 62 | + example by applying domain-driven design, implementing hexagonal |
| 63 | + architecture, or designing self-contained systems. |
| 64 | + |
| 65 | + Excellent, submit a research paper! |
| 66 | + |
| 67 | +- You've worked on a large project using functional programming, |
| 68 | + and it's worked out well, or terribly, or a mix of both; bonus |
| 69 | + points for deriving architectural principles from your experience. |
| 70 | + |
| 71 | + Wonderful, submit an experience report! |
| 72 | + |
| 73 | +- You know a neat architectural idiom or pattern that may be useful |
| 74 | + to others developing large functional software systems. |
| 75 | + |
| 76 | + Fabulous, submit an architectural pearl! |
| 77 | + |
| 78 | +- You have something that doesn't fit the above categories, but |
| 79 | + that still relates to functional software architecture, such |
| 80 | + as something that can be written up, or that could be part of |
| 81 | + the workshop format like a panel debate or a fishbowl. |
| 82 | + |
| 83 | + Superb, submit to the open category! |
| 84 | + |
| 85 | +Research papers should explain their research contributions in both |
| 86 | +general and technical terms, identifying what has been accomplished, |
| 87 | +explaining why it is significant, and relating it to previous work, |
| 88 | +and to other languages where appropriate. |
| 89 | + |
| 90 | +Experience reports and architectural pearls need not necessarily |
| 91 | +report original research results. The key criterion for such papers |
| 92 | +is that they make a contribution from which others can benefit. |
| 93 | +It is not enough simply to describe a large software system, or |
| 94 | +to present ideas that are specific to a particular system. |
| 95 | + |
| 96 | +Open category submissions that are not intended for publication |
| 97 | +are not required to follow the formatting guidelines, and can |
| 98 | +submit in PDF, word or plain text format as preferred. Not knowing |
| 99 | +what kinds of submissions we will receive, we cannot be specific as to |
| 100 | +how they will be evaluated. However, submissions that seem likely to |
| 101 | +stimulate discussion around practices in functional architecture |
| 102 | +are encouraged. |
| 103 | + |
| 104 | +If you are unsure whether your contribution is suitable, or if you need any kind |
| 105 | +of help with your submission, please email the program chairs |
| 106 | + |
| 107 | + |
| 108 | +Papers must be submitted by 16th June 2025 using the hotcrp submission |
| 109 | +page (https://funarch25.hotcrp.com/). |
| 110 | + |
| 111 | +Formatting: submissions intended for publication must be |
| 112 | +in PDF format and follow the ACM SIGPLAN style guidelines, |
| 113 | +using the acmart format and the sigplan |
| 114 | +sub-format. Please use the review option when submitting, as this |
| 115 | +enables line numbers for easy reference in reviews. For further |
| 116 | +details, see SIGPLAN's author information: |
| 117 | + |
| 118 | +http://www.sigplan.org/Resources/Author/#acmart-format |
| 119 | + |
| 120 | +If your submission is not a research paper, please mark this using |
| 121 | +a subtitle (Experience Report, Architectural Pearl, Open Category). |
| 122 | + |
| 123 | +Length: submissions must adhere to the limits specified below. |
| 124 | +However, there is no requirement or expectation that all pages |
| 125 | +are used, and authors are encouraged to strive for brevity. |
| 126 | + |
| 127 | +Research papers 5 to 12+ pages |
| 128 | +Architectural pearls 5 to 12 pages |
| 129 | +Experience reports 3 to 6 pages |
| 130 | +Open category 1 to 6 pages |
| 131 | + |
| 132 | +Publication: The proceedings of FUNARCH 2024 will be published in the ACM Digital |
| 133 | +Library, and authors of accepted papers are required to agree to one |
| 134 | +of the standard ACM licensing options. Accepted papers must be |
| 135 | +presented at the workshop by one of the authors, but in special cases |
| 136 | +we may consider remote presentation. |
| 137 | + |
| 138 | +The official publication date is the date the papers are made |
| 139 | +available in the ACM Digital Library. This date may be up to two |
| 140 | +weeks prior to the first day of the conference. The official |
| 141 | +publication date affects the deadline for any patent filings |
| 142 | +related to published work. |
| 143 | + |
| 144 | +PROGRAM CHAIRS: |
| 145 | + |
| 146 | +Jeffrey Young (Unaffiliated) |
| 147 | +Cristine Rizkallah (University of Melbourne) |
| 148 | + |
| 149 | +PROGRAM COMMITTEE: |
| 150 | + |
| 151 | +Isabella Stilkerich (Schaeffler Technologies) |
| 152 | +Ryan Scott (Galois) |
| 153 | +Facundo Dominguez (Tweag) |
| 154 | +J. Garrett Morris (University of Iowa) |
| 155 | +Nada Amin (Harvard University) |
| 156 | +Tom Ellis (Groq) |
| 157 | +KC Sivaramakrishnan (IIT Madras and Tarides) |
| 158 | +Hidehiko Masuhara (Institute of Science Tokyo) |
| 159 | + |
| 160 | +WORKSHOP VENUE: |
| 161 | + |
| 162 | +Room to be determined. The workshop will be co-located with the ICFP 2025 |
| 163 | +conference at the Marina Bay Sands Convention Centre, Singapore. |
| 164 | + |
0 commit comments