| | 1 | In January 2013, the Boost Community Maintenance team (CMT) was created in January 2013 to provide maintenance for libraries where the author is unable to provide it. |
| | 2 | |
| | 3 | The mailing list [boost-maint http://lists.boost.org/mailman/listinfo.cgi/boost-maint] is for discussions of the team. |
| | 4 | |
| | 5 | This is a public group; all people who wish to contribute are welcome to join the mailing lists and to help out. |
| | 6 | |
| | 7 | == Goals of the CMT == |
| | 8 | 1. Keep things building on all the supported compilers (and as many others as possible) |
| | 9 | 2. Get the test matrix “all green” and keep it that way. |
| | 10 | 3. Fix the accumulated bugs; drive the bug count to zero, and keep it there. |
| | 11 | 4. Improve the documentation for the libraries maintained by the CMT. |
| | 12 | 5. Add new features. |
| | 13 | |
| | 14 | Also, a long term goal of the CMT is to find maintainers for these libraries. |
| | 15 | |
| | 16 | == Libraries maintained by the CMT == |
| | 17 | * Boost.ConceptCheck |
| | 18 | * Boost.DisjointSet |
| | 19 | * Boost.DynamicBitset |
| | 20 | * Boost.Format |
| | 21 | * Boost.Function |
| | 22 | * Boost.Logic |
| | 23 | * Boost.PropertyMap |
| | 24 | * Boost.Signals (which is deprecated) |
| | 25 | |
| | 26 | == Procedures for the CMT == |
| | 27 | |
| | 28 | The CMT will operate on a "propose and review" process, where a change goes through the following phases. |
| | 29 | |
| | 30 | 1. Someone decides to work on a bug/test failure/etc and announces this on the mailing list. |
| | 31 | 2. Discussion may ensue on the ML about the best way to proceed. |
| | 32 | 3. The code is developed and a pull request is made (on the list). |
| | 33 | 4. The request is reviewed by other members of the list. (repeat steps 3 and 4 as necessary) |
| | 34 | 5. The request is committed to the "develop" branch by a CMT manager. |
| | 35 | 6. The person who made the pull request is responsible to watching the test results, and notifying the CMT manager when it is ready to be merged to "master" |
| | 36 | |
| | 37 | For this to work, we need several people who are willing to review other people's pull requests (as well as developing their own patches). |
