Moving Boost to a distributed and modularized structure

This page is about managing the process of moving Boost version control from Subversion to Git, and in doing so move from a centralized structure to a distributed, modular structure.

Master Action Plan

✔	Action	Manager	Due
✔	Preliminary Steering Committee approval	S/C	May, 2012
95%	Subversion to Git repo move scrips ready	Daniel Pfeifer
45%	Documentation Action Plan (see below)	Beman
	Regression test scripts, procedures ready	Test & build teams
	Inspect and Release scripts, procedures ready	Release mgrs
40%	Modularized Boost 'Help Desk'	Beman
	Final Steering Committee approval	S/C	Prep complete
	Make Subversion trunk read-only
	Execute final trunk conversion
	Regression testing, inspect, daily snapshots go live	Release mgrs
	Web site changes go live	Beman
✔	'Help Desk' goes live
	Open GitHub repos for developer use

Each time an action item is checked as completed, a brief progress report message should be posted on the developers and users mailing lists. If the milestone is particularly newsworthy, a notice should also be posted on the announce mailing list.

Documentation Action Plan

✔	Action	Manager	Due
	Web site branch: Instructions, etc, that mention Subversion changed to use Git
	Web site branch: "Getting Started with Boost" updated for Git and Modularization	Dave
	Trac Wiki: Instructions, etc, that mention Subversion changed to use Git
90%	Develop, document, modularization "Getting Started" for developers	Beman
90%	Develop, document, suggested developer workflows based on Gitflow	Beman
80%	Develop, document, how per library GitHub projects will work, including how permissions work	Beman

Any newly developed documentation must be integrated with the current documentation.