http://google-opensource.blogspot.com/2008/07/and-winners-of-2008-google...
http://drupal.org/webchick-wins-best-contributor-open-source-awards

I have lots I'd like to say about this, but am a bit overwhelmed just at the moment. Suffice it to say, my sincerest thank you to everyone who nominated me for this award, and to O'Reilly, Google, and the Drupal community in general for being so unbelievably awesome.

Here's the presentation that Marianne Masculino and I did about how to contribute to both WordPress and Drupal:

It was really cool to see the overlap between how WordPress does stuff and how Drupal does stuff, and all the ways the communities are similar and how they're different in how they work. Also, Marianne was really awesome and nice. :)

Thanks to everyone who turned out to see it... It was great to meet you! :)

Also, I found a "live blogging" version of the session at http://www.sparkplugging.com/marketing/blogher-2008-open-source/.

So the past couple months have been completely nuts trying to get Drupal Jumpstart out the door (one month left! eek!), I haven't had the chance to write about this.

Tomorrow, I'm headed to San Francisco, California for BlogHer '08, and will be co-presenting with Marianne Masculino from WordPress on Saturday about how to participate in an open source community; I of course will be talking about the Drupal community. :)

Then Monday, I'm headed out to Portland, Oregon for OSCON 2008 and will be hanging at the OSCON Welcome for the Drupal Community and hopefully the Drupal Media/Files Code Sprint. I also get to meet our book's editor, Julie Steele from O'Reilly, which I'm really excited about. :D

Anyone else going to be at either of those events?

I'm officially headed to Drupalcon Szeged in August (thanks, Lullabot!), and so naturally submitted a few session proposals this weekend. :) Incidentally, if you haven't yet registered for Szeged, you really ought to do so soon -- the price goes up after June 30, and their website has a super smooth registration process.

So in addition to the "usual" Drupalchix BoF and Summer of Code showcase proposals, I also really want to try something new this year in support of spreading the testing love.

So I'm proposing.... Awesome Testing Party, a working session where coders from newbie to ninja gather in a room together and help each other to write tests for Drupal core.... and win prizes! :)

Earlier today, I asked the fine folks from the Chicago Technology Cooperative what the status is of GMap and Location in terms of a Drupal 6 port. I expected at best a brief reply, probably followed by a "buzz off." ;)

Instead, Brandon Bergren and Rebecca White decided to join #drupal-dojo and spoke at length about the current status of the modules, what's needed to get them stable, and what the roadmap to Drupal 6 is. And, most importantly, they also went into details about how we can help (coders and non-coders alike! :)).

A summary of the talk (as well as the full IRC log) are posted at groups.drupal.org at The State of Geospatial in Drupal. The general plan is to get stable releases of the 5.x modules out first, then do straight ports to Drupal 6, followed by new development.

Want to help speed things along? Here's a list of the places to jump in if getting these modules stable is an itch for you, too.

Earlier tonight, Jimmy Berry posted a plea for the Drupal community to clean up their messes in terms of testing. Since Jimmy did a whole bunch of the heavy lifting involved in getting the SimpleTest framework ready to commit to core, a major milestone in Drupal's development, we'd do well to listen to his words and his frustrations when he sees all of his hard work falling apart due to neglect.

SimpleTest has only been in core for a month now, and already we've managed to break more than half the tests. This is a big problem. :\

In order for our community to embrace testing, we're required to bring several hundred people who've never written a test before in their lives (and might not even have heard of automated testing until heard some Drupal people talking about it) up to speed on what testing is, why it's a good thing, and how to do it.

But every time there's a bug in the testing framework, and every time an existing core test fails to run, this serves to completely destroy developers' confidence. If we're lucky, these people will go work on other things for a little while, and then check back periodically to see if things have been sorted things out yet. If we're unlucky, they start to develop animosity and resentment about the very idea of testing, and then start to distance themselves from doing development and encourage others to as well. Either way, the end result is stalling development on D7, and fewer people to spread the work around of writing further tests.

So how can someone concerned about the state of D7 development help?

Today, the Google Summer of Code 2008 accepted students were announced. 7,000+ applications to 175 mentoring organizations from nearly 4,000 students, of which 1,125 will be funded. Altogether, this means a $5.6+ million dollar investment in open source from our buddies at Google. Kick ass!

How did Drupal make out? We will be mentoring 21 Summer of Code projects from our 84 submissions. Drupal's mentor team did an outstanding job of weighing the pros and cons of each proposal, making difficult decisions, and ultimately choosing an exciting mix of projects and students:

Note: Please read the date of this post before sending me e-mails about it. Thanks. ;)

Since I got my start in the Drupal community in 2005, most have noticed that I've been a wee bit, erm. Obsessed. I try to help out in as many ways as possible, and often this means juggling about 50,000 different priorities at a given time, the last of which is always sleep.

Well, it was fun for the last 2.5 years, but enough is enough. While I will always have a soft spot in my heart for the Drupal community, my participation has often been at the expense of relationships with family and friends as well as my own personal health and well-being. :( So, it's time to say "goodbye, world" to the Drupal community and instead embark on a new chapter in my life...

In case word hasn't reached you yet for some reason, Summer of Code 2008 is a go, and this is the week for college/university students to submit applications to work on projects for their mentoring organization of choice over the summer. Our hope is of course that a whole bunch will choose Drupal, which is an awesome, knowledgeable, and fun community to be a part of, and very supportive of SoC students (I know, because I was one myself back in 2005! :D).

As part of my duties for the Drupal Association, I help to administer initiatives that help bring in new contributors, like Drupal's involvement in Google Summer of Code. A huge thanks to the admin team -- chx, cwgordon7, and dmitrig01 -- for their tremendous efforts in getting the program kick-started!

We're trying something new this year that we haven't done in years past: public community review of student ideas and proposals, prior to their submission as formal applications for Summer of Code. There are multiple reasons why we chose to "beta test" this approach, which I will detail after the break.

However, for those who want to help bring new contributors to the Drupal project, and have a hand in deciding what new awesome projects get funded over the summer with Google's multi-thousand dollar investment, please jump in and help review some student proposals! The absolute deadline for student applications is Monday, March 31, 2008 at 17:00 PDT, so it's imperative that students get their questions answered and their proposals reviewed and refined as soon as possible so they have ample time to get their applications in.

Still stuck... er, I mean... visiting ;) Boston after Drupalcon, thanks to a lovely winter storm in Canada that refuses to go away. Karen Stevenson was nice enough to put me up in her hotel room for a night, so I wanted to pay her back by making this important issue my "itch of the week": we need to figure out a data model in order to move CCK fields in core efforts forward. See Karen's Field Structure thread for more details.

Currently, regular old single-value fields (like "first name") are easy. Just cram 'em in the content type table. But when you start moving into more advanced areas like shared fields (such as a "picture" field that's attached to both "book" and "video game" content types), or multiple-value fields (such as a group of checkboxes for "interests"), those currently get split off into their own tables in order to normalize things. Moving fields to and from multiple value and shared has always been a harrowing process, involving table structure manipulation and data migration. However, with the abstraction brought on by the new Schema API in core, this suddenly became a lot tougher.

A couple of options have been proposed, which include a de-normalized schema per content type (leading to a bunch of NULL values for multivalue fields and data duplication for shared fields), and a "each field in its own table" approach, which involves many (sometimes MANY many) joins, which can kill performance on a large site.

So, calling all database schema experts, SQL gurus, performance nuts, etc. We need your help. We need to make sure we're not missing any obvious options that would make this work more slickly, and we also need some help benchmarking to determine what the best option is going to ultimately be. Please head over to http://groups.drupal.org/node/9297 and post your thoughts!