121–126 of 126 posts
Earlier quoted context omitted.
Considering Microsoft owns GitHub, there's no reasons their internal teams aren't choosing to host more code on there.
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?
> This evening, a hacker going by the name Shiny Hunters contacted BleepingComputer to tell us they had hacked into the Microsoft GitHub account, gaining full access to the software giant's 'Private' repositories. Well, someone asked the other day whether or not private repositories on GitHub were safe: [0] I think you now have a concrete answer regardless if this is true or not. I have already made the case to priva…
This got me thinking. How many companies, in terms of Market Cap are currently relying on GitHub Private Repo for their source code? And how does very large enterprise, or financial institution ( Which is like the foundation of modern day society ) handle their source code? I presume they wont use Github for anything important?
Earlier quoted context omitted.
Wouldn't that mean any computer connected to the internet shares that risk?
yeah, that's why in an average on-prem setup you usually would have firewalls, DMZs, IDS/IPS and all the good stuff - and people have been doing on-prem security for decades and accumulated an enormous wealth of knowledge and practice. in cloud - it all new. people are still figuring out how to deploy their software so that it works both for users and developers. That's why on average onprem is more secure than cloud…
Also firewalls/DMZ/IDS has nothing to do with a SaaS offering from GitHub. That on prem setup you mentioned would be practiced by GitHub.
My opinion of general on-prem security is that it's often haphazard and updates are almost never applied.
But also a lot of on prem security practices hamper developers and users. Because they rely on decades old outdated ways of working.
Also your comment makes no sense as this is likely to be a hack through stolen credentials.
Earlier quoted context omitted.
Considering Microsoft owns GitHub, there's no reasons their internal teams aren't choosing to host more code on there.
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. Th…
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-organizat...
Earlier quoted context omitted.
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.
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")
While I prefer GitHub Actions in most respects, duplicated setup work and jobs are handled much better by the Azure version currently IMO.
Earlier quoted context omitted.
Ah source code at MS. Always amusing to me. VSS [1] (Visual Source Safe) was terrible and I always wondered how "real" companies could use it. From what I heard, MS never did use it, they bought it and sold licenses. That's it. That being said, Microsoft actually moved Windows to Git [2] years and years ago. Presumably they did the same with everything else. Team Foundation Server (TFS) supports Git, so they probably…
They moved to Git, from what I can tell as an outsider, as part of the "Balmer fucked Microsoft" clean up duty that produced a toxic and soon-to-be-fatal culture over there. Github ended up being the final piece they needed after years of effort. Most of what I said in the earlier comment was what I pieced together from multiple (ex-)Microsoft people who chose to talk about it, over years. TFS afiact started as just…