Yeah, I think for the most part I agree with you, but I think its a matter of integration.
We want people to use our modelling repository, but its not the only tool in our arsenal. There is an entire groupware structure thats in place that helps people coordinate and know where other things are in our environment. What kinds of things? User manuals, source control repositories and architecture repositoriies. Any one who comes into our organization as an architect will be "folded" into the process of building and maintaining models in the repository, but ... when they want to communicate with one another (or with other users), they're going to do that through a groupware medium (IM, mail, bulletin board or wiki). What I want to avoid is them putting up messages that look like this:
"Go to the repository and look under the 'Data Engine' project, logical view, physical structure package and you'll find a detailed layout in the diagram in there"
Ugg... Now everyone who receives that message (and with persistent mediums like wiki's this can be a more pressing issue) will have to read it, parse it and figure out where to go.
We can live with the lack of integration... if it gets to a point where we can't, then we'll build our own integration mechanism. It shouldn't be too difficult to write a wrapper that can launch EA pointing at a specific repository.
BTW, if we were using file based repos this wouldn't be as much of an issue, but because we use an RDBM-based repository there's no easy URI that we can toss out there to point it at our repo.
