Contribution Formats & Details

OSPERT’17 strives for an interesting, interactive, inclusive, and diverse program. To this end, contributions are solicited in a number of different formats. All proposals and papers will be reviewed by the program committee. See the submission instructions for details on how to submit a paper or a talk proposal for review.

  1. Technical presentations: OSPERT thrives from lively discussions and its interactive format. In continuation of this tradition, OSPERT’17 seeks proposals for technical presentations of various lengths. Each technical presentation may be optionally accompanied by a short paper; however, proposals for stand-alone talks (without accompanying papers) are similarly welcome. Suggested topics include (but are not limited to) the following three categories.
    • Open problemsfuture challenges, and critiques of standards and existing systems: these talks serve to draw the community’s attention to issues and shortcomings of the the current state of the art. A good talk in this category will identify and clearly define an existing or emerging problem, provide a compelling argument for its importance, provide an overview of related work, and propose possible solutions. The target length for a talk in this category is 16-20 minutes.
    • Demos and tutorials: presentations in this category aid in familiarizing the audience with new systems and novel features of existing systems. They serve the audience by providing a quick, low-effort guided tour of a system’s unique capabilities, and allow the authors to promote the fruits of their implementation efforts. The target length for a demo or tutorial is 30-60 minutes, but proposals for longer, more in-depth tutorials may be considered if sufficiently justified.
    • Calls to actioncalls for collaboration, and short announcements: these serve to advertise new and on-going initiatives, to attract new collaborators, and to highlight the release of novel systems software with substantially improved capabilities. The target length for such a talk is five minutes.
  2. Experiment reports: OS work inherently involves substantial experiments, and OSPERT’16 welcomes in-depth presentations and experimental reports that go beyond the level of detail typically presented at conferences. Each accepted experimental study will be presented by the authors at the workshop (target length: 16-20 minutes) and may be optionally further documented in a short or full paper. The range of solicited contributions includes (but is not limited to) the following report types.
    • Replication studies: replication studies (attempt to) reproduce the results of prior published experiments and report on their success in doing so. Such studies serve to corroborate (or reject) original results that are either of particular significance, particularly curious and unexpected, or that were initially met with disbelief. A good replication study clearly identifies which original study is being replicated, why it was chosen, how the experimental setup was matched, and analyzes to which extent the observed measurements corroborate the original results. Replication studies, while not yet common in computer science, are a centerpiece of many sciences and make an important contribution by furthering the community’s trust in the existing body of literature. The chairs of OSPERT’17 strongly encourage the submission of replication studies.
    • Preliminary evaluations: a report on a preliminary evaluation provides the authors with an opportunity to receive feedback from the community at large on both their experimental design and their interpretation of initial results. At the same time, the community is provided with an opportunity to critique ongoing work before it enters a more formal reviewing context (i.e., before it may be too late to incorporate major changes). It is expected that preliminary evaluations will eventually lead, after the feedback provided at OSPERT’17 has been taken into consideration, to full publications elsewhere. (For instance, OSPERT’17 is well-aligned with the expected submission deadlines of both RTAS’17 and EuroSys’17.)
    • Experience reports do not necessarily make a novel technical contribution, but relate interesting and unexpected experiences with RTOS technology. We especially encourage submissions of negative results, projects with unplanned outcomes, and unforeseen challenges.
  3. And last but not least, the usual technical papers. Each accepted technical paper will be presented by the authors at the workshop and distributed online and at the workshop in the proceedings. Two categories of technical papers are solicited.
    • Short papers (up to 3 pages): these papers either accompany a technical presentation, an experimental study, or report on current work that is still in progress. Papers discussing ongoing developments in open-source projects are equally encouraged.
    • Full papers (up to 6 pages): these papers are the traditional form of OSPERT papers focused on technical contributions that advance the state of the art. A good technical paper will identify a shortcoming in the current state of the art, propose a solution, and present an evaluation of a practical implementation. (Papers exceeding 6 pages may be considered for acceptance in exceptional cases; please contact the workshop chairs for details.

For further details see the call for papers (pdf / txt) and the submission instructions.