On 1:59 PM, Eddie Carle wrote:
Start with a Trac ticket ... But don't stop there. Get in touch with the author (see libs/maintainers.txt in your boost distribution), and propose it to him. If his e-mail is out of date, maybe someone on this list could help find him. It's all up to the maintainer. Pitch it to him as requiring very little of his time. It appears he hasn't been around for a while, based on posts to this list. I have noticed his inactivity as well. I sent out the email and am hoping that he gets back to me. What happens if he is incognito? Would
On Wed, 2011-02-09 at 18:21 -0600, Jim Bell wrote: there still be any mechanism to pursue this if that is the case?
We say "MIA", and there's lots of, um, lively discussion here about what ought to be done then. <http://www.google.com/search?q=MIA+site%3Alists.boost.org> Any maintainer can commit a change, but all are busy with their own libs & lives, and none want to commit a patch to something they're not intimately familiar with. (Understandably.) If your maintainer is MIA, your options seem to be ... * Petition to maintain it yourself (if you're sufficiently motivated). Not sure what's involved with that except that the current maintainers need to establish confidence in your abilities. * Put it on the Google SoC (Summer of Code) list for an intern to work on. Not sure the details here. * Petition the "roving hit squad" to hit it next. <http://lists.boost.org/Archives/boost/2010/12/174459.php>. They're currently working on boost.pool <http://groups.google.com/group/boostpool?hl=en>, and experimenting with the whole "roving hit squad" approach. Not sure how that's going. Hope that helps.