Posted by kwalker on April 16, 2007 at 4:22am
I see that the Summer of Code slots have been set. 20 of them are drupal related and of those
Unified File Management http://code.google.com/soc/drupal/appinfo.html?csaid=FA475F12A343C364
Private versus Public File Management for Drupal http://code.google.com/soc/drupal/appinfo.html?csaid=31A32F81A3DD031
and perhaps
Taxonomy Manager http://code.google.com/soc/drupal/appinfo.html?csaid=5374D02AB6384CDF
may have application here.
Comments
Rationalize this!
Boy, having summer of code proposals be relevant to this sounds really advantageous.
But, it would really be good if the proposal accepting folks could help guide / shepherd these into being rationalized into some form of architecture for how document management could / should be done. I'd hate to have these summer of code efforts pour concrete that would NOT work well for document management. How do we communicate this, and to who?
Also, it's useful for this group here to re-read the Forum posting from 2004 that did a great job of requirements specification.
I, for one, agree that document management is going to be key for the future. Just as Drupal has grown from a blog-like system to becoming a full web CMS, I think it is likely to need strong document management to become a significant Intranet tool (vs. tool to create blogs, internet sites, etc.). Existing Enterprise Content Management Systems (ECMS) are now adding more and more web CMS functionality, and will soon provide all that Drupal does. But Drupal can trump them via being a great open source project (and community) - as long as it can match at least some minimum set of document management features like those provided by ECMS systems.
I may not be able to code much, but I can certainly help with requirements, testing, and brain power (to the extent it's helpful) on this project.