Drupal is a 2008 Open Source CMS Award Finalist

By Amazon on 4 Sep 2008 at 02:20 UTC

Vote for Drupal as best Overall Open Source 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 www.PacktPub.com. You have the chance to support your favourite CMS by submitting a vote when the final five are announced."

Comments

Voted - Drupal boost world

Wolfflow commented 4 September 2008 at 04:23

Voted - Drupal boost world wide - Wolfflow

Contact me for drupal projects in English, German, Italian, Drupal Hosting Support.

Just voted. Drupal rocks!

seakayjay commented 4 September 2008 at 04:52

Just voted. Drupal rocks!

Voted!

vyvee commented 4 September 2008 at 06:52

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!

Voted!

dries commented 4 September 2008 at 07:30

Voted! :)

One question, the award is

dropcube commented 17 September 2008 at 19:01

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

for the project

silverwing commented 17 September 2008 at 21:13

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

~silverwing

_____________________________________________
MisguidedThoughts

I had the doubt because the

dropcube commented 17 September 2008 at 22:36

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

i usually imagine things

Feiiiiiii commented 4 September 2008 at 08:22

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

__
Piano&Rock

From Norway

Ole Martin commented 4 September 2008 at 09:16

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

Drupal i Norge - (DiN)
Ole Martin
http://www.drupal.no

Super

eric.chenchao commented 4 September 2008 at 11:02

Super! Drupal boost the world!

voted :) --- Spread Google

toma commented 4 September 2008 at 11:38

voted :)
---
Spread Google Chrome
http://www.spreadgooglechrome.com

voted! -- Pedro Faria de

pedrofaria commented 4 September 2008 at 11:41

voted!

--
Pedro Faria de Mirando Pinto
http://www.phpavancado.net - DevBlog (pt_BR)
http://www.eusouopedro.com - Blog (pt_BR)
irc://irc.freenode.org/drupal-br - IRC Help channel (pt_BR)

voted. love drupal!

danithaca commented 4 September 2008 at 11:56

voted. love drupal!

I did it ;)

duser commented 4 September 2008 at 12:33

I did it ;)

Voted :)

kecinzer commented 4 September 2008 at 13:29

Voted :)

+1 :)

kleorn commented 4 September 2008 at 13:55

+1 :)

kleorn commented 4 September 2008 at 13:58

+1 :)

Voted=)

mac_perlinski commented 4 September 2008 at 14:07

Voted

sumitk commented 4 September 2008 at 14:35

Happy to vote :)

sumit kataria
www.sumitk.net

Sumit Kataria
http://sumitk.net
http://twitter.com/sumitk

Voted

sumitk commented 4 September 2008 at 14:36

Happy to vote :)

sumit kataria
www.sumitk.net

Sumit Kataria
http://sumitk.net
http://twitter.com/sumitk

Drupal rocks!

mulogic commented 4 September 2008 at 15:32

Voted.
hope drupal wins this year too!!!

______________________
Jaanlo - The how to site

Too bad they link to that

laura s commented 4 September 2008 at 15:47

Too bad they link to that awful demo.

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

Don't just vote, Digg, too!

robertdouglass commented 4 September 2008 at 16:33

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

+3

Marc Bijl commented 5 September 2008 at 08:05

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

___________________
discover new oceans
lose sight of the shore

Dugg

BioALIEN commented 5 September 2008 at 15:40

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

---
Dee
iScene.eu :: UK Drupal Consultancy

voted and...

silverwing commented 4 September 2008 at 16:51

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

~silverwing

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

I voted for Drupal anyway

aryanto commented 4 September 2008 at 18:44

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.

The drop is always moving...

dropcube commented 4 September 2008 at 19:53

On backwards compatibility: the drop is always moving...

I read that months ago

aryanto commented 4 September 2008 at 20:49

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.

Porting modules is easier than you think...

webchick

she/they

English

Vancouver 🇨🇦

commented 4 September 2008 at 22:40

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.

http://www.lullabot.com/videocast/porting-drupal-modules

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. :)

I would really like to believe what you said its true

aryanto commented 4 September 2008 at 23:21

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 http://drupal.org/node/285087. 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 :)

wtf?

pasqualle

🇭🇺 Budapest

commented 5 September 2008 at 00:20

Drupal 7 is not released. STOP! pleeeeeeeeeeeeeeeeeeeeeeeeeeeease

Please read my post carefully

aryanto commented 5 September 2008 at 00:28

I said also about Drupal 6.4. How about that?

I did

pasqualle

🇭🇺 Budapest

commented 5 September 2008 at 00:49

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

http://drupal.org/node/217702#comment-932708
http://drupal.org/node/287203#comment-946995

No. You don't need to

aryanto commented 5 September 2008 at 01:31

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.