I don't know if this is what you're suggesting, but I can't overemphasize how odious I find the idea of capitalizing on Boost's ready-made community, knowledge, and mailing lists, only to take the successful project away later and run it under "a separate umbrella."
This directly concerns me because I have a lot at stake with the upcoming Boost Interfaces Library. When it is proposed to Boost and goes through the inevitable evolution, if it doesn't meet my rather stringent guidelines I will be forced to create my own version of the library. Would doing so be odious? It seems to me that if a new project is spawned, then it becomes healthy competition for Boost and promotes technological progress. Christopher Diggins http://www.cdiggins.com http://www.heron-language.com