Why Is Drupal Thriving?

At DrupalCon 2009 last week, it was abundantly clear that Drupal is picking up speed quickly as an open source content management system (CMS).  The Economist magazine is switching to Drupal as its CMS; many web sites run by the major record labels are using Drupal.  And for some factoids about Drupal's community activity: 200,000 downloads per month, 1.5 million unique visits per month to the drupal.org web site, 4400 contributed projects, all of these are doubled since last year.  The sheer number of contributed projects in particular impresses me; that is a lot of people contributing back to Drupal.  Why is Drupal thriving?  Here is what I was able to discern from talking to people at the conference, including Drupal key contributors and the founder to attendees who simply use Drupal.

When I asked attendees "Why are you at DrupalCon?", several who are building online newspaper sites and record label sites for artists replied that they were there seeking talent to help them build and maintain web sites.  I asked them "Why Drupal?"  A fairly common response was something like this: "I looked at other CMSs and it came down to a couple of factors.  First, it's cheap (free).  Second, it is easy for me to extend Drupal so if I don't like what it does, I can easily modify Drupal itself.  Third, there are lots of people who know Drupal so I can find talent at a cheap price.  We (record labels) used to hire talent in L.A. to do our Drupal work, but we don't want to pay the kind of money that Angelinos need to support the cost of living, so we look for talent outside of L.A.  With Drupal, we can easily find talent in cheaper parts of the country, or the world."

So: there is a large ecosystem of developers for Drupal, which pushes down the cost of hiring for people who want a web site built for them.  Why do so many people become Drupal developers?

Because it is easy to say you're a Drupal developer; it seems to be a key attribute of Drupal.

You can "develop" for Drupal in several ways that I learned at the conference:
  1. you can contribute to what is called "Drupal core", the core functionality of Drupal.  It's written in PHP, and is tightly controlled by a small set of committers (i.e., people who are allowed to check in code into the codebase).  To give you a sense of how tightly controlled: Acquia is a company of 30 people formed by the founder of Drupal to commercialize Drupal, Dries Buytaert; only one of the employees has committer privileges to Drupal core.  That one person is Dries.
  2. you can create your own modules, also in PHP.  I think of modules as plug-ins, like with a browser.  Drupal core comes with a small number of modules; much of Drupal's functionality is through non-core modules.  The number of committers here is much larger.  You can create your own module or offer patches to somebody else's module.  You can become an owner of an existing module, if the current owner wishes to move on and relinquish control.
  3. you can create your own themes.  Themes are a big deal for web sites, since it defines the look and feel.  You don't need to know PHP to define a theme; HTML + CSS is good enough, which greatly expands the number of people who can contribute to Drupal.
There's a page on drupal.org that summarizes all the ways you can contribute to Drupal.

When Dries founded Drupal, he decided to use PHP as the development language even though he's completely comfortable with Java.  He chose PHP because he wanted to reduce the barrier to contribution; PHP is easier to learn than Java.  And allowing people to contribute HTML + CSS increases the contributor pool even more.  The design of the community is brilliant in this way; it is clearly focused on getting as many people contributing as possible.  That was clear from the conference.

So what you have is a community where contribution is incredibly easy.  Lots of people use Drupal and identify themselves as Drupal developers; this in turn increases the pool of talent familiar with Drupal, which increases the pace of improvement to Drupal and also puts downward pressure on the price of developer talent, which makes Drupal more attractive to customers who want to use a CMS.  This puts Drupal in use in the marketplace, which in turn drives demand for Drupal developers, and now you have a thriving ecosystem.

Powered by ScribeFire.


Nice post George. Sounds like a virtuous cycle going on there in Drupal Land. Not a foreign concept to us here at Sun. In fact, Dries told me last summer soon after they formed Acquia that their open source based business is modeled largely after Sun's software business and specifically on MySQL's model. I continue to be awestruck by the amazing things happening in the Drupal community, which is still very much true to it's roots as a platform for social change, and is now becoming a great platform for business too. Maybe those two use cases are not so distinct and separate anymore. It's almost certainly one of the reasons there was so much interest in Sun's CSR program that we promoted at DrupalCon this year.

Posted by Scott Mattoon on March 10, 2009 at 06:09 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

The views expressed on this blog are my own and do not necessarily reflect the views of Oracle. What more do you need to know, really?


« July 2016