On 1:59 PM, John Maddock wrote:
Interesting. So if I wanted to get SVN access and start working on things in a private branch [...]
It depends - if the library has an active maintainer, then yes, you just ask the maintainer or file a ticket [...]
I accept that there may be an issue with there not being enough folks for the above to work all that well though. The basic problem is that to maintain quality we've generally required all library maintainers to already have one accepted Boost library, so I guess the question we're struggling with is how to broaden the field without risking screwing things up too badly :-0
The crux of Boost.Guild's debate. And so many topics touch on this. So how would you measure, or design a test, to determine how badly things would get screwed up under various scenarios?
Thinking out loud here... one option might be for someone to say "I'm going to try and give library X a decent update" and solicit the mailing list for bug/feature requests, then carry out the work in the sandbox and ask for a mini-review - at which point you're sort of lumbered with being the new maintainer ;-)
If someone is that motivated. But could something useful happen if ten people, each 1/10th as motivated, were to apply themselves?