Have you been looking for an excuse to play around a bit with Drupal 7, and have an interest in helping to directly shape it? Would you like to not only see how Drupal core contributors collaborate together, but become one yourself? Do you have an itch you'd like scratched and are willing to help scratch others' in return? Would you like to be exposed to new and interesting areas of Drupal you might not have otherwise experienced? Are you exceptionally good at finding faults and breaking things?

If so, drop by #drupal-dev on irc.freenode.net on Saturday (May 16) for a patch review sprint! (What is a patch review sprint? / How to connect to IRC?) While somewhat informal, there will be people around all weekend to help get new patch reviewers started and to help guide seasoned contributors to important patches.

Our goal is to try and knock the core patches to review queue down to zero (or as close to it as possible) by trying out patches to see how they work, and recommending ways that they can be improved. The Patch review sprints page has more information on how patch reviews work, a handy cheat-sheet of all the commands you need, and a list of prerequisites in order to participate.

Please note that "coding skills" is not on the list of prerequisites. While people with coding skills can perform certain types of reviews better than non-coders, non-coders can also perform certain types of reviews better than coders. In short: everyone is welcome!

Hope to see you there! :)

Comments

Dave Reid’s picture

Awesome! :D

lut4rp’s picture

^ me likes this

junedkazi’s picture

Awesome would like to chip in as well .

Thanks

Juned Kazi

xmacinfo’s picture

That's way cool!

The results of this patch review sprint will bring down the amount of critical issues as well.

Anyone can join and not sleep for two days or, for the rest of us, come and review a single patch, two or all. ;-)

webchick’s picture

See http://drupal.org/node/444718/revisions/531110/view for a partially documented summary of the day's events.

In short:

  • Over 50 patches knocked out of the "needs review" queue.
  • Of those, 14 were committed.
  • There were more than 25 people who participated in the sprint.
  • Several of these people were new faces to the core queue, and did a wonderful job on their first patch reviews. :)
  • Nearly 150 issues were added or updated within the past 24 hours, including a lot of patches that hadn't gotten eyeballs on them in quite some time.

And the fun continues on into the evening/morning/afternoon! Drop by #drupal-dev whenever you're awake. :) It's a great time for people who have patches in the queue they feel haven't received enough attention; lots of new faces are showing up and asking for patch review recommendations. Great opportunity to pounce on these people, guide them toward your patch, and mentor them on how to give good reviews.

Hope to see you there!

webchick’s picture

We got a little lazy with the wiki page today, but the summary is:

On Thursday afternoon when I posted this announcement, the "patches to review" queue had 277 items in it.

Tonight, after a full weekend of sprinting, this number is down to 176.

That means that over one hundred patches were either sent back to developers for improvements or escalated to the core committers in one weekend. This is tremendous progress, and has also resulted in lots of new faces in the core queue over the past couple of days which is great to see. :D

I want to sincerely thank everyone who took part; this weekend was a blast, and really felt like it had the spirit of the "sprint days" we have at Drupalcons that those of us who have been fortunate enough to attend Drupalcon cherish so much.

I'll try and schedule more of these in the coming months leading into code freeze. In the meantime, hope to see you in the queue. :D

webchick’s picture

Since the first one was a lot of fun, and since I'll be around on Saturday, we're doing this again. :D Updated the post for the correct date (probably will spill over into Sunday, too). Come on by!!