1 | <html> |
---|
2 | |
---|
3 | <head> |
---|
4 | <meta http-equiv="Content-Language" content="en-us"> |
---|
5 | <meta name="GENERATOR" content="Microsoft FrontPage 5.0"> |
---|
6 | <meta name="ProgId" content="FrontPage.Editor.Document"> |
---|
7 | <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> |
---|
8 | <title>C++ Committee Meetings</title> |
---|
9 | </head> |
---|
10 | |
---|
11 | <body bgcolor="#FFFFFF"> |
---|
12 | |
---|
13 | <h1>C++ Committee Meeting FAQ for Boost Members</h1> |
---|
14 | <p><b>Who can attend C++ Committee meetings?</b> Members of |
---|
15 | J16 (the INCITS/ANSI committee) or of a WG21 (ISO) member country committee |
---|
16 | ("national body" in |
---|
17 | ISO-speak). <a href="http://www.ncits.org/"> |
---|
18 | INCITS</a> has broadened J16 membership requirements so anyone can |
---|
19 | join, regardless of nationality or employer.</p> |
---|
20 | <p>In addition, a small number of "technical experts" who are not committee |
---|
21 | members can also attend meetings. The "technical expert" umbrella is broad enough to cover |
---|
22 | the |
---|
23 | Boost members who attend meetings.</p> |
---|
24 | <p><b>When and where is the next meeting?</b> There are two meetings a year. The |
---|
25 | Fall meeting is usually in North America, and the Spring meeting is usually |
---|
26 | outside North America. See a general |
---|
27 | <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/meetings">list of meeting locations and |
---|
28 | dates</a>. Detailed information about a particular meeting, including hotel |
---|
29 | information, is usually provided in a paper appearing in one of |
---|
30 | <a href="#Mailing">mailings</a> for the prior meeting. If there isn't a link to |
---|
31 | it on the <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/meetings"> |
---|
32 | Meetings</a> web page, you will have to go to |
---|
33 | the committee's <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/"> |
---|
34 | Papers</a> page and search a bit.</p> |
---|
35 | <p><b>Is there a fee for attending meetings?</b> No, but there can be a lot of |
---|
36 | incidental expenses like travel, lodging, and meals, and there is a $US 800 a |
---|
37 | year INCITS fee to become a voting member.</p> |
---|
38 | <p><b>What is the schedule?</b> The meetings start at 9:00AM on |
---|
39 | Monday, and 8:30AM other days, unless otherwise announced. It is best to arrive |
---|
40 | a half-hour early to grab a good seat, some coffee, tea, or donuts, and to say |
---|
41 | hello to people. (There is also a Sunday evening a WG21 administrative meeting, |
---|
42 | which is closed except to delegates from national bodies.)</p> |
---|
43 | <p>The meetings generally end on Friday, although there is discussion of |
---|
44 | extending them one extra day until the next standard ships. The last day the meeting is generally over by 11:00AM. Because |
---|
45 | the last day's meeting is for formal votes only, it is primarily of interest only to |
---|
46 | actual committee |
---|
47 | members.</p> |
---|
48 | <p>Sometimes there are evening technical sessions; the details aren't |
---|
49 | usually available until the Monday morning meeting. There may be a |
---|
50 | reception one evening, and, yes, significant others are |
---|
51 | invited. Again, details usually become available Monday morning.</p> |
---|
52 | <p><b>What actually happens at the meetings?</b> Monday morning an hour or two |
---|
53 | is spent in full committee on administrivia, and then the committee breaks up |
---|
54 | into working groups (Core, Library, and Enhancements). The full committee also |
---|
55 | gets together later in the week to hear working group progress reports.</p> |
---|
56 | <p>The working groups are where most technical activities take place. Each |
---|
57 | active issue that appears on an issues list is discussed, as are papers from the |
---|
58 | mailing. Most issues are non-controversial and disposed of in a few minutes. |
---|
59 | Technical discussions are often led by long-term committee members, often |
---|
60 | referring to past decisions or longstanding working group practice. Sometimes a |
---|
61 | controversy erupts. It takes first-time attendees awhile to understand the |
---|
62 | discussions and how decisions are actually made. The working group chairperson |
---|
63 | moderates.</p> |
---|
64 | <p>Sometimes straw polls are taken. In a straw poll anyone attending can vote, |
---|
65 | in contrast to the formal votes taken by the full committee, where only voting |
---|
66 | members can vote.</p> |
---|
67 | <p>Lunch break is an hour and a half. Informal subgroups often lunch |
---|
68 | together; a lot of technical problems are discussed or actually solved at lunch, |
---|
69 | or later at dinner. In many ways these discussions involving only a few people |
---|
70 | are the most interesting. Sometimes during the regular meetings, a working group |
---|
71 | chair will break off a sub-group to tackle a difficult problem. </p> |
---|
72 | <p><b>Do I have to stay at the main hotel?</b> No, and committee members on |
---|
73 | tight budgets often stay at other, cheaper, hotels. (The main hotels are usually |
---|
74 | chosen because they have large meeting rooms available, and thus tend to be pricey.) |
---|
75 | The advantage of staying at the main hotel is that it is then easier to |
---|
76 | participate in the off-line discussions which can be at least as interesting |
---|
77 | as what actually happens in the scheduled meetings.</p> |
---|
78 | <p><b>What do people wear at meetings?</b> Programmer casual. No neckties |
---|
79 | to be seen. </p> |
---|
80 | <p><b>What should I bring to a meeting?</b> It is almost essential to have a |
---|
81 | laptop computer along. There is a committee LAN with a wiki and Internet connectivity. |
---|
82 | Wireless connectivity has become the norm, although there is usually a wired hub |
---|
83 | or two for those needed wired access.</p> |
---|
84 | <p><b>What should I do to prepare for a meeting?</b> It is helpful to have |
---|
85 | downloaded the mailing or individual papers for the |
---|
86 | meeting, and read any papers you are interested in. Familiarize yourself with |
---|
87 | the issues lists if you haven't done so already. Decide which of the working |
---|
88 | groups you want to attend.</p> |
---|
89 | <p><b>What is a "<a name="Paper">Paper</a>"?</b> An electronic document containing issues, |
---|
90 | proposals, or anything else the committee is interested in. Very little gets |
---|
91 | discussed at a meeting, much less acted upon, unless it is presented in a paper. |
---|
92 | <a href="http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/">Papers are available</a> |
---|
93 | to anyone. Papers don't just appear randomly; they become available four (lately |
---|
94 | six) times a |
---|
95 | year, before and after each meeting. Committee members often refer to a paper by |
---|
96 | saying what mailing it was in: "See the pre-Redmond mailing."</p> |
---|
97 | <p><b>What is a "<a name="Mailing">Mailing</a>"?</b> A mailing is the |
---|
98 | set of papers prepared four to six times a year before and after each meeting, |
---|
99 | or between meetings. It |
---|
100 | is physically just a |
---|
101 | <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/mailings/">.zip or .gz</a> |
---|
102 | archive of |
---|
103 | all the papers for a meeting. Although the mailing's archive file itself is only available to committee members and technical |
---|
104 | experts, the contents (except copies of the standard) are available to the |
---|
105 | general public as individual papers. The ways of ISO are |
---|
106 | inscrutable.</p> |
---|
107 | <p><b>What is a "Reflector"?</b> The committee's mailing lists are |
---|
108 | called "reflectors". There are a number of them; "all", "core", "lib", and "ext" |
---|
109 | are the main ones. As a courtesy, Boost technical experts can be added to |
---|
110 | committee reflectors at the request of a committee member. </p> |
---|
111 | <hr> |
---|
112 | <p>Revised |
---|
113 | <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%B %d, %Y" startspan -->April 17, 2005<!--webbot bot="Timestamp" endspan i-checksum="17669" --></p> |
---|
114 | <p>© Copyright Beman Dawes, 2002</p> |
---|
115 | <p> Use, modification, and distribution are subject to the Boost Software |
---|
116 | License, Version 1.0. (See accompanying file <a href="../LICENSE_1_0.txt"> |
---|
117 | LICENSE_1_0.txt</a> or copy at <a href="http://www.boost.org/LICENSE_1_0.txt"> |
---|
118 | www.boost.org/LICENSE_1_0.txt</a>)</p> |
---|
119 | |
---|
120 | </body> |
---|
121 | |
---|
122 | </html> |
---|