I'm glad you are optimistic. GitHub will need employees with that attitude if they're going to pull out of their current trajectory.

To be clear- from a user perspective, "improving GitHub" means "restoring reliability to what it was 6 years ago". There's no killer feature that makes people stop leaving, if my PRs don't lead every third day and actions never work.

▲

grogenaut 5 hours ago | parent | next [-]

I may have my timelines wrong but I don't remember github being rock solid 5 years ago. I remember multiple outages keeping us from pulling code for go packages that were not using an enterprise dependency cache and killing multiple days of work a year for those systems. It's what I used as a forcing function to move people TO an enterprise dependency cache, and to find the few scofflaws running work code off of github.com versus enterprise.

	▲	margalabargala 4 hours ago \| parent [-]
		You're right. I was misremembering this graph: https://damrnelson.github.io/github-historical-uptime/

▲

slowmovintarget 5 hours ago | parent | prev [-]

Security: No leaking PII, no compromised build pipelines.

Uptime: 4 9s minimum for paying customers for the core service (not necessarily the social features, but pull requests have to work).