Also, gitlabs needs to start sending out more stickers like github. I want some.
edit: Congrats to Zach Holman & Gitlab team!
GitLab installations on-premises should be fast already. But the nice thing is they are also benefitting from the improvements we're making for .com
We cannot know for sure whether it has anything to do with his firing (and he doesn't mention it in the writeup), but Julie Ann Horvath did accuse Zach of harassing her at GitHub.
Regardless of what happened or didn't happen, his close association with her probably didn't help anything.
It's a really tight knit subculture with its own rules and a vicious ingroup/outgroup attitude.
Like goths or old school hippies, they have a distinct way of dressing and signalling to each other that they belong: purple or pink hair, Twitter profiles that specify "he/him" or "she/her" even when it's obvious, using words like "mansplaining", etc
--
Outrage culture is a kind of conspiracy theory: people who are into it see oppression and harassment everywhere, and cast themselves as victims.
Here's a great explanation of the history and ideology of outrage culture: https://youtube.com/watch?v=cYpELqKZ02Q
---
Github has been taken over by outrage culture. Check out this insane story from earlier this year: https://news.ycombinator.com/item?id=11049067
* Leaked internal HR slides talking about how "white women" are often "part of the problem"
* An employee casually mentioning to BusinessWeek that "it's hard to even interview white people"
* One Github executive sending this flagrantly illegal tweet: http://static4.businessinsider.com/image/56b3d2f12e526555008...
Imagine the instant EEOC investigation if that tweet said "black, male" instead of "white, male".
--
Anyway, Zach Holman is also a white male. I don't want to speculate on exactly what went down, but the circumstantial evidence is pretty strong that he was railroaded out of the company in the wake of the Julie Hovarth scandal.
--
I don't in any way defend the most visible opponents of outrage culture -- rank bigots like r/RedPill, Trump enthusiasts, and so on.
I just want to point out that outrage culture is, itself, bigoted and intolerant, just in a different way.
I really respect Zach. I learned how to give better talks from his amazing ones. He was the face of Github to me and I wish him the best!
> As to the remaining allegations, the investigation found no evidence of gender-based discrimination, harassment, retaliation, or abuse.
https://github.com/blog/1823-results-of-the-github-investiga...
I totally agree with that vision and I'm very glad to have Zach join. He is an amazing advocate for developers and I feel honored that he joined us.
More information about Zach Holman https://zachholman.com/about
Of course, maybe that's exactly why the let him go. Regardless, I'm looking forward to seeing him do the same for GitLab. (Minus the firing.)
Given that GitLab and GitHub have similarities in terms of the technologies used(RoR, git, fileservers, cache systems for git metadata), Zach could bring a lot to the table on the technical side. Could sytse or holman clarify if Zach will also get invloved with the engineering department as well?
I really enjoy the blog posts on GitLab, but some posts tend to be light on technical details such as this[1]. Regarding the mentioned post, it would be great if you can provide more details about the exact server specifications, the amount of traffic you recieve, the size and variety of the hosted repos, basically more of the numbers. One of the things that interests me is how GitLab scales and I hope you continue posting updates about the work you do to scale GitLab.
[1] https://about.gitlab.com/2016/04/29/look-into-gitlab-infrast...
Numbers: About 1MM projects, >.5MM users. Repos range from smallest to 45GB (although we have a limit of 10GB). I have no quick data on languages, but I'm sure we'll blog about it some time.
Specs: Runs on Azure. Last I remember in total we have >100 servers, maybe half of which run GitLab.com. I've asked my colleagues for further detail and will update here.
As of the latest Gitlab (8.8.1), my "this breaks Gitlab" commit of the Linux Kernel sources (https://gitlab.com/nrclark/dummy_project/commit/81ebdea5df2f...) still breaks Gitlab.
When I first submitted this as a bug in December, the act of clicking on the commit would cause a Gitlab worker crash and the UI would either hang or return a 503 error. Five releases later, my sample commit still takes 10-20 seconds to load. Once it does load, it grinds my browser to a painful javascript standstill, and I have to close the tab.
Can we get some smarter diff handling on the roadmap? Please? There was a fix deployed a couple of releases ago, but the behavior is still pretty broken. :(
As for my browser, I'm on the latest Firefox on Fedora 23. Something interesting - I think it's related to some kind of internal cache on Gitlab's side. Could I maybe get you to try loading the same page in a few hours and see what it does for you then?
Following Zach on his blog and his talks, I think he has a lot of input to add. I feel this will be good for Gitlab users.
Good luck, to both sides.
Congrats, Mr. Holman!
