Vote for Drupal as best Overall Open Source CMS

Vote for Drupal as best PHP CMS

Last year Drupal won 2007 Best Overall Open Source CMS. That was before we released Drupal 6.

This year, Drupal 6 was nominated for best CMS in two categories. Please help us by voting for Drupal in both of them:

"Following six weeks of intense voting, Packt can now exclusively reveal the Content Management Systems that have made the final of the four different categories. With the final voting stage opening on September 1, the competition is likely to be strong with new CMS's joining some of the more established names in each category to compete for a share of the $20,000 prize money."

"As usual, judging comes from a panel of experienced and respected figures from the Content Management and Open Source industry. They will be selecting their top three based on a number of factors including performance, usability, accessibility, ease of configuration and customization, scalability and security.

The final judge is made up of votes from customers and visitors to You have the chance to support your favourite CMS by submitting a vote when the final five are announced."


Wolfflow’s picture

Voted - Drupal boost world wide - Wolfflow

Contact me for drupal projects in English, German, Italian, Portuguese and Drupal Hosting support.

kuanjian’s picture

Just voted. Drupal rocks!

vyvee’s picture

Voted! I have studied several CMS systems before, and decided to use Drupal. I have used Drupal for 2 years and it's still the best!

Dries’s picture

Voted! :)

dropcube’s picture

One question, the award is for Drupal as a whole, or Drupal 6.x as a CMS release?

silverwing’s picture

it's for the project as a whole and not any specific release.



dropcube’s picture

I had the doubt because the post says:

This year, Drupal 6 was nominated for best CMS in two categories. Please help us by voting for Drupal in both of them

Feiiiiiii’s picture

i usually imagine things like this.."you wanna high votes? hey,come to china. we have plenty of people."
just a joke.
drupal rocks!


Ole Martin’s picture

Like I always do, I voted again, twice.
Go Drupal, go!!!

Drupal i Norge - (DiN)
Ole Martin

eric.chenchao’s picture

Super! Drupal boost the world!

toma’s picture

voted :)
Spread Google Chrome

pedrofaria’s picture


Pedro Faria de Mirando Pinto - DevBlog (pt_BR) - Blog (pt_BR)
irc:// - IRC Help channel (pt_BR)

danithaca’s picture

voted. love drupal!

duser’s picture

I did it ;)

kecinzer’s picture

Voted :)

kleorn’s picture

+1 :)

kleorn’s picture

+1 :)

mac_perlinski’s picture


sumitk’s picture

Happy to vote :)

sumit kataria

sumitk’s picture

Happy to vote :)

sumit kataria

mulogic’s picture

hope drupal wins this year too!!!

Jaanlo - The how to site

laura s’s picture

Too bad they link to that awful demo.

_____ ____ ___ __ _ _
Laura Scott :: design » blog » tweet

robertDouglass’s picture

Our days of easy Digg front pages are over. We have to do more work now, but this is definitely worth it. Use the Digg link please.

- Robert Douglass

my Drupal book

my Drupal book | Twitter | Director, Product Operations Commerce Guys

Marc Bijl’s picture

1. Voted!
2. Voted!
3. Dugg!

discover new oceans
lose sight of the shore

BioALIEN’s picture

Dugg, you think we can get this to the digg frontpage? Lets try!

Dee :: UK Drupal Consultancy

silverwing’s picture

a bit surprised that wordpress wasn't there... (and Xoops was.) Time's are a-changin'!


zinzinny - more than tv (alpha)| MisguidedThoughts | showcaseCMS

aryanto’s picture

Even though I disagree with the strategy to ignore backward compatibility with old releases, I voted for it anyway.

What I said about ignoring backward compatibility is, every time new version of Drupal being released, all modules have to be upgraded to be able to work with the new version. This is really unnecessary double work, which most module maintainers do not want to do. In the end, it takes months before all modules support the new version.

aryanto’s picture

I read that in March before I decided to use Drupal, after trying a lot of CMS'. I also read Dries' blog, along with the discussion there. I didn't want to bring up the same discussion, but I just would like to express my opinion on this.

I totally agree with the idea of always getting at the top notch of technology. But that should not mean breaking the support of previous versions, particularly the old versions' API. If the users want to upgrade to the new version, all APIs from the old versions should just work in the new versions. That would make very little effort in upgrading the old version's modules. But all new features in the new versions should not be backported to the old ones, as that also means double works.

I am not a software programmer so I am not sure how to implement that. But I think there must be a way to workaround that as it is just a piece of software. Maybe that can be done by implementing a "compatibility interface" or something like that. So API’s that are not supported by the new version can be managed via that interface. Of course, performance will be affected. But at least that will provide the choice to the users to use new features and also still use the old version’s modules. And that will also make the module maintainers more relax.

webchick’s picture

Even if you're not a programmer. If you can copy/paste PHP around, you can often get a good chunk of the way there yourself.

Maintaining a backwards-compatibility layer, however is a) (at least) double the maintenance work, b) incurs a performance overhead, c) extremely error-prone, and d) often times simply impossible. Most changes are not as simple as "rename function_a() to function_b()" and in fact result in huge underlying changes with many benefits that would be lost if we were doing things twice.

So my suggestion: help chip in and port the modules you want to see ported. For the vast majority of modules, it's relatively quick and easy, and helps get you more familiar with the code so you can make the leap to creating your own modules one day. :)

aryanto’s picture

I don't think what you said is entirely true. To give you an overview about my understanding of Drupal, my comment is actually coming from my frustrations which I wrote in So yes, I did try porting some modules without success. Maybe I am a complete idiot :)

If porting old version's modules is piece of cake, why there is only a few modules ported to Drupal 7 even it was first released more than a year ago (2nd of July 2007)? In fact until now, there is practically no usable modules in Drupal 7 for the end users, a part from development related modules. If you said, Drupal 7 is not the stable release, let's talk about Drupal 6.4 then. Why there are a lot of people still asking when this or that modules will be ported to Drupal 6.x? The module maintainers can definitely do more than just copy and paste, so they should be able to upgrade their modules in a split second, if what you said is true. But in reality, it is not like that.

My suggestion is actually to create entirely new separate interface in the new version, to manage the backward compatibility. But as I said, I am not a software programmer so I don’t know how to make it happen. If I could I will definitely create my own CMS or at least fork Drupal :)

Pasqualle’s picture

Drupal 7 is not released. STOP! pleeeeeeeeeeeeeeeeeeeeeeeeeeeease

aryanto’s picture

I said also about Drupal 6.4. How about that?

Pasqualle’s picture

but you want me to answer the same question every month. My answer is still: NO

aryanto’s picture

I am just explaining the fact based on what webchick said. The fact is, it is not easy to port the old version's modules to the new version, even for the experience PHP programmers as they can not even do that in short period of time, e.g. in a month.

You don't need to answer the same question every month. Actually, you don't even need to answer such of these questions. I am not sure with the other who raised the same questions, but for me I am hoping that somebody or a group of programmers with different view (instead of just sticking to the word: "no backward compatibility") will say: "OK, maybe that is not a bad idea. I know how that should be done, but I don't have time. So let's do that together". After all, collaboration is the key word in FOSS.

dropcube’s picture

Please, continue this discussion in the other threads dedicated to that. I don't think this is the right place to discuss about that.

aryanto’s picture

I stop that.

dropcube’s picture

Voted and Dugg!’s picture

Voted, and calling a dozen of friends to vote.
"Design Professionals Community"

gloscon’s picture

Voted for Drupal!

Next year I hope to see some Ruby on Rails based contenders!
Gloscon Solutions Inc

pivica’s picture

Exar’s picture

Possibly the worst documented open-source contribution in the history of the Intranet! Takes time to learn, but when you get it to work, it does work well!! Liking it! Voted!

SunnyBlack’s picture

Voted! i think that drupal have to win :D
lets go for the win *katsching*


gj23488313’s picture

Jusrt Voted!


My Drupal Site:

freedguy’s picture

Go Drupal Go...........!!!’s picture


Go Drupal - Go!

Kenneth,’s picture

Drupal FTW!

giorgio79’s picture

amedjones’s picture

voted :), hope you win drupal

giozdemir’s picture

voted! i hope drupal will win again.

mrbert’s picture

skimmerboi’s picture

voted.. drupal f***in' rocks..!!

betz’s picture

Guess what ... I voted :)

duntuk’s picture

voted... thanks drupal.

sudhirpatel’s picture

Voted :-)

Last time there were too many people who digged this - lets hope Drupal wins this time.


vkr11’s picture

John27’s picture

Voted for the BEST!

mimosa2002’s picture

Just voted! Hopefully, it isn't too late!

betz’s picture

the voting is already finished.
Drupal won!!!

Have a look at