| 35 | | To gain developer access to the Boost Subversion repository, please send a email to the [http://www.boost.org/more/moderators.html Boost Moderators] at `boost-owner -at- lists.boost.org` stating why you need write access to the Boost Subversion repository, and which parts of the repository--boost itself, the sandbox, or the web site--you need access to. Once a moderator has approved you for access to the Subversion repository, you will receive an invitation via e-mail that asks you to provide a user name and a password, which will be used to access both the Boost Subversion repository and the Boost Trac. You will also be asked to grant permission for your past and future Boost contributions to be licensed under the [http://www.boost.org/more/license_info.html Boost Software License] version 1.0 and future versions: your permission is required to work with the Boost Subversion repository, so that we can ensure that Boost code is licensed under the Boost Software License. |
| | 35 | To gain developer access to the Boost Subversion repository, please send a email to the [http://www.boost.org/more/moderators.html Boost Moderators] at `boost-owner -at- lists.boost.org` stating why you need write access to the Boost Subversion repository, and which parts of the repository--boost itself, the sandbox, or the web site--you need access to. Once a moderator has approved you for access to the Subversion repository, you will receive an invitation via e-mail that asks you to provide a user name and a password, which will be used to access both the Boost Subversion repository and the Boost Trac. You will also be asked to grant permission for your past and future Boost contributions to be licensed under the [http://www.boost.org/more/license_info.html Boost Software License] version 1.0 and future versions: your permission is required to work with the Boost Subversion repository, so that we can ensure that Boost code is licensed under the Boost Software License. Once you have signed in, you should notify the moderator of your username, and he will complete the process. |
| | 37 | Once you have write access to Subversion, you may want to "upgrade" your anonymous checkouts to developer checkouts. You can do so with the [http://svnbook.red-bean.com/en/1.0/re27.html svn switch] command. For example, if `boost-devel` is a checkout of Boost's development branch, change into that directory and execute: |
| | 38 | |
| | 39 | svn switch https://svn.boost.org/svn/boost/devel |
| | 40 | |
| | 41 | == Sandbox Organization == |
| | 42 | 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: |
| | 43 | |
| | 44 | sandbox/xml/ |
| | 45 | boost/ - Contains xml.hpp, which includes all of the headers from xml/ |
| | 46 | xml/ - Contains Boost.XML headers |
| | 47 | libs/ |
| | 48 | xml/ |
| | 49 | build/ - Contains Jamfiles to build Boost.XML |
| | 50 | |
| | 51 | doc/ - Contains documentation for Boost.XML |
| | 52 | |
| | 53 | src/ - Contains Boost.XML compiled source files |
| | 54 | |
| | 55 | Many existing projects in the sandbox do not follow this structure, opting to place headers in `sandbox/boost` and supporting files in `sandbox/libs`. We encourage developers to migrate these projects to the project-centric organizational structure. |
| | 56 | |
| | 57 | |
