cpp_committee_meetings.html 6.9 KB

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