Using git (or some other VCS) at your company

Question

Some friends of mine and I were talking recently about version control, and how they were using VSS at their jobs, and were probably going to be moving off of that soon. One of them said that his company will likely be going with Team Foundation Server.

Eventually, the conversation did get around to talking about some of the open source VCSes out there, including git and SVN. None of us really knew about any companies that use either of these internally, although we imagined that a number of them did so for SVN, but we weren't too sure about git. I brought up Google and Android using it, but my friend figured that's only for the public facing source code, and that they may use something different for internal projects.

Apparently it's more than just SCM that makes TFS so intriguing:

1. Microsoft Sales people and support (although my friend did point out somethings to his managers that he thought might be misleading on MS' part)
2. Integration of things beyond SCM, including project management (I'm just finding out that there are geared towards the same things for git)
3. Again, it's Microsoft, and the transition from VSS to TFS seems logical (or does it?)

I'm not much of a fan of SVN, so I didn't really bring it up much, but I am curious about whether or not git is used at your company for internal projects.

Have you thought about it, and decided against it? Any reason why?

Answer 1

We use git for all of our source code. It just makes sense.

• It's quite nearly impossible for us to lose anything since at the point where two people touch a project, we have three complete copies of it (and our backups of those repos).
• We do not rely on any centralized infrastructure -- including network. I've worked on projects in BART tunnels.

In theory these commercial systems should save you from broken repositories and all kinds of wonderful things with their support.

In practice I've lost more code and time to centralized repositories than distributed.