Conversion of the Subversion repository to Git public repositories

As part of the process of moving to modularized Boost, the single Subversion repository at ​https://svn.boost.org/svn will be converted to multiple public Git repositories hosted at ​GitHub:

• The public ​Super-project for modularized Boost repository, that at conversion will have no history. History will begin to accumulate as changes occur.
• A public ​repository for each Boost library, that at conversion will have no history. History will begin to accumulate as changes occur. Each individual Boost library is treated as a separate sub-module by the Boost super-project. The URL for each library's repository is formed by appending the library name to https://github.com/boost-lib/. For example, ​https://github.com/boost-lib/algorithm.
• A public ​Boost history repository, with the full history from the old Subversion repository.

Individual Libraries

The directory structure of each individual Boost library will be the same as the library's current directory structure under boost-root/libs, except that it will also include a new sub-directory tree include/boost/ containing the library's header files. For details, see Getting Started with Modular Boost Library Development using Git.

At conversion, each individual Boost library's public repository will contain two branches, master, converted from Subversion branches/release, and develop, converted from trunk. The library maintainer may want to add other branches, as described in Getting Started with Modular Boost Library Development Workflow.

History

If the Boost Subversion repository was being converted to a single Subversion repository, the history would just be converted along with everything else. But instead, Boost is being modularized into 120 or so separate repositories. If all history were just blindly included for each library, 233 megs of history would be multiplied by 120 libraries, resulting in a file size of 28 gigs. If you are doing release management or testing, that isn't really acceptable.

Discussion is underway of providing a script to graft on individual library history from the overall history.

Administrative Privileges

Each library's public repository will have its own set of maintainers with write privileges. See Library Administrative Privileges.