We should also publicize/update these existing resources to help patch authors find reviewers for their patches:
http://trac.webkit.org/wiki/CodeReview http://trac.webkit.org/wiki/WebKit%20Team I think the most effective approach is when patch authors proactively seek out reviewers. We're all busy, but when I'm asked to review a patch, I make time for it or point the person at another reviewer. Dave -- Sent from my iPhone 4 On Jul 22, 2010, at 12:29 AM, Maciej Stachowiak <m...@apple.com> wrote: > > On Jul 21, 2010, at 3:41 PM, Eric Seidel wrote: > >> Wow. I really like this idea of helping contributors better >> understand what's going wrong. >> >> But, I think that even better would be to build a better front-end for >> reviews. Or a bot which knew how to suggest reviewers (based on >> annotate information from lines changed). > > > I think a better UI for reviews, plus some better attempts at active > notification of potential reviewers, could go a long way. I'm a strong > believer in trying nudges and positive incentives before implementing harsher > policies. > > Regards, > Maciej > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev