For the past few months, we have been holding "Drupal.org Office Hours" on IRC. Each Monday anyone interested in contributing to Drupal.org development had a chance to talk to the team, get support and advice, generally see what we are working on. Lately we noticed that less and less people attend office hours. We would like to know what is the reason and how can we make office hours more efficient. Please fill out this short survey to let us know how we can improve!

Now to the updates.

Thanks to the fast feedback from mikeker, maintainer of the Better Exposed Filters module, new Events page for groups.drupal.org is very close to deployment.

The new Books section of the Marketplace is almost ready as well. Marketplace improvements are in progress. Last week eigentor started working on the basic project reviews.

The Case studies section still needs more content. You can help by writing a case study or reviewing some.

COD Team is sprinting hard with less than 2 weeks to go! Relevant issues tagged as "da_drupalcon". The team is looking for community members to jump in on any of those issues and help push them forward by reviewing patches, coding patches or engaging in discussions.

Drupal 7 upgrade

The most exciting event of the past 2 weeks was the Second Drupal 7 upgrade sprint for Drupal.org. This time the sprint was international, happening simultaneously in Portland (US), London (UK) and Lima (Peru), turning it into almost 24 hour a day marathon. A lot of progress has been made, particularly for the Solr, drupalorg, Project*, and other modules. Blog post about the sprint is coming soon, meanwhile you can read these short notes made during the sprint.

The Bluecheese team converted the "Getting Started" page's steps to pure CSS, worked on styling of the various parts of Drupal.org and other tasks, such as "Partialify the Bluecheese theme".

The Customizations team worked on making sure that lists, drupalorg_metrics, drupalorg_handbook, and drupalorg sub-module working well on Drupal 7.

The Git team: jhedstrom has implemented drush as a way to set up and teardown user data.

The Infrastructure team upgraded Drush to v5 on all servers.

The Project team released v1.0 of a brand new module called "Entity JSON" and worked on lots of issues:

• Port 'Project selection widget' setting
• Make the 'Display user signatures on issue followups' setting per-node-type
• Make the 'Reply-to address on e-mail notifications' setting per-node-type
• Port project issue text filter"
• Make dereference_list depend on core 7.14 or later
• Project issue settings D7 cleanup
• "Remove 'Site-wide help text for new issues' setting
• Port issue following functionality to D7
• Update install functions for new field_name in nodechanges module
• D7 solution for when multiple users are updating an issue simultaneously
• Persistent (atomic) numbering of comments needed

As you can see, the Drupal.org upgrade project is moving. If you would like to help us finish it - contact Joel 'Senpai' Farris, manager of the project!

And once again: do fill out our survey and make sure to follow @drupal_org on Twitter!

---
Originally posted at http://groups.drupal.org/node/244098