Core changes

User module

The user module is one of those parts of code that nobody really dares touch. It is a really critical part of the system. Without user accounts so much in Drupal just stops working properly. Hence it hasn't had a really good cleanup for a long time. Some of the other features I want to add to Drupal require that user module work in a more unified way. Currently a lot of code is duplicated and hence unnecessary complex, this causes frequent bugs when someone does dare to mess with the module.

Generic insert/update handlers

I have also been working on generic db_insert() and db_update() functions that will replace a lot of the logic in node_save() and user_save(). It will also make other modules have more robust tools available, and make it easier to manage large database insert/updates.

_nodeapi and _user hooks

The plan is to rename _nodeapi and _user hooks to _extend_node and _extend_user, and add a new hook for _extend_comment. As well as the rename the parameters and functionality will be unified as much as possible to make it easier for developers. The current common operations I have noted down are: form pre, form post, validate,
insert, update, delete, load, view, and fields.

File API

Not much to say about this. Taking the current proposals extracting the basics and making a file.inc.

Doxgen comments

Need to group and document some of the core functions. Also need to setup a crontab for auto generation of documentation on drupal.org and promote it.

Taxonomy module

Not sure I will do any coding on this. I would like to see the module split into a common API that is always available in taxonomy.inc, and taxonomy.module become an admin interface in the short term. In the long term we shouldn't have a generic taxonomy admin, instead the modules that use it should make their own interface using the API. Forum and image modules would be a lot simpler to administer if the taxonomy were in the modules with the proper terminology. Still thinking.

Misc

• Timezone handling.
• If-Modified-Since.
• Race condition in sess_read()/sess_write().

Contrib changes

Project and cvs module

I would like tighter integration with CVS or the Drupal cvs module. I have already prototyped a much more powerful cvs module. Just not sure how or where I can make the tarballing of projects quicker. Might just do it on the CVS server level and not worry about Drupal. Some of the changes might make the project module unusable for anything but drupal.org, which isn't good.
Going to add some way to make each project a taxonomy (see http://drupal.org/node/view/4485). Still not convinced it is a good idea, but I am willing to try it out. Again not sure if this belongs in project module or someplace else.

Event module

Recurring events.