Personal battle plans for Drupal 6

I'm working towards integration of (a portion of) the workflow module into core. At least, ending the status column's reign of terror and replacing it with a flexible workflow. The UI will probably remain in contrib.

After I get workflow to at least 5.0 compatability, I'd like to help strip down the query builder in views and make that a core .inc. I've been writing modules that rely on views, and I can see some areas that need to be decoupled from the views front end.

If CCK fields get into core, I will happily work to rewrite more things as fields (my first target would be taxonomy).

Cheers
-M
--
http://www.advantagelabs.com

Rework the menu system (underway), rehaul the path system, better ordering of hooks, better dependency handling. Probably a tree API with some form of materialized path to make it faster. Splitting up modules into module and include files. Lend a hand on the template patch and data API. I am pretty sure some more ideas will come to me as we on.
--
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.

I'm going to work on creating and including one or more additional install profiles that ship with core. Perhaps a single user "blogger" one as well as a multi-user "community" type one.

--
The future is Bryght.

I would like to make the search system more modular. In particular, I like the extensibility of the search system and the interface that is open to modules, but I want to decouple its dependency on the Drupal-built search index. I would then like to provide a Lucene based index as a potential replacement (as a contrib module).

- Robert Douglass

-----
Lullabot | My Drupal book | My Digg RSS feed

I'll continue to work on caching and general performance improvements. Together with chx' menu work I want Drupal 6 to be the fastest Drupal ever.

--
Drupal services
My Drupal services

I plan to help make the 'cck fields in core' thing become real (and keeping most of the current cck fields features). Not sure I'll be able to initiate this, though :-)

I've also started to work on an api that would generalize the 'progressbar' operations provided in update.php, and allow modules to tackle potentially time-consuming operations (mass update, mass delete...) without dreading php timeout. "Progressive operations", "batch operations", not settled on a name yet. This will probably start in contrib, but would ideally reside in core to allow other modules to confidently rely on it.

We'll going to translate Drupal 5 to Calatalan, but we'll end the Drupal 4.7 translation first ;-)

It's much longer than I can actually get to, but these are all of the things that I want to work on, or am currently working on.

• views_query -- I want to extract the views_query object and submit it to core as query.inc.
• go through each block and theme -- I believe there are still blocks in Drupal that have too much hardcoded output; I want to spend some time pulling these into theme functions. This leads to:
• help with making it easier to turn theme functions into templates. Possibly go through every theme function in core and provide a template pack, that has distilled the theme function into code (in a template-functioname.php) and a functionname.tpl.php). People theming a site could then simply go through this list, enable the ones they want (include them in their template.php) and start modifying. -- This is a group project, and my current thinking is that I want to pitch it to the Drupal Dojo as a great way to get something AND teach a lot of people about theme functions.
• I want to ajax/js the menu config -- I'm pretty sure this one is going to fall off my TODO list for lack of time.
• I want to submit dhtml_menu module for core
• I want to spend some time evaluating the Drupal API for consistency.
• I want to work on finding a way to better document form api via api.module.
• I want to submit a patch to node_feed so views can use it instead of its own copy of the function
• (small patch) remove ancient use of hook_content from book.module
• I want to redo the permissions (access control) screen that's not quite so unwieldy
• I want to add per user permission support. This looks pretty easy and I think I can do the first patch in an evening.
• I want to write a 'lj-cut' syntax module (If you're familiar with livejournal, it's basically a way of using markup to cut specific chunks out of the body for the teaser, rather than a simple break.
• Submit the theme imagebutton in core -- I have like 3 modules that use it.
• The node access system needs configurable node access priorities, with and/or logic so that site admins have finer control over how multiple node access modules interact.
• add the 'fields' op back to nodeapi -- I've reversed my position about modules not modifying the 'node' table, and believe this op should return.
• I want to patch in this function: node_url($node) { $url = node_invoke($node, 'url'); if (!$url) { return "node/$node->nid"; } }
• I want to patch so that comment threading options should be per node type, not global

Additionally, I'm working on Panels 2 (see the entry on my angry donuts blog) and I've got some plans for Views 2. At this point I'm thinking that work on Views 2 will probably start around summer, and I am trying to work on an advanced forum module too, but am kind of hoping someone else will get to that before I do.

We'll see how much of that I can get through. Some of them are much easier than others!

-- Merlin

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

Not all administrators want to do PHP or even to create new module. I believe Dript has a capability to extend any Drupal installation from the outside. Currently Dript can manipulate CCK field well to even make any field a calculated field. I'm planning for Dript to do theming and web service interfacing. Dript is also open for other modules to make use of it. In fact any developer can add more functions to Dript. I will write more documentation.

At the same time I will do Malay translation. I'm already half way through.

FormAPI improvements: More consistency, more clarity, more simplicity
The last two revisions of Drupal have seen major improvements in Forms handling (obviously). It's time for us to focus on cleaning up inconsistent and baffling parts of the API, smooth out rough spots, and so on. Several patches are already in the queue to accomplish those things. #111079 and #81308 are two examples of how that can be done.

CCK Fields in core
This also means finding ways to simplify the process of writing CCK stuff. The mental model for developers is still pretty complex, but the challenge isn't insurmountable.

Leverage shared structures and APIs more: Consistency and clarity again!
5.0's drupal_render() function is the first example of an awesome shared function that can simplify life for developers. As we begin to develop consistent ways of working with lots of data in Drupal, and doing various system tasks like CRUD and so on, cleaning up and merging almost-exactly-the-same APIs will bring major gains. #110888, #79684 and #79227 are all excellent examples of that stuff in progress.

Improve content rendering
Building node bodies improved dramatically in Drupal 5 from a flexibility standpoint, but it's still only halfway there. Decoupling comment.module from node.module, enabling intelligent rendering in a variety of formats (print-friendly, atom, rss, plain html, json, etc.), and solving a couple of other thorny problems will all help a lot. The way that CCK module now handles separate teasers and full nodes hints at what I hope to bring to all output styles.

Iterative improvements to PHPTemplate
Our theming system is tremendously powerful. There are still a number of really tricky bits, though, especially when you start pushing the high end. Mapping theme functions to tpl.php files -- in particular, modules exposing 'default, easily hackable' tpl.php files -- would be a huge gain. Also, paving the way for 'pure css' themes is low-hanging fruit. #89602 is a start to the process; with .info files we could capture things like theme/module dependencies and capture description text as well.

Non-core profiles.
if I have any time left after that fun, I want to look at getting a couple of targeted profiles (Drupal for Webcomics, and a resurrected Drupal For Bloggers) would be awesome. Building support modules to enable those profiles to work cleanly (custom_pagers in particular) has already gotten me a lot closer.

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

I would like to help improve Autolocale module and get it into core. Especially automatic importing of translations per module enable.

...that I plan to assist on. Right now that's probably a good place for me to be and learn. Besides that though I'd like to see something done to shore up Drupal's default theme package.

At a minimum chameleon/marvin should be converted to phptemplate (something I'd be glad to do) or dropped from the install asap, since as a non-phptemplate it's officially not a supported format. As a semi-recent convert from x-template I've seen first hand how hard it is to get support from other Drupal developers or modules themselves for non-phptemplates (some modules require phptemplate to work and nearly all handbook pages assume phptemplate for instructions).

Additionally, it would make sense to look at adding a theme or two (like BlueBreeze or Zen) as either additions to, or replacements for BlueMarine and Pushbutton (perhaps those could be 'refreshed' a bit if they are to stay in core). I have seen a lot of support request for css and/or table based themes which would make good 'starting points' for creating a custom theme (something which, Garland for instance, is not). Perhaps that would be good criteria for any new themes that get folded into core.

As my primary background is (was) in graphic design I would like to spend some serious time contributing to the down loadable themes.

I would also like to add specialized themes to the forthcoming install schemes. Such as for a blog site build blog-centric themes with some user customization such as adding a picture of the blogger and/or modifying colors via the new module in use in Garland.

We are going to translate Drupal 5.0 to Kiswahili.

I am going to translate Drupal to Lithuanian, spread Drupal at Lithuania and manage new Drupal Lithuania (lietuviškai) community.

1. First of all I want to offload more modules and projects. Less projects to maintain, more focus on those that matter (to me)
2. Secondly, I want to put my weight behind the Distributed web. Whereverver and whenever possible. Starting with help on openID. But also looking at distributed search, tag-sharing an more of such cool stuff.
3. And thirdly, I hope to work more with Drupal-alternatives, Joomla, Wordpress, Railfrog (off course) and some Typo3. Not just to use them, but also to see what they can do for Drupal.

On a smaller note:

• My attempt to get a real semantic, consistent basetheme will be continued.
• I want to try to get sympal (a Drupal distro for developers who develop for end-users) into a real installation profile for 5.x
• I plan (want) to spend more time on themeing, LDAP (integration), tagadelic, profiles-as-nodes (usernodes) and actions+workflows.

---
Professional | Personal

Here's a few ideas I want to turn into code:

1. Convert existing modules into CCK fields
   - NewsPage
   Add a keyword filtered aggregation of rss feed items into any node type.
   - Side Content
   Add block(s) to individual pages as CCK fields, multiple blocks in various positions, all part of the node.
2. User Import - Not Just For Admins
   Enable some options of saved settings to be locked and not shown, so that a user import form can be provided for someone in department x,y or z without allowing too much control of a site.
3. HTML2Txt Library Into Core

Cortext Communications
Drupal Themes & Modules

• jQuery
  • Default to correct timezone during registration.
  • Default to current user's timezone during installation.
  • Check for cleanURLs using Ajax (in progress - http://drupal.org/node/97213)
  • Automatically test for and enable cleanURLs on install (in progress - http://drupal.org/node/103059)
• E_ALL compliance (http://drupal.org/node/99625 and http://drupal.org/node/103250)
• Install system improvements
• Get Advanced Poll to the level where poll.module can be removed from core. (http://drupal.org/node/61285)
• Restructure the caching API (http://drupal.org/node/81461)
• Custom date formats (in progress - http://drupal.org/node/105039)
• Improve the flexibility of the bootstrapping system
• Help with project.module improvements (download tracking, module ratings, etc.)
• Drupal marketing
• Data mining of Drupal metadata

We'll see how much of this I can get to.

First of all, it turns out my battle plans for 2006 worked out just fine :).

Things I want to work on specifically in 2007:

• Refine the color.module to be more flexible (this would require at least one other person to make a colorizable theme). I already have working code in Bryght SVN for automatic resizing and compositing of a transparent PNG logo onto the Garland header.
• .info files for themes. These could carry the color.module info, regions list, supported features, etc. No need for phptemplate.engine as a lousy pass-through hatch.
• jQuery teaser splitter in core. 'nuff said.
• A real patch for global, per-role default input formats. The current proposals are not clean enough and/or only work for nodes and comments.
• PHP 6 Unicode support in Drupal. This is coming relatively soon. Luckily I already did most of the work ages ago :P.

That said, I will be following the work on drag-and-drop blocks and panels closely, as well as any other work on PHPTemplate (such as 'split mode' for theme functions/template files and structured theme output).

And maybe some other stuff I don't yet want to talk about :).

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

My battleplans include the following:

• Finally get default files directory moved to sites/default/files. Patch existed for 5 but it wasn't committed
• Revamp mail template handling by building a mail subsystem that uses token module (which is targeted for D6 core inclusion) and drupal_mail(). This is already implemented as a proof of concept in the upcoming release of E-commerce for 4.7 and 5.0 (ec_mail module). I'll add in translation support for mail templates once the concept has proven itself. At the same time i'll be exploring some additional features including better core support for HTML mails.

That's all I can think of at this stage.

--
Sammy Spets
Synerger Pty Ltd
http://synerger.com

I will work towards improving Drupal's out of the box security story for user login on password-accessed sites (i.e. most of them), including:

• Persistent Login (a.k.a. Remember Me)
• No more long-life PHP session cookies (since PL makes them obsolete)
• Conversion of "please change your password" to "password change is required."
• Configurable SSL support with the Secure Pages module
• Non-hijackable mixed plaintext/SSL sessions

The code for all of this is already written. This battleplan mostly only requires getting buy-in.

I observe, however, that a whole lot of battleplans consist of "get X into core." Somehow I doubt it will all go in. :-)

Goal

I will be working on setting up Drupal using community supported modules to best facilitate groups of people collaboratively building content together.

Plan

I will do this through:
- Testing various modules and themes to make the end user experience as easy as possible
- Recommending and testing changes to modules to enhance workflow and content organization
- Documenting the process so others can 1) track the progress of the project, 2) lend a helping hand, and 3) ultimately use the resources as a guide to setup their own collaborative workspace.

Current Ideas

I am currently exploring and evaluating the book module as the base of the project along with the organic groups module, taxonomies, WYSIWYG editors, and various filters (including footnoting, freelinking, & Markdown).

If you are interested in the idea or I was not clear please reply or send me a PM!

Cheers
Nik

In no particular order:

• JS file aggregation
• Gzip for aggregated CSS/JS
• 'Education stuff' (OG tools and perhaps SCORM import/export)
• Become a jQuery hacker :)
• Help get a Zen (or Zen-like) standardized theme in core
• Write an install profile
• Make phpfreechat even easier to install and more stable by the 1.0 release

I'll continue to work on adding internationalization support to Drupal
to build multilingual websites with my Localizer module.

1) Become proficient in Drupal
2) Improve the filehandling of Drupal (per-module setting of public/private downloads) and write a contrib module that allows you to create a download database that balances load between all Drupal instances that you've set up to do so, automatically backs up all files to Amazon's S3 (that's [url=http://groups.drupal.org/node/2099]already done[/url]) and allow downloads from there in case you've ran out of bandwidth, automatically syncs files between all servers using cron, selects the optimal download server based on both the location of the user.
3) Improve Drupal's performance (improvements to caching mechanisms mostly, probably).
4) Assist in others' plans.
5) ... I'm sure there will be lots of other things I can't think of right now...

Though I wish I could contribute in other areas, a new addition to our family in April only allows me to commit myself to one project right now.

I will be systematically working my way through all of the Handbook. I hope to have a system in place to push my way through the documentation once every 60 days. This will hopefully keep those capable of editing for code and functionality focused on their areas of expertise and not on the more annoying aspects of documentation.

Top three areas to keep in check:
1) Spelling
2) Grammar
3) Comment fold-in and reduction

1. Finally, after years of tinkering, become thoroughly proficient in Drupal theming and coding.
2. Create a contrib module overhauling Drupal's Promote-to-front-page functionality, enabling posts to be promoted to multiple "front page"s at different times, and keeping a record of those times.

... are simple. I will continue to maintain my existing modules and create a new one: In Nov 2006 I started to abstract Drupal nodes and files into WebDAV collections. Unfortunately I didnt have much time (and still dont have). But I hope to get a first version ready for initial commit before Drupal 6 is ready (but I wont promise). I also plan to help in Drupal core with some small patches and bug hunting after the major changes went in.

Most of my effort will, next to upgrading the modules I currently maintain to Drupal 5, upgrade existing modules so that they allow for multi-user blogging. For instance:

• Upgrading the month module so it allows a block per blog.
• Allowing users to create a block only visible on their blog page and only controlable by themselves.
• Allow a blogger to moderate comments on his, and only his, posts.
• A search per blog, for instance in a block on that blog page or blog article.

Here are some of the things I'd like to get to:

• More work on CCK
  • Follow up on the many legitimate feature requests that are not or only partially implemented.
  • Continue to add more 'field stuff' to the content module -- this will make it easier and easier to create custom modules by reducing the things that the field module needs to handle
  • Help issue some of this into core, not sure how much and when...
  • Too many other things here to mention, so moving on...
• Date module - I've just added from/to date capability to the HEAD version and want to get that working better and added to all branches, then work in some way to do repeating dates using API logic from the event repeat module.
• Calendar Views module - continue to work on timezone conversion issues, more flexibility in themeing the results, and maybe a plugin to add date-based back/next navigation to other kinds of views.
• Views Calc - I've been wanting to get back and do more work on this but just haven't had time. I want to make it possible to total up columns for the whole view output not just the displayed part, add in more types of calculations to both rows and columns, and integrate with other modules like viewfield and editview.
• Location Views - I got the proof of concept GMap proximity search working where you can select a point on a map and sort your view by proximity to that point but the code could use improvements and incorporate more features to make it better and more useful.

There are undoubtedly other things I'm not thinking of right now, but those are some that I would particularly like to get done.

I'll update as I think of more stuff.

Help make the Drupal API easier/more intuitive
I want to do things like build a library of CRUD functions for Drupal to get rid of these 50-line form submit handler things. Among other things, this will make writing install profiles easier. I also want to work around simplifying the Form API.

Enhance code quality
I'd like to work on tools like Coder module, automated unit testing, etc. to help core's code quality increase, and reduce the likelihood of subtle bugs making their way in. One great start would be E_ALL compliance in Drupal 6.

Fix signatures
Yes. ;) This is still my holy battle. ;)

Stuff on my long-term todo that I'll probably not actually have time to do much with:

Make a DruBB install profile
PHPBB in Drupal. Finally get rid of Drupal's reputation for having a featureless forum, and at the same time retain all the extensibility features that Drupal provides.

Make module builder kick ass
I'm starting to learn some jQuery, and was thinking it would be neat to make module_builder more full-featured, so it could generate db schemas, forms, etc.

I plan to contribute inline-images support module for Mailhandler module. Per our discussions with Moshe Weitzman, it will be a separate module, initially.

I plan to contribue a module that will enable SEO-friendly domain alias-management. For brand management purposes, a lot of websites have several domains attached but it is NOT a good idea to have different URLs lead to the same page. So, an SEO-friendly behavior would be to have one main URL and have alternative domains to the same URI issue a polite 301 redirect response. DomainAliases module will make easy configuring such behavior for mere mortals.

I know a person who is planning to contribute AJAXized, paging, sortable table view (for the Views module) and I plan to contribute to that effort.

I plan to contribute a module that provides integration (allows republishing of reports) with Omniture SiteCatalyst.

I plan to contribute to Url_Profile and Leech modules

I have a few goals for what I want to contribute to Drupal, but one in particular is something I'm going to need in the near future, so I feel comfortable saying I'll get it done before Druppal 6 comes out.

I plan on creating a simple module that utilizes the functionality of mailhook.org to allow users to easily insert content from emails into drupal nodes. The intended use of this is to allow content in email conversations to be CCed to an email address that will cause their content to be added to incorporated into the database. A more advanced version might infer some information about title or taxonomy from the email contents.

Us good folks at http://web.net recently released the WebFM module at http://drupal.org/project/webfm, which changes everything (for the better) when it comes to managing files on a Drupal website.

As a non-profit social enterprise ourselves, we share Drupal's valuing of community. We will continue to manage the development of WebFM, and welcome comments and contributions.

Thanks,

Oliver Zielke, Executive Director
Web Networks: Celebrating our 20th anniversary
oliver@web.net
1.416.596.0212 x.18
http://web.net

I'll continue working with dopry and others on improving the image handling functionality available in Drupal. Imagecache and imagefield are only the beginning of something much bigger, as we work to make Drupal's image handling rise above the competition.

I'm also working on jQuery based weights in tables (drag and drop). Finally we'll be able to rid ourselves of the awkward 'change the weight, refresh the page' workflow we've been using for so long.

Nathan Haug
_{creative graphic design        w: quicksketch.org
& software development       e: nate@quicksketch.org}

I am managing the Drupal 5 Hebrew translation project, and other projects related to the Hebrew localization of Drupal, including :

• Drupal Israel - A Hebrew Drupal developer community
• Garland RTL an Bi-Directional theme, which switches it's direction automatically according to the page language, which is the first step in improving Drupal's RTL languages support in core and contrib modules.

Also I'm involved in the Auto Registration workflow and hopefully with other usability and social networking enhancements.

Amnon
-
Drupal Focused Search Engine | Drupal Israel
Personal: Hitech Dolphin: Regain Simple Joy :)

Other than ongoing E-Commerce responsibilities, three projects are important to me. Like most module developers with little time, I'm keen for collaborators.

Eye-drop Editor. Eye-drop Editor is a client-side javascript image editor that will integrates with server-side image manipulation via callbacks. The goal is to make it easy for other Image management modules to integrate the editor, focussing initially on dopry's transformer and imagecache.

SWF Tools. This is a collection of Flash-related tools (filters, embedding, flash-replacement) which will ship with flash players. The goal is to integrate other Flash related modules.

Tipping. Sports tipping, a hobby project. I'm looking to join forces with Australian Drupallers who like footy tipping (the basis is tenrapid's worldcup tipping module).

Drupal site is anti-frame (can I say that?) Because everything opens in a new page. It will not stay. Why is it so important to me to have the frames inside the Drupal site?

Well the answer is, it could be wonderful when you can put an MP3 player or online TV/video player or CCTV real-time video side by side in independent frame (simply say that we can put any content that moving or progressing in the independent frame) without having it stops or disappear or rewind.

Can we do something like modification for Drupal 5? Or there is actually a lot of things to do coz maybe it will cause a lot of thing malfunction?

- - - - - -

My idea is to have the nodes run in AJAX so we can have a static page where we can put the MP3 player or online TV/video player or CCTV real-time video.

• Contribute to a unified object handling API, http://drupal.org/node/79684 and http://drupal.org/node/113435.
• Finish the patch I roughed in to make install profiles updatable (if this still seems to fit).
• Continue work on Javascript Tools. In particular, I've just posted an initial version of an in-place editing module, activeedit, that I plan to develop further (collaborators welcome!).

I'm still focused on the same things, file API and CCK fields. Just moving at a relatively tectonic pace. ;)

Within the next weeks I will contribute a fully-featured Classified module meeting the needs of online and print media. Some work will go into making event calendar and location handling more useful. Probably some work on the workflow.module is needed as well. On PDF handling I will have do dig into what already exists... I might later put this and some other things together to some kind of install profile for print media.

Additionally I'm planning to work on some handbook pages as well as de.po (possibly contributing a de-informal.po). For some time I've been thinking of a script automatically translating t()-texts into hardcode for efficiency reasons - still not sure yet whether that'd make sense or not...

I often complain about the lack of good user documentation.
So instead of complaining I will help writing. Please contact me if you want help.
The only thing I asked for is support from the module maintainer(s).

Development on the Drupal 5 module has stalled, but will resume again. For Drupal 6, I'd like to see microformats supported from the core, with a module to build up a microformat (e.g. hCard, hCalendar) using existing fields.

The work on this will begin again this weekend, and any one who would like to contribue, please join the Microformats group over at http://groups.drupal.org

Count on met to translate modules into Dutch (and Drupal Core) and beta testing. I'm no coder, but I can translate en into nl, fr and ge. But I'll focus to nl first an others later.

Hi,

First of all I am planing to build a forum that will be a complete solution, and will act as vBulletin/phpbb/ibf/smf/etc...

The forum will be based on Drupal's core modules, as the node and taxonomy system. The main goal is to use modules that already exists, and to code some modules that don't.

Each node type will act as forum topic.

You can check for updates here:
http://groups.drupal.org/drubb

Another thing that I want to work on, is an advanced KARMA system for users, nodes and taxonomy. Using this module, it will be possible to almost automate your whole site.

And finally, when I'll finish with the two above, I'll start working on Football (Soccer) modules: Stats, Tables, Team reviews, etc...

I think it's lot of work for 2007 :)

My personal plan is:
1. Replace current hook_cron and cron module with more flexible cron mechanism which might facilitate time-related module execution.
2. A better relationship between node-types. (node family, node relativity and node reference in one module)
3. Extending views to allow actions over viewed nodes not just "viewing".

• modify core search.module using techniques from views_fastsearch. This comes with an accompnaying articles on why Drupal search is slow and how to search with views, views_filterblock, views_fastsearch, and daterange.
• submit core patches found by coder, improve security review, create a D6 coder review early enough for people to actually use during the D6 code freeze
• propose core patches to implement a simplified releasemonitor and patches to support an enhanced releasemonitor contrib module

Doug Green
www.civicactions.com
www.douggreenconsulting.com

I'd like to do some or all of this, time permitting:
http://drupal.org/node/84756

--
Jakob Persson
Drupal developer, web designer and usability consultant
http://www.jakob-persson.com

Here is a list of things I consider important for Drupal 6.0:

1. Bringing CCK and Views into core.

2. Stop hardcoding node types (organic groups, forum, blog, book, event, video, etc.) All these modules should use CCK to create their node types and fields. This will give an ability to customize them and their output. Just like forum module utilizes taxonomy to create a Forum vocabulary it should also use CCK to create a 'forum topic' content type.

3. Improving Form API (ability to change button texts, normal multistep forms support).

4. Creating a directory for common 3d party components. Since, many modules may use the same components/libs (i.e. getid3) it is better to store them somewhere in '[drupal_root]/misc/libs' or even '[drupal_root]/libs'.

5. JSTOOLS: Bring more jQuery pluggins into Drupal as jstools modules.

----------------
Regards,
Dmitry Kresin, ARDAS group (ARDAS group)

More ajax ( more jquery)
Simplify Form Api
Faster search
Better performance
ImageMagic Integration.
Persistent Login (a.k.a. Remember Me)
Newsletter
moderation in forum
swf and action script support.
dorp down / pop up menus
---
Sharique uddin Ahmed Farooqui
IT head, Managefolio.com

- Better performance (it's a must) :)
- Costume user profile per user (using theme)
- Blog theme per user
- Faster search