patches

In case you don't know, Edward Z. Yang (ezyang) is squashing a lot of bugs in coder_format in the scope of a GHOP task currently.
In case you don't know coder_format, it's a script I wrote some time ago which re-formats one PHP file, or recursively all files in a directory according to Drupal's Coding Standards. Doug Green has been so kind to add it to the Coder module, so if you are a Drupal developer, you probably have (an out-dated version of) it already. Unfortunately, it did not receive that much attention yet.

I do not yet want to promote coder_format with this post. Today, I just want to show you the results of an experiment, which in turn will show you, what you can expect from coder_format.

Guess, what this ugly code snippet is:

The past two-three weeks I've spent a lot of time in the Drupal 6 issue queue. This involved a mixture of reviewing patches I really wanted to see get into Drupal 6, writing or re-rolling some small patches for small bugs and typos, and trying to clear the issue queue as much as I could down to a manageable size. I commented on something like 160 issues in seven days, and read through many more.

Give the gift of a Drupal 5 release candidate this holiday season by fixing bugs!

The Vancouver League of Drupaliers is answering the call and organizing a Drupal 5 bug hunt!

Drupal 5 is in beta 2 and will be released when all the critical bugs are dealt with. There's also non-critical bugs and each one fixed makes Drupal 5 a better release. Your help, regardless of whether you're new or a ninja, makes the release happen at the best quality possible. (More about the ways you can help here: http://drupal.org/drupal-5.0-beta2)

What's in it for you?