samien
/
boost
espejo de https://github.com/boostorg/boost


			
				
					
						
						
							12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394
							<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Formal Review Process</title>
</head>

<body bgcolor="#FFFFFF" text="#000000">

<table border="1" bgcolor="#007F7F" cellpadding="2">
  <tr>
    <td bgcolor="#FFFFFF"><img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" width="277" height="86"></td>
    <td><a href="../index.htm"><font face="Arial" color="#FFFFFF"><big>Home</big></font></a></td>
    <td><a href="../libraries.htm"><font face="Arial" color="#FFFFFF"><big>Libraries</big></font></a></td>
    <td><a href="../people.htm"><font face="Arial" color="#FFFFFF"><big>People</big></font></a></td>
    <td><a href="faq.htm"><font face="Arial" color="#FFFFFF"><big>FAQ</big></font></a></td>
    <td><a href="index.htm"><font face="Arial" color="#FFFFFF"><big>More</big></font></a></td>
  </tr>
</table>
<h1>Formal Review Process</h1>
<p>The Formal Review process determines if a proposed library should be accepted
as a Boost library.</p>
<p>The final &quot;accept&quot; or &quot;reject&quot; decision is made by the
Review Manager, based on review comments received from boost mailing list
members.</p>
<p>Members only can see <a href="http://www.egroups.com/files/boost/Members+Only/formal_review_schedule.htm">Formal
Review Schedule</a> for the current review schedule.&nbsp;</p>
<h2>Comments</h2>
<p>All Boost mailing list members are encouraged to submit Formal Review
comments:</p>
<blockquote>
  <ul>
    <li>Publicly on the mailing list.</li>
    <li>Privately to the Review Manager. (See Formal Review Status page )</li>
    <li>Privately to the library submitter.</li>
  </ul>
</blockquote>
<p>Private comments to a library submitter may be helpful to her or him, but
won't help the Review Manager reach a decision, so the other forms are
preferred.</p>
<h2>Preparing review comments</h2>
<p>Comments may be brief or lengthy, but basically the Review Manager needs your
answers to several questions.&nbsp; If you identify problems along the way,
please note if they are minor, serious, or showstoppers.</p>
<ul>
  <li>What is your evaluation of the design?<br>
  </li>
  <li>What is your evaluation of the implementation?<br>
  </li>
  <li>What is your evaluation of the documentation?<br>
  </li>
  <li>What is your evaluation of the potential usefulness of the library?<br>
  </li>
  <li>Did you try to use the library?&nbsp; With what compiler?&nbsp; Did you
    have any problems?<br>
  </li>
  <li>How much effort did you put into your evaluation? A glance? A quick
    reading? In-depth study?<br>
  </li>
  <li>Are you knowledgeable about the problem domain?<br>
  </li>
  <li>Finally, do you think the library should be accepted as a Boost
    library?&nbsp; Be sure to say this explicitly so that your other comments
    don't obscure your overall opinion.</li>
</ul>
<h2>Results</h2>
<p>At the conclusion of the comment period, the Review Manager will post a
message to the mailing list saying if the library has been accepted or
rejected.&nbsp; A rationale should be provided, but its extent is up to the
Review Manager.</p>
<h2>Notes for Review Managers</h2>
<p>Consider writing a Review page for posting on the web site.</p>
<p>In Review pages or mailing list postings, do quote review comments if you
wish, but don't identify authors of private comments.</p>
<h2>Notes for Library Authors</h2>
<p>A proposed library should remain stable during the review period; it is just
going to confuse and irritate reviewers if there are numerous changes.&nbsp; It
is, however, useful to upload fixes for serious bugs right away, particularly
those which prevent reviewers from fully evaluating the library.&nbsp; Post a
notice of such fixes on the mailing list.</p>
<p>Library improvements suggested by reviewers should be held until after the
completion of review period. Such changes can then be incorporated in the <a href="submission_process.htm#Final">final
submission file</a> sent to the webmaster for posting.&nbsp; If the suggested
changes might affect reviewer's judgments,&nbsp; post a notice of the pending
change on the mailing list.</p>
<hr>
<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->13 June, 2000<!--webbot bot="Timestamp" endspan i-checksum="19835" --></p>
<p>&nbsp;</p>

</body>

</html>