Redirect to the BoostCon site

[SVN r37076]
This commit is contained in:
Dave Abrahams 2007-02-26 06:42:41 +00:00
parent 7e043f6736
commit 41a0f39f87
2 changed files with 12 additions and 522 deletions

View File

@ -1,418 +1,12 @@
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" />
<title>BoostCon 2007 • May 14-18 2007 Boost</title>
<style type="text/css">
/*
:Author: David Goodger
:Contact: goodger@python.org
:Date: $Date$
:Revision: $Revision$
:Copyright: This stylesheet has been placed in the public domain.
Default cascading style sheet for the HTML output of Docutils.
See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
customize this style sheet.
*/
/* used to remove borders from tables and images */
.borderless, table.borderless td, table.borderless th {
border: 0 }
table.borderless td, table.borderless th {
/* Override padding for "table.docutils td" with "! important".
The right padding separates the table cells. */
padding: 0 0.5em 0 0 ! important }
.first {
/* Override more specific margin styles with "! important". */
margin-top: 0 ! important }
.last, .with-subtitle {
margin-bottom: 0 ! important }
.hidden {
display: none }
a.toc-backref {
text-decoration: none ;
color: black }
blockquote.epigraph {
margin: 2em 5em ; }
dl.docutils dd {
margin-bottom: 0.5em }
/* Uncomment (and remove this text!) to get bold-faced definition list terms
dl.docutils dt {
font-weight: bold }
*/
div.abstract {
margin: 2em 5em }
div.abstract p.topic-title {
font-weight: bold ;
text-align: center }
div.admonition, div.attention, div.caution, div.danger, div.error,
div.hint, div.important, div.note, div.tip, div.warning {
margin: 2em ;
border: medium outset ;
padding: 1em }
div.admonition p.admonition-title, div.hint p.admonition-title,
div.important p.admonition-title, div.note p.admonition-title,
div.tip p.admonition-title {
font-weight: bold ;
font-family: sans-serif }
div.attention p.admonition-title, div.caution p.admonition-title,
div.danger p.admonition-title, div.error p.admonition-title,
div.warning p.admonition-title {
color: red ;
font-weight: bold ;
font-family: sans-serif }
/* Uncomment (and remove this text!) to get reduced vertical space in
compound paragraphs.
div.compound .compound-first, div.compound .compound-middle {
margin-bottom: 0.5em }
div.compound .compound-last, div.compound .compound-middle {
margin-top: 0.5em }
*/
div.dedication {
margin: 2em 5em ;
text-align: center ;
font-style: italic }
div.dedication p.topic-title {
font-weight: bold ;
font-style: normal }
div.figure {
margin-left: 2em ;
margin-right: 2em }
div.footer, div.header {
clear: both;
font-size: smaller }
div.line-block {
display: block ;
margin-top: 1em ;
margin-bottom: 1em }
div.line-block div.line-block {
margin-top: 0 ;
margin-bottom: 0 ;
margin-left: 1.5em }
div.sidebar {
margin-left: 1em ;
border: medium outset ;
padding: 1em ;
background-color: #ffffee ;
width: 40% ;
float: right ;
clear: right }
div.sidebar p.rubric {
font-family: sans-serif ;
font-size: medium }
div.system-messages {
margin: 5em }
div.system-messages h1 {
color: red }
div.system-message {
border: medium outset ;
padding: 1em }
div.system-message p.system-message-title {
color: red ;
font-weight: bold }
div.topic {
margin: 2em }
h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
margin-top: 0.4em }
h1.title {
text-align: center }
h2.subtitle {
text-align: center }
hr.docutils {
width: 75% }
img.align-left {
clear: left }
img.align-right {
clear: right }
ol.simple, ul.simple {
margin-bottom: 1em }
ol.arabic {
list-style: decimal }
ol.loweralpha {
list-style: lower-alpha }
ol.upperalpha {
list-style: upper-alpha }
ol.lowerroman {
list-style: lower-roman }
ol.upperroman {
list-style: upper-roman }
p.attribution {
text-align: right ;
margin-left: 50% }
p.caption {
font-style: italic }
p.credits {
font-style: italic ;
font-size: smaller }
p.label {
white-space: nowrap }
p.rubric {
font-weight: bold ;
font-size: larger ;
color: maroon ;
text-align: center }
p.sidebar-title {
font-family: sans-serif ;
font-weight: bold ;
font-size: larger }
p.sidebar-subtitle {
font-family: sans-serif ;
font-weight: bold }
p.topic-title {
font-weight: bold }
pre.address {
margin-bottom: 0 ;
margin-top: 0 ;
font-family: serif ;
font-size: 100% }
pre.literal-block, pre.doctest-block {
margin-left: 2em ;
margin-right: 2em }
span.classifier {
font-family: sans-serif ;
font-style: oblique }
span.classifier-delimiter {
font-family: sans-serif ;
font-weight: bold }
span.interpreted {
font-family: sans-serif }
span.option {
white-space: nowrap }
span.pre {
white-space: pre }
span.problematic {
color: red }
span.section-subtitle {
/* font-size relative to parent (h1..h6 element) */
font-size: 80% }
table.citation {
border-left: solid 1px gray;
margin-left: 1px }
table.docinfo {
margin: 2em 4em }
table.docutils {
margin-top: 0.5em ;
margin-bottom: 0.5em }
table.footnote {
border-left: solid 1px black;
margin-left: 1px }
table.docutils td, table.docutils th,
table.docinfo td, table.docinfo th {
padding-left: 0.5em ;
padding-right: 0.5em ;
vertical-align: top }
table.docutils th.field-name, table.docinfo th.docinfo-name {
font-weight: bold ;
text-align: left ;
white-space: nowrap ;
padding-left: 0 }
h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
font-size: 100% }
ul.auto-toc {
list-style-type: none }
</style>
<meta http-equiv="refresh" content="0; URL=http://www.boostcon.com">
</head>
<body>
<div class="document" id="boostcon-2007-may-14-18-2007-logo">
<h1 class="title">BoostCon 2007 • May 14-18 2007 <a class="reference" href="../index.htm"><img alt="Boost" src="../boost.png" /></a></h1>
The BoostCon site is
<a href="http://www.boostcon.com">live</a>!
</body>
</html>
<!-- Copyright David Abrahams 2006. Distributed under the Boost -->
<!-- Software License, Version 1.0. (See accompanying -->
<!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
<style type="text/css">
table.borderless {
border: 0;
}
table.borderless td {
border-style: none none none none;
}
</style><hr class="docutils" />
<p>This inaugural Boost conference promises to be the main
face-to-face venue for all things Boost, from using libraries to
writing them, from evangelizing Boost to deployment within your
organization, from infrastructure and process to vision and
mission, and from TR1 to TR2. Given the range and interests of the
participants, the event is going to be intense and in-depth.</p>
<div class="contents topic">
<p class="topic-title first"><a id="index" name="index">Index</a></p>
<ul class="simple">
<li><a class="reference" href="#tracks" id="id8" name="id8">Tracks</a></li>
<li><a class="reference" href="#sessions" id="id9" name="id9">Sessions</a></li>
<li><a class="reference" href="#venue" id="id10" name="id10">Venue</a></li>
<li><a class="reference" href="#hotel" id="id11" name="id11">Hotel</a></li>
<li><a class="reference" href="#conference-size" id="id12" name="id12">Conference Size</a></li>
<li><a class="reference" href="#id5" id="id13" name="id13">Sessions</a></li>
<li><a class="reference" href="#registration" id="id14" name="id14">Registration</a></li>
<li><a class="reference" href="#organizing-committee" id="id15" name="id15">Organizing Committee</a></li>
</ul>
</div>
<div class="section">
<h1><a class="toc-backref" href="#id8" id="tracks" name="tracks">Tracks</a></h1>
<p>Recognizing the breadth of the community, we are offering two
primary tracks: the first three days will be focused mostly on the
practical interests of Boost and TR1 end-users, and the last three
will be directed more towards hard-core Boost developers, with one
overlap day at midweek. Thus, the conference fosters interaction
both within <em>and</em> across these tracks, with an emphasis on service
to our user base.</p>
<p>Sessions will run in the morning and evening, leaving a midday
break of several hours so that attendees can get out and enjoy the
town and its surroundings, or just to have time to work together in
small, informal groups.</p>
</div>
<div class="section">
<h1><a class="toc-backref" href="#id9" id="sessions" name="sessions">Sessions</a></h1>
<p>In the spirit of Boost, many sessions will be participatory and/or
collaborative in nature. The program committee has issued a <a class="reference" href="http://www.boost.org/more/BoostCon07_session_call.html">call
for sessions</a>. Please raise any questions about—or ideas for—the
conference on the <a class="reference" href="http://www.boost.org/more/mailing_lists.htm">Boost mailing lists</a>.</p>
</div>
<div class="section">
<h1><a class="toc-backref" href="#id10" id="venue" name="venue">Venue</a></h1>
<p>The main venue for this conference will be the <a class="reference" href="http://www.aspenphys.org">Aspen Center for
Physics</a> in Aspen, Colorado. The town of Aspen is known for its
world-class cuisine and its envigorating, natural setting. As
generations of scientists can attest, the Center's beautiful
location and its low-key atmosphere create a unique and lively
environment for thought, education, and collaboration.</p>
</div>
<div class="section">
<h1><a class="toc-backref" href="#id11" id="hotel" name="hotel">Hotel</a></h1>
<p>The main conference hotel will be the <a class="reference" href="http://aspenmeadowsresort.dolce.com/">Aspen Meadows Resort</a>.
Located within walking distance of the Physics Center, the Meadows
provides 90 rooms, a restaurant, and overflow conference facilities
should the event expand.</p>
</div>
<div class="section">
<h1><a class="toc-backref" href="#id12" id="conference-size" name="conference-size">Conference Size</a></h1>
<p>Much more than having a great number of attendees, it's important
that this first BoostCon be a success, so we're starting small.
Registration will initially be limited to just 100 places, except
that we'll accomodate 200 participants on Wednesday, when the two
main tracks overlap. Contingency plans are in place that <em>may</em> allow
us to expand registration should demand prove overwhelming, but
when registration opens we recommend securing your place early, in
case that isn't possible.</p>
</div>
<div class="section">
<h1><a class="toc-backref" href="#id13" id="id5" name="id5">Sessions</a></h1>
<p>The program committee is currently forming and drafting a call for
sessions; watch this space in upcoming weeks for an outline of
workshop, session, and talk ideas, and a request for submissions.</p>
</div>
<div class="section">
<h1><a class="toc-backref" href="#id14" id="registration" name="registration">Registration</a></h1>
<p>Official Registration is not yet open, but an <a class="reference" href="http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?BoostCon">informal attendee
list</a> for those likely to attend has been set up on the Boost
Wiki. The conference organizers would very much appreciate it if
you could add an entry to this list if you think you'll be there,
to help us with planning.</p>
<div class="admonition-register-interest-in-attending-boostcon-2007 admonition">
<p class="first admonition-title"><a class="reference" href="http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?BoostCon">Register interest</a> in attending BoostCon 2007</p>
<p class="last">Thank you!</p>
</div>
</div>
<div class="section">
<h1><a class="toc-backref" href="#id15" id="organizing-committee" name="organizing-committee">Organizing Committee</a></h1>
<table border="1" class="borderless docutils">
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<tbody valign="top">
<tr><td>David Abrahams</td>
<td>Beman Dawes</td>
<td>Jeff Garland</td>
</tr>
<tr><td>Joel de Guzman</td>
<td>Kevlin Henney</td>
<td>Scott Meyers</td>
</tr>
<tr><td>Eric Niebler</td>
<td>Sean Parent</td>
<td>Rene Rivera</td>
</tr>
<tr><td>Jeremy Siek</td>
<td>Matthias Troyer</td>
<td>&nbsp;</td>
</tr>
</tbody>
</table>
</div>
</div>
</body>
</html>

View File

@ -1,116 +1,12 @@
<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>
<meta http-equiv="refresh" content="0; URL=http://www.boostcon.com/program/call-for-sessions">
</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 Sessions</h1>
<p>The first annual Boost conference will take place in Aspen, Colorado, May
14-18, 2007.</p>
<p>This inaugural Boost conference promises to be the main face-to-face
venue for all things Boost, from using libraries to writing them, from
evangelizing Boost to deployment within your organization, from
infrastructure and process to vision and mission, and from TR1 to TR2. Given
the range and interests of the participants, the event is going to be
intense and in-depth.</p>
<p>BoostCon 2007 is looking for session presenters. 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 practitioners 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 into 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>Tentative scheduling plans are for 90 minute sessions. You may submit a
proposal for fractions or multiples of 90-minutes. Fractional proposals will
be grouped into 90 minute sessions covering related topics. Longer sessions,
such as tutorials and classes, will be assigned 90 minute, three hour (i.e.
half day), or six hour (i.e. full day) time slots.</p>
<p>Please include: </p>
<ul>
<li>The working title. </li>
<li>Type of session: presentation/panel/tutorial/workshop/lightning-talk/other </li>
<li>A paragraph or two describing the topic covered, suitable for the conference
web site </li>
<li>Proposed length: 10-20 minute lightning-talks, 45 minutes, 90 minutes, half-day, full day </li>
<li>Alternate lengths, if you are willing to made adjustments: 10-20
minute lightning-talks, 45 minutes, 90 minutes, half-day, 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>
</ul>
<p>Please submit via email to <a href="mailto:boostcon-program@lists.boost-consulting.com">boostcon-program@lists.boost-consulting.com</a>, with a
subject that begins &quot;BoostCon
proposal&quot; </p>
<hr>
<p>Revised:
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B %Y" startspan -->4 December 2006<!--webbot bot="Timestamp" endspan i-checksum="40199" --></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>
The BoostCon site is
<a href="http://www.boostcon.com/program/call-for-sessions">live</a>!
</body>
</html>
<!-- Copyright David Abrahams 2006. Distributed under the Boost -->
<!-- Software License, Version 1.0. (See accompanying -->
<!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->