But, since you asked...
We have said we would like to make syncing with the server more automatic.
If there are other specific changes you would like, please post your most important one or two.
That's basically it. I need it to work with all fields, and all file types, just like accessing a "shared" library does, but with all of the copies of MC on the network to have some version of read/write access. I agree that the SVN "check in/out" model is probably the best one to go with, considering the existing infrastructure. However, the check in/out process needs to be almost entirely automatic and asset-level granular rather than library-level granular. So, for example:
I need to be able to do this:
1. Have one user (wife/children) watching a show on the HTPC (which involves "tagging" files with Number of Plays, Last Played, and Bookmarking, among other things). Maybe they will do a few "light tagging" duties too.
2. Simultaneously have another user (me probably) on my laptop or in my office working with media files and tagging other things. Changes to the library seamlessly sync to the HTPC without having to close and restart or anything like that (there can be a delay of some kind, that's fine).
3. If both users try to "tag" a particular file simultaneously (which would count when a file is playing back elsewhere), then a "read only" error message should appear, maybe showing which machine has the file "checked out", allowing you to continue but changes will be lost (so two machines can simultaneously play back one file), and maybe even giving you the option to "force check out" the asset.
If I can do that, it would go a LONG way towards making the system much more usable. The last thing might be some sort of "server managment" system that can check to make sure the Library Server stays running on the serving machine, disconnect clients on a schedule to make backups and whatnot, upgrade to new versions automatically, etc. These things may or may not be needed depending on the implementation. So long as it can sit there rock-solid stable for a month, and make backups of the library, and everything.
We could do it. I just don't think it would affect our sales.
I would pay for a "Pro" or "Server Edition" license. I think others would as well.
Think about the food fight we've had over search suggestions the last week or so. Multiply it by 100 and that's the direction you're proposing.
Tech enthusiasts often don't respond well to change, which is odd since they're enthusiasts in the most quickly-changing industry in history. Personally, I was pretty enthusiastic over the suggestion engine changes. With the changes in the latest build, I think it is about perfect.
But yes, changing the system dramatically would probably rile up the troops. That's why I think the best solution would build on what you already have.