Comment by wmij
8 years ago
> 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...).