mailing_lists.htm 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403
  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</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>Archives of Boost messages include the
  166. <a href="http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.devel">Boost
  167. GMane NNTP Archive</a>, <a href=
  168. "http://www.mail-archive.com/boost%40lists.boost.org/">The Mail
  169. Archive</a>, <a
  170. href="http://archives.free.net.ph/list/boost.en.html">The Free
  171. Network Group</a>, and of course there is a Google search link for our <a href=
  172. "http://lists.boost.org/Archives/boost/">MailMan Archive</a> on
  173. <a href="../index.htm">our home page</a>.
  174. <h2>Boost <a name="announce" id="announce">Announce</a> mailing list</h2>
  175. <p>This is an announce-only list for notification of upcoming software
  176. releases and formal reviews of proposed libraries. One to three messages
  177. per month.&nbsp; Subscribe or unsubscribe at the <a href=
  178. "http://lists.boost.org/mailman/listinfo.cgi/boost-announce">Boost Announce
  179. list home page</a>.</p><a name="interest" id="interest"></a>
  180. <h2>Boost Interest Mailing List</h2>
  181. <p>This list is a moderated low-traffic announcement-only list of
  182. interest to the Boost community. On topic messages will include
  183. announcements of books, magazine articles, papers, talks, seminars,
  184. products, tools, events, or conferences on advanced uses of C++,
  185. generic/generative/meta-programming, and, of course, the Boost
  186. libraries. Off topic will be discussion of any kind. Job postings
  187. are accepted at the moderators' discretion. Subscribe or
  188. unsubscribe at the <a href=
  189. "http://lists.boost.org/mailman/listinfo.cgi/boost-interest">Boost-Interest
  190. home page</a>.</p>
  191. <h2><a name="projects" id="projects">Project-Specific lists</a></h2>Several
  192. mailing lists have been established for specific Boost projects:
  193. <dl>
  194. <dd>
  195. <h3><a name="jamboost" id="jamboost">Boost.Build</a>
  196. list</h3>The mailing list for the <a href=
  197. "../tools/build">Boost Build System</a> is located <a href=
  198. "http://lists.boost.org/mailman/listinfo.cgi/boost-build">here</a>. GMane provides
  199. <a href="news://news.gmane.org/gmane.comp.lib.boost.build">NNTP
  200. access</a> and <a href=
  201. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.build">Searchable
  202. Archives</a> as well.
  203. <h3><a name="cplussig" id="cplussig">Python C++-Sig</a> (for
  204. Boost.Python)</h3>The <a href=
  205. "http://www.python.org/community/sigs/current/c++-sig/">Python C++-sig</a> is not
  206. strictly Boost-specific, but nearly all the traffic concerns <a href=
  207. "../libs/python">Boost.Python</a>. See also the <a href=
  208. "#langbinding">Language Binding</a> list below. GMane provides <a href=
  209. "news://news.gmane.org/gmane.comp.python.c%2b%2b">NNTP access</a> and
  210. <a href=
  211. "http://news.gmane.org/thread.php?group=gmane.comp.python.c%2b%2b">Searchable
  212. Archives</a> as well. There are also searchable archives at
  213. <a href=
  214. "http://aspn.activestate.com/ASPN/Mail/Browse/Threaded/cpp-sig">ASPN</a>.
  215. <h3><a name="langbinding" id="langbinding">Language Binding</a></h3>The
  216. <a href=
  217. "http://lists.sourceforge.net/lists/listinfo/boost-langbinding">Language
  218. Binding</a> list is for discussion of a generalized framework for
  219. binding C++ to other languages and systems based on the technology of
  220. <a href="../libs/python">Boost.Python</a> and <a href=
  221. "http://luabind.sourceforge.net/">Luabind</a>. The plan is to provide a
  222. single front-end for describing bindings with runtime-pluggable back
  223. ends for binding to specific languages. It is <b>highly recommended</b>
  224. that new subscribers read through the <a href=
  225. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.langbinding">
  226. message history</a> <b>from the beginning</b> before posting; it will
  227. save time as much design progress has already been made. GMane provides
  228. <a href="news://news.gmane.org/gmane.comp.lib.boost.langbinding">NNTP
  229. access</a> and <a href=
  230. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.langbinding">
  231. Searchable Archives</a> as well.
  232. <h3><a name="spirit" id="spirit">Boost.Spirit</a> lists</h3>Spirit has
  233. two additional mailing lists. <a href=
  234. "https://lists.sourceforge.net/lists/listinfo/spirit-general">Spirit-general</a>
  235. for Spirit users and <a href=
  236. "https://lists.sourceforge.net/lists/listinfo/spirit-devel">Spirit-devel</a>
  237. for Spirit developers (open to anyone who wishes to hang out with
  238. Spirit coders). Both have <a href="http://www.gmane.org">GMane</a> NNTP
  239. access (<a href=
  240. "news://news.gmane.org/gmane.comp.parsers.spirit.general">Spirit-general</a>
  241. and <a href=
  242. "news://news.gmane.org/gmane.comp.parsers.spirit.devel">Spirit-devel</a>)
  243. with searchable archives ( <a href=
  244. "http://news.gmane.org/thread.php?group=gmane.comp.parsers.spirit.general">
  245. Spirit-general</a> and <a href=
  246. "http://news.gmane.org/thread.php?group=gmane.comp.parsers.spirit.devel">
  247. Spirit-devel</a>).
  248. <h3><a name="boostdocs" id="boostdocs">Boost.Documentation</a>
  249. list</h3>The SourceForge mailing list for the <a href=
  250. "../doc/html/boostbook.html">Boost Documentation System</a> is located <a href=
  251. "https://lists.sourceforge.net/lists/listinfo/boost-docs">here</a>.
  252. GMane provides <a href=
  253. "news://news.gmane.org/gmane.comp.lib.boost.documentation">NNTP
  254. access</a> and <a href=
  255. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.documentation">
  256. Searchable Archives</a> as well.
  257. <h3><a name="ublas" id="ublas">uBLAS development</a> (ublas-dev)
  258. list</h3>A seperate user and developer mailing list for <a href=
  259. "../libs/numeric/ublas/doc/index.htm">Boost uBLAS</a> specific topics is
  260. located <a href="http://lists.boost.org/">here</a>.
  261. <h3><a name="thread" id="thread">Thread development</a> (threads-devel)
  262. list</h3>A seperate developer mailing list for <a href=
  263. "../libs/thread/doc/index.html">Boost Thread</a> specific topics is
  264. located
  265. <a href="http://lists.boost.org/mailman/listinfo.cgi/threads-devel">here</a>.
  266. <p><strong>Important: </strong>This mailing list is for the discussion of
  267. the specification and implementation of Boost.Threads only &mdash;
  268. questions regarding usage should be directed to the
  269. <a href="#users">Boost Users</a> list, or the main
  270. <a href="#main">Boost developers</a> list.
  271. <p>GMane provides <a href=
  272. "news://news.gmane.org/gmane.comp.lib.boost.threads-devel">NNTP
  273. access</a> and <a href=
  274. "http://news.gmane.org/thread.php?group=gmane.comp.lib.boost.threads-devel">
  275. Searchable Archives</a> as well.
  276. <h3><a name="testing" id="testing">Testing</a> list</h3>
  277. <p>The setup, procedures and tools necessary for running Boost
  278. regression tests are discussed on <a href=
  279. "http://lists.boost.org/mailman/listinfo.cgi/boost-testing">this
  280. list</a>. The list main participants are regression runners - people
  281. who run Boost tests on a variety of compilers and platforms, and the
  282. maintainers of tools for collecting and processing test results.</p>
  283. <p><b>Important:</b> questions relevant to a wider audience, including
  284. questions about Boost.Test framework or test results for a particular
  285. library, should be posted to main development list.</p><a href=
  286. "news://news.gmane.org/gmane.comp.lib.boost.documentation">NNTP
  287. access</a> and <a href=
  288. "http://news.gmane.org/gmane.comp.lib.boost.testing">Searchable
  289. Archives</a> are available on <a href="http://www.gmane.org">GMane</a>.
  290. <h3>Boost Subversion Commit Messages</h3>
  291. <p>The <a
  292. href="http://lists.boost.org/mailman/listinfo.cgi/boost-commit">boost-commit</a>
  293. mailing list receives messages whenever a change is committed to
  294. the Boost Subversion repository.</p>
  295. </dd>
  296. </dl>
  297. <h2>Boost <a name="sandbox" id="sandbox">Sandbox</a></h2>
  298. <p>In addition to the main <a href="getting_started.html#CVS">Boost CVS
  299. repository</a>, a separate Sandbox is available for Boost developers
  300. wishing to collaborate on projects prior to formal acceptance of a new
  301. library.&nbsp; Read-only access is available via Subversion and web browser at
  302. <a href=
  303. "http://svn.boost.org/svn/boost/sandbox">http://svn.boost.org/svn/boost/sandbox</a>.
  304. <p>Developer access to the sandbox uses the Subversion repository
  305. at <a href=
  306. "https://svn.boost.org/svn/boost/sandbox">https://svn.boost.org/svn/boost/sandbox</a>. For more information about the Boost Subversion repository,
  307. please
  308. see <a href="http://svn.boost.org">http://svn.boost.org</a>.</p>
  309. <h2>#boost <a name="IRC" id="IRC">IRC</a> channel</h2>
  310. <p>In addition to the mailing lists presented above, a #boost IRC channel on
  311. <a href="http://freenode.net">freenode</a> is frequented by some boost users.
  312. As usual with IRC channels, one should not necessarily expect that his questions
  313. will be answered. The channel is not moderated.</p>
  314. <hr>
  315. <p>Revised
  316. <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y"
  317. startspan -->04 December, 2005<!--webbot bot="Timestamp" endspan
  318. i-checksum="39365" --></p>
  319. <p>Copyright Beman Dawes and David Abrahams 2001-2005</p>
  320. <p>Distributed under the Boost Software License, Version 1.0. (See
  321. accompanying file <a href="../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy
  322. at <a href="http://www.boost.org/LICENSE_1_0.txt">http://www.boost.org/LICENSE_1_0.txt</a>)</p>
  323. </body>
  324. </html>
粤ICP备19079148号