diff --git a/more/discussion_policy.htm b/more/discussion_policy.htm index 432bb40379..f28f1156cc 100644 --- a/more/discussion_policy.htm +++ b/more/discussion_policy.htm @@ -46,8 +46,12 @@ will let you know.

  • Requests for help interpreting the C++ standard. Try the comp.std.c++ newsgroup instead.
  • Job offers.
    • -
  • Requests for solutions to homework assignments - +
  • Requests for solutions to homework assignments. +

    Message size

    +

    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.

    Prohibited behavior

    Prohibited behavior will not be tolerated. The moderators will ban postings by abusers.

    @@ -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. 

    -

    Revised 25 January, 2002 +

    Revised 13 May, 2002

    - + \ No newline at end of file diff --git a/more/formal_review_process.htm b/more/formal_review_process.htm index 705ff90723..45d65fd6c2 100644 --- a/more/formal_review_process.htm +++ b/more/formal_review_process.htm @@ -122,6 +122,9 @@ there is consensus to accept the library, and if there are any conditions

    In other words, it is the Review Manager's responsibility to make sure the review process works smoothly.

    Notes for Library Submitters

    +

    See Submission Process for a description +of the steps a library developer goes through to get a library accepted by +Boost.

    A proposed library should remain stable during the review period; it will just confuse and irritate reviewers if there are numerous changes.  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.  Post a notice of such fixes on the mailing list.

    Library improvements suggested by reviewers should normally be held until after the completion of review period.  If the suggested -changes might affect reviewer's judgments,  post a notice of the pending +changes might affect reviewer's judgments, post a notice of the pending change on the mailing list.

    -

    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.

    Review Wizard

    The Review Wizard coordinates the formal review schedule:

    Revised -08 May, 2002

    +13 May, 2002

     

    diff --git a/more/submission_process.htm b/more/submission_process.htm index 4391646045..19b1f6163d 100644 --- a/more/submission_process.htm +++ b/more/submission_process.htm @@ -2,7 +2,7 @@ - + Boost Library Submission Process @@ -20,9 +20,8 @@

    Boost Library Submission Process

    -

    This page describes the process of getting a library accepted by Boost.  -The process is still evolving, so if you have suggestions for improvement by all -means post them on the mailing list.

    +

    This page describes the process a library developer goes through to get a +library accepted by Boost.

    See the Boost Library Requirements and Guidelines page for issues of content.

    Steps for getting a library accepted by Boost:

    @@ -39,7 +38,7 @@ page for issues of content.

    Learn about Boost

    Subscribe to the mailing list for a -while, or look through the archives.  +while, or look through the archives.  Click around the web site.  Understand the Requirements.  Read the rest of this page to learn about the process.  Otherwise, you will just end up wasting everyone's time.

    @@ -48,7 +47,7 @@ libraries by a process of discussion and refinement.

    If what you really want is a site that will just post your library without even looking at it, you should go elsewhere.

    Determine interest

    -

    Potential library submitters should use the mailing +

    Potential library submitters should use the Boost developers mailing list as a forum to gauge interest a possible submission.

    A message might be as simple as "Is there any interest in a library which solves Traveling Salesperson problems in linear time?"

    @@ -69,8 +68,8 @@ on the mailing list, sometimes a lot of discussion happens in private emails.  For some libraries the process is over quickly, for others it goes on for months.  It's often challenging, and sometimes leads off in completely unexpected directions.  

    -

    The archive of past -messages is one way to see how this process worked for other boost +

    The archive of past +messages is one way to see how this process worked for other Boost libraries.

    Submission for review 

    All of the files which make up the library should be combined and compressed @@ -97,16 +96,12 @@ the form "Review Request: library" where library is replaced by the library name.

    See Formal Review Process for details.

    -

    Formal Review schedules are posted on the boost mailing list.. 

    -

    Boost site posting after acceptance

    -

    There are two ways that files are posted on the boost web site:

    - +

    Formal Review schedules are posted on the mailing lists. 

    +

    Boost web site posting

    +

    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.

    People page

    If the boost.org web site doesn't already have your capsule biography and  picture (optional, with not-too-serious pictures preferred), please @@ -117,11 +112,15 @@ common formats are acceptable.  The preferred image size is 500x375 but the webmaster has photo editing software and can do the image preparation if necessary.

    Lifecycle

    -

    Libraries are software; they lose their value over time if not -maintained.  Details still hazy.

    +

    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.

    -

    Revised 19 August, 2001

    +

    Revised 13 May, 2002

    - + \ No newline at end of file