Boost.Array Maintainer
Good day everyone, Does anybody already maintain Boost.Array? I see quite a number of patches and "todo" tickets and am wondering whether someone should be taking care of such a crucial piece of the collection. If there isn't anybody willing to maintain Boost.Array I don't mind looking after it until someone else does. 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? HTH -- Dean Michael Berris blog.cplusplus-soup.com | twitter.com/mikhailberis linkedin.com/in/mikhailberis | facebook.com/dean.berris | deanberris.com
Dean Michael Berris wrote:
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.
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. Thoughts? John.
2009/11/27 John Maddock <john@johnmaddock.co.uk>:
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
On Nov 27, 2009, at 3:02 AM, John Maddock wrote:
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.
I think that this is a great idea.... -- Marshall
John Maddock wrote:
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.
Thoughts? John.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi, I don't know if this is the best way, but it is clear that we have a problem with very old tickets. It will be great to identify the libraries that will need this kind of help, and make a call for volunteers. Best, Vicente -- View this message in context: http://old.nabble.com/Boost.Array-Maintainer-tp26534655p26544289.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Dean Michael Berris wrote:
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?
I think the current system of library "ownership" is a big problem for Boost. When the owner/maintainer is around, things work fine, but simply letting libraries rot because their owner moved on to other projects is not acceptable. We shouldn't advertise that they're of "Boost quality" when bugs are not being addressed (particularly when patches are provided, and all that has to be done is commit, watch the tests cycle, and merge -- users end up having to maintain these patches themselves against their local installation of Boost). Either unmaintained libraries should be removed from Boost, or anyone else willing to take responsibility for them should be allowed to do so. --Jeffrey Bosboom
participants (6)
-
Dean Michael Berris -
Jeffrey Bosboom -
Joel Falcou -
John Maddock -
Marshall Clow -
Vicente Botet Escriba