The past two days I've been studying this and several other discussions of the moodle2.0 issues. We'll be sticking with moodle 1.9 for the next school year, and using that year to decide whether to continue with moodle and upgrade to 2.0 or else go with some other solution - based on an effective response to the concerns people have brought forward. I'll need to decide what we're going to do by early March of next year. Here's what I would like to see.
1) Moodle filesystem repositories that can be owned by a "cohort" of teachers. This could end up being all teachers in a department, all teachers teaching sections of the same course, or co-teachers of a single course, but it would give that group a secure area to collaborate on content. Moodle already has cohorts - system-wide groups - so how difficult would this be? As a file is "copied" if it is linked to an activity or resource, there should be no problems with access by students once a teacher attaches a file from the repository to an activity in their course, at least if I am understanding the new system correctly.
2) Implement the solution suggested in this thread, so that if I replace a file in a repository, I'm asked whether to also change the "copy" attached to any resources. Rather than an all or nothing solution, it would be nice to have the list of linked resources and activities and be able to check the ones I want to change. Thinking this through, I guess if someone else owns the activity or resource, then they should get a notice asking whether they want to change to the new version??? I can see this gets complicated. The same thing should happen if I try to change the file from one of the associated activities rather than the repository.
3) A reliable way for teachers to backup their course from the 1.9 moodle instance and restore it to the 2.0 instance. This is tangential to this thread, and I understand that it is in the pipeline to be developed. I hope it happens before March.
My initial reaction upon trying out a test server was one of frustration as I realized the course file area was gone and my plans to enjoy the other new features of moodle 2.0 evaporated. I've tried to keep an open mind as I've read through all of this and understood the changes and why they were made, and tried to figure out how teachers would use moodle 2.0. The bottom line at our school is that most teachers choose to use moodle - rather than alternatives - because of the easy and transparent maintenance of their file area, and the ease of getting their course ready for the next year. After getting familiar with moodle to serve content to students, they begin to play with the more interactive features because they have become comfortable with moodle, and the other features - the heart of moodle - are then right at their fingertips. Without the hook of simplifying their basic task of building and maintaining a course web site, they will never try the rest of moodle, nor will most of them have the time and energy to implement forums, blogs, wikis, etc. from other sources.
Content management may not be the key feature of moodle, but its still important for moodle to do a competent job of this basic task. If I have to go to another system for content management, that becomes an external repository for moodle, I'm afraid most of my teachers would then simply switch to the new content management system and forget about moodle. I can try to sell moodle anyway, but its better to entice people in by first making their lives easier.