Dries Buytaert

State of Drupal presentation (August 2011)

Three weeks ago, at DrupalCon London, I gave my traditional State of Drupal presentation. In good tradition, you can download a copy of my slides (PDF, 37 MB) or you can watch a video recording of my keynote.

My presentation was based on the results of the State of Drupal survey, which got over 3,000 responses from people all over the world. Because I didn't have time to talk about all the survey questions in my keynote, I've decided to make a summary of all the survey results (PDF, 160 KB) available as well. It gives a more complete view on the survey results.

However, there is much more data hidden in the raw survey results, so if you'd like to do your own analysis, you can download a copy of the raw survey results (CSV format or XLS format) and look at the raw data yourself. I anonymized the data by removing the name and company information. If you decide to analyze the raw data, consider sharing your findings with all of us.

DrupalCon London was a blast and I would like to thank everyone for making it such a great event.

State of Drupal presentation (March 2011)

Two weeks ago, at DrupalCon Chicago, I gave my traditional State of Drupal presentation. In good tradition, you can download a copy of my slides (PDF, 52 MB) or you can watch a video recording of my keynote on archive.org.

Just before DrupalCon, m62.net, a presentation development company, offered to help me with the production of my slides. I took them up on their offer. They helped me put together the video and helped me with the visuals, as well as the delivery. They went above and beyond to help me -- all free of charge. I think the slides were very effective in delivering the message so a big "Thank you!" to m62.

State of Drupal presentation (April 2010)

Two weeks ago at DrupalCon San Francisco I gave my traditional state of Drupal presentation. A total of 6000 people watched my keynote live; 3000 were present at DrupalCon, and another 3000 watched the live video stream. Nonetheless, a lot of people asked me for my slides. So in good tradition, you can download a copy of my slides (PDF, 48 MB) or you can watch a video recording of my keynote on archive.org.

Picture taken backstage while waiting to go on stage for my keynote.

Picture taken after my keynote just before packing up my laptop.

State of Drupal presentation (September 2009)

Two weeks ago at DrupalCon Paris, I gave my traditional state of Drupal presentation. The video of the presentation is available from archive.org, and you can download a copy of my slides (PDF, 8 MB) as well.

I don't want to give away the spoiler, but essentially, the state of Drupal is strong. :) We should be really proud of what we have accomplished with Drupal 6, and what we're about to accomplish with Drupal 7. In the presentation, I also talk about what it means for Drupal to grow up, and what the next phase of our life will most likely look like.

State of Drupal presentation (March 2009)

Last week at DrupalCon DC I gave my traditional state of Drupal presentation in front of 1400 Drupalistas. The video of the presentation is provided below, and you can download a copy of my slides (PDF, 20 MB) as well. The video is available in alternative encoding formats from archive.org. Topics I talked about: the history of Drupal, the Drupal 7 release, the future of Drupal, etc. Have a look!

Drupal 7 code freeze: September 1st

As I announced in my keynote presentation at DrupalCon DC this morning, the next code freeze will be on September 1st, a little less than six months from now. It's been more than a year since we started work on Drupal 7, and we have two-thirds of the development cycle behind us.

After September 1, we'll focus on the performance, usability and stability of the code we have in hand, and begin preparing for the release of Drupal 7. As a general rule, after the code freeze, only bug fixes will be allowed.

Announcing a code freeze date is always a little bit dangerous in light of a possible slip, but doing so helps prioritize development efforts and helps end-users in their planning. Drupal 7's release date is still unknown. As always, it's ready when it's ready, and the actual release date will depend on the length of the code freeze, which, in turn, depends on how well the Drupal community continues to embrace test-driven development.

I decided on September 1st after talking with people in the community (including my Drupal 7 co-maintainer webchick), reading forums topics, listening to users and examining the download and usage statistics. Now that most of the major modules work with Drupal 6, it's clear that Drupal 6 has really taken off. As an example, Drupal.org is humming along on Drupal 6.

To make Drupal 7 a killer release, we have a lot of work remaining. Another six months of development should leave us with enough time to complete existing work (like fields in core and our database abstraction layer), to add additional features, to incorporate various usability improvements (based on the usability team's work and that of Mark Boulton), and more.

With only six months ahead of us, now is the time to get involved. As usual, the amount of core contributions increases as we approach code freeze so the sooner your patches land, the better.

I haven't blogged much about Drupal 7 yet, and have resisted the urge to do so because I felt people weren't ready for it. For many of us, instead, we've used the last few months to focus on some heavy backend work like the new database abstraction layer and fields in core. As we begin to build the momentum for our next release, expect me to blog more about the exciting development efforts occuring in Drupal 7.

State of Drupal presentation (August 2008)

Last week at DrupalCon Szeged I gave my traditional state of Drupal presentation. The video of the presentation is provided below, and you can download a copy of my slides (PDF, 11MB) as well.

The presentation discusses the results of the recent survey that I conducted; the survey ran for 30+ days and collected more than 1300 responses so it should provide a good idea of the community's current thinking. I'll provide more color and details about the survey results in a number of follow-up posts.