> help make sure contributed code gets reviewed. I've seen a lot of code
> rotting in Bugzilla because the author didn't know about the review
> process,
If that's the case, we need to improve either the content or the
visibility of the docs that describe the process. All suggestions welcome.
> or couldn't get r= when he solicited and gave up, etc.,
If they can't get review, they should be talking to
[EMAIL PROTECTED] or [EMAIL PROTECTED] .
> and I'm
> worried that soliciting new contributions may result in a lot of code
> going the same way. IMO, we should have some sort of periodic sweep
> (like BugDay perhaps, but monthly), wherein people hunt through bugs with
> the "patch" keyword (and attach the keyword, if they hit a bug with an
> attached patch) and ascertain the status of the patch, try to get review
> moving on it, &etc.
There's nothing to stop contributors doing this off their own bat, and
that would be great. IMO, though, attaching the patch keyword does
absolutely nothing - reviewers are too busy to go through their
components looking for patches to review. You need to ask them by email.
Gerv
