mailing_lists.htm 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  2. <html>
  3. <head>
  4. <title>Mailing Lists</title>
  5. <meta name="generator" content=
  6. "Microsoft FrontPage 5.0">
  7. <meta name="generator" content="Microsoft FrontPage 5.0">
  8. <meta name="generator" content="Microsoft FrontPage 5.0">
  9. <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
  10. <meta name="GENERATOR" content="Microsoft FrontPage 5.0">
  11. <meta name="ProgId" content="FrontPage.Editor.Document">
  12. <style type="text/css">
  13. @import ../boost.css
  14. .first {
  15. margin-top: 0 }
  16. .last {
  17. margin-bottom: 0 }
  18. div.attention, div.caution, div.danger, div.error, div.hint,
  19. div.important, div.note, div.tip, div.warning, div.admonition {
  20. margin: 2em ;
  21. border: medium outset ;
  22. padding: 1em }
  23. div.attention p.admonition-title, div.caution p.admonition-title,
  24. div.danger p.admonition-title, div.error p.admonition-title,
  25. div.warning p.admonition-title {
  26. color: red ;
  27. font-weight: bold ;
  28. font-family: sans-serif }
  29. div.hint p.admonition-title, div.important p.admonition-title,
  30. div.note p.admonition-title, div.tip p.admonition-title,
  31. div.admonition p.admonition-title {
  32. font-weight: bold ;
  33. font-family: sans-serif }
  34. </style>
  35. </head>
  36. <body bgcolor="#FFFFFF" text="#000000">
  37. <table summary="Navigational header"
  38. border="1" bgcolor="#007F7F" cellpadding="2">
  39. <tr>
  40. <td bgcolor="#FFFFFF"><img src="../boost.png" alt=
  41. "boost.png (6897 bytes)" width="277" height="86"></td>
  42. <td><a href="../index.htm"><font face="Arial" color=
  43. "#FFFFFF"><big>Home</big></font></a></td>
  44. <td><a href="../libs/libraries.htm"><font face="Arial" color=
  45. "#FFFFFF"><big>Libraries</big></font></a></td>
  46. <td><a href="../people/people.htm"><font face="Arial" color=
  47. "#FFFFFF"><big>People</big></font></a></td>
  48. <td><a href="faq.htm"><font face="Arial" color=
  49. "#FFFFFF"><big>FAQ</big></font></a></td>
  50. <td><a href="index.htm"><font face="Arial" color=
  51. "#FFFFFF"><big>More</big></font></a></td>
  52. </tr>
  53. </table>
  54. <h1>Boost Mailing Lists and other resources</h1>
  55. <p>The mailing lists are the heart of the Boost community.&nbsp; You may
  56. read the lists via full-content email, email digests, or via newsgroup
  57. reader.</p>
  58. <p>Hosting for the mailing lists is donated by the <a href=
  59. "http://www.osl.iu.edu/">Open Systems Lab at Indiana University</a>.</p>
  60. <p>Access to Boost mailing lists via newsgroup (NNTP) is contributed by
  61. <a href="http://www.gmane.org/">GMANE</a>.</p><a name="gmane_post" id=
  62. "gmane_post"></a><a name="important_notes" id="important_notes"></a>
  63. <div class="admonition-note admonition">
  64. <p class="first admonition-title">Before Posting</p>
  65. <p class="last">
  66. <b>Read the <a href="discussion_policy.htm">Discussion Policy and
  67. Guide to Effective Posting</a>.</b>&nbsp; Doing so will help you
  68. to ensure that your post is read by the people who can help you
  69. and received in the spirit in which it was intended.
  70. <p>
  71. <b>Subscribe your posting address.</b>&nbsp; As an anti-spam
  72. measure, postings to most Boost mailing lists will only be
  73. accepted if the posting's "From:" header contains an email
  74. address that is subscribed to the list.&nbsp; If you try to post from
  75. an address that isn't subscribed, you will probably get a
  76. message that says:</p>
  77. <blockquote>
  78. <tt>You are not allowed to post to this mailing list, and your message
  79. has been automatically rejected. If you think that your messages are
  80. being rejected in error, contact the mailing list owner at</tt> <i>list
  81. administrator's email address</i>.
  82. </blockquote>If you need to post from multiple email addresses, you
  83. should subscribe each one separately.&nbsp; You can configure your subscription
  84. settings for any address to disable mail delivery via each mailing list's
  85. web interface.
  86. <p>Even postings made through the <a href=
  87. "http://www.gmane.org">GMane</a> news server need to be made from
  88. subscribed addresses because GMane simply forwards your postings
  89. on to the appropriate email list.&nbsp; Don't be fooled by GMane's
  90. authentication message that says "you are now authorized to post
  91. to this list" after you answer its autogenerated mail; only
  92. subscribed addresses may post.</p>
  93. </div>
  94. <dl>
  95. <dt><a href="#users">Boost Users</a> list
  96. <dt><a href="#main">Boost developers</a> list</dt>
  97. <dd>
  98. <dl>
  99. <dt><a href="#archive">Archives</a> for the Boost developers
  100. list</dt>
  101. </dl>
  102. </dd>
  103. <dt><a href="#announce">Boost Announce</a> list</dt>
  104. <dt><a href="#interest">Boost Interest</a> list</dt>
  105. <dt><a href="#projects">Project-Specific</a> lists</dt>
  106. <dd>
  107. <dl>
  108. <dt><a href="#jamboost">Boost.Build</a> list</dt>
  109. <dt><a href="#cplussig">Python C++-Sig</a> (for Boost.Python)</dt>
  110. <dt><a href="#langbinding">Language Binding</a> (for generalized C++
  111. bindings)</dt>
  112. <dt><a href="#spirit">Boost.Spirit</a> lists</dt>
  113. <dt><a href="https://lists.sourceforge.net/lists/listinfo/boost-docs">Boost.Documentation</a> list</dt>
  114. <dt><a href="#testing">Testing</a> list (about regression-testing the
  115. boost libraries, not for the Boost.Test library specifically)</dt>
  116. <dt><a href="#ublas">Boost.uBlas (numerics)</a> list</dt>
  117. <dt><a href="#thread">Boost.Thread</a> list</dt>
  118. </dl>
  119. </dd>
  120. <dt><a href="#sandbox">Boost Sandbox CVS</a></dt>
  121. <dt><a href="#IRC">#boost IRC channel</a></dt>
  122. </dl>
  123. <h2>Boost <a name="users" id="users">Users</a> mailing list (also available
  124. via newsgroup)</h2>
  125. <p>This list is oriented toward casual users of the Boost
  126. libraries.&nbsp;It is a good place to start if you are having
  127. trouble getting started with Boost or its individual libraries. Feel
  128. free to post both "newbie" and more challenging questions, but
  129. please check first to see if there's an
  130. appropriate <a href="#projects">Project-Specific</a> list; you'll
  131. often get better answers in a forum dedicated to your problem
  132. area.&nbsp; This list is relatively
  133. low volume (less than 500 per month).&nbsp; Subscribe or unsubscribe
  134. at the <a href=
  135. "http://lists.boost.org/mailman/listinfo.cgi/boost-users">Boost Users list
  136. home page</a>.
  137. </p>
  138. <p>For those who prefer to participate via an NNTP (<a name=
  139. "users_newsgroup" id="users_newsgroup">newsgroup</a>) interface, a gateway
  140. to the Boost Users mailing list is available at <a href=
  141. "news://news.gmane.org/gmane.comp.lib.boost.user">news://news.gmane.org/gmane.comp.lib.boost.user</a>.
  142. You can also browse <a href=
  143. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.user">Gmane's
  144. searchable archive</a>.</p>
  145. <h2><a name="main" id="main">Boost</a> developers mailing list (also
  146. available via newsgroup)</h2>
  147. <p>This is the main Boost mailing list.&nbsp; It is high volume (over 1000
  148. messages per month), very technical, and oriented toward Boost library
  149. developers. It is also read by many other members interested in watching
  150. the Boost library development process.&nbsp; Virtually all Boost decisions,
  151. major or minor, technical or otherwise, are reached via public discussion
  152. on this mailing list.&nbsp; It is where the formal reviews of proposed
  153. libraries take place. Subscribe or unsubscribe at <a href=
  154. "http://lists.boost.org/mailman/listinfo.cgi/boost">http://lists.boost.org/mailman/listinfo.cgi/boost</a>.</p>
  155. <p>When we talk about the "members of Boost", we are talking about those
  156. signed up for this main mailing list.</p>
  157. <p>For those who prefer to participate via an NNTP (<a name="newsgroup" id=
  158. "newsgroup">newsgroup</a>) interface, a gateway to the Boost mailing list
  159. is available at <a href=
  160. "news://news.gmane.org/gmane.comp.lib.boost.devel">news://news.gmane.org/gmane.comp.lib.boost.devel</a>.
  161. <p>Preliminary libraries under discussion are available from the <a href=
  162. "http://boost-consulting.com/vault/">Vault</a>.</p>
  163. <h3><a name="archive" id="archive">Archives</a> for Boost developers
  164. list</h3>
  165. <p>A <a href=
  166. "http://aspn.activestate.com/ASPN/Mail/Browse/Threaded/boost/">searchable
  167. mailing list archive</a> has been generously contributed to the <a href=
  168. "http://aspn.activestate.com">ActiveState Programmer Network</a> by
  169. <a href="http://aspn.activestate.com">ActiveState Corporation</a>. <a href=
  170. "http://aspn.activestate.com"><img alt="ASPN logo" align="top" src=
  171. "http://www.activestate.com/img/ASPN_logo_smallest.gif" width="65" height=
  172. "20"></a><a href="http://www.activestate.com"><img alt="Active State logo"
  173. align="top" src="http://aspn.activestate.com/ASPN/img/ASLogo_57x25.gif"
  174. width="57" height= "25"></a></p>Other archives of Boost messages include the
  175. <a href="http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.devel">Boost
  176. GMane NNTP Archive</a>, <a href=
  177. "http://www.mail-archive.com/boost%40lists.boost.org/">The Mail
  178. Archive</a>, <a
  179. href="http://archives.free.net.ph/list/boost.en.html">The Free
  180. Network Group</a>, and of course there is a Google search link for our <a href=
  181. "http://lists.boost.org/Archives/boost/">MailMan Archive</a> on
  182. <a href="../index.htm">our home page</a>.
  183. <h2>Boost <a name="announce" id="announce">Announce</a> mailing list</h2>
  184. <p>This is an announce-only list for notification of upcoming software
  185. releases and formal reviews of proposed libraries. One to three messages
  186. per month.&nbsp; Subscribe or unsubscribe at the <a href=
  187. "http://lists.boost.org/mailman/listinfo.cgi/boost-announce">Boost Announce
  188. list home page</a>.</p><a name="interest" id="interest"></a>
  189. <h2>Boost Interest Mailing List</h2>
  190. <p>This list is a moderated low-traffic announcement-only list of interest
  191. to the Boost community. On topic messages will include announcements of
  192. books, magazine articles, papers, talks, seminars, products, tools, events,
  193. or conferences on advanced uses of C++,
  194. generic/generative/meta-programming, and, of course, the Boost libraries.
  195. Off topic will be discussion of any kind and job postings. Subscribe or
  196. unsubscribe at the <a href=
  197. "http://lists.boost.org/mailman/listinfo.cgi/boost-interest">Boost-Interest
  198. home page</a>.</p>
  199. <h2><a name="projects" id="projects">Project-Specific lists</a></h2>Several
  200. mailing lists have been established for specific Boost projects:
  201. <dl>
  202. <dd>
  203. <h3><a name="jamboost" id="jamboost">Boost.Build</a>
  204. list</h3>The mailing list for the <a href=
  205. "../tools/build">Boost Build System</a> is located <a href=
  206. "http://lists.boost.org/mailman/listinfo.cgi/boost-build">here</a>. GMane provides
  207. <a href="news://news.gmane.org/gmane.comp.lib.boost.build">NNTP
  208. access</a> and <a href=
  209. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.build">Searchable
  210. Archives</a> as well.
  211. <h3><a name="cplussig" id="cplussig">Python C++-Sig</a> (for
  212. Boost.Python)</h3>The <a href=
  213. "http://www.python.org/community/sigs/current/c++-sig/">Python C++-sig</a> is not
  214. strictly Boost-specific, but nearly all the traffic concerns <a href=
  215. "../libs/python">Boost.Python</a>. See also the <a href=
  216. "#langbinding">Language Binding</a> list below. GMane provides <a href=
  217. "news://news.gmane.org/gmane.comp.python.c%2b%2b">NNTP access</a> and
  218. <a href=
  219. "http://news.gmane.org/thread.php?group=gmane.comp.python.c%2b%2b">Searchable
  220. Archives</a> as well. There are also searchable archives at
  221. <a href=
  222. "http://aspn.activestate.com/ASPN/Mail/Browse/Threaded/cpp-sig">ASPN</a>.
  223. <h3><a name="langbinding" id="langbinding">Language Binding</a></h3>The
  224. <a href=
  225. "http://lists.sourceforge.net/lists/listinfo/boost-langbinding">Language
  226. Binding</a> list is for discussion of a generalized framework for
  227. binding C++ to other languages and systems based on the technology of
  228. <a href="../libs/python">Boost.Python</a> and <a href=
  229. "http://luabind.sourceforge.net/">Luabind</a>. The plan is to provide a
  230. single front-end for describing bindings with runtime-pluggable back
  231. ends for binding to specific languages. It is <b>highly recommended</b>
  232. that new subscribers read through the <a href=
  233. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.langbinding">
  234. message history</a> <b>from the beginning</b> before posting; it will
  235. save time as much design progress has already been made. GMane provides
  236. <a href="news://news.gmane.org/gmane.comp.lib.boost.langbinding">NNTP
  237. access</a> and <a href=
  238. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.langbinding">
  239. Searchable Archives</a> as well.
  240. <h3><a name="spirit" id="spirit">Boost.Spirit</a> lists</h3>Spirit has
  241. two additional mailing lists. <a href=
  242. "https://lists.sourceforge.net/lists/listinfo/spirit-general">Spirit-general</a>
  243. for Spirit users and <a href=
  244. "https://lists.sourceforge.net/lists/listinfo/spirit-devel">Spirit-devel</a>
  245. for Spirit developers (open to anyone who wishes to hang out with
  246. Spirit coders). Both have <a href="http://www.gmane.org">GMane</a> NNTP
  247. access (<a href=
  248. "news://news.gmane.org/gmane.comp.parsers.spirit.general">Spirit-general</a>
  249. and <a href=
  250. "news://news.gmane.org/gmane.comp.parsers.spirit.devel">Spirit-devel</a>)
  251. with searchable archives ( <a href=
  252. "http://news.gmane.org/thread.php?group=gmane.comp.parsers.spirit.general">
  253. Spirit-general</a> and <a href=
  254. "http://news.gmane.org/thread.php?group=gmane.comp.parsers.spirit.devel">
  255. Spirit-devel</a>).
  256. <h3><a name="boostdocs" id="boostdocs">Boost.Documentation</a>
  257. list</h3>The SourceForge mailing list for the <a href=
  258. "../doc/html/boostbook.html">Boost Documentation System</a> is located <a href=
  259. "https://lists.sourceforge.net/lists/listinfo/boost-docs">here</a>.
  260. GMane provides <a href=
  261. "news://news.gmane.org/gmane.comp.lib.boost.documentation">NNTP
  262. access</a> and <a href=
  263. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.documentation">
  264. Searchable Archives</a> as well.
  265. <h3><a name="ublas" id="ublas">uBLAS development</a> (ublas-dev)
  266. list</h3>A seperate user and developer mailing list for <a href=
  267. "../libs/numeric/ublas/doc/index.htm">Boost uBLAS</a> specific topics is
  268. located <a href="http://lists.boost.org/">here</a>.
  269. <h3><a name="thread" id="thread">Thread development</a> (threads-devel)
  270. list</h3>A seperate developer mailing list for <a href=
  271. "../libs/thread/doc/index.html">Boost Thread</a> specific topics is
  272. located
  273. <a href="http://lists.boost.org/mailman/listinfo.cgi/threads-devel">here</a>.
  274. <p><strong>Important: </strong>This mailing list is for the discussion of
  275. the specification and implementation of Boost.Threads only &mdash;
  276. questions regarding usage should be directed to the
  277. <a href="#users">Boost Users</a> list, or the main
  278. <a href="#main">Boost developers</a> list.
  279. <p>GMane provides <a href=
  280. "news://news.gmane.org/gmane.comp.lib.boost.threads-devel">NNTP
  281. access</a> and <a href=
  282. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.threads-devel">
  283. Searchable Archives</a> as well.
  284. <h3><a name="testing" id="testing">Testing</a> list</h3>
  285. <p>The setup, procedures and tools necessary for running Boost
  286. regression tests are discussed on <a href=
  287. "http://lists.boost.org/mailman/listinfo.cgi/boost-testing">this
  288. list</a>. The list main participants are regression runners - people
  289. who run Boost tests on a variety of compilers and platforms, and the
  290. maintainers of tools for collecting and processing test results.</p>
  291. <p><b>Important:</b> questions relevant to a wider audience, including
  292. questions about Boost.Test framework or test results for a particular
  293. library, should be posted to main development list.</p><a href=
  294. "news://news.gmane.org/gmane.comp.lib.boost.documentation">NNTP
  295. access</a> and <a href=
  296. "http://news.gmane.org/gmane.comp.lib.boost.testing">Searchable
  297. Archives</a> are available on <a href="http://www.gmane.org">GMane</a>.
  298. </dd>
  299. </dl>
  300. <h2>Boost <a name="sandbox" id="sandbox">Sandbox</a> CVS</h2>
  301. <p>In addition to the main <a href="getting_started.html#CVS">Boost CVS
  302. repository</a>, a separate Sandbox CVS is available for Boost developers
  303. wishing to collaborate on projects prior to formal acceptance of a new
  304. library.&nbsp; Read-only access is available <a href=
  305. "http://boost.cvs.sourceforge.net/boost-sandbox/boost-sandbox/">
  306. via the web</a>, or via CVS client at:</p>
  307. <blockquote>
  308. <p>
  309. &nbsp;<code>:pserver:anonymous@boost-sandbox.cvs.sourceforge.net:/cvsroot/boost-sandbox</code></p>
  310. </blockquote>
  311. <p><b>For write access</b> to the sandbox, contact the project admins
  312. listed on its <a href=
  313. "http://sourceforge.net/projects/boost-sandbox/">Sourceforge Project
  314. Page</a>.</p>
  315. <h2>#boost <a name="IRC" id="IRC">IRC</a> channel</h2>
  316. <p>In addition to the mailing lists presented above, a #boost IRC channel on
  317. <a href="http://freenode.net">freenode</a> is frequented by some boost users.
  318. As usual with IRC channels, one should not necessarily expect that his questions
  319. will be answered. The channel is not moderated.</p>
  320. <hr>
  321. <p>Revised
  322. <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y"
  323. startspan -->11 December, 2006<!--webbot bot="Timestamp" endspan
  324. i-checksum="39365" --></p>
  325. <p>Copyright Beman Dawes and David Abrahams 2001-2005</p>
  326. <p>Distributed under the Boost Software License, Version 1.0. (See
  327. accompanying file <a href="../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy
  328. at <a href="http://www.boost.org/LICENSE_1_0.txt">http://www.boost.org/LICENSE_1_0.txt</a>)</p>
  329. </body>
  330. </html>
粤ICP备19079148号