Improve consistency between several pages

[SVN r13833]
This commit is contained in:
Beman Dawes 2002-05-13 14:43:56 +00:00
parent 4fa9188210
commit 323fb8836b
3 changed files with 34 additions and 32 deletions

View File

@ -46,8 +46,12 @@ will let you know.</p>
<li>Requests for help interpreting the C++ standard. Try the comp.std.c++
newsgroup instead.</li>
<li>Job offers.</li>
<li>Requests for solutions to homework assignments
</ul>
<li>Requests for solutions to homework assignments.</ul>
<h2>Message size</h2>
<p>The mailing list software automatically limits message and attachment size to
a reasonable amount, typically 75K, which is adjusted from time-to-time by the
moderators.. This limit is a courtesy to those who rely on dial-up Internet
access.</p>
<h2>Prohibited behavior</h2>
<p>Prohibited behavior will not be tolerated. The moderators will ban
postings by abusers.</p>
@ -114,9 +118,9 @@ spent discussing where to put the bicycle shed (the parking lot would
be a modern equivalent) because everyone
understood the issues and felt comfortable discussing them.&nbsp;</p>
<hr>
<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->25 January, 2002<!--webbot bot="Timestamp" i-checksum="38448" endspan -->
<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->13 May, 2002<!--webbot bot="Timestamp" i-checksum="13969" endspan -->
</p>
</body>
</html>
</html>

View File

@ -122,6 +122,9 @@ there is consensus to accept the library, and if there are any conditions
<p>In other words, it is the Review Manager's responsibility to make sure the
review process works smoothly.</p>
<h2>Notes for Library <a name="Submitters">Submitters</a></h2>
<p>See <a href="submission_process.htm">Submission Process</a> for a description
of the steps a library developer goes through to get a library accepted by
Boost.</p>
<p>A proposed library should remain stable during the review period; it will just
confuse and irritate reviewers if there are numerous changes.&nbsp; It
is, however, useful to upload fixes for serious bugs right away, particularly
@ -129,12 +132,8 @@ 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 normally be held until
after the completion of review period.&nbsp; If the suggested
changes might affect reviewer's judgments,&nbsp; post a notice of the pending
changes might affect reviewer's judgments,&nbsp;post a notice of the pending
change on the mailing list.</p>
<p>Once an accepted library is ready for inclusion on the Boost web site, the
submitter is typically given Boost CVS write access, and expected to check-in
and maintain the library in the CVS. Contact the moderators if you need write
access or CVS use isn't possible for you.</p>
<h2>Review <a name="Wizard">Wizard</a></h2>
<p>The Review Wizard coordinates the formal review schedule:</p>
<ul>
@ -161,7 +160,7 @@ access or CVS use isn't possible for you.</p>
</ul>
<hr>
<p>Revised
<!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->08 May, 2002<!--webbot bot="Timestamp" endspan i-checksum="13978" --></p>
<!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->13 May, 2002<!--webbot bot="Timestamp" endspan i-checksum="13969" --></p>
<p>&nbsp;</p>
</body>

View File

@ -2,7 +2,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Boost Library Submission Process</title>
</head>
@ -20,9 +20,8 @@
</tr>
</table>
<h1>Boost Library Submission Process</h1>
<p>This page describes the process of getting a library accepted by Boost.&nbsp;
The process is still evolving, so if you have suggestions for improvement by all
means post them on the mailing list.</p>
<p>This page describes the process a library developer goes through to get a
library accepted by Boost.</p>
<p>See the <a href="lib_guide.htm">Boost Library Requirements and Guidelines</a>
page for issues of content.</p>
<h3><b>Steps for getting a library accepted by Boost:</b></h3>
@ -39,7 +38,7 @@ page for issues of content.</p>
</ul>
<h2><a name="Learn">Learn</a> about Boost</h2>
<p>Subscribe to the <a href="../index.htm#Mailing List">mailing list</a> for a
while, or look through the <a href="http://www.yahoogroups.com/messages/boost">archives</a>.&nbsp;
while, or look through the <a href="mailing_lists.htm#archive">archives</a>.&nbsp;
Click around the <a href="../index.htm">web site</a>.&nbsp; Understand the <a href="lib_guide.htm">Requirements</a>.&nbsp;
Read the rest of this page to learn about the process.&nbsp; Otherwise, you will
just end up wasting everyone's time.</p>
@ -48,7 +47,7 @@ libraries by a process of discussion and refinement.</p>
<p>If what you really want is a site that will just post your library without
even looking at it, you should go elsewhere.</p>
<h2>Determine <a name="interest">interest</a></h2>
<p>Potential library submitters should use the <a href="../index.htm#Mailing List">mailing
<p>Potential library submitters should use the Boost developers <a href="mailing_lists.htm">mailing
list</a> as a forum to gauge interest a possible submission.</p>
<p>A message might be as simple as &quot;Is there any interest in a library
which solves Traveling Salesperson problems in linear time?&quot;</p>
@ -69,8 +68,8 @@ on the mailing list, sometimes a lot of discussion happens in private
emails.&nbsp; For some libraries the process is over quickly, for others it goes
on for months.&nbsp; It's often challenging, and sometimes leads off in
completely unexpected directions.&nbsp;&nbsp;</p>
<p>The <a href="http://www.yahoogroups.com/messages/boost">archive</a> of past
messages is one way to see how this process worked for other boost
<p>The <a href="mailing_lists.htm#archive">archive</a> of past
messages is one way to see how this process worked for other Boost
libraries.</p>
<h2><a name="Submission">Submission</a> for review&nbsp;</h2>
<p>All of the files which make up the library should be combined and compressed
@ -97,16 +96,12 @@ the form &quot;Review Request: library&quot; where <i>library</i> is replaced by
the library name.</p>
<p>See <a href="formal_review_process.htm">Formal Review Process</a> for
details.</p>
<p>Formal Review schedules are posted on the boost mailing list..&nbsp;</p>
<h2>Boost <a name="site posting">site posting</a> after acceptance</h2>
<p>There are two ways that files are posted on the boost web site:</p>
<ul>
<li>Direct update of the boost CVS repository.&nbsp; This requires write
access, and is primarily used for larger libraries, or for libraries
maintained by very active boost developers.</li>
<li>Packaging all files into a submission file (same content as for submission
for review), and emailing it to the Boost webmaster <a href="mailto:bdawes@acm.org">bdawes@acm.org</a>.</li>
</ul>
<p>Formal Review schedules are posted on the <a href="mailing_lists.htm">mailing lists</a>.&nbsp;</p>
<h2>Boost web <a name="site posting">site posting</a></h2>
<p>Once an accepted library is ready for inclusion on the Boost web site, the
submitter is typically given Boost CVS write access, and expected to check-in
and maintain the library in the CVS. Contact the moderators if you need write
access or CVS use isn't possible for you.</p>
<h2><a name="People">People</a> page</h2>
<p>If the boost.org web site doesn't already have your capsule biography
and&nbsp; picture (optional, with not-too-serious pictures preferred), please
@ -117,11 +112,15 @@ common formats are acceptable.&nbsp; The preferred image size is 500x375 but the
webmaster has photo editing software and can do the image preparation if
necessary.</p>
<h2><a name="Lifecycle">Lifecycle</a></h2>
<p>Libraries are software; they lose their value over time if not
maintained.&nbsp; Details still hazy.</p>
<p>Libraries are software; they lose their value over time if not maintained.
Postings on the Boost developers or users mailing lists can alert you to
potential maintenance needs; please plan to maintain your library over time. If
you no longer can or wish to maintain your library, please post a message on the
Boost developers mailing list and help someone else take over as the library
maintainer.</p>
<hr>
<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>
<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->13 May, 2002<!--webbot bot="Timestamp" endspan i-checksum="13969" --></p>
</body>
</html>
</html>