Hello folks,
since the submission deadline is getting close, just a small reminder.
Sorry if I'm bothering you, but I discovered a reminder to be somewhat
useful these times...
(Our apologies if you receive multiple copies of this CfC)
EuroPLoP(tm) 2003
Eighth European Conference on Pattern Languages of Programs
25th-29th June 2003
Irsee, Germany
http://www.hillside.net/patterns/EuroPLoP/
EuroPLoP 2003 - Second Call for Contributions
Important Dates
---------------
28th February Papers and focus group proposals due
10th March Shepherding starts
24th March Notification of focus group acceptance or rejection
5th May Conference registration opens
Notification of acceptance
30th May Shepherding ends
Conference drafts due
20th June Conference registration closes
25th-29th June Conference
Early 2004 Final versions of papers due for proceedings
Focus group reports due for proceedings
Submission Guidelines
---------------------
A pattern paper should consist of an individual pattern, a collection of
related patterns or a pattern language. Note that pattern experience
reports, tutorials and other papers that are about patterns, but that do not
actually present patterns, are not the intended target for the writers'
workshops. However, the content of such papers may provide a suitable basis
for focus groups and BoF sessions.
All aspects of software development are suitable topics for submitted
patterns, pattern collections or pattern languages. We invite pattern papers
on programming, software design, project management, education, etc. In
particular, submissions from domains not previously covered by the patterns
literature are welcome. 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, both related pattern
material and related non-pattern material.
Authors should submit an electronic copy of their paper in English. We
recommend that submissions not exceed 10 pages. However, complete pattern
languages and mature collections can be longer than that. In such cases
authors should either identify a part of their paper on which the feedback
should be concentrated or invite feedback on the paper as a whole, but not
on specific details.
###########################################################################
Kevlin Henney, Curbralan Limited, United Kingdom [EMAIL PROTECTED]
Dietmar Sch�tz, Siemens AG, Germany [EMAIL PROTECTED]
