This is my first blog post in 2011, so first things first: happy New Year to all of you!
As I do each year, I want to stop for a moment and reflect on the past, before jumping head-first into the new year.
Last year was another year of growth for Drupal: the number of active committers grew; the number of visitors to drupal.org grew; the number of Drupal sites grew; and the number of Drupal events and meet-ups grew. Drupal grew by almost every discernible metric.
Overall, we became a better and more well-rounded team in 2010. We've always had many kick-ass engineers in the Drupal community. However, 2010 was the year in which we achieved noticeably better usability, design, accessibility and marketing. These are important developments, as these new skills will help prepare us for even more success in the long run.
On a personal level, 2010 was a very busy Drupal year for me. I committed 1,683 patches -- that's up from 1,567 patches in 2009 and 1,031 patches in 2008. I accepted many more speaking engagements to evangelize our work. While in 2009 I flew about 100,000 km (62,000 miles), in 2010 I flew over 300,000 km (190,000 miles). That's a lot of evangelizing. I was more 'outward facing' in 2010 than ever before, which seems to be a trend. Although I enjoy meeting Drupal users, I'm glad to stay closely involved with the day to day development of Drupal core. Being able to combine these two essential elements is both important and healthy. I hope and predict that 2011 will bring more of the same.
My personal low for Drupal in 2010 is the fact that we didn't release Drupal 7. It is a consolation, however, it has been delayed for good reasons and we didn't compromise on quality. One thing is a given though: 2011 will be the year of Drupal 7. It will be a nicer-looking, more powerful, and more scalable Drupal that will be easier to use. If you've overlooked Drupal previously in favor of some other system, it's time to revisit it again.
My biggest wish for 2011 is that our community remains strong. We are our biggest asset. We make Drupal both vibrant and innovative. It has been an honor to be a part of the Drupal project, and it remains so today. I have no reason to believe that that will change in 2011.
After working on Drupal 7 for three years, I'm looking forward to start working on Drupal 8. One of the things that I like most is figuring out the future, and leading the community in the right direction.
I'm utterly convinced that user experience remains the single most important thing that is holding back Drupal adoption. I want to spend time listening and talking to each of Drupal's users and learn more about their experiences. That includes content creators, site builders, developers, designers, system administrators, owners of small Drupal sites, owners of large Drupal sites and more. I also want to learn more about other systems and learn from them. There is only so much we can do in one release, especially if we want shorter release schedules. So I want to have a very clear picture of how we can improve the user experience of each of Drupal's target audiences.
Based on the 300,000 km of listening I did last year, I predict that the following three items will make it in the top five new features of Drupal 8: general usability improvements for content creators and site builders; performance improvements for single machine installations; life cycle and release management (e.g., development-staging-production, configuration management, testability).
It's clear that the mobile web will become mainstream in a big way in 2011. On top of that, the iPad is changing our world. We should think long and hard about how we can make Drupal the go-to-platform for building web applications in a world of tablets and mobile handheld devices. One of my objectives is to write a small iPhone or Android application that connects with Drupal. I want to learn more about it so I'm going to try and make it one of my weekend projects.
I also predict that in 2011, we'll see the first Drupal website that serves a billion page views per month, and that Drupal.org will be upgraded to Drupal 7 before the end of 2011.
I've spent a lot of time time thinking about Drupal distributions in 2010. While we made a lot of progress in making distributions feasible from a technical point of view, we have yet to figure out the business model around Drupal distributions. Unless we make it commercially interesting or at least commercially viable for organizations to build and maintain high quality distributions, distributions might not be as popular as we'd like. I think 2011 might be the year where many of us test how important Drupal distributions are really going to be for us.
Looking back at 2010, I'm happy with the way the Drupal Association evolved. We did some unusual things this year. We hired two full-time employees; Megan Sanicki (sponsor wrangler) and Neil Kent (events manager), and paid for the drupal.org redesign to be completed. We're also paying for the migration from CVS to Git. It isn't always easy to mix paid staff into a volunteer-driven open source project, but without that, two of my 2010 highlights would not have happened.
Relative to the bigger market, 2010 was also the year where I felt core development of Joomla! slowed down a bit. As part of that, I noticed that the Joomla community started to expand to Drupal. WordPress, on the other hand, seems to be accelerating. Slowly but certainly, it's growing from a blogging platform into a content management system. Kudos to Matt Mullenweg and Automattic for their progress. While WordPress has a long way to go to compete with Drupal on the high-end, I expect that we will see it compete more and more in the low-end of the market. I won't let them take the low-end of the market -- it has been too important for Drupal's growth and adoption. I'm very passionate about making small sites successful, and I wish they were better represented in the Drupal.org issue queues. It is going to be interesting to see how these things play out. Either way, the real competition is not other Open Source projects, but proprietary software vendors and the many static HTML websites. There is so much room for growth that we shouldn't worry too much about Open Source competition.
2011 is also the year that Drupal turns 10 years old. We're starting off the year with our biggest release ever, followed by our biggest party ever. We'll have lots of things to talk about, lots of planning to do, and lots of initiatives to kick off. Expect 2011 to get very busy.
No blog post of this type would be complete if I didn't end with a sincere, heart-felt "Thank you!" to the many members of our community. Without your contributions, Drupal wouldn't exist, and my past years and future years to come would be devoid of something I love dearly. So, from me to you, for making Drupal what it is today, and for working with me to make it better day by day, let me say, simply, thank you.
Ten years ago, the average organization had one website. Since then, the world has become a more complex place with a diverse set of needs. If you're like most organizations the number of sites you have continues to grow at a rapid clip. You've dipped your toe into the social media waters by setting up one or more blogs, you use microsites for the foundation of your marketing efforts to promote products and events, and community sites to engage with the people who use your products. And of course, you have your corporate website, as well as your intranet and a number of internal collaboration websites for different projects. This is today's reality.
During the past year, I've met with many organizations that have hundreds of sites; some even have thousands of sites. Most of these sites are vastly different in terms of scale, functionality, complexity and longevity. As a result, the level of investment and the time to market requirements are usually very different. Some of the websites are owned by the company's IT department while other websites may be owned by their marketing department.
For most organizations, one tool cannot get the job done, so they keep multiple tools in their toolbox - whether they intend to or not. Unfortunately this is a common scenario in many enterprises. We see many organizations that run on Vignette, but they add WordPress to power their blog, and use SharePoint for their intranet. Managing integration and multiple (proprietary) solutions is not only costly but it acts as a roadblock to innovation and slows time to market when changes are needed.
It can be a complete mess.
CIOs are now waking up; they're realizing that the cost of running twenty different content management systems on twenty different stack configurations is an expensive, unnecessary burden for the organization. They can see that there are cost savings to be made if they standardize. What they want is something more than a content management system: they need a single platform that meets their needs. They need Drupal.
The New York Stock Exchange is launching 30 sites on Drupal. Turner Broadcasting is migrating 80 sites to Drupal. A large consumer pharmaceuticals company might end up with over 3000 Drupal sites. Why? Because Drupal gives their IT team an agile platform to deliver new sites quickly with the breadth of capabilities to meet their needs, but broad enough in scope to serve as a web platform too.
More and more, I see large organizations standardize on Drupal. Drupal's low-cost entry point and open, modular architecture provides the perfect foundation. Drupal is one of the few solutions that can scale from very small to extremely large, and has the depth and breadth of functionality to support thousands of different use cases. Drupal sites can span a wide range of functionality; from blogs, to marketing microsites, social business community sites, corporate intranets, e-commerce sites and more. There are incredible success stories for each of these use cases already. Plus, we've now reached a point where many open source content management systems outperform proprietary solutions on technical superiority and pace of innovation. Drupal is in a very unique position.
This is an immensely powerful trend. If we navigate this well, Drupal could become truly ubiquitous and go from powering 1% of the web, to quickly powering 5% of the web and even further. It requires us to keep making Drupal a better platform, to crack the code on how to make Drupal distributions truly compete with commercial point solutions, and to build out an even larger commercial ecosystem and community. Needless to say, I'm super excited about Drupal's future and the opportunity ahead of us.
Ray Ozzie, who took over the role of Chief Software Architect at Microsoft when from Bill Gates retired about five years ago, announced recently that he will be retiring soon. When Ozzie first became Chief Software Architect, he wrote a famous 5000-word internal memorandum titled, The Internet Services Disruption. The memo outlined the transformative and disruptive potential of web services.
Ozzie wrote, "The ubiquity of broadband and wireless networking has changed the nature of how people interact, and they’re increasingly drawn toward the simplicity of services and service-enabled software that ‘just works’. Businesses are increasingly considering what services-based economics of scale might do to help them reduce infrastructure costs or deploy solutions as-needed and on subscription basis.". Ozzie was spot on as this is what today's Software as a Service (SaaS) and Cloud Computer are all about.
Now, five years later, just before he is about to retire, Ozzie wrote another 5000-word memo entitled Dawn of a New Day. In this memo, Ozzie reflects on how Microsoft has been transformed over the past five years with regards to so-called 'services'. Despite many successes, Ozzie acknowledges that for the most part, Microsoft missed the boat on mobile and social software.
More importantly, he also lays out his vision of where things are going in a post-PC world: "To cope with the inherent complexity of a world of devices, a world of websites, and a world of apps and personal data that is spread across myriad devices and websites, a simple conceptual model is taking shape that brings it all together. We’re moving toward a world of 1) cloud-based continuous services that connect us all and do our bidding, and 2) appliance-like connected devices enabling us to interact with those cloud-based services."
I spent most of my evening reading both memos. It provides some unique insight about what it means to be Chief Software Architect at one of the largest software companies in the world, as well as how they see the future. In general, I agree with Ozzie's vision of the future as he explains it in his latest memo. The part on complexity also resonated with me. I think the points he makes are very relevant for most of us that make a living with Drupal. Like Ozzie, I think development of this new service-connected world will be neither fast nor easy. However, I think Drupal is uniquely qualified to play a prominent role in such a world. It requires us to make the right decisions, to manage complexity, and to stay on top of our game. Whether you like Microsoft or not, the memo is worth reading.
In the Open Source software community, there is a considerable nervousness regarding paying people to work on volunteer-driven projects. For example, Joomla recently hired some developers to work on their core software, a decision that has caused much debate in their community. At Drupal, we recently hired a temporary staff to help with the Drupal.org redesign. There is an understandable concern that the spirit of volunteerism will be lost or a volunteer project will be tainted when a paid staff is introduced. There are worries that a project's agenda will change to suit the needs of 'privateers'. However, many projects that rely completely on volunteers fall short of what can be done by a paid staff. Some projects can't afford not to make use of the benefits that a full-time, focused staff can provide.
The concept of major projects growing out of a volunteer, community-based model is not new to the world. Throughout history there are examples of pure volunteer organizations that were instrumental in the founding and formation of many projects. The first trade routes were ancient trackways which citizens later developed on their own into roads suited for wheeled vehicles in order to improve commerce. Transportation was improved for all citizens, driven by the commercial interest of some. Today, we certainly appreciate that our governments maintain the roads. However, we still see road signs stating that a particular section of a highway is kept clean and trim by volunteers -- at least in some countries. When new ground needs to be broken, it's often volunteer communities that do it. But a full-time, paid infrastructure can be necessary for the preservation and protection of what communities begin. And when new advances are to be made or gaps to be filled in, volunteers rise up within the paid infrastructure. There will always be a place for volunteers, just as there is a place for professionals.
It's quite common in the software industry that great movements are started by volunteers. While this can work quite well initially, there comes a time when a volunteer-based project becomes a threat to larger, controlled organizations (e.g., MySQL to Oracle, Linux to Microsoft). At that point, if the Open Source organization is to survive and compete, it may have to fortify its position by fostering commercial involvement that helps the project advance and compete. Red Hat is a good example. Without Red Hat, Linux might not have the strong market share it has today. It is also one of the reasons I co-founded Acquia, and why it is important that all Drupal companies contribute back to the project.
Within the Drupal project, we don't have a paid staff to advance the core software. However, many of the developers who contribute to critical parts of the Drupal code base make their living by building complex Drupal websites. Some Drupal developers are paid by customers to contribute their expertise to the Drupal project or are employed by companies 'sponsoring' Drupal development. Tens of thousands of developers are working with Drupal today, and many of them contribute back to the project. Albeit different, neither Joomla or Drupal are exclusively a volunteer run project, and that is one of the reasons we've grown so big. Ditto for WordPress that gets a lot of help from Automattic.
Volunteers rally together at times when they're needed and they play a critical role, particularly in the beginning. Without them, we would be nowhere in the Open Source software industry. Over time the maintenance and operation and in some cases the leadership are transferred to paid personnel. We have to accept into our projects those with commercial interests, without capitulating to rigid and narrow commercial interests. The commercialization of a volunteer-driven Open Source project is part of a project's natural life-cycle. While it can be a significant change, it is a great opportunity. We can reap the benefits of growth, prevent volunteer burn-out and distribute the effort.
Like all the hipster fixie kids in the hilly San Francisco, I recently bought a Citizen Messenger Bag by Chrome. I sport the black on black version. Over the last two months, as I've actively used it, I've come to conclude that this is quite possibly the best bag ever made.
Technically, the Chrome Citizen Messenger Bag is not a laptop case; it is designed by bike couriers for bike couriers. That said, I use it for my everyday activities, including business meetings, conferences, day trips, etc. It stows my laptop, my Kindle, my iPad, a notebook, a jacket, my camera, a water bottle and more. I definitely recommend this bag to anyone who likes to carry a few things around. In fact, this was the first bag big enough to hold all the schwag I got at DrupalCon -- and that means something. But if all you need to store is a laptop and a few other items, it's still a great bag as it compresses down.
As someone who travels a lot, I need a bag that can handle a lot. The Chrome Citizen bag is built like a tank; it's made from weatherproof heavy-duty 1000-denier Cordura with a weatherproof liner and sealed seams for serious protection. The shoulder strap is made of seatbelt material, which obviously makes it mighty tough. The bag is extremely durable and has proven to be waterproof, even in pouring rain. It is the first bag that I have owned that comes with a lifetime guarantee.
I'm thinking about buying the accessory pouch for quick access to my cell phone and wallet but it might be a bit small for both.
Chrome bags cost a bit more, but so far it has been worth every penny. Highly recommended!