Comment by wmij
8 years ago
There probably won't be (m)any noticeable changes for the open source and devs running personal private repos and possibly the same for GitHub team plans. However, I'd bet Microsoft will plan on a sunset timetable for TFS and push their licensing and sales machine toward GitHub for Enterprise. I'm glad my group isn't on GitHub for Enterprise because after seeing this news I'd be looking to migrate away ASAP. I can envision the the potential for their draconian licensing lock-in and TOS language spawning a nightmare for teams that are running GH Enterprise. These GH enterprise installations will likely be required to purchase MSDN licenses.
Why would they sunset TFS (Or VSTS)? I use both and there is barely any overlap in features. GitHub is only code storage + a rudimentary issue manager. There is very little release management, test management, CI/CD etc.
If anything I’d expect them to integrate better and of course integrate more with Azure (e.g one-click setup of build/test on azure from any Github project)
> Why would they sunset TFS (Or VSTS)?
Admittedly I've been away from TFS for a number of years, however, it seems that GitHub Enterprise is a natural fit product wise for revenue stream via licensing thru MSDN to get organizations onboard with GitHub that weren't before. If they were to sunset TFS and provide a migration path, it would end up giving them significant licensing dollars.
The more important point I was trying to make is that orgs that are now on GitHub Enterprise would need to subscribe to MSDN enterprise licenses for a bunch of things that aren't relevant and get locked into TOS that they hadn't been previously.
Regardless of sunsetting TFS/VSTS, I think that Github Enterprise will be only available through a MSDN enterprise/premium license or whatever that is now in 2018.
Superficially it seems there is some overlap, but github’s issue tracking for example is very simple (assuming enterprise is the same, I haven’t seen it).
VSTS supports the JIRA level of features like complex workflows, hierarchical issues, scrum/kanban boards (including hierarchical sub teams with differing sprint dates), burndowns and hundreds of other charts.
I would love to see all that ported to github, but it just wouldn’t be GitHub any more then.
To me they seem like VS and VS code. One is a big fat enterprisey thing and one is lighter. The enterprise version of GitHub doesn’t seem so focused on enterprise processes as VSTS is, but rather on enterprise infrastructure things (auth stuff, cloud integration stuff...).
Agreed. I see MSFT keeping GitHub as a "simple" choice for repo hosting.
VSTS is awesome, and quite feature-packed. Maybe Microsoft will use GitHub specifically for repo hosting, while offering VSTS as an CI/CD/ALM platform.
> I see MSFT keeping GitHub as a "simple" choice for repo hosting.
I didn't say that the "simple" choice for repo hosting would go away... My point was that if you need GitHub Enterprise, you get it only with the biggest MSDN subscription and end up with a bunch of things either you don't need or don't want and having to agree to licensing that's MS/MSDN specific.