mirror of
https://github.com/boostorg/website.git
synced 2026-01-29 20:12:14 +00:00
de7de29833
Unmerged changesets: [44594],[44596]. ------------------------------------------------------------------------ r44579 | danieljames | 2008-04-19 14:49:55 +0100 (Sat, 19 Apr 2008) | 1 line Add comments linking to the website updating page to all html pages and index.php. ------------------------------------------------------------------------ r44580 | danieljames | 2008-04-19 15:00:58 +0100 (Sat, 19 Apr 2008) | 1 line Replace unicode quotes with character entities. ------------------------------------------------------------------------ r44581 | danieljames | 2008-04-19 15:03:59 +0100 (Sat, 19 Apr 2008) | 1 line Convert a couple more quotes to character entities. ------------------------------------------------------------------------ r44582 | danieljames | 2008-04-19 15:05:44 +0100 (Sat, 19 Apr 2008) | 1 line Run tidy on the html files. ------------------------------------------------------------------------ r44583 | danieljames | 2008-04-19 15:21:52 +0100 (Sat, 19 Apr 2008) | 3 lines Redirect boost.org => www.boost.org, so that there is a cannonical URL. (This won't have any real effect until it's merged into live). ------------------------------------------------------------------------ r44598 | danieljames | 2008-04-19 17:58:42 +0100 (Sat, 19 Apr 2008) | 2 lines Try to fix Boost.Test's test tool reference. Refs #1799 ------------------------------------------------------------------------ [SVN r44745]
203 lines
9.8 KiB
HTML
203 lines
9.8 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
|
<head>
|
|
<title>C++ Committee Meetings</title>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
|
|
<link rel="icon" href="/favicon.ico" type="image/ico" />
|
|
<link rel="stylesheet" type="text/css" href=
|
|
"/style/section-community.css" />
|
|
<!--[if IE]> <style type="text/css"> body { behavior: url(/style/csshover.htc); } </style> <![endif]-->
|
|
</head><!--
|
|
Note: Editing website content is documented at:
|
|
http://www.boost.org/development/website_updating.html
|
|
-->
|
|
|
|
<body>
|
|
<div id="heading">
|
|
<!--#include virtual="/common/heading.html" -->
|
|
</div>
|
|
|
|
<div id="body">
|
|
<div id="body-inner">
|
|
<div id="content">
|
|
<div class="section" id="intro">
|
|
<div class="section-0">
|
|
<div class="section-title">
|
|
<h1>C++ Committee Meetings</h1>
|
|
</div>
|
|
|
|
<div class="section-body">
|
|
<h1>C++ Committee Meeting FAQ for Boost Members</h1>
|
|
|
|
<p><strong>Who can attend C++ Committee meetings?</strong>
|
|
Members of J16 (the INCITS/ANSI committee) or of a WG21 (ISO)
|
|
member country committee ("national body" in ISO-speak).
|
|
<a href="http://www.ncits.org/">INCITS</a> has broadened J16
|
|
membership requirements so anyone can join, regardless of
|
|
nationality or employer.</p>
|
|
|
|
<p>In addition, a small number of "technical experts" who are
|
|
not committee members can also attend meetings. The "technical
|
|
expert" umbrella is broad enough to cover the Boost members who
|
|
attend meetings.</p>
|
|
|
|
<p><strong>When and where is the next meeting?</strong> There
|
|
are two meetings a year. The Fall meeting is usually in North
|
|
America, and the Spring meeting is usually outside North
|
|
America. See a general <a href=
|
|
"http://www.open-std.org/jtc1/sc22/wg21/docs/meetings">list of
|
|
meeting locations and dates</a>. Detailed information about a
|
|
particular meeting, including hotel information, is usually
|
|
provided in a paper appearing in one of <a href=
|
|
"#Mailing">mailings</a> for the prior meeting. If there isn't a
|
|
link to it on the <a href=
|
|
"http://www.open-std.org/jtc1/sc22/wg21/docs/meetings">Meetings</a>
|
|
web page, you will have to go to the committee's <a href=
|
|
"http://www.open-std.org/jtc1/sc22/wg21/docs/papers/">Papers</a>
|
|
page and search a bit.</p>
|
|
|
|
<p><strong>Is there a fee for attending meetings?</strong> No,
|
|
but there can be a lot of incidental expenses like travel,
|
|
lodging, and meals, and there is a $US 800 a year INCITS fee to
|
|
become a voting member.</p>
|
|
|
|
<p><strong>What is the schedule?</strong> The meetings start at
|
|
9:00AM on Monday, and 8:30AM other days, unless otherwise
|
|
announced. It is best to arrive a half-hour early to grab a
|
|
good seat, some coffee, tea, or donuts, and to say hello to
|
|
people. (There is also a Sunday evening a WG21 administrative
|
|
meeting, which is closed except to delegates from national
|
|
bodies.)</p>
|
|
|
|
<p>The meetings generally end on Friday, although there is
|
|
discussion of extending them one extra day until the next
|
|
standard ships. The last day the meeting is generally over by
|
|
11:00AM. Because the last day's meeting is for formal votes
|
|
only, it is primarily of interest only to actual committee
|
|
members.</p>
|
|
|
|
<p>Sometimes there are evening technical sessions; the details
|
|
aren't usually available until the Monday morning meeting.
|
|
There may be a reception one evening, and, yes, significant
|
|
others are invited. Again, details usually become available
|
|
Monday morning.</p>
|
|
|
|
<p><strong>What actually happens at the meetings?</strong>
|
|
Monday morning an hour or two is spent in full committee on
|
|
administrivia, and then the committee breaks up into working
|
|
groups (Core, Library, and Enhancements). The full committee
|
|
also gets together later in the week to hear working group
|
|
progress reports.</p>
|
|
|
|
<p>The working groups are where most technical activities take
|
|
place. Each active issue that appears on an issues list is
|
|
discussed, as are papers from the mailing. Most issues are
|
|
non-controversial and disposed of in a few minutes. Technical
|
|
discussions are often led by long-term committee members, often
|
|
referring to past decisions or longstanding working group
|
|
practice. Sometimes a controversy erupts. It takes first-time
|
|
attendees awhile to understand the discussions and how
|
|
decisions are actually made. The working group chairperson
|
|
moderates.</p>
|
|
|
|
<p>Sometimes straw polls are taken. In a straw poll anyone
|
|
attending can vote, in contrast to the formal votes taken by
|
|
the full committee, where only voting members can vote.</p>
|
|
|
|
<p>Lunch break is an hour and a half. Informal subgroups often
|
|
lunch together; a lot of technical problems are discussed or
|
|
actually solved at lunch, or later at dinner. In many ways
|
|
these discussions involving only a few people are the most
|
|
interesting. Sometimes during the regular meetings, a working
|
|
group chair will break off a sub-group to tackle a difficult
|
|
problem.</p>
|
|
|
|
<p><strong>Do I have to stay at the main hotel?</strong> No,
|
|
and committee members on tight budgets often stay at other,
|
|
cheaper, hotels. (The main hotels are usually chosen because
|
|
they have large meeting rooms available, and thus tend to be
|
|
pricey.) The advantage of staying at the main hotel is that it
|
|
is then easier to participate in the off-line discussions which
|
|
can be at least as interesting as what actually happens in the
|
|
scheduled meetings.</p>
|
|
|
|
<p><strong>What do people wear at meetings?</strong> Programmer
|
|
casual. No neckties to be seen.</p>
|
|
|
|
<p><strong>What should I bring to a meeting?</strong> It is
|
|
almost essential to have a laptop computer along. There is a
|
|
committee LAN with a wiki and Internet connectivity. Wireless
|
|
connectivity has become the norm, although there is usually a
|
|
wired hub or two for those needed wired access.</p>
|
|
|
|
<p><strong>What should I do to prepare for a meeting?</strong>
|
|
It is helpful to have downloaded the mailing or individual
|
|
papers for the meeting, and read any papers you are interested
|
|
in. Familiarize yourself with the issues lists if you haven't
|
|
done so already. Decide which of the working groups you want to
|
|
attend.</p>
|
|
|
|
<p><strong>What is a "<a name="Paper" id=
|
|
"Paper">Paper</a>"?</strong> An electronic document containing
|
|
issues, proposals, or anything else the committee is interested
|
|
in. Very little gets discussed at a meeting, much less acted
|
|
upon, unless it is presented in a paper. <a href=
|
|
"http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/">Papers are
|
|
available</a> to anyone. Papers don't just appear randomly;
|
|
they become available four (lately six) times a year, before
|
|
and after each meeting. Committee members often refer to a
|
|
paper by saying what mailing it was in: "See the pre-Redmond
|
|
mailing."</p>
|
|
|
|
<p><strong>What is a "<a name="Mailing" id=
|
|
"Mailing">Mailing</a>"?</strong> A mailing is the set of papers
|
|
prepared four to six times a year before and after each
|
|
meeting, or between meetings. It is physically just a <a href=
|
|
"http://www.open-std.org/jtc1/sc22/wg21/docs/mailings/">.zip or
|
|
.gz</a> archive of all the papers for a meeting. Although the
|
|
mailing's archive file itself is only available to committee
|
|
members and technical experts, the contents (except copies of
|
|
the standard) are available to the general public as individual
|
|
papers. The ways of ISO are inscrutable.</p>
|
|
|
|
<p><strong>What is a "Reflector"?</strong> The committee's
|
|
mailing lists are called "reflectors". There are a number of
|
|
them; "all", "core", "lib", and "ext" are the main ones. As a
|
|
courtesy, Boost technical experts can be added to committee
|
|
reflectors at the request of a committee member.</p>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
|
|
<div id="sidebar">
|
|
<!--#include virtual="/common/sidebar-common.html" -->
|
|
<!--#include virtual="/common/sidebar-community.html" -->
|
|
</div>
|
|
|
|
<div class="clear"></div>
|
|
</div>
|
|
</div>
|
|
|
|
<div id="footer">
|
|
<div id="footer-left">
|
|
<div id="revised">
|
|
<p>Revised $Date$</p>
|
|
</div>
|
|
|
|
<div id="copyright">
|
|
<p>Copyright Beman Dawes 2002.</p>
|
|
</div><!--#include virtual="/common/footer-license.html" -->
|
|
</div>
|
|
|
|
<div id="footer-right">
|
|
<!--#include virtual="/common/footer-banners.html" -->
|
|
</div>
|
|
|
|
<div class="clear"></div>
|
|
</div>
|
|
</body>
|
|
</html>
|