<html>
<head>
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>Boost Conference 2007</title>
</head>
<body>
<p><a href="http://www.boost.org">
<img border="0" src="../boost.png" width="277" height="86"></a></p>
<h1>Boost Conference 2007:
Call for Session Proposals</h1>
<p>The first annual Boost conference will take place in Aspen, Colorado, May
14-18. This promises to be the main face-to-face event for all things Boost,
from generic-programming techniques to Boost community, from using Boost
libraries to writing Boost libraries, from deployment considerations to
promoting the use of Boost more widely, from TR1 to TR2. Given the range and
interests of the participants, this event promises to be intense and in
depth. We invite you to propose a session. </p>
<p>More <a href="http://www.boost.org/more/BoostCon07.html">
BoostCon 2007 information</a> is available on the Boost web site.</p>
<p><a href="#formats">Session formats</a><br>
<a href="#topics">Session topics</a><br>
<a href="#proposal">Submitting a proposal</a><br>
<a href="#Timeline">Timeline</a><br>
<a href="#Other">Other arrangements</a></p>
<h2>Session <a name="formats">formats</a></h2>
<p><strong>Presentations</strong> focus on a practitioner�s ideas and
experience with anything relevant to Boost and Boost users. </p>
<p><strong>Panels</strong> feature three or four people presenting their
ideas and experiences relating to Boost relevant, controversial, emerging,
or unresolved issues. Panels may be conducted in several ways, such as
comparative, analytic, or historic. </p>
<p><strong>Tutorials</strong> are formally prepared sessions at which
instructors teach conference participants specific Boost relevant skills.
</p>
<p><strong>Workshops</strong> provide an active arena for advancements in
Boost relevant topics. Workshops provide the opportunity for experienced
practitioners to develop new ideas about a topic of common interest and
experience. </p>
<p><strong>Other formats</strong> may also be of interest. Don't hold back a
proposal just because it doesn't fit in a pigeonhole. </p>
<h2>Session <a name="topics">topics</a></h2>
<p>Topics of interest include, but are not restricted to, the following: </p>
<ul>
<li>General tutorial sessions introducing one or more Boost libraries </li>
<li>In-depth sessions on using specific libraries </li>
<li>Case studies on using Boost </li>
<li>Experts panels </li>
<li>Advanced sessions on implementation techniques used within Boost
libraries </li>
<li>TR1 (and TR2) </li>
<li>Development workshops to extend or enhance existing Boost libraries
</li>
<li>Workshops on design process </li>
<li>Infrastructure workshops
<ul>
<li>Build tools </li>
<li>Website </li>
<li>Testing </li>
</ul>
</li>
<li>C++0x and how it will change life for users and library writers </li>
<li>Concepts and Generic Programming </li>
<li>Other topics likely to be of great interest to Boost users and
developers </li>
</ul>
<p>Interactive and collaborative sessions are encouraged, as this is the
nature of both the online Boost community and the style of learning and
participation that has proven most successful at such events. Sessions can
be tutorial based, with an emphasis on interaction and participant
involvement, or workshop based, whether hands-on programming or paper-based,
discussion-driven collaborative work. </p>
<h2>Submitting a <a name="proposal">proposal</a></h2>
<p>Please include: </p>
<ul>
<li>The working title of the session </li>
<li>Type of session: presentation/panel/tutorial/workshop/other </li>
<li>A paragraph or two describing the session, suitable for the conference
web site </li>
<li>Proposed length: 45/90 minutes, half/full day </li>
<li>Alternate length, if any: 45/90 minutes, half/full day </li>
<li>Audience: users/developers/both </li>
<li>Level: basic/intermediate/advanced </li>
<li>A biography, suitable for the conference web site </li>
<li>Your contact information (will not be made public) </li>
<li>Financial support needs, if any, with rationle (will not be made
public) </li>
</ul>
<p>Please submit via email to conference@boost-consulting.com, with a
subject that begins "BoostCon
proposal" </p>
<h2><a name="Timeline">Timeline</a></h2>
<p><strong>Proposals due</strong> October 27, 2006 </p>
<p><strong>Proposals acceptances sent</strong> November 10, 2006 </p>
<p><strong>Session materials due</strong> March 15, 2007 </p>
<h2 id="Otherarrangements"><a name="Other">Other</a> arrangements</h2>
<p>Like Boost itself,
BoostCon is strictly non-profit. Conference organizers and presenters
are not paid for their time. Any surplus money will be rolled over into the
succeeding year
BoostCon budget. </p>
<p>To reduce the price for attendees this first year, conference organizers
and presenters will pay the regular admission fee and will receive no
compensation. We recognize this is tough for presenters on tight budgets, so
will consider providing financial support if requested, based on budget and
the applicant's needs.</p>
<hr>
<p>Revised:
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B %Y" startspan -->29 September 2006<!--webbot bot="Timestamp" endspan i-checksum="39511" --></p>
<p>� Copyright David Abrahams and Beman Dawes 2006</p>
<p>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="http://www.boost.org/LICENSE_1_0.txt">
LICENSE_1_0.txt</a> or copy at
<a href="http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)
</p>
</body>
</html>