Code review for security advisory coverage applications

We should highlight all the great people that have done reviews. This is a wiki page to do that. Please note that there is also a I reviewed Project applications checkbox in your Drupal.org profile.

We have many individuals waiting to be reviewed, and few reviewers. This gives us a backlog of applications awaiting review, which makes both reviewers and applicants unhappy. So how can we improve this?

As I updated all the CVS applications tonight (with some great help), I couldn't help but think that its still so unwieldy. So, I was thinking about maybe organizing a code review sprint at DrupalCon Chicago next week focused on the new Full Project applications.

It would be super cool to get applicants and reviewers paired up in person.

So, I am wondering if anyone has any thoughts or suggestions, especially on logistics. Also, my bandwidth is pretty low so maybe someone is willing to help out on this.

All issues requesting peer review use the peer-review tag (with a dash, like this group). People can also optionally focus the review they are looking for with tags such as code-review, ux-review, etc.

I noticed that the Peer Review group is being revitalized and the mission expandedand there is a movement for a more structured peer review of modules program, which is awesome.

Code review of existing contributed modules is frequently cited as a means to improving the quality of existing contributed modules. However, the task of performing a code review falls somewhere between documentation, writing and reviewing patches, reviewing CVS applications, and creating new modules.

This is a proposal to elevate the visibility of module review, and make it easier for newcomers to perform module reviews.

I'm writing that new developers can ask for a code review quite apart from the application review process, but i don't have much i can tell them except ask in IRC and (suggested by beejeebus ask in a g.d.o group on a topic related to your module.

Should we try to create a clearinghouse?

A "code review requested" tag for issues– or projects?

Any other places that exist or ideas for what should or should not be created?

So, the whole purpose of this group is to create discussion, document, rally around getting more people involved in reviewing new contributors applications.

In Copenhagen, @webchick gave a talk about how this process is pretty negative to most people applying. And, with @webchick's help, we were able to get a BoF going and some short-term, new interest around reviewing application. I even spent a fair amount of time documenting how to review code.