If a tradition is defined as something that happens once before, we have a long standing tradition of making predictions for the Drupal year ahead. This year as well, we will be looking back to see how people predicted 2006 and you can make your own predictions for Drupal in 2007.

Review of last years predictions:

  • Adrian was right when he predicted "More core developers employed full time on drupal." but wrong with a thousand Drupal distributions that will see the light.
  • silverwing was right when he predicted "There will be more then 70.0000 users. In the next couple of days we will welcome our 100.000th member!
  • Zack was spot on when he said "A major public technology corporation (Yahoo, Google, Sun, IBM) will invest directly in Drupal development." IBM contributed not in the way that anyone had foreseen but they are practically writing a book about our beloved CMS.
  • Dries was right on several points, more AJAX, the fact that other systems have grown faster in certain (smaller) markets, the growing pains and the substantial progress.
  • gtoddv was in the right direction for his "Global Warming Creation Module", close but no cigar.

Retrospective

Nobody predicted that MTV.co.uk would be running Drupal, we would have the best DrupalConference in Brussel, Rasmus speaking (briefly) about Drupal on TWIT or the amount of quality books about Drupal or a great Drupal birthday cake. And one of the most visible things, are very very good default theme for the upcoming Drupal version!

Not that many good predictions last year, you need to do better this year! The one person who won the great prize by having all predictions right was hunmonk.

End Fortuneteller Agreement:

So feel free to post your predictions for 2007. What will happen with Druplicon or Drupal core in 2007? What modules will see the light and what major sites will make the switch? It is up to you to predict how the community and the code will evolve next year and what the trends will be. This year we introduce some rules for our fortunetellers:

  1. You need to download and install Drupal 5 beta, play with it and hunt for bugs. You cant predict the future without tasting it!
  2. No jokes about Drupal in Java, RoR or any other language, that has been done extensively for many years now.
  3. Comments wont be nodes, also not in 2007.
  4. You are free to describe something that what will not happen in 2007 as well. Since this is a new tradition started by Killes.

By submitting your prediction you agree to The Rules. Let the future come!

Comments

NikLP’s picture

I suspect that after a strong showing in this year's competition, and following on from growing success and adoption of Drupal version 5, we will see this headline in the next year:

Drupal claims first prize in the 2007 Packt Open Source CMS Award!

Duplika’s picture

Indeed we will.
--
Duplika | Web Hosting

--
Web Hosting por Duplika

chx’s picture

will be held at 1127 Mainland Street, Vancouver.
--
The news is Now Public | Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

Steven’s picture

  • Drupal wins a major open-source award for all the effort put in to make Drupal more usable, without compromising its flexibility.
  • With the shiny new default theme, designers give Drupal a second chance, and start theming again. Thanks to more serious PHPTemplate improvements, theming becomes easier and more powerful, still.
  • 2007 sees the inclusion of some form of drag-and-drop blocks to the admin. Possibly reordering book pages and menu items.
  • After having upgraded the plumbing underneath Drupal.org, the site gets a serious restructuring and facelift on the outside too.
  • Someone sets up a major OpenSearch-powered search hub/service, on top of Drupal.
  • Another core committer steps up.
  • At least one more Drupal developer moves to Vancouver.
  • The Drupal Association gets significant money from big Web players who join it.
  • Dries starts a company.

:)

--
If you have a problem, please search before posting a question.

chx’s picture

Aside from Adrian and myself, you mean :)
--
The news is Now Public | Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

alexandreracine’s picture

meba’s picture

Well, i am from Prague and this is very surprising for me :-) Maybe http://www.Drupal.cz website made Drupal very popular in Czech Republic :-)

I predict that Drupal 6.0 will get Long Term Support (as Ubuntu Dapper) for updates

ontwerpwerk’s picture

  1. Still no WYSIWYG editor in drupal core, but less people will care because the "Drupal for Dummies" profile will include it.
  2. Same goes for image / asset management, because upload previews will take care of that and will be in the "Drupal for Dummies" profile too
  3. Of course "Drupal for Dummies" will be an instant hit.
  4. More pretty themes will be made for drupal, and more drupal themes will be ported to wordpress
  5. The downloads section of drupal.org will be redesigned again, with a lot of goodies like community rating of contributions, and prominently featured install profiles.
  6. Drupal.org will get more than 200.000 nodes before the 3rd quarter of 2007

--
I work for Ontwerpwerk

filiptc’s picture

  • One main drupal developer leaves the project.
  • Drupal 5 provokes a major boom of the drupal community (exponential growth does not stagnate and become linear ;-) )...
  • ...and makes it win a couple (more than one, less than four :-) ) major CMS prizes.
  • There is a module creation boom
  • An awesomely impacting new theme comes out (other than garland)
  • I will only get 4 predictions right :-p

Cherrs,
Phil

chx’s picture

During the years Drupal saw many talented people appear and disappear. Often these are not consious decisions much rather they just drift away, their dayjob requires something else etc.
--
The news is Now Public | Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

filiptc’s picture

I meant to say main drupal core developer (say one of the ten most active core developers, narrow it down if it still is too vague. One whose leaving will not go unnoticed).

Bèr Kessels’s picture

I am not giong to predict what stuff will and won't be nodes. I lost all confidence in that part ever becoming right anyway :). So here is a more general prediction:

I think Drupal will play a big part in something that will start in 2007: 'We' taking back the web from the big companies like Yahoo! and Google. The distribution of the web2.0: social web communities, but ran from our on small servers. "We" taking back our ownership of our web.

Bèr
---
Professional | Personal
| Sympal: Development and Hosting

Gunnar Langemark’s picture

We've been doing that for 5 years now!
:-)

Gunnar Langemark
http://www.langemark.com

Gunnar Langemark
http://www.langemark.com

jacauc’s picture

World Domination!!! :D

.and a way to subscribe to a thread without having to reply to it :P

jeforma’s picture

Ha, I am glad to see that Drupal is still growing strong with it's community.

I stopped developping or woreking with Drupal for a good 8 months, but now I want to get back at it with a new site I will be developping only with Drupal 5.

Hope everyone has an awesome year, and let's see these modules come out, I will be sure to make my site the best of it's kind with the help of Drupal.

(previous sites I have developped with Drupal include: myetalk, GameBGS)

jeforma - beautifying the world of humans.

jeforma - beautifying the world of humans.

ChickenStone.com - For the hardcores.

alexandreracine’s picture

Last year, I was right 1 out of 4. Let's try to make it better!

1- Bad news first. Drupal will become so popular that one of the server holding drupal.org infrastructure will not hold the pressure and will crash. (Hope you have backups)

2- There will be a module that will interface with one of Apple product. iMac .Mac ipod, iTV, etc. One of them!

3- The views module will be the most downloaded module. (Or is it already?)

4- Some major government always announcing that they will switch to Linux will actually also switch to Drupal!

5- And this extra one is for the developpers, cvs will switch to subversion (svn).

Alexandre Racine

www.salsamontreal.com La référence salsa à Montréal

piersonr’s picture

There are already lots of non-official congressional sites (i.e. campaign sites) running drupal, as well as an official US Senate site running drupal... and very possibly more to come.

The US government is switching over to Drupal, slowly but surely. ;)

ChrisKennedy’s picture

See http://groups.drupal.org/node/2156 for data on the most downloaded packages. Views is #3 for modules, after TinyMCE and Image.

Crell’s picture

Not on their public site, but the US Postal Service uses Drupal 4.6 for an internal application with about 15,000 users. I know because I built it. :-)

--
Larry Garfield
http://www.garfieldtech.com/blog

neoliminal’s picture

  • Someone creates a Texas-Holdem Module
  • A Module is created that installs other modules and makes it easy to browse modules.
  • Drupal.org is one of three major websites with Drupal Modules. The other two only have some duplicates.
  • Searching for 'drupal' on HotJobs or Monster will turn up +100X more results.
  • First Drupal Worm will spread similarly to the phpBB worm.

I must say, this Drupal thing sure is fun.

chx’s picture

First, about a Module that installs other modules -- we discussed this so many times. It's a secuirty hole to let a web application perform self modification. If such a module is written it will not be hosted on Drupal infrastructure and will be strongly advised against. Unless, of course, someone has a truly genous idea which escaped us.

A Drupal Worm is unlikely as it's not easy to google Drupal sites. yes, you can write a spider which crawls sites and checks them for Drupalness but the speed of spread would be agonizingly slow.
--
The news is Now Public | Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

neoliminal’s picture

A Module that installs other Modules... as long as you're running execs that require root (or at least 'owner') access to install I don't see how this is any different from doing it through FTP/SCP/WGET or any other way of getting the data and putting it in the right folder. What am I missing?

A drupal worm would just need to look for 192.168.0.2/node/ and if it loads that's a drupal site (99.99%) of the time.

I must say, this Drupal thing sure is fun.

zoon_unit’s picture

Why not a module that builds a non-functioning "module template" in response to some general questions? That way, security is maintained, but the neophyte module developer would have a framework for a module that used proper design principles, acted as a learning tool, and resulted in even more secure module development.

pwolanin’s picture

zoon_unit’s picture

There are so many modules, it's hard to keep up with them all. That looks like the exact solution.

Frankly, I'd love to see CCK and Views modules to become powerful enough that 50% of most module functions could be done through them. With import and export, the node and view definitions would be distributed just like modules.

scroogie’s picture

  • It will be possible to download and install modules directly from the administration UI including automatic dependency fulfillment
  • The former popular WYSIWYG editor modules will stagnate because a jQuery powered Drupal-specific solution will appear integrating / interfacing with existing modules
  • The administration interface will get a lot of ajax enhancement as drag-n-drop ordering, working without page reloads, etc.
  • drupal.org will see a lot of traffic which leads to improvements of the tracker and thread subscriptions
kreynen’s picture

An academic program that has gone Drupal wins an award and/or is profiled in an academic technology publication. Deans everywhere tell their 'webmasters' they want a Drupal.

bonobo’s picture

Yup. This one would not surprise me one bit :)

-------
http://www.funnymonkey.com
Tools for Teachers

eaton’s picture

I was a little ambitious in my 2006 predictions, but I *very nearly* nailed it with one of them: a major post-4.7 Drupal release would ship in 2006. Drupal 5 might not be released before the new year rolls around, but we all know it's darn close. ;-)

Without further ado, here are my predictions for 2007.

  1. There will NOT be a huge explosion in Drupal installation profiles. That's a good thing; profiles will take a lot of work to do well. Instead, we'll see a handful of highly targeted profiles that combine best-of-breed modules with 'glue' modules to tie them together. Profiles will also emerge as a great way for top-flight Drupal consultants to package up work for their clients in an easily maintainable format.
  2. Along the same lines, Drupal For Bloggers will be reborn as a profile, and will make setting up a Drupal blog much easier. Wordpress will continue to dominate the dedicated blogging market, however, because it's a more focused tool. Again, that's a good thing.
  3. As more sites us CCK and Views, there will be more demand for performance optimization.
  4. The community of core Drupal participants will face important choices about the project's architecture: radically rework the CRUD infrastructure? Ad a query builder? Keep things simple? Add more jQuery magic? Reducing API complexity, maintaining the readability of the core codebase, and solving underlying architectural limitations without bloating core will be the biggest challenges.
  5. Drupal will 'arrive' and no longer be seen as the hot newcomer. This will be evidenced by individuals and companies that use 'Drupal' as a resume-fodder buzzword without actually knowing how to work with it, an increase in of 'Drupal backlash' on sites like SlashDot and Digg, and blog stories by disgruntled former Drupal users. This won't be an inherently bad thing: it's what every system experiences. As Yogi Berra once said, "No one goes to that restaurant anymore: it's too busy."

Hmmmm. All my predictions sound bad, but I don't believe they are. They're all about Drupal maturing into a web platform that has its home in the real world, and that excites me. 2007 will be a great year to Drupal. ;-)

--
Lullabot! | Eaton's blog | VotingAPI discussion

bonobo’s picture

The installation profile prediction is spot on -- doing it right takes a lot of work, as "doing it right" requires thought about how to help users of an installation profile keep their sites current and secure. A small number of well maintained installation profiles will be a Good Thing.

RE performance optimization of cck and views -- the good things just keep getting better

RE CRUD: I predict that 2007 will see easily accessible, per user, node level access control.

Cheers,

Bill

-------
http://www.funnymonkey.com
Tools for Teachers

peterx’s picture

Objects will creep into Drupal. One morning you will wake up and find Drupal core being kind to objects, welcoming their arrival and making them a nice espresso. No, it is not 3007, it is 2007.

petermoulding.com/web_architect

chx’s picture

http://api.drupal.org/api/HEAD/file/oop.html
--
The news is Now Public | Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

peterx’s picture

Must be time for Dries to produce something other than Drupal releases. Time for Drupalettes. Would make great human interest story on the home page. Better use for the photo gallery than geeks at a conference. Fifty percent chance we will find drupal.org blue theme changed to pink.

petermoulding.com/web_architect

newms’s picture

I hope for rapid growth following the release of v 5.0. Hopefully there will be great development in the organic groups module and affiliated modules that will allow community sites to grow rapidly leading to more buzz for drupal.

Also I think that there will be more than 300,000 registered users by this time next year.

newms

newms’s picture

Oh and a few (more than 2) US presidential campaigns will use drupal to power their site.

newms

Moltke’s picture

I will have to join this one year, so I might as well do it now. :-)

My predictions are the following:

1.) Garland will become the most-ported theme ever.
2.) Colour pickers will become a standard feature of any future "big" theme.
3.) Future releases will be design-driven - as opposed to code-driven. Better looks and usability, same code quality.
4.) The Drupal CI will noticably change in 2007.

That's it, now looking forward to the results.

Nick Lewis’s picture

Okay, I'll take a shot:

1. A new theming engine based on drupal_render(), formapi-like #keyed arrays, and hook_elements will emerge. This advance will be a prerequisite for a powerful theme editor aimed at non-coding users. People will realize that arrays are a much more efficient and less error-prone way of expressing HTML than actual HTML tags.

2. A drupal-centric CSS framework will appear in the contributions repository -- this framework will quickly become friends with the engine mentioned in prediction 1.

3. A contributed module based on importexportapi will enabled drupal users to share, enable, and disable site configurations as though they were a module. This same advance will allow a true "undo" button that potentially works for an entire site.

4. There will be a renewed interest in functions in a features geared towards making development less time consuming.

5. Competing platforms and products will catch up to us faster than anyone expects. This will fuel a boom of innovations.

6. The formapi, module install files, and importexportapi will have a mutant child that thinks a form, its validation process, its db inserts, updates, deletes, as well as db_schemas declared in install files should not be seperated since they completely depend on each other's consistency to work. This mutant will demand a distinct "state" for a drupal site called "development".

7. Chx will continue to remain impervious to distraction.

8. O'Reilly will publish a book on drupal development.

9. A new formapi key will control, and configure jquery effects.

10. Ditto for the theming engine mentioned in 1.

11. FAPI 3 will make FAPI 2 look like the form functions in 4.6

12. I'll show signs of insanity as I work on items 1,2,3, and 6.

13. Many of these predictions won't affect the core until drupal 7.

--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.onnetworks.com

--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.zivtech.com

peterx’s picture

Internet phones, such as Wengo phone, are becoming Web phones. Pick one and make it work in a Drupal block using a phone.module. Add a phone number to registered users. Add the directory stuff to a Drupal site. Instant phone calls to any other person registered at your Web site.

I do not know which of the open source phone applications would best suit Drupal. Some were flaky last time I tried them. Some are browser resident instead of Web page resident. All will need Ajax to deliver a large phone directory search or select from a block. Drupal 5.0 with Ajax looks like a much easier base for a phone than Drupal 4.7.

petermoulding.com/web_architect

moshe weitzman’s picture

CCK will get into core. Views will not.

Comments as nodes will not be in core but will become an option for those who want it. It pretty much is there now.

Menu API will become much faster and consume less memory

We will finally get quality metrics and even even user ratings for projects

We will have selfish loudmouths on the developer mailing list

bonobo’s picture

I was thinking you were pretty prophetic until I saw your last one...

-------
http://www.funnymonkey.com
Tools for Teachers

mki’s picture

We will have selfish loudmouths on the developer mailing list

That sounds disturbing, since I posted some stories on groups.drupal.org. I am really sorry if I or someone else have caused you some fuss. But this isn't the place for such aggressive tone. Please confirm this, say it point-blank, so I can delete my own stories, now I don't do that becouse some people write comments that could be lost.

And please be patient and understanding for new community members, that are so madly fascinated by Drupal, that are forgeting oneself, but they acting in good faith.

Dollars5’s picture

1. Drupal receives a huge donation from a site/company/group that uses Drupal.

2. A huge social networking site using Drupal and more social networking modules coming in row.

3. Improved Instant Messenger (IM) modules - now they not just show our status online, instead allow you to chat with persons using a pop-up chat box. (No they are not gonna use online tools or APIS from Meebo etc)

4. Online phone module that will launch up and dial any number (may be pick a contact # from the user profile) and speak freely.

I hope Drupal will achieve more than what it is currently, wish all Success in the New year :)

Dollars 5 Solution
Mobile Software Developer

Dollars 5 Solution
Mobile Software Developer

merlinofchaos’s picture

Moshe took all of mine. I'll reiterate a view.

  • CCK will get into core. Views will not.
  • A query builder will get into core, but there will be a huge fight over it.
  • A new theme engine will absolutely revolutionize theming with drag & drop configuration and easy-to-use site sectioning.
  • The administration, which has already undergone vast transformations, will continue.
  • AJAX and JS effects will become a major part of Drupal but a core value of always-degrade-gracefully will persist, but this will come under fire from both sides.
  • New caching methods will be introduced to greatly improve Drupal's overall performance
  • New file handling and excellent media management modules will make Drupal a platform of choice for media hosting, but this will not be fully realized until 2008.
  • Dries will still be married. Steven will still not be married. [I know I'm not reaching too far with this one]
  • Toward the end of the year a sudden fear that the market is saturated with competent Drupal developers will create a scare that may cause good developers to leave or scale back for financial reasons.
  • The tracker module will go the way of the archive module.

-- Merlin

[Point the finger: Assign Blame!]
[Read my writing: ehalseymiles.com]
[Read my Coding blog: Angry Donuts]

-- Merlin

[Read my writing: ehalseymiles.com]
[Read my Coding blog: Angry Donuts]

Caleb G2’s picture

I'm currently evaluating views and am very interesting in hearing you reasons for why it would not work itself into core (even in an abbreviated form), merlinofchaos.

=====
Turnkey Drupal solutions

Bèr Kessels’s picture

As soon as Dries looks at CCK in depth he will (This is just my idea :)):
a) "demand" stripping of over 40% of its features
b) "require" a lot of code to be simplified
c) need so much testing and performance tweaking
d) have to avoid so much fuzz, "discussion"(as result of a and b) and "clutter" in the issue queues that
..I beleive this wont happen. Not in its current state, not in a state that will "look" like CCK. The "thing" that gets into core will be so different from CCK that it can hardly be called that. It will also only get in in various steps. Many various steps.

The end result will be a stripped, skimmed, clean but incompatible CCK. CCK will remain in contrib as the "more complex and powerful alternative" of the core content builder.

Bèr
--
Professional | Personal
| Sympal: Development and Hosting

eaton’s picture

..I beleive this wont happen. Not in its current state, not in a state that will "look" like CCK. The "thing" that gets into core will be so different from CCK that it can hardly be called that. It will also only get in in various steps. Many various steps.

This is something that Dries has talked about in conversations on IRC, and I think it's important. I don't think it will be *incompatible* -- there will definitely be a migration path -- but I think simplifying the process of writing CCK modules, and making it more intuitive for developers, WILL result in something that is 'CCK-Like but not exactly CCK' making it into core.

--
Lullabot! | Eaton's blog | VotingAPI discussion

Bèr Kessels’s picture

Off course there will be an upgrade path.

But: An upgrade path does not mean your own, homebrewn, form overrides, your customised field modules, and your code talking to the database will be upgraded too.
So, still there will be a lot of fuzz going on.

Take this fact: the fields modules as we see them in contribs now are HUGE. Complex. Monsters. No way that they will make it into core with this core CCK (CCCK). Practical result is a lot of work on the sides of the maintainers of these fields modules to get them either in sync with the by-then-defined-core-apis-and-hooks, or strip half of their features and complexity (and loose half of the audience).

Take datefields: CCCK will need datefields, without it, a CCCK will be pretyy useless. So we will need to look at how to do this: build a new simpledatefield.module? strip date.module to its bare minimums and leave all its current users in the cold? Or fork it and maintain two versions?
In either way, we have a lot of work to do, to keep both the power of CCK in CCCK, yet to strip the Flexibility.

The problematic part IMO is summarised with: The success of CCK lies in its great power and flexibility. That requires lots of code and complex code. In core we don't want complexity and lots of code. So we will have to strip complexity and code: result: A less powerfull and less flexible CCCK: We have stripped CCK from its success-factor

---
Professional | Personal
| Sympal: Development and Hosting

mki’s picture

1. Form generation: at present, core functions generate just forms, but this isn't connected with data type, that are entered. So developers must get everything done if we consider lend type and validation, becouse text field could mean text, number, color or everything else.

Widgets with Validation API/UI (clean validation rules) will be more efficient. In CCK approach, every field type have related widgets, for example color and color picker, and will have related validation rules, for example text and regular expresion.

2. Data processing: Developers have great support in processing they data, becouse fields can have own functions for data processing adapted to data type, for example converting RGB to hexadecimal color.

3. Database abstraction layer: at present, all modules are using SQL-jungle, instead of common business model, like nodes and fields. Situation is the same as above, data don't have defined type, so developers must do all CRUD efforts alone.

CCK have (will have) own and efficient methods for CRUD data adapted to field types.

Conclusion: In CCK we have pair: widgets and fields, that could be using as Lego blocks for input, process and CRUD all data, everywhere (not only in content, but for example auxiliary data, like settings). That's why CCK is tremendous idea, that should impact on core, not vice versa. So third possibility, that we shoud consider: "CCK way" will embed in and partly substitute above-mentioned core systems. Growth of code will be smaller, or just the opposite, it is likely that we'll lose a lot of code by this in many places of both core and additional modules.

jacauc’s picture

An easy, straightforward, no frills way of adding an image into a post will be created.
I.E. a user would be able to click browse, upload an image, and move it around in the post.
...But in a clean (not-as-clunky) interface unlike TinyMCE and it's counterparts.

...ok maybe this is more of a wish than a prediction, but let's see.

BioALIEN’s picture

Sorry guys, I've just come from the future heres what I can confirm:

1. Drupal will be html, css, sql and js preprocessed and/or cached to such a degree that if your database falls off it'll still manage to keep going (for anonymouse users at least).

2. Major reduction to the number of queries per page.

3. Significant speeds and page loads. Beating our nearest rivals in terms of performance benchmarks.

4. Drupal 6 will be released and become a record breaker opensource CMS beater with many prizes under its belt.

------------------------------
BioALIEN
Buy/Sell/Trade with other webmasters: WebMasterTrader.com

ChrisKennedy’s picture

Here are some of my 2007 predictions:

  • Poll.module will be removed from core. During Q2 most likely.
  • jQuery will become pervasive to the extent that every core module will have an accompanying .js file.
  • As a result, Drupal coding standards will be extended to apply to javascript files.
  • Sites will be automatically notified of module updates and will be able to install new versions via a web interface.
  • True i18n support will be integrated into Drupal core, including RTL languages.
  • Drupal will become E_ALL compliant.
  • The Drupal Association will be launched and will raise $100,000 for Drupal.
  • Zen will be added to core (with color.module support).
  • Drupal will add native support for DST and pre-1970 dates.
  • Drupal won't switch to SVN.
  • Drupal will add support for MSSQL and Oracle.
  • A Drupal blogging installation profile will emerge to compete with wordpress/livejournal/xanga/etc.
  • A Drupal forum profile will emerge to compete specifically with phpBB/vBulletin.
  • A Drupal mass hosting company will be created to compete with wordpress/livejournal/xanga/etc.
  • Book.module and forum.module will be removed/abstracted from core.
  • Drupal.org will double its hardware infrastructure.
  • Theme functions in core will be replaced with .theme files.
  • Drupal will gain a web-based theme editor.
  • Drupal will support ssl-logins.
  • Drupal will support WAP.
  • Groups.drupal.org will be refactored and will become an effective collaboration tool.
rport’s picture

Hi Chris.

This is amongst the best predictions yet! Thanks for spending the time!

Russ

Steven’s picture

We already use a consistent code style in our .js files. It's the same as the PHP one, except with a different variable/function naming convention, to match JavaScript's.

--
If you have a problem, please search before posting a question.

--
If you have a problem, please search before posting a question.

kbahey’s picture

What? No jokes about DruJava? Can I predict the move from CVS to SVN then? Darn. Someone else did already.

You said no "comments as nodes", but actually users as nodes is on its way to being reality (started by Ber Kessels, and Wolfgang's SoC project which became usernode), albeit outside of code.

I got two right last year, almost two. http://themes.drupal.org/ DOES finally has its DNS pointing right. http://association.drupal.org is up, and the organization is registered.

As for predictions, they are fun, but that is it. They remind me of an old woman with a head scarf gazing in tarot cards. If you see the industry pundits, they thrive on that stuff, because being wrong has no downside. The rest of the industry still listens, and being right one of out 10 predictions still pays. For example look at John Dvorak and his continued predictions.

Some of that is wishlist, some is humor, some is crystal ball gazing ...

So, here are mine:

The NOTs:
- Users as Node will NOT not be in core during 2007.

The WILLs:
- Community continues to grow, including new developers and shops jumping on the bandwagon (yeah, Mr Obvious).
- More core module will continue to evolve into being APIs (following the lead of voting api, ecommerce api, ...etc.)

Other stuff:
- The "community" will be more courteous and sensitive to newbies and outsiders, even if they are criticizing us.
- Less discussions leading to surprise decisions on the dreaded IRC (an unofficial channel).

--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

neural’s picture

- the multi-domain feature will become a multi-site feature or the possibility to run multiple sites with different content & design using the same source files and database and not having to deal with table prefixes
- users/roles will get better user information and role settings management
- access control will be improved using the code of the taxonomy access control module
- the Forums module will see major improvements
- the blog module too
- by improving CCK, drupal will allow better integration between content pages (stories or blog posts...) and the forums, allowing to display the content pages and their comments into the forums
- drupal will add scalability features, among them better multi-database support that doesn't require as much tweaking as now

These are actually half predictions and feature request :).

andremolnar’s picture

And how very good theses are... almost all hit the mark in 2006

andre

Jax’s picture

The jQuery effect will be removed from collapsible fieldsets because it is as annoying as those fade-in/out and effects in Windows. Or at least I will get an administration option to turn that off.

And don't say to turn off javascript completely because I do think it has its place, but slowly showing fieldsets is not one of them!

Steve McKenzie’s picture

i feel this is something that needs to be addressed for v5 but dunno if others feels this way.

my reasons is that currently on a fresh install of HEAD, all I've done was put all my default login and navigation blocks on the right side instead of left and i find that the collapse effect is rather buggy.. you have to hit it a few times for the effect to look smooth. On top of that, I also find the effect sometimes annoying.

with the JS side, we need to start taking advantage of Drupal.settings and have more settings in it.

I tried making the jQuery patch of a Drupal.settings.basePath but I dunno why that never made it in.

Would be cool if we had more settings like Drupal.settings.collapsibleFieldSets and it being a boolean to check if we can allow this effect.
then we could have a JS admin page to configure stuff like that.

so my prediction is a major increase in wicked jQuery stuff that is really going to put drupal over the top! w00t!

andremolnar’s picture

Digital asset management becomes a priority.
A major restaurant adopts drupal for its web site presence.
Drupal is asked for by name in ever more RFPs.
YAAPI!
The drupal icon toy hits virtual shelves.
andre

peterx’s picture

Customer: Give me a large server, a router, and a Red Hat cd.
Sales person: Do you want Drupal with that?

petermoulding.com/web_architect

mrlovecraft’s picture

- Full integration with web services, at the level of database layer, to send and receive data from external systems (expected to be bug-free by june 2008)
- Real full multilanguage support in the core, using external automatic translator services to assist the translations (integration in the core of Drupal 6)
- Improved learning curve, much more easy to create a fully functional site for a newbe, as well as the powerful already existing system.
- According to google trends, Drupal will be more relevant than Joomla: http://google.com/trends?q=drupal%2C+joomla
- Easy to install clones (themes) for major social sites (such as digg, youtube, ... and of course, blogs)
- Major CMSs' companies start to contribute with their modules
- Full integration with 'free' external services (maps, OGC, video, photos, ...)
- Module providing comprehensive license system for all content of sites(Creative commons, ...)

When all these points are achieved:
- Drupal is awarded nr 1. CMS by several online and offline media
- Drupal is studied at universities as "the CMS"
- The web evolves: the information can be accesed in our usual way (web page); all kind of gadgets can use the information provided by drupal sites (thanks to the use of web services); servers comunicate between each other to transfer information by web services in a completely cooperative new way.

Jaza’s picture

  1. Drupal developers will feel 'interfaced out' after all the work that they put into usability and UI improvements back in 2006. The first half of 2007 will consist of long hours that are spent staring at the Garland theme (and the new jQuery effects, and the color picker, and the new admin front page) in loving admiration. The second half of 2007 will be spent coming to terms with the fact that the UI hasn't been improved since 2006 (gasp!).
  2. One new contrib module will emerge as the 'must have' module for 6.0 (at least one - maybe more). This module will be another one that — like its predecessor 'must have' modules, Views and CCK — will be incredibly versatile / extensible / themable / swiss-army-like, and will instantly make another 5 existing core modules redundant.
  3. With the rise of install profiles, there will be a growing demand to reduce Drupal core to a developer framework, to move all the extra cruft to the default install profile, and to split the default install profile off into a completely separate project (with a separate name). "That's how it is with Zope and Plone; that's how it is with RoR and Typo; that's how it should be with Drupal", people will say. The core committers will reduce core a bit, but not nearly as much as many developers will want them to. The 'default install profile as separate project' thing will most likely not eventuate.
  4. The menu system will suck a lot less than it does now.
  5. There will be less hooks in core, and more callback mechanisms.
  6. People will try to build really rich AJAX apps (e.g. Gmail-like apps) using Drupal, and in the process, will cause Drupal's AJAX support to rapidly mature and blossom. For example, AJAX-based dynamic loading of page elements ( currently in the dynamicload module in the jstools contrib package) will hit core.
  7. A simple relationship API will get into core, and will allow modules to easily provide their functionality to all entities within Drupal, rather than just (for example) to nodes. E.g., taxonomy will let you tag not just nodes, but also users, comments, CCK fields, etc. Similarly, you will be able to comment on users, on views, on files, etc.
  8. FAPI3 will be very cool, but it won't quite qualify as an "everything API".
  9. Drupal Buytaert will be born.
  10. Everyone else will have to make these predictions come true, because I won't be around to do so: I'll be on vacation for most of 2007! :-)

Jeremy Epstein - GreenAsh

Jeremy Epstein - GreenAsh

Bahattee’s picture

  • Drupal.org will get a new look
  • Drupal will be second at CMS awards ... Joomla will win again
  • One of the main developers will leave the team
  • Drupal will have something with Microsoft
  • Drupal 7.0 will be released
Robert Castelo’s picture

  1. Drupal is used more for non-HTML applications
    email, SMS, VOIP, and sector applications that define their own DTDs
  2. Jakob Nielsen, Edward R. Tufte, and Donald A. Norman start using Drupal, usability goes through the roof
  3. teddy_bear.module is released, someone is distracted

Cortext Communications
Drupal Themes & Modules

------------------------------------------
Drupal Specialists: Consulting, Development & Training

Robert Castelo, CTO
Code Positive
London, United Kingdom
----

mohammed76’s picture

I have to say that I am both wishful and fearful for what the future holds for our beloved Drupal:

  • although I hope that "True i18n support will be integrated into Drupal core, including RTL languages", I think this won't be done during this year, however, one of the contributed related modules will improve drastically.
  • drupal.org will undergo some serious improvements mainly in terms of functionality, like the ability to subscribe to nodes without having to comment on them, :)
  • I am worried for the future of accessibility of drupal especially if "AJAX and JS effects will become a major part of Drupal".
  • forum.module, or a similar contributed module, will surely recieve some attention this year.
  • more awards and adobtion will be granted to Drupal, (the project)

Mohammed al-shar'

Nattiq Technologies

Mohammed al-shar'

The Explorer

deathgod’s picture

Drupal will not be renamed to "lapurd", other than that one prediction, I have no idea ?_?
------------------------------
Naruto - narutomonkey.net - Naruto Forums

engelsol’s picture

1)
Drupal will be in the the 2007 EContent 100 List.

2006 list is here:
http://www.econtentmag.com/Articles/ArticleReader.aspx?ArticleID=18642

Typo3, eZ systems and WordPress are listed for the 2006 list.
Plone, a Python CMS is in the list.
Liferay and Alfresco two other Java Open Source system are also listed.

Engel Sanchez
Solunion Group

Engel Sanchez
Solunion Group

Chill35’s picture

Drupal wins a major open-source award for all the effort put in to make Drupal more usable, without compromising its complexity -- yes Steven. (Although you said "flexibility" instead of "complexity").

"With the shiny new default theme, designers give Drupal a second chance, and start theming again. Thanks to more serious PHPTemplate improvements, theming becomes easier and more powerful" -- yes, that will happen. I can "feel" it.

The publication of a book makes themeing easier to understand. That book includes a long reference section that presents the Drupal API – that part is also made available through download as pdf on Drupal.org for free.

Still no WYSIWYG editor in drupal core. However, someone contributes a module that does not rely on a third-party editor. The contributed module is simple, makes good use of W3C DOM scripting, and it becomes a hit.

Simple insertion of images in nodes is made possible by a few, very good contributed modules. Still Drupalers refuse to put it in core despite all the complaining.

The views module will still be the most downloaded module. (It already is, right ?)

"Drupal For Bloggers will be reborn as a profile, and will make setting up a Drupal blog much easier. Wordpress will continue to dominate the dedicated blogging market, however, because it's a more focused tool. Again, that's a good thing." – Eaton, yes.

"Drupal will 'arrive' and no longer be seen as the hot newcomer. This will be evidenced by individuals and companies that use 'Drupal' as a resume-fodder buzzword without actually knowing how to work with it, an increase in of 'Drupal backlash' on sites like SlashDot and Digg, and blog stories by disgruntled former Drupal users. This won't be an inherently bad thing: it's what every system experiences. As Yogi Berra once said, "No one goes to that restaurant anymore: it's too busy."" – Eaton, double yes.

Garland will NOT be popular (people will go "ahhhh" but not many will use it.)

Colour pickers will become a standard feature of any future "big" theme. -- yes, Motlke.

O'Reilly will publish a book on drupal development. – Lewis, yes.

Drupal will become E_ALL compliant in 2007, yes ChrisKennedy !!! Oh yes!

According to google trends, Drupal will be still be less relevant than Joomla. However…

YES, Drupal is studied at universities as "the CMS" – LoveCraft, you've got it.

Searching for 'drupal' on HotJobs or Monster will turn up +100X more results. – Neoliminal, you've got that right.

4 people will romantically hook up with other 4 people because of Drupal.org.

That's about all I am seeing for now.

Caroline

Caroline
11 heavens.com

ChrisKennedy’s picture

Nice post :)

Views is the third most popular module, based on October download statistics (the most recent), after TinyMCE and Image. After Views come cck, Event, Gallery, AcidFree, Ecommerce, IMCE, and finally Pathauto as #10. More info on the top 30 packages, and a chart I made, is at http://groups.drupal.org/node/2156.

Dries’s picture

Only one prediction this year, see http://buytaert.net/drupal-predictions-for-2007 :

"There are many million websites out there. But by the end of 2007, if you take 1,000 random websites, at least 3 of them will run Drupal. Spam sites and pornographic websites must be excluded from any such experiment."

(A review of last year's predictions can be found at http://buytaert.net/evalutaing-my-drupal-predictions-for-2006.)

tcblack’s picture

sparr’s picture

Views and/or CCK will become core modules.

I got nothing else, since I am new around here.

GiorgosK’s picture

1. The drupal.org site will setup up a donors page with direct links to the donors sites similar to http://moodle.org/donations/ and money will start coming in since lots of companies (and individuals) will like to have a link from drupal.

2. Internationalization and multilingual support would be a core feature (or at least would be a breeze to install in a module)

3. Modules will be able to detect newer versions and autoupdate with a push of a button from the admin

world experts tag cloud

Bèr Kessels’s picture

3. has been discussed many times on all sorts of places. Bottomline is: It is technically impossible to do without opening up critical security holes. This lies in the nature of the server, and PHP. So even if people code something up (should not be hard, even), Drupal should (and Will, I am certain) advice no-one to use that: you will bring your site and your server into danger. Summarised: Allowing a web-application to write its own code is just insane.

However, I have spent the last year working/reviewing and maintaining several solutions such as debian-alike apt-get installations, or module installation from commandlines. This does not allow you to install code from within Drupal, but from external applications.

info about sympal scripts
the apt-get alike module installers
the project itself

This can be tied to environments like plesk or webmin. The latter is what I am working on right now for a new hosting startup.

Bèr
---
Professional | Personal
| Sympal: Development and Hosting

filiptc’s picture

Newest version of gallery just included feature 3. Did they overcome the security holes or just ignored them?

Phil

Bèr Kessels’s picture

But I scannedt he code and the docs just now: my conclusion: your webserver is a wide open , shooting duck if these module installs work.

It is very simple: if your web-application can (re)write itself as result of a command given from that web, that means that your application is not secure.

This does not mean that gallery2.2 is insecure right now. But it means that you have to configure your server in such a way, that if someone hijacks your site (because of some other minor security hole, or just a mistake by you) they have ALL the rights they want: after all, you can rewrite the application to be some monster.

If you read http://codex.gallery2.org/index.php/Gallery2:Security#Restricting_the_Ri... it shows that they do have a good gripe about the permissions. And It is impossible that gallery2 can write new code to the modules/ directory if gallery2 has only Read+Execute permissions there! So my gripe is that, if you follow these instructions, your module installer won't work. Wich means you have a secure installation!

---
Professional | Personal

GiorgosK’s picture

Thanks for clearing that up Ber,
------
world experts tag cloud

kbahey’s picture

For #1, some of that exists, but was not very visible. I added a direct link from the "Contribute" tab to the donation page.

You can see the latest donations to Drupal here.

There are links to the user page on Drupal.org, provided the donations is made using the same email address. From there there may be a link to the user's web site, so one more click.

Your idea is quite good though. Please file a request for it like this one http://drupal.org/node/105306 (under Drupal.org maintenance).
--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

GiorgosK’s picture

about that page,

my 2 cents on it (probably not the place to discuss it ... )

1)companies want a direct link to their website with high PR if possible.
2)the names of donor dissapear after a while from the page. right ?

--------------------------------------------------------------
world experts tag cloud

kbahey’s picture

Yes, your points are valid.

Opening an issue about it will prevent this info from getting lost in the forums in the next months.
--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

bertboerland’s picture

my rants on myblog feel free to comment either there or here

--
bert boerland

--
groets
bert boerland

peteThomas’s picture

-- Drupal collaboration with the 'NGO in a box' project grows, benefitting from Drupal forks into NGO all-round functionality
(à-la-carte cookbooks, focused distros of contrib+core modules)
http://openpublishing.ngoinabox.org/toolpage/1/6

-- a Europe-based Drupal-focused development company launches (as opposed to a web boutique), benefitting from Venture Capital

-- a Drupal site for language-learning and computational linguistics launches

bertboerland’s picture

an european bryght/lullabot is bound to happen

see also the icecream

--
groets
bert boerland

peteThomas’s picture

Once you have a business plan, let me know if you need me to put you in touch with VCs.

-- I'd focus on getting about 50K kick-off capital (friends/family who can add business value... never bank... I'm sure the more monied among us on Drupal.org would be willing to chance 5-20K).
-- Use this to get a few talented people working for shares or at 25% time for a few months (include a start-up strategist and salesperson, not just techs), with the explicit aim of getting 1-2 million euros in seed capital from a suitable VC.
-- From there, start thinking like a real startup... the physical stuff (offices), VCs, potential exit phases, etc.

Packaged Drupal consulting would seem to have strong sales targets in the following areas:
---> piggyback projects for system integrators (subcontracting for the larger companies);
---> the corporate intranet market -- particularly in the clusters of HQs in the 'Benelux diamond' (Amsterdam-Cologne-Lux-Lille-Bru)
---> local government projects (info campaigns, education, tourism) with a budget of 20-250K;
---> web communities linked to R&D projects with a budget of 1m-20m, in particular any Europe-wide research projects under the 7th Framework

egawater’s picture

Hopefully drupal will continute to provide an awesome blogging platform. Hopefully add some better support for Atom feeds tho.

--
Eric Gawater's Blog - http://www.pro-article.com

george simon’s picture

While I agree slightly that it will continue to provide an awesome blogging platform, I think the support for the atom feeds is already fine and needs no improvement. but that is just my opinion.

---
My Personal Paid Survey Blog - Companies spend millions every year to find out what customers want, take paid surveys and get your piece of the pie.

My Personal Paid Survey Blog - Companies spend millions every year to find out what customers want, take paid surveys and get your piece of the pie.

jhriss’s picture

What I would really truly love, and believe me it would be awesome, is for someone to create some sort of program for updating data bases on linux based servers so that the next time I go to update to a new drupal or wordpress platform I don't have to pay some nerd $100 to do it for me cause it's so dang difficult! So, yeah, I left wordpress in the dust, and Drupal is rad, I wish you luck and look forward to using some atom feeds.