[cptskippy]

I questioned their engineering competence during their last outage and the general responses I got were very dismissive. Gitlabs were able to spin the last disaster into a publicity stun with the live streaming but I feel like that was a fluke. Bro coding and "openness" will only garner you so much good will with paying customers who are more concerned with availability.

The unavailability of a code repository might be more of an inconvenience for a single developer but in an enterprise environment with teams of coders being able to quickly disseminate code changes can be critical. The unavailability of a source repository becomes a huge liability and a waste of man hours.

[xena]

If you are relying on something for your business that you paid nothing for, you get your money's worth.

[cptskippy]

That excuse doesn't really work because Gitlab offers a premium paid option for repositories hosted on Gitlab.com.

[Perihelion]

.com is free -- paying customers/CE users weren't affected by the outage.

[cptskippy]

> .com is free

Yes, and Gitlab.com Bronze Support is a premium service offered on the Gitlab.com platform. It is not the hosted or self hosted premium offerings.

> paying customers/CE users weren't affected by the outage.

That is incorrect. If you pay for Bronze Support you are definitely affected by this outage. Hosted and Self-hosted customers are unaffected.

[Piskvorrr]

Which is why I have yet to see a company with a gitlab.com important repo - but Gitlab local installs? Aw yeah! (Gitlab EE is their main focus, IMHO - providing a public Github alternative seems to be an afterthought.)