| 2 | | The Boost Sandbox (housed in the `sandbox` subdirectory of the Subversion repository) contains unreviewed code that is intended to eventually become a part of the Boost libraries. Because there are typically many projects in the sandbox at any one time (in various stages of development), the sandbox should be organized by project. Each project should have its own subdirectory inside `sandbox`. For example, a new XML library would reside in `sandbox/xml`. Inside that project-specific subdirectory, the project should be organized like any other Boost library, with a `boost` subdirectory (for headers) and `libs` subdirectory (for source code, build files, and documentation). Our hypothetical XML project would likely have the following structure: |
| | 2 | The Boost Sandbox (housed in the `sandbox` subdirectory of the Subversion repository) contains unreviewed code that is intended to eventually become a part of the Boost libraries. |
| | 3 | |
| | 4 | -- Accessing the Boost Sandbox -- |
| | 5 | The Boost Sandbox lives at https://svn.boost.org/svn/boost/sandbox within the Boost Subversion repository. To access the Boost Sandbox, please refer to the BoostSubversion page. Anyone interesting in working on Boost code is welcome to a sandbox developer account; see the instructions on the BoostSubversion page. |
| | 6 | |
| | 7 | -- Organization -- |
| | 8 | Because there are typically many projects in the sandbox at any one time (in various stages of development), the sandbox should be organized by project. Each project should have its own subdirectory inside `sandbox`. For example, a new XML library would reside in `sandbox/xml`. Inside that project-specific subdirectory, the project should be organized like any other Boost library, with a `boost` subdirectory (for headers) and `libs` subdirectory (for source code, build files, and documentation). Our hypothetical XML project would likely have the following structure: |
