April 19th to April 22nd, 2018
Fredensborg, North Zealand, Denmark
- 2017 December 31st: Submission of abstract
- 2018 January 7th: Submission of full initial paper
- 2018 January 14th: Beginning of shepherding
- 2018 February 18th: Second draft deadline
- 2018 February 25th: Paper acceptance notification
- 2018 March 4th: Registration deadline
- 2018 April 1st: Conference version deadline & End of shepherding
- 2018 April 19th- 22nd: Conference
- 2018 August 30th: Final version deadline
- Embedded systems, distributed control systems, and other low level systems
- Web applications, JS frameworks, artificial intelligence and data mining
- Software design, architecture, management, and continuous deployment pipelines
- Patterns covering commercial aspects
- Human computer interaction (user interface aspects and novel modes of interaction)
- Pedagogy and education (both professional training and classroom teaching)
The submitted papers should contain one or more patterns or report results from applying patterns. The papers should have up to 10 pages, but longer pattern sequences might be considered for inclusion. The final versions of the papers should be formatted according to the ACM single column template. For the conference version of the paper, less strict formatting is accepted. ACM single column templates are available on the VikingPLoP website.
First-time pattern authors are especially welcomed to participate in the conference. All papers accepted for the shepherding process will receive in-depth shepherding by an experienced pattern author before the conference. If any questions will arise, contact the conference chairs.
We also accept papers on the application of patterns in practice. The focus of these papers should be on applications of patterns in industrial projects, as well as on systematizing the application of patterns. They should stimulate a general discussion on how to disseminate the patterns literature more widely in higher education and training.
The core of VikingPLoP is writers’ workshops where authors work together to improve their papers. Before patterns or other papers are accepted for a writers’ workshop, they are shepherded (non-anonymously). This means that an experienced author will discuss your submission with you, so that you can refine your paper prior to the conference. All accepted submissions will be workshopped and peer-reviewed in the conference.
Papers discussed at a writer’s workshop at this conference qualify for submission to the Transactions on Pattern Languages of Programming journal published by Springer.
The shepherding process is essentially a peer reviewing process. The Shepherd guides the sheep into a more mature understanding of his or her pattern. Shepherds are individuals, with experience in pattern writing, assigned to an author’s paper for helping the author improve the pattern. Shepherds also have experience with the shepherding process, either having been a shepherd before or a sheep (an author). Shepherding is about improving the pattern itself, while the Shepherd maintains that the author is the one responsible for the pattern writing. The shepherding process is done before the paper is to be presented at a conference.
There is a four stage submission process:
- Submission of the abstract. This expresses your intent to participate to conference and gives the program committee a chance to assess the suitability of your topic.
- Initial submission. The papers are checked by the program committee. Papers are then accepted for shepherding and the author is assigned a shepherd who will help to improve the paper.
- Half way through the shepherding process, the authors are expected to submit a second draft. The paper will be assessed for quality and the author’s willingness to accept feedback is considered. This review will determine whether a paper is accepted to the conference or not.
- Authors and shepherds are expected to continue working on the paper. Final drafts for the conference are submitted couple of weeks before the conference. The authors of the accepted papers are also expected to register for the conference before the closing of registration. Failing to do so may result in acceptance being withdrawn. In the case of papers with multiple authors at least one author is expected to register to attend by the close of registrations.