[29] | 1 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
---|
| 2 | <html> |
---|
| 3 | |
---|
| 4 | <head> |
---|
| 5 | <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> |
---|
| 6 | <meta name="GENERATOR" content="Microsoft FrontPage 5.0"> |
---|
| 7 | <meta name="ProgId" content="FrontPage.Editor.Document"> |
---|
| 8 | <title>Boost Library Submission Process</title> |
---|
| 9 | </head> |
---|
| 10 | |
---|
| 11 | <body bgcolor="#FFFFFF" text="#000000"> |
---|
| 12 | |
---|
| 13 | <table border="1" bgcolor="#007F7F" cellpadding="2"> |
---|
| 14 | <tr> |
---|
| 15 | <td bgcolor="#FFFFFF"><img src="../boost.png" alt="boost.png (6897 bytes)" width="277" height="86"></td> |
---|
| 16 | <td><a href="../index.htm"><font face="Arial" color="#FFFFFF"><big>Home</big></font></a></td> |
---|
| 17 | <td><a href="../libs/libraries.htm"><font face="Arial" color="#FFFFFF"><big>Libraries</big></font></a></td> |
---|
| 18 | <td><a href="../people/people.htm"><font face="Arial" color="#FFFFFF"><big>People</big></font></a></td> |
---|
| 19 | <td><a href="faq.htm"><font face="Arial" color="#FFFFFF"><big>FAQ</big></font></a></td> |
---|
| 20 | <td><a href="index.htm"><font face="Arial" color="#FFFFFF"><big>More</big></font></a></td> |
---|
| 21 | </tr> |
---|
| 22 | </table> |
---|
| 23 | <h1>Boost Library Submission Process</h1> |
---|
| 24 | <p>This page describes the process a library developer goes through to get a |
---|
| 25 | library accepted by Boost.</p> |
---|
| 26 | <p>See the <a href="lib_guide.htm">Boost Library Requirements and Guidelines</a> |
---|
| 27 | page for issues of content.</p> |
---|
| 28 | <h3><b>Steps for getting a library accepted by Boost:</b></h3> |
---|
| 29 | <ul> |
---|
| 30 | <li><a href="#Learn">Learn about Boost</a>.</li> |
---|
| 31 | <li><a href="#interest">Determine interest</a>.</li> |
---|
| 32 | <li><a href="#Preliminary">Preliminary submission</a>.</li> |
---|
| 33 | <li><a href="#Refinement">Refinement</a>.</li> |
---|
| 34 | <li><a href="#Submission">Submission for review</a>.</li> |
---|
| 35 | <li><a href="#Review">Formal Review</a>.</li> |
---|
| 36 | <li><a href="#SitePosting">Web site posting</a>.</li> |
---|
| 37 | <li><a href="#People">People page.</a></li> |
---|
| 38 | <li><a href="#Lifecycle">Lifecycle</a>.</li> |
---|
| 39 | </ul> |
---|
| 40 | <h2><a name="Learn">Learn</a> about Boost</h2> |
---|
| 41 | <p>Subscribe to the <a href="mailing_lists.htm#main">main developers mailing list</a> for a |
---|
| 42 | while, or look through the <a href="mailing_lists.htm#archive">archives</a>. |
---|
| 43 | Click around the <a href="../index.htm">web site</a>. Understand the <a href="lib_guide.htm">Requirements</a>. |
---|
| 44 | Read the rest of this page to learn about the process. Otherwise, you will |
---|
| 45 | just end up wasting everyone's time.</p> |
---|
| 46 | <p>There is a culture associated with Boost, aimed at encouraging high quality |
---|
| 47 | libraries by a process of discussion and refinement.</p> |
---|
| 48 | <p>If what you really want is a site that will just post your library without |
---|
| 49 | even looking at it, you should go elsewhere.</p> |
---|
| 50 | <h2>Determine <a name="interest">interest</a></h2> |
---|
| 51 | <p>Potential library submitters should use the Boost developers <a href="mailing_lists.htm">mailing |
---|
| 52 | list</a> as a forum to gauge interest a possible submission.</p> |
---|
| 53 | <p>A message might be as simple as "Is there any interest in a library |
---|
| 54 | which solves Traveling Salesperson problems in linear time?"</p> |
---|
| 55 | <p>A bit of further description or snippet of code may be helpful. Messages |
---|
| 56 | should be plain text; not rich text, HTML, etc.</p> |
---|
| 57 | <p>Please don't post lengthy descriptions, documentation, or code to the mailing |
---|
| 58 | list, and no attachments, even small ones. Please post lengthy material in |
---|
| 59 | the <a href="http://boost-consulting.com/vault/">Boost Vault</a>. </p> |
---|
| 60 | <h2><a name="Preliminary">Preliminary</a> submission</h2> |
---|
| 61 | <p>If response to an initial query indicates interest, then post the preliminary |
---|
| 62 | submission files in the <a href="http://boost-consulting.com/vault/">Boost Vault</a> on |
---|
| 63 | the sourceforge web site if you haven't already done so.</p> |
---|
| 64 | <h2><a name="Refinement">Refinement</a></h2> |
---|
| 65 | <p>Discuss, refine, resubmit. Repeat until satisfied.</p> |
---|
| 66 | <p>The exact details of this process varies a lot. Sometimes it is public, |
---|
| 67 | on the mailing list, sometimes a lot of discussion happens in private |
---|
| 68 | emails. For some libraries the process is over quickly, for others it goes |
---|
| 69 | on for months. It's often challenging, and sometimes leads off in |
---|
| 70 | completely unexpected directions. </p> |
---|
| 71 | <p>The <a href="mailing_lists.htm#archive">archive</a> of past |
---|
| 72 | messages is one way to see how this process worked for other Boost |
---|
| 73 | libraries.</p> |
---|
| 74 | <h2><a name="Submission">Submission</a> for review </h2> |
---|
| 75 | <p>All of the files which make up the library should be combined and compressed |
---|
| 76 | into a single submission file using the .zip format. Free encoders |
---|
| 77 | and decoders for this format running on many different platforms are available |
---|
| 78 | at the <a href="http://www.info-zip.org/pub/infozip/">Info-ZIP</a> web site, which |
---|
| 79 | includes a FAQ and much other useful information about the .zip format. Many |
---|
| 80 | commercial compressor-archiver utilities also support this format.</p> |
---|
| 81 | <p>The submission file should contain material as if on the |
---|
| 82 | boost.org web site. The closer the submission file mirrors the final |
---|
| 83 | <a href="lib_guide.htm#Directory_structure">directory |
---|
| 84 | structure</a> and format of the web site, the better. |
---|
| 85 | <p>Like a preliminary submission, post the final submission .zip file in the <a href="http://boost-consulting.com/vault/">Boost Vault</a>. |
---|
| 86 | <h2>Formal <a name="Review">Review</a></h2> |
---|
| 87 | <p>Before asking for formal review, your submission should be posted in the |
---|
| 88 | Boost files/vault. Please verify that your submission compiles |
---|
| 89 | and runs under at least two compilers. This flushes out obvious |
---|
| 90 | portability problems. If you don't have access to a second compiler, ask |
---|
| 91 | for help on the Boost mailing list.</p> |
---|
| 92 | <p>Once a library author feels a submission (which presumably is now in the |
---|
| 93 | files/vault) has matured enough for formal review, the author sends a message |
---|
| 94 | requesting a formal review to the mailing list. Please use a subject in |
---|
| 95 | the form "Review Request: library" where <i>library</i> is replaced by |
---|
| 96 | the library name.</p> |
---|
| 97 | <p>See <a href="formal_review_process.htm">Formal Review Process</a> for |
---|
| 98 | details.</p> |
---|
| 99 | <p>Formal Review schedules are posted on |
---|
| 100 | the <a href="formal_review_schedule.html">web site</a>. </p> |
---|
| 101 | |
---|
| 102 | <h2>Boost web <a name="SitePosting">site posting</a></h2> |
---|
| 103 | <p>Once an accepted library is ready for inclusion on the Boost web site, the |
---|
| 104 | submitter is typically given Boost CVS write access, and expected to check-in |
---|
| 105 | and maintain the library in the CVS. Contact the moderators if you need write |
---|
| 106 | access or CVS use isn't possible for you.</p> |
---|
| 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 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. The preferred picture format is .jpg, but other |
---|
| 113 | common formats are acceptable. 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 maintained. |
---|
| 118 | Postings on the Boost developers or users mailing lists can alert you to |
---|
| 119 | potential maintenance needs; please plan to maintain your library over time. If |
---|
| 120 | you no longer can or wish to maintain your library, please post a message on the |
---|
| 121 | Boost developers mailing list and help someone else take over as the library |
---|
| 122 | maintainer.</p> |
---|
| 123 | <hr> |
---|
| 124 | <p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->26 November, 2003<!--webbot bot="Timestamp" endspan i-checksum="39365" --></p> |
---|
| 125 | |
---|
| 126 | <p>© Copyright Beman Dawes 2000</p> |
---|
| 127 | <p>Distributed under the Boost Software License, Version 1.0. (See |
---|
| 128 | accompanying file <a href="../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy |
---|
| 129 | at <a href="http://www.boost.org/LICENSE_1_0.txt">http://www.boost.org/LICENSE_1_0.txt</a>)</p> |
---|
| 130 | |
---|
| 131 | </body> |
---|
| 132 | |
---|
| 133 | </html> |
---|