From: Akos Hajdu <akoshajdu@meta.com>
To: Akos Hajdu <akoshajdu@meta.com>
Subject: [Caml-list] FTfJP 2026 at ECOOP Call for Papers
Date: Fri, 16 Jan 2026 13:19:52 +0000 [thread overview]
Message-ID: <PH7PR15MB54266B41795B7E459D4C2CE9CC8DA@PH7PR15MB5426.namprd15.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3061 bytes --]
Dear researchers,
We would like to invite you to submit your work as a paper to FTfJP 2026 (https://2026.ecoop.org/home/FTfJP-2026). The Formal Techniques for Judicious Programming (FTfJP) workshop is an established workshop which has run annually since 1999 alongside ECOOP, with the goal of bringing together people working in both fields.
Important dates
- Submission deadline: 18th February, 2026
- Notification: 1st April, 2026
- Camera ready: 30th April, 2026
- Workshop: 30th June, 2026
Paper categories
We solicit two categories of papers:
- Full Papers (12 pages, excluding references) present a technical contribution, case study, or detailed experience report. We welcome both complete and incomplete technical results; ongoing work is particularly welcome, provided it is substantial enough to stimulate interesting discussions.
- Short Papers (6 pages, excluding references) should advocate a promising research direction, or otherwise present a position likely to stimulate discussion at the workshop. We encourage e.g. established researchers to set out a personal vision, and beginning researchers to present a planned path to a PhD.
Both types of contributions will benefit from feedback received at the workshop. Submissions will be peer reviewed and will be evaluated based on their clarity and their potential to generate interesting discussions. Reviewing will be single blind, i.e, submissions need not be anonymized.
The format of the workshop encourages interaction. FTfJP is a forum in which a wide range of people share their expertise, including experienced researchers, industry practitioners, and early-stage PhD students.
Submission guidelines
Papers must be formatted according to the guidelines for ACM sigplan papers (\documentclass[sigplan,screen]{acmart}), see https://www.sigplan.org/Resources/Author/ for details. Submissions should be made via Easychair (https://easychair.org/conferences?conf=ftfjp2026). There is no need to indicate the paper category (long/short).
The accepted papers will be published in the ACM Digital Library, though authors will be able to opt out of this publication, if desired. At least one author of an accepted paper must register to the workshop by the early registration date and attend the workshop to present the work and participate in the discussions.
Lightning talks
In addition to papers, we also invite lightning talks (~10 minutes) on topics related to the workshop goals that allow participants to present preliminary work in academia and industry. Examples include but not limited to
- Proposing a research problem/challenge
- Presenting a tool/demo
- Presenting a short summary of a work already published elsewhere
Submission information will be announced closer to the workshop, but we plan it to be a lightweight process (e.g. title/abstract submission via Google Form).
Invited speakers
Bart Jacobs (KU Leuven)
Julien Lange (Royal Holloway, University of London)
Akos Hajdu
Software engineer
Meta/WhatsApp
PC Chair
[-- Attachment #2: Type: text/html, Size: 5532 bytes --]
reply other threads:[~2026-01-16 13:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH7PR15MB54266B41795B7E459D4C2CE9CC8DA@PH7PR15MB5426.namprd15.prod.outlook.com \
--to=akoshajdu@meta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox