NEW this year: ECOOP 2022 will have two rounds of reviewing.
Round 1 paper submission deadline: ** December 1, 2021 **
============================
ECOOP 2022 Call for Papers
ECOOP 2022 will be held on Mon 6th - Fri 10th of June in Berlin, Germany.
============================
ECOOP is a conference about programming originally focused on object-orientation, but now including all practical and theoretical investigations of programming languages, systems and environments. ECOOP solicits innovative solutions to real problems as well as evaluations of existing solutions.
Authors are asked to pick one of the following categories:
- Research. The most traditional category for papers that advance the sate of the art. - Reproduction. An empirical evaluation that reconstructs a published experiment in a different context in order to validate the results of that earlier work. - Experience. Applications of known PL techniques in practice as well as tools. Industry papers will be reviewed by practitioners. We welcome negative results that may provide inspiration for future research. - Pearls/Brave New Ideas. Articles that either explain a known idea in an elegant way or unconventional papers introducing ideas that may take some time to substantiate. These papers may be short.
==== Submissions ====
Submission must not have been published, or have major overlap with previous work. In case of doubt, contact the chair. Proceedings are published in open access by Dagstuhl LIPIcs in the Dagstuhl LIPIcs LaTeX-style template.
ECOOP uses double-blind reviewing. Authors’ identities are only revealed if a paper is accepted. Papers must 1. omit author names and institutions, and 2. use the third person when referencing the authors’ own work. Nothing should be done in the name of anonymity that weakens the submission; see the DB FAQ. When in doubt, contact the chair.
There is no page limit on submissions, but authors must understand that reviewers have a fixed time budget for each paper, so the quality of the comments is likely to be inversely proportional to length. Brevity is a virtue.
Authors will be given a three-day period to read and respond to the reviews of their papers before the program committee meeting. Responses have no length limit.
==== Artifact Evaluation and Intent ====
To support replication of experiments, authors of research papers may submit artifacts to the Artifact Evaluation Committee. They will be asked whether they intend to submit an artifact at submission time. It is understood that some paper do not have artifacts.
======== Important Dates ========
ECOOP 2022 will have two deadlines for submissions, three months apart. Future years may have more deadlines. Papers submitted in each round can be (a) accepted, (b) rejected, or (c) asked for revisions. Revisions can be submitted at a later round. Papers retain their reviewers during revision.
- Submission R1: 1 December 2021 - R1 Artifacts due: 10 December 2021 - Response R1: 23 January 2022 - Notification R1: 1 February 2022
- Submission R2: 1 March 2022 - R2 Artifacts due: 10 March 2022 - Response R2: 23 April 2022 - Notification R2: 1 May 2022
==== Journal First and Journal After ====
We have Journal First / After arrangements with ACM’s Transactions on Programming Languages and Systems (TOPLAS), Elsevier’s Science of Computer Programming (SCP) and AITO’s Journal of Object Technology (JOT).
Only new research papers are eligible to be Journal First (JF). JF papers will have an extended abstract in the ECOOP proceedings. The deadline is that same as round 1 of submissions and the notification is aligned with round 2 notification. TOPLAS JF papers should be submitted according to this announcement. SCP JF papers should follow this call for papers. JF papers are presented at the conference and eligible for awards.
Journal After (JA) papers are papers for which the authors request to be considered for post conference journal publication. Once accepted by the ECOOP PC, these papers will be forwarded to the journal editors. Reviews and reviewers will be forwarded and used at the editor’s discretion. JA papers will have an extended abstract (up to 12 pages) in the conference proceedings.
Find answers to frequently asked questions on our website: https://2022.ecoop.org/track/ecoop-2022-papers
As an independent developer, I reckoned I could give some feedback about how it feels to read a Call for Papers like this one.
I have nearly twenty years of work with Squeak behind me. I developed an original framework for music composition, with brand new techniques and domain modelling architectures. I used it to produce about 70 pieces of music. I made a modular Lisp interpreter, a DSL for functional programming in Smalltalk, several games and a game engine with its own original brand of component-based architecture for autonomous agents. All of this is freely available and open-sourced [1].
Now I would be very glad to be solicited for introducing, documenting and elaborating on what, among all the above, may be of interest to others. But not on my spare time - that time, I use it for fun, that is, actually doing the stuff.
When I read the Call for Papers which, I know, is not meant for unaffiliated people like me, what I feel is: WTF?
Here I am asked to do some more work, with hard deadlines and very specific contraints, just to get a chance to have my research published in non-open, expensive journals that nobody among the people I would like to reach will ever read.
This work is ordered to me like a school assignment, with no detectable sign of respect for the independent mindset required to explore new venues, that is, not detectable sign of respect for the human being behind the research. Actually I feel offended just by the tone of that Call from Above, as it seems, which makes me feel like I should only be glad to have been given a chance to exist in the eye of the Man.
And of course, all this I am supposed to do for nilch.
Having read countless papers and theses in my domains of research, I have no hesitation to claim that I have a lot of material to provide, enough for a thesis or two in fact, and of course for many papers. I will never do this for free though - because fun is fun, and work is work.
So I am asking myself, and also asking you people BTW: is there another, more human, more respectul, and maybe even rewarding, way to have one's own research be known in the large?
Stef
vm-dev@lists.squeakfoundation.org