docs.module in cvs

I uploaded a simple file/document management module. I consider it a pre-beta quality, so you won't get it through the project interface, just cvs. It targets D5 at the moment, but is trivial to port to D6.

There are quite a few more things I want to add to it. Some of them are probably going to end as extension modules.

Why just another module doing something like file management?

• no dependencies outside core
• upload.module might be a hack, but it supports revisions and other goodies
• taxonomy is a good analogy for folders
• no extra types required, piggyback as much as possible what is in the centre of the universe
• Minimal code maintenance and brain effort should be required between core trasitions => reuse code from core.
• Minimal time to update to a new core release => no dependency outside of core

What do I want?

• Feedback. Is it useful?
• Feature suggestions, requests. I don't guarantee any of them will end up being implemented, but still, they might. HACKME.txt in cvs contains more information about planned features and the reasons behind some of the decisions.
• Read the README.txt and HACKME.txt

Some pictures attached