Vicente J. Botet Escriba <vicente.botet <at> wanadoo.fr> writes:
What about forking the Boost.Test library into a new Boost.XTest with the contents of the Boost.Test release and your documentation and taking care of the issues associated to the release branch?
I do not believe this is a good solution. The intersection (name collision) between two libraries is going to be way too big and we'll never know which one code refers to (user complains about). This will lead to no end of confusion. Richard is free to develop a new library from scratch and eliminate all the things he believes are not important (and for that matter add anything he believe is lacking), pass it through the review and maintain it.
What the Boost community thinks about this proposition? Will competition between two libraries be a good thing for Boost?
We had few examples like this, but I do not think this is ideal. At least libraries should present different tradeoffs for users: one big but complete, another one is small, but not as extendible (or something along these lines) Gennadiy