Subject: Re: [boost] [date_time] Who is in charge?
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2012-07-07 19:46:22
Olaf van der Spek wrote:
> On Fri, Jun 29, 2012 at 12:02 PM, Klaim - Joël Lamotte
> <mjklaim_at_[hidden]> wrote:
> > I was surprised too, almost a year ago, that there have
> > been no reaction - not even a reply - to a date_time bug I
> > reported on this mailing list
> > (https://svn.boost.org/trac/boost/ticket/5753).
I've been in contact with Jeff and he acknowledges that he needs to do something about this.
> Boost does not appear to have a policy for maintainers that
> go missing in action.
We have this policy, which is half of the equation:
> I think someone (maybe steering committe) should come up with
> some policy.
This sounded awfully familiar, so I checked. I'm supposed to write up something like the following and post it to the web site:
"When a Boost library maintainer becomes unresponsive, the following process provides a means to take over maintenance:
"1. Identify the maintainer of the code that is languishing.
"2. Appeal to the maintainer, by name, in a properly targeted message to the developer's list (with the right '[library]' tag in the subject line).
"3. Bump the message a time or two over the course of a month or so.
"4. Try contacting the maintainer directly yourself or through others on the developer's list.
"5. Declare the library to have no maintainer on the developer's list and volunteer to be the new maintainer.
"6. Assume maintenance of the library if there are no objections raised on the developer's list within two weeks."
This is certainly a good start and I welcome any input you may have before I post it. At any rate, step 4 has worked, though Jeff has not yet responded on-list.
Rob Stewart robert.stewart_at_[hidden]
Software Engineer using std::disclaimer;
Dev Tools & Components
Susquehanna International Group, LLP http://www.sig.com
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk