Drupal.com refresh launched
Back in March 2008, I blogged about a much-needed redesign soon to be deployed onto Drupal.com, to replace the oh-so-embarrassing placeholder page I've had there for years. I'm happy to announce that -- thanks in large measure to the great design and development work of the good folks at Development Seed -- the new and much improved Drupal.com has been launched.
The old Drupal.com site had always just been a way to protect our Drupal identity and direct folks to our true home at drupal.org. Over the years, I'd never put much thought into that site. Drupal's adoption has grown, however, and so has the traffic to Drupal.com – mostly from people typing that address directly into their browser. At 30,000 unique visitors a month, too many people see it for it to have remained its old simple self, but I still wanted a way to protect our identity and direct folks to Drupal.org.
The new site design does just that. First, it serves as a spotlight for Drupal and the Drupal community. Second, it continues to drive traffic to Drupal.org, the Drupal Planet, and groups.drupal.org. And, third, it protects our identity in two ways: when published, the Drupal.com trademark page will serve as the official repository of the Drupal trademark policy (and also generate some much-needed revenue from site ads to defray some of the licensing and trademark expenses that I am responsible for personally). Publishing the trademark policy is next on my TODO list (I'm currently incorporating some last feedback from Larry Garfield) and launching the ads will follow thereafter (more details to come).
As always, and as with any fresh launch of a new site, comments and suggestions are always welcome. Feel free to leave them here, attached to this post. I'll continue to add and tweak the the site over time, and I welcome your input.
The old Drupal.com design that we have had for years.
The new Drupal.com design that we plan to launch shortly.
On Drupal certification programs
Every once in a while, the discussion of Drupal cerification comes up. Is a Drupal certification program a good thing or a bad thing? Are certification programs overrated? Isn't one's track record as a contributor on drupal.org the best measure of someone's past (and possibly future) performance? Should the Drupal Association manage the program, and if not, then who? What do other Open Source projects do?
Lots of unknowns and lots of subjective questions always make for a good discussion.
While I'm often skeptical about certification programs myself, I do see the value in them. Certification isn't for everyone but for some people it is valuable. A masters degree from MIT, an MBA from Harvard or a Ph.D. from Stanford is a form of certification too. But, just as there are good examples, there is no lack of examples where bad certification programs deliver certified engineers that don't know what they are actually doing. That fact, though, doesn't invalidate the valuable certification programs that do exist; for example, the CISCO certification program is very thorough and valued by the market. Similarly, I think that employers do value certificates achieved in higher education. All things considered, I believe there is value in having a well-executed high-quality Drupal certification program, especially as Drupal continues to grow.
My personal view is that the Drupal Association is not the best body to create "the" Drupal certification program. It is my belief that we are best served by allowing many organizations to create their own Drupal certification programs, and have the marketplace set their value -- similar to how universities build reputations. Competition around Drupal certification programs could be a great thing, because it would likely improve quality and allow for specialization. A certification, of course, is ultimately only as valuable as the organization standing behind it. In such a scenario, it is very important that the certification programs are labeled properly; that is, "ACME Drupal certified" rather than just "Drupal certified", where ACME is the name of the company or organization providing the service. It has to be ACME's reputation that is on the line for the quality of their participants. The Drupal trademark policy is designed to help achieve that.
I also don't believe that a certification program is a zero-sum game: that is, holding a certification doesn't imply that your track record on drupal.org (through your user profile) is of either less or more value. Again, the market and the buyer will determine the value of a drupal.org user profile versus a certification program versus a resume versus a portfolio versus degrees obtained through higher education. In any event, it is unlikely that one would hire someone solely on the basis of having a Drupal certification. I certainly wouldn't.
When we launched Acquia two years ago, we announced a Drupal certification program code named 'Yellow Jersey'. That program hasn't materialized yet, and we're not putting resources in it at this point in time. Building a high-quality certification program is a significant undertaking and we're not ready to take on such a program. And last but not least, the marketplace hasn't demanded these types of programs to a sufficient degree. Yet.
Other Open Source projects like MySQL, Zend, Linux, Ubuntu, RedHat, BSD all have certification programs so I think it is a matter of time before we see one or more Drupal certification programs emerge. Personally, I would support a well-executed high-quality Drupal certification program.
Acquia adds 200 new customers in six months
I've posted a good bit about Acquia lately, because we had a lot of exciting things happening, and because I'm proud of the body of work that the Acquia team is producing, often in close cooperation with the Drupal community.
Still, a lot of people ask me how Acquia is doing and whether the support business model is working. In this post, and in an accompanying press release, I want to provide some additional insight in the state of Acquia's support business model.
As you might remember, Acquia opened for business in October 2008, less than one year ago. In less than one year, Acquia now supports over 250 enterprise customers across a wide variety of markets. In the last six months, we've quadrupled our customer base and now help support open-source solutions in places where proprietary software once predominated. Places like The Economist, Intuit, WEEI, Sony Music, Adobe and more.
The reality is that with less than one year into the Drupal support business, it is too early for us to tell if the support business model will be viable for Drupal. We need many more customers before we've built a scalable business; however, the early signs are good and beat our expectations.
Acquia has grown substantially from its beginnings less than two years ago, and since opening its doors for business less than one year ago. The road to making Acquia a successful company is still long but I'm very excited about what we have accomplished to date, and where Acquia is heading with its new products and services.
Mollom for Laconica
Laconica, billed as an open-source microblogging tool similar to Twitter or Jaiku, now has its own Mollom plugin to reduce comment and posting spam. Laconica is designed to allow people in a community, company or group to exchange short messages of 140 characters or less, over the web. The Mollom plugin for Laconica is available at http://gitorious.org/laconica-mollom-plugin/mainline/trees/master, and is written in PHP.
IIS module for Mollom
Zion Security, a Belgium-based company specializing in the security analysis of web sites and systems, has used Mollom's open API to develop a Microsoft IIS module utilizing Mollom to detect and prevent comment and posting spam.
This module is unique in that it is a HTTP module coded for Microsoft IIS, comparable to an Apache module, and allows Mollom to potentially expand to a number of ASP/IIS based systems.
The Mollom IIS module is available as a zipped file for download here and is listed on our downloads page. It checks any submitted form for spam using Mollom's spam detection analysis, and like other Mollom plugins, requires you to obtain a set of registration keys from mollom.com before it can be actively used to protect your ASP-based forms.
Because it is written as a module at the webserver layer, it may be possible to use Mollom's spam-detection and CAPTCHA challenge ability with existing web applications running on IIS (think SharePoint or DotNetNuke). It's an interesting approach and one we haven't really considered ourselves. It will be interesting to see how this develops, and if it sticks.
Internet Systems Consortium using Drupal
Internet Systems Consortium, also known as ISC, is using Drupal on their website at http://isc.org. ISC was founded by three internet pioneers Rick Adams, Carl Malamud and Paul Vixie to support BIND and other software that helps power the internet. ISC also operates one of the 13 root name servers. Pretty cool and a testament to Drupal!
