SoylentNews is people
SoylentNews
Three and a half years after his return, Chris Wanstrath will step down as CEO of popular developer platform GitHub after leading the search to find his own replacement.
Wanstrath will continue as chief executive until the new leader is found, at which time he'll move into an executive chairman role, he told employees at an all-hands meeting on Thursday [August 17]. Staff had convened at GitHub's San Francisco headquarters to celebrate the company passing $200 million in annualized revenue and reaching new user highs for its popular code repository site valued by investors at $2 billion.
The decision to step down was one that Wanstrath has been considering for months, he told Forbes in an interview. The beginning of 2017 marked the ten-year anniversary of the first commit of code getting pushed to GitHub (the company was formally founded in February 2008). Around that time, Wanstrath began speaking with investors, advisers and friends about the long-term future of the company. "GitHub has a great brand and we have a great community," Wanstrath says. "We could find someone really seasoned to take the CEO role and lead us for the next ten years, and we wouldn't need to lose me."
Source: https://www.forbes.com/sites/alexkonrad/2017/08/17/github-ceo-chris-wanstrath-to-step-down/?c=0#33c9269eadd3 [Javascript essential]
(Score: 2) by Immerman on Monday August 21 2017, @04:23PM
Exactly. Plus a huge existing body of members/users that are already invested in using it.
It wouldn't surprise me in the least if a lot of companies actually did maintain in-house source control, but also used Github to host their "public input" branch. Why give company servers that level of exposure?
Though once you're doing that... well why bother maintaining an internal VCS at all? Just keep internal backups in case anything goes really wrong, and factor in the expected X hours of downtime into your cost analysis. Assuming you're actually using the decentralized power of git, having the central server be down isn't actually much of a problem.
I'd hesitate to use "private" repositories for any code I *really* wanted to keep secret, but it you're working on open source software I don't see any downside.