A couple weeks ago, I wrote an email emphasizing the need to fix flakiness/crashes/etc. Since you might be having trouble figuring out how to bite off a piece of that problem, here are concrete ways you can help: * 20 people needed to fix failing LayoutTests. src/webkit/tools/layout_tests/test_expectations.txt gives a list. All kinds of experts are useful here: Mac, Windows or Linux people; WebCore hackers; Skia and graphics people.
* 10 people needed to triage bugs with "crash" in them, determine whether they are actionable, and send them to the right people. http://code.google.com/p/chromium/issues/list?q=crash People who are good at debugging crashes anyway especially welcome here. Any of the ex-Green Border folks, like finnur or cpu, can probably help look at individual cases. * 6 people needed to rewrite ui_tests as unit_tests, in-process Browser tests, or some other less flaky kind of test. Anyone with frontend experience is especially valuable here. Talk to jcampan to find out what to do. * 3 people needed to eliminate Purify suppressions (src/chrome/test/data/purify/*) and fix related bugs. erikkay can help you with what to do. * 3 people needed to review Coverity results and fix any problems. Look at http://code.google.com/p/chromium/issues/list?q=coverity . * 2 people needed to triage "leak" bugs. http://code.google.com/p/chromium/issues/list?q=leak has the list. Figure out which of these we can do something about. * 2 people needed to eliminate existing valgrind suppressions (src/chrome/test/data/valgrind/*) and help track down other problems that show up in valgrind. deanm is an expert here and could help you learn how to use this powerful tool. * 2 people needed to look into http://code.google.com/p/chromium/issues/detail?id=11700 , general jank after things get swapped out (e.g. when using your computer after it's been asleep for hours). We have ideas on how to solve this, mbelshe is one of the most knowledgeable consults here. * 1 person needed to triage bugs with "jank" in them ( http://code.google.com/p/chromium/issues/list?q=jank ) and figure out what the magnitude of the effects are, and how to prioritize the bugs. * 1 person needed to improve infrastructure so flakiness is easier to deal with. Flakiness dashboards, stack traces on buildbots when things fail, etc. phajdan.jr and ojan have both worked in this area and might have projects you can help with, and pamg and nsylvain know a lot in general about our infrastructure and how to improve it. If you add those up, you get 50 people, each being asked to devote a significant portion of the next few months to the problem in question. And this is (IMO) a conservative estimate of what will be needed to deal with the problems at hand. If you are a Googler, go over this with your manager and figure out something you can help with. Put it on your OKRs. Earn a peer bonus from me at EOQ. Make Chrome 4 the fastest, most stable release ever. If you don't work at Google, this is a chance for you to help make the browser much better, and earn commit access (if you don't have it). PK --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
