[EMAIL PROTECTED]: > I often encounter a problem when finding reviewers, and have to ask > who should review what. It's no problem for me, but maybe the process > could be smoother if we had a page saying "build system -> contact (e- > mail1), webkit/glue/ -> (e-mail2)" etc. Probably it won't cover all > cases, but IMHO would be a nice addition.
I think we did have such a list at one point, I agree it would be helpful to external contributors. In the past, when I've submitted patches to large open-source projects with similar review models, reviewer selection was always one of the least-explained areas, and therefore one of the most difficult. Often, commit logs can be a help, but our repository is only a month and a half old and "initial.commit" isn't always a responsive reviewer. Fortunately, there are a bunch of active folks on chromium-reviews, so even if you pick a reviewer who's out on vacation, someone who can help might see it. Even if they can't help direclty, they can offer advice on who might be a well-equipped victim. In the mean time, if you have anything for review in base, anything on the Mac, POSIX implementations, or multiplatform stuff generally, or anything involving build-driving, or stuff that's usually tossed into the "weird language/compiler/linker/system programming stuff" bin, you can send it my way. Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
