submission_process.htm 7.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127
  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="#Submission">Submission for review</a>.</li>
  32. <li><a href="#Review">Formal Review</a>.</li>
  33. <li><a href="#site posting">Web site posting</a>.</li>
  34. <li><a href="#People">People page.</a></li>
  35. <li><a href="#Lifecycle">Lifecycle</a>.</li>
  36. </ul>
  37. <h2><a name="Learn">Learn</a> about Boost</h2>
  38. <p>Subscribe to the <a href="../index.htm#Mailing List">mailing list</a> for a
  39. while, or look through the <a href="http://www.yahoogroups.com/messages/boost">archives</a>.&nbsp;
  40. Click around the <a href="../index.htm">web site</a>.&nbsp; Understand the <a href="lib_guide.htm">Requirements</a>.&nbsp;
  41. Read the rest of this page to learn about the process.&nbsp; Otherwise, you will
  42. just end up wasting everyone's time.</p>
  43. <p>There is a culture associated with Boost, aimed at encouraging high quality
  44. libraries by a process of discussion and refinement.</p>
  45. <p>If what you really want is a site that will just post your library without
  46. even looking at it, you should go elsewhere.</p>
  47. <h2>Determine <a name="interest">interest</a></h2>
  48. <p>Potential library submitters should use the <a href="../index.htm#Mailing List">mailing
  49. list</a> as a forum to gauge interest a possible submission.</p>
  50. <p>A message might be as simple as &quot;Is there any interest in a library
  51. which solves Traveling Salesperson problems in linear time?&quot;</p>
  52. <p>A bit of further description or snippet of code may be helpful. Messages
  53. should be plain text; not rich text, HTML, etc.</p>
  54. <p>Please don't post lengthy descriptions, documentation, or code to the mailing
  55. list, and no attachments, even small ones.&nbsp; Please post lengthy material in
  56. the YahooGroups boost <a href="http://www.yahoogroups.com/files/boost/">Files section</a>
  57. (formerly called the &quot; vault&quot;).&nbsp;</p>
  58. <h2><a name="Preliminary">Preliminary</a> submission</h2>
  59. <p>If response to an initial query indicates interest, then post the preliminary
  60. submission files in the <a href="http://www.yahoogroups.com/files/boost/">files section</a> of
  61. the Boost YahooGroups web site if you haven't already done so.</p>
  62. <h2><a name="Refinement">Refinement</a></h2>
  63. <p>Discuss, refine, resubmit.&nbsp; Repeat until satisfied.</p>
  64. <p>The exact details of this process varies a lot.&nbsp; Sometimes it is public,
  65. on the mailing list, sometimes a lot of discussion happens in private
  66. emails.&nbsp; For some libraries the process is over quickly, for others it goes
  67. on for months.&nbsp; It's often challenging, and sometimes leads off in
  68. completely unexpected directions.&nbsp;&nbsp;</p>
  69. <p>The <a href="http://www.yahoogroups.com/messages/boost">archive</a> of past
  70. messages is one way to see how this process worked for other boost
  71. libraries.</p>
  72. <h2><a name="Submission">Submission</a> for review&nbsp;</h2>
  73. <p>All of the files which make up the library should be combined and compressed
  74. into a single submission file using the .zip format.&nbsp; Free encoders
  75. and decoders for this format running on many different platforms are available
  76. at the <a href="http://www.info-zip.org/pub/infozip/">Info-ZIP</a> web site, which
  77. includes a FAQ and much other useful information about the .zip format. Many
  78. commercial compressor-archiver utilities also support this format.</p>
  79. <p>The submission file should contain material as if on the
  80. boost.org web site.&nbsp; The closer the submission file mirrors the final <a href="lib_guide.htm#Directory structure">directory
  81. structure</a> and format of the web site, the better.
  82. <p>Like a preliminary submission, post the final submission .zip file in the <a href="http://www.yahoogroups.com/files/boost/">files section</a> of
  83. the Boost YahooGroups web site
  84. <h2>Formal <a name="Review">Review</a></h2>
  85. <p>Before asking for formal review, your submission should be posted in the
  86. Boost files/vault. Please verify that your submission compiles
  87. and runs under at least two compilers.&nbsp; This flushes out obvious
  88. portability problems.&nbsp; If you don't have access to a second compiler, ask
  89. for help on the Boost mailing list.</p>
  90. <p>Once a library author feels a submission (which presumably is now in the
  91. files/vault) has matured enough for formal review, the author sends a message
  92. requesting a formal review to the mailing list.&nbsp; Please use a subject in
  93. the form &quot;Review Request: library&quot; where <i>library</i> is replaced by
  94. the library name.</p>
  95. <p>See <a href="formal_review_process.htm">Formal Review Process</a> for
  96. details.</p>
  97. <p>Formal Review schedules are posted on the boost mailing list..&nbsp;</p>
  98. <h2>Boost <a name="site posting">site posting</a> after acceptance</h2>
  99. <p>There are two ways that files are posted on the boost web site:</p>
  100. <ul>
  101. <li>Direct update of the boost CVS repository.&nbsp; This requires write
  102. access, and is primarily used for larger libraries, or for libraries
  103. maintained by very active boost developers.</li>
  104. <li>Packaging all files into a submission file (same content as for submission
  105. for review), and emailing it to the Boost webmaster <a href="mailto:bdawes@acm.org">bdawes@acm.org</a>.</li>
  106. </ul>
  107. <h2><a name="People">People</a> page</h2>
  108. <p>If the boost.org web site doesn't already have your capsule biography
  109. and&nbsp; picture (optional, with not-too-serious pictures preferred), please
  110. send them to the Boost webmaster.. It is
  111. up to you as to whether or not the biography includes your email address or
  112. other contact information.&nbsp; The preferred picture format is .jpg, but other
  113. common formats are acceptable.&nbsp; The preferred image size is 500x375 but the
  114. webmaster has photo editing software and can do the image preparation if
  115. necessary.</p>
  116. <h2><a name="Lifecycle">Lifecycle</a></h2>
  117. <p>Libraries are software; they lose their value over time if not
  118. maintained.&nbsp; Details still hazy.</p>
  119. <hr>
  120. <p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->19 August, 2001<!--webbot bot="Timestamp" endspan i-checksum="34359" --></p>
  121. </body>
  122. </html>
粤ICP备19079148号