[boost] How about a call for bug-fix volunteers?

Subject: [boost] How about a call for bug-fix volunteers?
From: Jim Bell (Jim_at_[hidden])
Date: 2010-10-26 11:00:08

Library authors shouldn't have to bear the burden of bug reports for
their libraries alone. Even maintaining their regression tests across
all platforms isn't realistic (and isn't being done).

So what if we try to recruit a couple helpers for each library?

I see two avenues where we can use some volunteer help to improve
boost's quality.

1. Dandelion pickers: look at failed/yellow regression tests and try to
fix them. Volunteers could pick a platform they have access to, and try
to work across all libraries. You might be surprised at how easy many
are to fix.
2. Ticket triage: pick a library and go through all open tickets. Change
severity, resolve, request more information, try to map to an existing
regression test, interact with the submitter in the comments. (I think
Trac needs a "requesting more information" state.)  Even a brief
'triage' on each would be helpful, and help users feel they're being
heard. (Trac needs to track this, too.)  Write new regressions from
legitimate issues.

Recruiting pitch: it's a great way to improve your
skills--troubleshooting, C++, platform-specific expertise, communication.

Not so glamorous, but important and great experience.

Perhaps we could assign a little of each to each SoC person.

Maybe put the word out on Slashdot.

See previous topic threads
(http://lists.boost.org/Archives/boost/2010/10/index.php)
"Report # 29 (aka 1.45 blockers) is too narrow"
"[1.45] Beta final schedule"
"[1.45] Thread issues"