submission_process.htm 8.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160
  1. <html>
  2. <head>
  3. <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
  4. <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
  5. <meta name="ProgId" content="FrontPage.Editor.Document">
  6. <title>Boost Library Submission Process</title>
  7. </head>
  8. <body bgcolor="#FFFFFF" text="#000000">
  9. <table border="1" bgcolor="#007F7F" cellpadding="2">
  10. <tr>
  11. <td bgcolor="#FFFFFF"><img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" width="277" height="86"></td>
  12. <td><a href="../index.htm"><font face="Arial" color="#FFFFFF"><big>Home</big></font></a></td>
  13. <td><a href="../libs/libraries.htm"><font face="Arial" color="#FFFFFF"><big>Libraries</big></font></a></td>
  14. <td><a href="../people/people.htm"><font face="Arial" color="#FFFFFF"><big>People</big></font></a></td>
  15. <td><a href="faq.htm"><font face="Arial" color="#FFFFFF"><big>FAQ</big></font></a></td>
  16. <td><a href="index.htm"><font face="Arial" color="#FFFFFF"><big>More</big></font></a></td>
  17. </tr>
  18. </table>
  19. <h1>Boost Library Submission Process</h1>
  20. <p>This page describes the process of getting a library accepted by Boost.&nbsp;
  21. The process is still evolving, so if you have suggestions for improvement by all
  22. means post them on the mailing list.</p>
  23. <p>See the <a href="lib_guide.htm">Boost Library Requirements and Guidelines</a>
  24. page for issues of content.</p>
  25. <h3><b>Steps for getting a library accepted by Boost:</b></h3>
  26. <ul>
  27. <li><a href="#Learn">Learn about Boost</a>.</li>
  28. <li><a href="#interest">Determine interest</a>.</li>
  29. <li><a href="#Preliminary">Preliminary submission</a>.</li>
  30. <li><a href="#Refinement">Refinement</a>.</li>
  31. <li><a href="#Review">Formal Review</a>.</li>
  32. <li><a href="#site posting">Web site posting</a>.</li>
  33. <li><a href="#Lifecycle">Lifecycle</a>.</li>
  34. </ul>
  35. <h2><a name="Learn">Learn</a> about Boost</h2>
  36. <p>Subscribe to the <a href="../index.htm#Mailing List">mailing list</a> for a
  37. while, or look through the <a href="http://www.egroups.com/messages/boost">archives</a>.&nbsp;
  38. Click around the <a href="../index.htm">web site</a>.&nbsp; Understand the <a href="lib_guide.htm">Requirements</a>.&nbsp;
  39. Read the rest of this page to learn about the process.&nbsp; Otherwise, you will
  40. just end up wasting everyone's time.</p>
  41. <p>There is a culture associated with Boost, aimed at encouraging high quality
  42. libraries by a process of discussion and refinement.</p>
  43. <p>If what you really want is a site that will just post your library without
  44. even looking at it, you should go elsewhere.</p>
  45. <h2>Determine <a name="interest">interest</a></h2>
  46. <p>Potential library submitters should use the <a href="../index.htm#Mailing List">mailing
  47. list</a> as a forum to gauge interest a possible submission.</p>
  48. <p>A message might be as simple as &quot;Is there any interest in a library
  49. which solves Traveling Salesperson problems in linear time?&quot;</p>
  50. <p>A bit of further description or snippet of code may be helpful. Messages
  51. should be plain text; not rich text, HTML, etc.</p>
  52. <p>Please don't post lengthy descriptions, documentation, or code to the mailing
  53. list, and no attachments, even small ones.&nbsp; Please post lengthy material in
  54. the eGroups boost <a href="http://www.egroups.com/files/boost/">Files section</a>
  55. (formerly called the &quot; vault&quot;).&nbsp;</p>
  56. <h2><a name="Preliminary">Preliminary</a> submission</h2>
  57. <p>If response to an initial query indicates interest, then post preliminary
  58. files in the <a href="http://www.egroups.com/files/boost/">Files section</a> of
  59. the boost eGroups web site if you haven't already done so.</p>
  60. <h2><a name="Refinement">Refinement</a></h2>
  61. <p>Discuss, refine, resubmit.&nbsp; Repeat until satisfied.</p>
  62. <p>The exact details of this process varies a lot.&nbsp; Sometimes it is public,
  63. on the mailing list, sometimes a lot of discussion happens in private
  64. emails.&nbsp; For some libraries the process is over quickly, for others it goes
  65. on for months.&nbsp; It's often challenging, and sometimes leads off in
  66. completely unexpected directions.&nbsp;&nbsp;</p>
  67. <p>The <a href="http://www.egroups.com/messages/boost">archive</a> of past
  68. messages is one way to see how this process worked for other boost
  69. libraries.&nbsp;</p>
  70. <h2>Formal <a name="Review">Review</a></h2>
  71. <p>Before asking for formal review, please verify that your submission compiles
  72. and runs under at least two compilers.&nbsp; This flushes out obvious
  73. portability problems.&nbsp; If you don't have access to a second compiler, ask
  74. for help on the Boost mailing list.</p>
  75. <p>Once a library author feels a submission (which presumably is now in the
  76. files/vault) has matured enough for formal review, the author sends a message
  77. requesting a formal review to the mailing list.&nbsp; Please use a subject in
  78. the form &quot;Review Request: library&quot; where <i>library</i> is replaced by
  79. the library name.</p>
  80. <p>See <a href="formal_review_process.htm">Formal Review Process</a> for
  81. details.</p>
  82. <p>Formal Review schedules are posted on the boost mailing list..&nbsp;</p>
  83. <h2>Boost <a name="site posting">site posting</a></h2>
  84. <p>There are two ways that files are posted on the boost web site:</p>
  85. <ul>
  86. <li>Direct update of the boost CVS repository.&nbsp; This requires write
  87. access, and is primarily used for larger libraries, or for libraries
  88. maintained by very active boost developers.</li>
  89. <li>Packaging all files into submission file, and emailing it to the boost
  90. webmaster.</li>
  91. </ul>
  92. <p>The submission file approach is as follows:</p>
  93. <h3>Packaging</h3>
  94. <p>All of the files which make up the library should be combined and compressed
  95. into a single final submission file using the .zip format.&nbsp; Free encoders
  96. and decoders for this format running on many different platforms are available
  97. at the <a href="http://www.info-zip.org/pub/infozip/">Info-ZIP</a> web site, which
  98. includes a FAQ and much other useful information about the .zip format. Many
  99. commercial compressor-archiver utilities also support this format.</p>
  100. <h3><a name="Final">Final</a> Submission file</h3>
  101. <p>The final submission file contains the material that will live on the
  102. boost.org web site.&nbsp; The closer the submission file mirrors the directory
  103. structure and format of the web site, the easier it is for the webmaster to
  104. integrate it into the web site.
  105. <p>The submission file for a library named <b>foo</b> should include these
  106. subdirectories, with the contents indicated:
  107. <blockquote>
  108. <p><b>libs/foo</b>
  109. <ul>
  110. <li>An introductory page named index.html or index.htm which looks like the
  111. initial page of other libraries. <a href="../libs/rational/index.html">Rational</a>&nbsp;
  112. is a model for single part libraries, <a href="../libs/integer/index.htm">Integer</a>
  113. is a model for
  114. multi-part libraries.</li>
  115. <li>The documentation page or pages, also in HTML format.</li>
  116. <li>Source files implementing the library if it isn't entirely header
  117. based.&nbsp; The boost file type convention for source files is <b>.cpp</b>.</li>
  118. <li>Test programs and data files if supplied.</li>
  119. <li>If the library has a large number of subsidiary files which aren't
  120. linked to from the documentation pages, these subsidiary files can be
  121. combined into a single .zip file.</li>
  122. </ul>
  123. <p><b>boost</b></p>
  124. <ul>
  125. <li>Public header files as described in the documentation for the
  126. library.&nbsp; The boost file type convention for header files is <b>.hpp</b>.</li>
  127. </ul>
  128. <p><b>boost/detail</b></p>
  129. <ul>
  130. <li>Implementation header files not normally accessed by library users.</li>
  131. </ul>
  132. </blockquote>
  133. <h3>Transmission</h3>
  134. <p>Submit via email to <a href="mailto:bdawes@acm.org">bdawes@acm.org</a>.&nbsp;&nbsp;
  135. Attach the .zip submission file.&nbsp; In the email message, please include your
  136. email address, postal mail address, and telephone number, if boost.org doesn't
  137. already have them. Your addresses and phone number will not appear on the web
  138. site (unless you include them in your biography).&nbsp; Anonymous postings are
  139. not accepted.</p>
  140. <h3>People pages</h3>
  141. <p>If the boost.org web site doesn't already have your capsule biography
  142. and&nbsp; picture (optional, with not-too-serious pictures preferred), please
  143. send them <a href="mailto:bdawes@acm.org">mailto:bdawes@acm.org</a>. It is
  144. up to you as to whether or not the biography includes your email address or
  145. other contact information.&nbsp; The preferred picture format is .jpg, but other
  146. common formats are acceptable.&nbsp; The preferred image size is 500x375 but the
  147. webmaster has photo editing software and can do the image preparation if
  148. necessary.</p>
  149. <h2><a name="Lifecycle">Lifecycle</a></h2>
  150. <p>Libraries are software; they loose their value over time if not
  151. maintained.&nbsp; Details still hazy.</p>
  152. <hr>
  153. <p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->10 March, 2001<!--webbot bot="Timestamp" endspan i-checksum="28765" --></p>
  154. </body>
  155. </html>
粤ICP备19079148号