drupal7

Last week, Zoe, Dave, and I made our way down to San Francisco for DrupalCon. It was a fantastic week, and even though I knew how many people were attending, I was still stunned by the actual size of the crowd, especially when we were all gathered together for the keynote sessions.

This post was originally posted on my personal blog, but we thought it was worth sharing here.

This one’s all Drupal folks, cause that’s pretty much all I’ve done for the last two and a half weeks. This is what happened when I asked the question, “Is there some reason we don’t just fix it all?” I did not know then what I was getting myself into…

A small inconsistency

It all started in late summer, when I was testing some Drupal 7 core patches for moving fields and image handling into core, and at some point clicked my way into the Help pages. There was a blatant typo on the Node module help, and then a change in language that needed to be made, so on August 1st, 2009 I created an issue for it.

This past weekend was the Drupal7 Contrib Module Upgrade Sprint that Károly Négyesi (aka chx) organized at the NowPublic offices in Vancouver. I spent a good part of Saturday there, helped out with coaching the one brave beginner who turned up to learn some of the tools for helping out in the community. Otherwise, after a bit of a rough start, the devs all hunkered down and made some Drupal magic, upgrading super important things like Views, Panels, database stuff, and various other bits and pieces of modules and themes.

As of today, we are now only two weeks from the Drupal 7 code freeze. When we hit Sept. 1, from then on in, only bug fixes will be worked on (no new features), as everyone focuses on generally improving the code and how it functions. Because of the deadline coming up, there is a lot of focus on getting new patches committed to HEAD before Sept. 1, and to get the patches committed, they need to be reviewed by the community and given a stamp of approval. As of 11:41am PST today, the D7 queue contains: