http://www.oopsla.org/2006/2006/index.php?option=com_content&task=view&id=27&Itemid=46

program registration submissions committee lodging portland

Submission Closed
The submission deadline for this track has passed. No further submissions are accepted.

CFP: Workshops

Chair: Tim Klinger, IBM Research,

Important Dates
    Submission deadline (firm)
  • March 18, 2006
    Notifications
  • May 12, 2006
  • Electronic submission of proposals is required through the OOPSLA submission system.

Overview

OOPSLA workshops provide intensive collaborative environments where attendees meet to surface, discuss, and solve challenging problems facing the field.

The topics covered by workshops are diverse, as are the workshop's formats. For example, a workshop may provide the opportunity for people working in a particular area to coordinate efforts and to establish collective plans of action, to collaborate on a book, or to discuss and share ideas on a hot new emerging technology.

Workshops are either full or half-day events that occur on the first two days before the conference. To ensure a sufficiently small group for effective interaction, workshop organizers manage attendance based on objective criteria--typically, they request a short position paper submitted by potential attendees. Other criteria are permitted as long as they are clearly specified in the workshop's call for participation. The workshop organizers are responsible for advertising their workshop in appropriate places to attract attendees.

We encourage proposals for innovative, well-focused workshops on a broad spectrum of topics. We particularly encourage proposals that seek to bridge or unify areas across the software life cycle in the service of a coherent, accountable development process.

Some possible topic areas include, but are not restricted to:

  • Software processes and collaborative development
  • Languages (including dynamic languages)
  • Technologies
  • Modeling
  • Design
  • Programming
  • Testing
  • Team or cultural issues
  • Software life cycle management
  • Education issues

Note that each workshop must have at least two organizers, preferably from different organizations. Preference will be shown to workshops with multiple organizers. Workshop organizers and participants have to register for the conference and workshops.

In addition, we expect organizers of an accepted workshop to maintain a web site as an expeditious way to make participant papers, workshop schedule, etc. available to participants; to help advertise the workshop; and, after the workshop, to serve as a primary vehicle to disseminate information about the workshop and its conclusions to the wider community.

Content

A workshop proposal is expected to include the following information:

The workshop's main theme and goals: The proposal must explain the importance of the theme to the OOPSLA community, and why it is appropriate for the OOPSLA conference. Goals should be clearly stated, e.g. the main goal may be to build collaborations for future research, to identify key obstacles to the adoption of a particular technology, to pool experience in a particular area, and so on. In addition, a 150 word abstract that describes the theme and goals of the workshop should be included. If the workshop is accepted, this abstract will be published in the advance and final program.

Organizing committee: The organizing committee is responsible for advertising the workshop, reviewing potential participants, running the workshop and collating the results of the workshop for dissemination to others. Members of the committee should be listed, together with their contact information. The chair of the committee and a primary contact for the workshop should be identified (they need not necessarily be the same person). For each committee member, the proposal should identify their responsibilities for this workshop and their background (expertise in the area, previous experience of running workshops, why they will be an excellent workshop organizer).

Previous related workshops: Highlight any previous workshops on the same or related themes, stating where and when they took place. In particular explain how this workshop builds upon this previous activity.

Expected number of participants: The ideal, minimum and maximum number of participants should be specified.

Workshop preparation: Workshop participants will be expected to prepare for the workshop, e.g. by reading others' position statements, or other background material. Your proposal should show how you plan to encourage participants to prepare appropriately, and how you will make preparation materials available. For example, reading material and activities could be posted to the workshop web site. In this case, the proposal should explain what materials will be available and when.

Workshop activities and format: The format of the workshop should be described and the timetable given, together with approximate timings. Please state clearly if a full-day or a half-day workshop is proposed. You should consider, for example, who will present papers and for how long, whether there will be any introductory material, any panel discussion, debate, or focus groups, how such groups will report back to the other participants, and so on.

Post-workshop activities: Your proposal should describe how the results of the workshop will be disseminated to the wider community. For example what output will be put on the web page, will summaries of discussions, key issues, and shared research agendas be published, and so on. One output could be a poster which can then be displayed during the conference poster session.

Special requirements: Please specify any special requirements.

Submission Process

Electronic submission of proposals is required through the OOPSLA submission system. You will receive confirmation by email that your proposal has been received and is complete. Proposals may be modified online up until the submission deadline.

Workshop proposals received will be reviewed by the Workshop Committee to determine a high quality and appropriate mix for the conference. (See content requirements for the expected format of your submission.)

Proposals will be reviewed against the following criteria:

Significance: Does the proposal present a compelling case for the importance of the topic area? Is this done succinctly and completely? Are the goals related clearly and appropriately to the topic area?

Relevance: Are the themes and goals of current interest to the OOPSLA community? Has the topic been covered before? Is there anything new being discussed? In particular, is the topic likely to be attractive to OOPSLA attendees?

Workshop format: Is the format clearly described and does it encourage a high level of interaction between the participants?

Appropriateness: Is a workshop the right venue to address the theme and goals or does the proposal fit better into another type of OOPSLA event?

Organizers: Are there at least two organizers and do they represent a reasonably varied cross-section of the community? Has the requisite background knowledge and experience of the organizers been established?

Completeness: Does the proposal cover all the information specified in the guidelines stated above?

For more information

For additional information, clarification, or questions, please contact the track chair.

Selection Committee

Brian Barry, Bedarra Research Labs, Canada
Jutta Eckstein, Independent consultant, Germany
Tim Klinger, IBM T. J. Watson Research Center, USA (chair)
Doug Lea, State University of New York at Oswego, USA
Bill Opdyke, North Central College, Illinois, USA
 

While Space Available
Search
program registration submissions committee lodging portland
For comments and questions about the web site
please contact us at support@oopsla.org
© 2005 OOPSLA