Patterns can be the basis for a handbook of software engineering. They embody core solutions to problems known to arise while building systems. A complete pattern language would guide developers to produce workable software solving ordinary problems.
These conferences follow a different format than conferences such as OOPSLA. The focus here is on learning, discussion, and reflection, not on the presentation of finished work. At a PLoP™ series conference, attendees review each others material and help each other refine their work, run workshops and engage in fruitful discussions.
EuroPLoP™ offers a variety of workshops that allow you to learn about patterns, to receive feedback on your own patterns, and to discuss patterns with fellow pattern enthusiasts. We have been running most of these workshops for many years at previous EuroPLoP™ conferences; the design fest and a special beginners' session, however, will be new to the conference in the year 2001.
Writers' workshops follow a special format which has been adopted from reviewing poetry. Before the conference, everybody reads each other's papers. In the actual workshop, authors give each other feedback on their work in a peer review fashion. Each writers' workshop contains 5 to 8 papers; a session of about 1 1/2 hours is devoted to each paper. In such a session, the authors of the paper under discussion remain silent while the other authors have a discussion about it, and explain what additional insights and views they have. Authors (as well as non-authors who may join) stay with their workshop over the entire conference. This way authors get a lot of ideas on how they can improve their work.
Before pattern papers are accepted for a writers' workshop, they are shepherded (non-anonymously). This means that if you submit a pattern paper, an experienced pattern author will get in touch with you and discuss your submission with you, so that you can improve your paper prior to the conference. At the end of the shepherding process, the shepherd and the program committee decide whether a paper is ready for a writers' workshop; experience shows that most submitted papers will.
Because the focus of the writers' workshops is on feedback and improvement, papers are not considered final once they have been workshopped. Authors incorporate the feedback they receive at the writers' workshop into their papers before the papers go into the final proceedings about half a year after the conference.
All aspects of software systems are suitable topics for submitted patterns or pattern languages. We invite patterns on programming, software design, project management, education, and so on. Submissions from areas which have not much been covered by patterns so far are particularly solicited. The actual subject of a pattern need not be original; it is essential that a pattern describes mature knowledge. However, patterns should always reference related work, that is related patterns as well as related non-pattern material.
Non-authors who join a writer's worshop are asked to stick to one writer's group and are supposed to read all the papers discussed in the group in advance, too.
We will have two different writing goups.
After the conference, the focus group leader summarizes the results in form of a short focus group report which will go into the final conference proceedings.
We plan to have 3 or 4 focus groups at the conference. Potential focus group leaders are invited to submit focus group proposals. There's a great diversity as far as suitable topics for focus groups are concerned. Possible topics include but are not restricted to experiences with patterns, patterns in research, and much more. Interdisciplinary topics are particularly welcome since they help us learn from other domains. These domains range from less obvious areas of computing, such as artificial intelligence, to other areas of science, such as building architecture, mechanical engineering, music, or film making.
Focus group proposals will be reviewed by the program committee. The accepted focus groups will be announced two to three months before the conference. Most focus groups allow conference attendees to simply join at the conference; however, focus group leaders are free to ask participants to register in advance and to do some kind of preparation.
Conference attendees can participate in such a group in different roles: those who proposed the design fest typically act as domain experts, someone else will be the moderator, someone else yet will write some kind of protocol, and several people will act as the actual designers. After the conference the design process will be summarized in a design fest report, typically authored by those who proposed the design fest and the peron who wrote the protocol, and maybe a few others. The design fest report will also go into the final conference proceedings.
We plan to have one or two half-day design fests. There are two kinds of design fest that we can think of.
In this session you learn about patterns in general, you get an overview of what patterns exist, you learn how patterns can improve your software, and you get exposed to the idea of pattern languages. This session also tells you about EuroPLoP™, its traditions and rituals, and is a chance to get in touch with many EuroPLoP™ people very quickly.
| Date | Conference | Pattern Papers | Writing Group | Focus Groups | Design Fest |
| February 25 | papers due | focus group proposals due | design fest proposals due | ||
| March 12 | shepherding starts | ||||
| March 26 | notification of acceptance or rejection for focus group proposals | notification of acceptance or rejection for design fest proposals | |||
| April 02 | registration for focus groups opens
(focus groups that require registration only) |
application for design fest participation opens | |||
| May 07 | conference registration opens | notification of acceptance or rejection | notification of acceptance or rejection for focus group participants
(focus groups that require registration only) |
notification of acceptance or rejection for design fest participants | |
| June 03 | shepherding ends | ||||
| June 10 | conference drafts due | registration
(unshepherded papers only) |
|||
| July 01 | conference registration closes | ||||
| July 04 - July 08 | conference | ||||
| late 2001 | final versions due | focus group reports due | design fest reports due |