You do not need programming skills, just a fair amount of Drupal experience and some time. There are a large number of older bug reports marked CVS that have not been closed out over time ago and may no longer be relevant. Here are the steps:

1. Download and install Drupal HEAD on a test site.
2. Visit the pending bugs list and start with the oldest reports.
3. If a bug is marked as 4.5 or cvs, check if it still applies to the current HEAD version you downloaded.
   • if it still applies, then set the version to cvs (if there is more than one cvs in the version menu, pick the first)
   • Click the follow up link and update the bug report with your findings so that work is not duplicated.
   • if the bug can no longer be reproduced as it is fixed or just no longer applies (several screens are reworked in HEAD), just change the status to fixed and update the comments acordingly.
4. If bug report version is marked as 4.6, then just follow up whether the bug still exists in HEAD and update accordingly with a comment "exists in current HEAD". If you feel like verifiying if the bug has been corrected in 4.6.2 then go ahead but the current focus is to clean up the oldest ones first.

There has been a surge of interest lately to try and create Drupal-driven artist and music websites. I know many members of the Drupal community have been frustrated in trying to leverage Drupal for art and music websites because:

1. Artists and musicians don't understand how Drupal could help them
2. The learning curve for Drupal is too high
3. Developers can't find other developers who are interested in using Drupal to create artist and music websites
4. Information overload on drupal.org

As a result, I've launched a website to address the problems above: http://www.drupalART.org/.

The Drupal community has been growing steadily over time, and recently started to outgrow our shared, single server system (Pentium Xeon 3Ghz with 1 GB of RAM). The server hosts a variety of Drupal websites, including http://www.drupal.org/, http://cvs.drupal.org/, http://www.drupaldocs.org/ and a number of other sites.

As mentioned earlier, we have been talking to the Open Source Lab (OSL) at Oregon State University and they generously offered to provide free rack space, bandwidth, power, backup facilities and on-site support. OSL is responsible for taking care of some of the largest projects in the Open Source community, including the Apache Foundation and the Mozilla Foundation. In order to take advantage of this generous offer, we need to supply our own equipment. Our initial plan was to purchase a modest dedicated server to replace our current shared system. However, thanks to the success of last week's donations, we will be able to roll out a more sophisticated server architecture to support the growth of our community. Read on for the details, and an extra "sun-prise" ...

On behalf of everyone who organized the fundraising, we want to extend a huge Thank You to everyone who donated and made this effort a monumental success!

In 48 hours, we managed to pull in just over $10,000 in mostly small donations from more than 250 generous folks. That's more than 300% of our intended goal -- an incredible feat for the Drupal community!

To maximize the benefit of your donations, we've partnered with the Open Source Lab at Oregon State University (thanks Scott and Corey!), and, in short order, have come up with a fantastic plan for the future infrasturcture of Drupal.org.

After what can only be described as the 'Extended Weekend from Hell', Drupal.org has been restored and is back in business.

First things first: what caused this outage, and why did it take so long to get the server back up? To phrase it simply and bluntly: misfortune, bad timing and miscommunication. Murphy's (annoying) law has been proven true once again.

In order to improve Drupal documentation usability, the Drupal handbook has been undergoing significant revision and feature enhancement:

• Longer handbook pages have been broken into multiple pages so as to allow the collaborative book to generate all section headings.
• Drupal handbook pages have DocBook XML and OPML export functions.
• The admin/help text available with Drupal core installations has been updated to include 60+ core and contributed modules (patch pending). Admin/help text will now be maintained on drupal.org in the modules and features section of the handbook.
• Handbook pages on drupal.org have additional blocks available in the sidebar providing useful links and information on handbook usage.
• Advanced Drupal users are providing additional configuration tutorials and code such as best practices and PHP page snippets.
• Based upon the user feedback gained in the recent card sort exercise, the Drupal handbook is being completely reorganized into multiple handbooks.