Subject: Re: [boost] Boost.Array Maintainer
From: Dean Michael Berris (mikhailberis_at_[hidden])
Date: 2009-11-27 06:36:37
2009/11/27 John Maddock <john_at_[hidden]>:
>>> 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 ! ;-)
Thanks for this John, I have to admit I didn't even bother looking at
the code or the list of maintainers before I asked the question -- I
just saw that in Trac, those tickets assigned to Boost.Array were
assigned to 'no-maintainer'. :)
> 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.
> Thoughts? Â John.
This sounds reasonable to me. :)
-- Dean Michael Berris blog.cplusplus-soup.com | twitter.com/mikhailberis linkedin.com/in/mikhailberis | facebook.com/dean.berris | deanberris.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk