I'm going through Pro Git and one thing isn't quite clear. Let's suppose that I have a GitHub private repo for a highly successful commercial app which I've made accessible to developers in my team. A developer can clone that repository to his computer but once it's on disk then he somehow quits and goes to work elsewhere, he'd still have that repo on his machine. What's to stop him from using that repo's source code in undesirable ways -- maybe selling it, or leaking it, or using it as the foundation for launching his own app, with a few custom tweaks here and there?
The most enlightening piece I could find was this one. Even then, it still left the local repo exposed to misuse. All other links contained information already available in Pro Git, which I have, so basically I'm yet to find solutions for this sort of thing.
So how are private projects that use Git handle scenarios such as this one?
A developer can clone that repository to his computer but once it's on disk then he somehow quits and goes to work elsewhere, he'd still have that repo on his machine. What's to stop him from using that repo's source code in undesirable ways -- maybe selling it, or leaking it, or using it as the foundation for launching his own app, with a few custom tweaks here and there?
Exactly the same thing that should be preventing that in any other situation: a decent contract, and (probably) your local copyright law.
Git doesn't change anything, legally speaking. What's to stop a developer working with code that only exists on a network share inside a company's VPN from copying that code onto a flash drive, taking it home, and using it in "undesirable ways"?