Subject: Re: [boost] Boost.Array Maintainer
From: John Maddock (john_at_[hidden])
Date: 2009-11-27 06:02:51
>> Question: does someone have to be a maintainer of an existing library
>> (or author of one of the accepted libraries) to become a maintainer of
>> an existing (orphaned?) library?
> This is a very interesting question. Some lingering tickets with patch
> could be cleared faster if soem orphaned components of bosot were
> assignated new manager.
Indeed. Something that occurred to me earlier was "how many tickets were
looked at in the last sprint, assigned a patch, but haven't been looked at
since?" That would be a good test of the owner being missing-in-action!
Re Boost.Array, I seem to remember Alisdair Meredith taking this on, I'm
cc'ing him just in case my memory isn't what it once was ! ;-)
It seems to me though that the bug sprints would be a good opportunity to
widen the maintainer list a little - what if we assigned an interested
volunteer to act as temporary maintainer for an orphan library during the
sprint. (S)he fixes whatever they can fix, then gets another bug sprint
volunteer to review the changes, if all looks well, and the tests are all
passing on Trunk, only then merge to release.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk