Thanks for all the suggestions to help not mess up the MDG development. We want one or two (so not loads more people to get it all messed up hopefully) to help out and remove the single point of failure.
Was timoc's Team Library suggestion intended as a way of team communication? I've never used that feature but it doesn't seem to address any other issue.
Team Library is a part of a model database that can be 'shared', with others working on other model databases. The Team Library seems to have been created with a specific idea about how teams should communicate, share information, etc. with a detailed review/team-support workflow in mind. It essentially allows you embed 'assets' with documents in a document tree. Where an asset can be a package an element, other resources that can be exported via XMI. This tree can be 'shared' with other model databases. Shared in this case means that it is available and editable while working in other model databases, and so can be used to share packages like a poor mans version control. Think of it like a kind of wiki+model pastebin? The manual seems to imply the documents are supposed to be some kind of team forum or something, i am not sure why.
The upshot is, if it is an asset that can be exported via XMI or 'cut and paste' to another model, then you can store it as a Resource alongside a document in the Team library. It is a nice feature if you are not using a central modelling database, a RAS or version control.
Anyway, my experience with Team library since EA 12, is that it has not seen alot of love since it was created. The implementation seems to rely on a cached index or something, and i have had to go back to backups in the past to recover library information. It seems a bit wobbly in EA16 with qeax files (bug submitted), but YMMV.
As a side note: Like pretty much everything else in EA (not just 'marketing features') the manual describes all of the menu options and what each option does. The manual assumes you know why it was designed the way it was, how and who it was designed to support, how it links to other features (associated report templates, calendar features, journals etc.). I am sure there are well defined user roles, use cases, review workflows etc. somewhere, but they are not in the manual. Users are essentially forced to bend the underlying design to fit their needs, re-implement 'out of the box' reports, possibly relying on edge cases or unintended features to support your reverse-engineered re-interpretation of the Team Library feature.
Meaning: the wobbly nature of EA16 may be due to my misusing Team Library in some way