4 ms·

Considering Microsoft owns GitHub, there's no reasons their internal teams aren't choosing to host more code on there.

ChuckNorris89 6y ago
They probably had their own internal version control for their IP before they bought GitHub. Can't imagine they suddenly migrated all their stuff to GitHub.
ComputerGuru 6y ago
That acquisition happened a blink of an eye ago, in the grand scheme of things. Things don’t change that fast, especially when you have the sheer amount and scope of DevOps and integrations that MS has. With the possible (but even then still unlikely) exception of greenfield projects, there’s basically no chance that anything but open source (or soon to be open source) MS projects were hosted on GitHub.
input_sh 6y ago
They also have a competing service: Azure DevOps (formerly Team Foundation Server, Visual Studio Team System), which somehow has barely anything to do with Azure. I believe that the stuff they're open sourcing go on GitHub, while the internal tools go on Azure DevOps. They also have their own VCS (Git alternative) called Team Foundation Version Control (TFVC), though I have no clue why they keep that thing around. They've also had Microsoft Visual SourceSafe, but even they themselves didn't really use that. On a side note, they really suck at naming things.
- outside1234 6y ago
  Azure Devops is increasingly based on the same code as Github. Github Actions and Azure Devops Pipelines, for example, utilize the same infrastructure in my understanding.
  - myko 6y ago
    It's a lot nicer to use on the GitHub side, and more organized (.github/workflows/foo.yaml vs a yaml in the root of the project for all "Actions")
    - jen20 6y ago
      Azure DevOps does not require a YAML file in the root of the repository either - it's quite common to have them in a 'ci' folder. While I prefer GitHub Actions in most respects, duplicated setup work and jobs are handled much better by the Azure version currently IMO.
- EdwardDiego 6y ago
  > which somehow has barely anything to do with Azure. This is some weird Microsoft thing. I think Windows 10 development is now handled by the "Azure" org[1] [1]:https://www.zdnet.com/article/how-microsofts-azure-organization-makes-the-windows-sausage/ https://www.zdnet.com/article/how-microsofts-azure-organizat...
pbhjpbhj 6y ago
Not my field, but security would clearly be a greater issue for repos held in a publicly accessible site vs those only accessible over a VPN. Sure, dogfooding is good, but commercially sensitive repos would seemingly - to my naive view - be better on private servers?
- hawaiianbrah 6y ago
  GitHub has an offering you can run on your own servers: GitHub Enterprise Server

They probably had their own internal version control for their IP before they bought GitHub. Can't imagine they suddenly migrated all their stuff to GitHub.

ComputerGuru 6y ago

That acquisition happened a blink of an eye ago, in the grand scheme of things. Things don’t change that fast, especially when you have the sheer amount and scope of DevOps and integrations that MS has. With the possible (but even then still unlikely) exception of greenfield projects, there’s basically no chance that anything but open source (or soon to be open source) MS projects were hosted on GitHub.

input_sh 6y ago

They also have a competing service: Azure DevOps (formerly Team Foundation Server, Visual Studio Team System), which somehow has barely anything to do with Azure. I believe that the stuff they're open sourcing go on GitHub, while the internal tools go on Azure DevOps. They also have their own VCS (Git alternative) called Team Foundation Version Control (TFVC), though I have no clue why they keep that thing around. They've also had Microsoft Visual SourceSafe, but even they themselves didn't really use that. On a side note, they really suck at naming things.

outside1234 6y ago
Azure Devops is increasingly based on the same code as Github. Github Actions and Azure Devops Pipelines, for example, utilize the same infrastructure in my understanding.
- myko 6y ago
  It's a lot nicer to use on the GitHub side, and more organized (.github/workflows/foo.yaml vs a yaml in the root of the project for all "Actions")
  - jen20 6y ago
    Azure DevOps does not require a YAML file in the root of the repository either - it's quite common to have them in a 'ci' folder. While I prefer GitHub Actions in most respects, duplicated setup work and jobs are handled much better by the Azure version currently IMO.
EdwardDiego 6y ago
> which somehow has barely anything to do with Azure. This is some weird Microsoft thing. I think Windows 10 development is now handled by the "Azure" org[1] [1]:https://www.zdnet.com/article/how-microsofts-azure-organization-makes-the-windows-sausage/ https://www.zdnet.com/article/how-microsofts-azure-organizat...

pbhjpbhj 6y ago

Not my field, but security would clearly be a greater issue for repos held in a publicly accessible site vs those only accessible over a VPN. Sure, dogfooding is good, but commercially sensitive repos would seemingly - to my naive view - be better on private servers?

hawaiianbrah 6y ago
GitHub has an offering you can run on your own servers: GitHub Enterprise Server