Please tell me you don't work in the industry.

If one of our clients has a security problem due to our software, you can bet we're in big trouble.

And starting next year the rules will get even more stringent. Basically every kind of protection that our clients are required to have, we'll have to have internally, especially wherever we have to handle patient health information.

And BTW, "portability" doesn't mean you get the code, it means you can take your records somewhere else. That's what I meant about "open interchange".

If you force open source, you'll quickly bring to the forefront every security issue in the code, which will be a HIPAA nightmare.

Moreover, I don't think the industry is ready to give up all its little proprietary secrets. A lot of places are reluctant even to give out the documentation on their database schemas, let alone any serious amount of source code.

Open interchange of information, on the other hand, is a big necessity and has been happening for a long time now.

SVN does not track the state of the repository globally.

Did I miss something? What are peg revisions for then? In the TortoiseSVN UI I can just type in the global revision number and browse the repo at any given point in time.