Did you know there is a DrupalCamp that is bigger than most past DrupalCons? It's the Bay Area Drupal Camp, or BADCamp which is expected to draw over 1,400 people this year for three days of trainings, summits, sprints, sessions, BOFs and parties all across Berkeley this weekend.


Instead of giving a morning keynote, I will be interviewed by Josh Koenig after we've been both been drinking for a while. I'm very excited about the interview format and having it in the evening. The traditional keynote presentation format works well for making statements, but DrupalCamps inspire often a different mood. I expect the interview format will fit this ambiance by being more probing and personal than a straightforward keynote could be.

We still haven't decided on the questions... and that is where you come in. If you were in Josh's positions, what would you ask me? What topics should we discuss together? Just suggest your questions in the comments of this post. Josh will pick both the most popular and the most interesting ones and see where they go.

I look forward to seeing many of you at BADCamp next week!


Lev (not verified):

Thanks for asking Dries. I think this one's obvious, but addressing the recent discussions of Acquia's influence in the community and on the direction of Drupal seems critical. Especially relevant given Pantheon's competition with Acquia hosting.

Steve T (not verified):

Nice, Im looking forward to the full day on sat, I wont be around on Friday but I think most of the stuff is happening on Saturday.

As for questions, I think their seems to be a of confusions as to what the difference between Pressflow, Drupal, Mercury, and all the fancy performance terms that gets thrown around. For example does someone need to just install Pressflow, or do they need the Mercury Profile to it? What does that actually do, I haven't been able to find any info on this, it may be well known but I have only been around in Drupal community for the last 2 years.

Nicholas Roberts (not verified):

I'd be interested to understand how the hundreds of millions of venture capital dollars invested into Drupal shops - i.e. Acquia, Pantheon, Palantir etc etc - can be reconciled with the Drupal community.

In other words, how can the almost half a billion in venture capital in the Drupal community be paid back with the returns normally expected by VC ?


As far as I know, only Acquia, Pantheon, CommerceGuys and SubHub raised money from venture capitalists. To the best of my knowledge, these numbers add up to a number in the $40 million range -- certainly not to $500 million.

greggles (not verified):

The second question seems hard to answer given the private nature of some of that information. I want to clarify some of your pronouns.

Was your question:

"How will the venture capital companies who have invested in the companies based on Drupal get a return on their investment?"

DjebbZ (not verified):

Basically Pressflow is a fork of Drupal. The only 'official' one living out there. How does Dries feel about it ? is there any plan merging the efforts, as I see a Pressflow 7 version ? And with Pantheon competing with Acquia's hosting, how do these plans (if they exist) fit with the community's wishes, which are basically a better Drupal software ?

End of my questions. Thanks !

Luis (not verified):

I would like to know what's your position in the Framework / Product / Platform / Small Core debate

nicl (not verified):

Hi Dries, my question is:

'How do we balance the benefits of Drupal's more-than-a-framework approach with the need to keep things simple?'



AndrewGearhart (not verified):

Personally, I welcome the ecosystem of development that is coming from companies such as Pantheon and Acquia. Given Acquia's existing position in the Drupal community, what is Acquia doing to clean-up the slovenly reputation caused by the immense number of issues (2,550+ in D7 Core only) that have remained open surrounding Drupal core?

Don Fukushima (not verified):

As Drupal gains traction in enterprise level organizations, what do you see as the key barriers to successfully sell into and deploy Drupal in these organizations?

Most likely Drupal needs to play nicely with other key software platform vendors such as Microsoft, SAP, Oracle, etc. How strong, deep, and complex are these integration challenges, are they deal breakers?

What about concerns and resistance to introducing a new open source platform such as Drupal, where does IT Architecture and Planning as well as the Development group stand? Is Drupal viewed as a point solution for content or as a potential enterprise application deployment platform?

Where does Drupal have the best chance to sell into the enterprise, IT, Marketing, etc.?

Kevin (not verified):

How do you feel about 'outsourcing' Drupal support to StackExchange?
(I am personally very much in favor of this option, and do not think it detracts from the community, but rather allows us to maintain focused on what Drupal does best, while letting other software do for us what it does best).
See here for more info: https://www.drupal.org/node/1236290

Dave T (not verified):

1. You recently conducted an in-depth Drupal survey (3000+ respondents) and shared the results – what data surprised you the most and why?

2. You’ve already accomplished a lot at a young age? What motivates you?

3. As a project lead for Drupal, you wear a lot of different hats (technologist, evangelist, product development, sales, etc.) – if you could choose only one role what would it be and why?

P.S. Absolutely brilliant format – love the Q&A round-table w/Josh as moderator; look forward to seeing the video.

Mark (not verified):

I'd like to hear a little explanation about how hosted solutions such as Drupal Gardens work within the GPL and how you see innovations created for these projects getting their way back into the wider community.

Gord Christmas (not verified):

The question I have had on my mind for quite a while is how is the complexity arising in core going to affect uptake for those new to Drupal? Do we end up with mostly surface dwellers who don't peek into the machinations with a dwindling crew of devotees? My main criteria for choosing Drupal in 2005 was it's elegance and simplicity, only one layer of abstraction. Now it appears those layers have deepened over time to allow all manner of wonderful interactions and possibilities, but at a cost.
If we can't return to simplicity we need amazing training, and solving that is an even bigger question.

Ryan (not verified):

Part of the answer may lay in Dries' keynote from 2009's Do It With Drupal conference. If I remember right, he said that Drupal's goal at one time was to eliminate the "web master" but that perhaps the future lies in eliminating the "web developer". In such a future, we'd still have developers building and refining the core systems, but perhaps the majority of new users wouldn't need to know more than how to configure a Drupal site, Views, Rules, Commerce, etc.

It's a bit fanciful, sure, but perhaps that topic could be revisited at the roundtable?