Packaging now standard, dependency proxy next?
about.gitlab.com
about.gitlab.com
But does it matter at all? If I host critical code somewhere, it has to be available, and GitLab's uptime history[0] is so much poorer compared to GitHub's[1], with service disruptions and degradations being more common, and far more severe. I don't understand why GitLab doesn't focus on improving the quality of their service. It's not like this is new.
Edit: I feel like I came across as very sour, and I am. But I do like GitLab. I've actually used its CI and Docker image repository in the past and prefer how everything is in one place. I've even written fairly a fairly comprehensive article outlining a deployment pipeline leveraging their tech, but I just don't like service disruptions, especially when they're normalized.
[0]: https://status.gitlab.com/pages/history/5b36dc6502d06804c083...
Link?
I don't use their container system here, though. It's just GitLab CI.
Now if I was going to complain about something it's that they STILL sort images in the registry alphabetically instead of chronologically. I can't even imagine a scenario where that makes any kind of sense.
So maybe the opposite is true. Maybe they're totally focused on reliability and common sense fixes have been ignored.
I respect the open source culture at GitLab. I like how transparent they are, how they handle issues together with the community. But, this is a feature that is very generic. You can't blame a phone company to put a camera to their phone because company-x had it before.
> It'd probably have been better handled more subtly.
I don't think they should've handled it at all, because of their past. Today's GitLab is very different than when it was first launched as an open source project - while the logo was more like a cat[1][2]. But being passive aggressive to GitHub, the company that they think that is stealing their ideas, while still having parts that are remnants of a copy/paste job from that same GitHub, I don't know. This shouldn't mean that GitHub or anyone can steal freely GitLab's ideas. It's hard to find a solution as to how one can fix such past mistakes, but maybe an acknowledgement/owning before going defense mode help.
> If I host critical code somewhere, it has to be available…
+1, GitHub had hiccups too, but they have been pretty solid.
[0]: https://venturebeat.com/2014/03/30/threes-vs-2048-when-rip-o...
[1]: https://web.archive.org/web/20130602065750im_/http://www.git...
[2]: https://web.archive.org/web/20131228051528/http://gitlab.org...
GitHub is competing for your attention and trying to convince you to use github.com similar to the way that Facebook wants you to use their site. GitLab is not.
If you don't want to use gitlab.com because of low uptime, GitLab doesn't care. GitLab cares about whether you want to buy a GitLab license. If you're not in the market for that, then you were never a potential customer, anyway. Expecting GitLab to care about what you think about the ops history for gitlab.com is like thinking that a car dealer cares about how satisfied the people are who come in to have a coffee, eat a cookie, and test drive a car from the showroom, and never intend to buy anything. That's what gitlab.com is: a showroom.
You're mistaken. This was true at one point, but no longer. GitLab maintains a document comparing itself to GitHub[0], has mature pricing tiers that go up to $99 per user[1], encouraged users to switch during the Microsoft acquisition by giving discounts on their higher tiers[3], and has paid me $500 in a bug bounty for reporting business logic flaws that allowed free users to leverage APIs that they shouldn't have had access to according to their plans.
If you're actively pulling devs to your product, and even charging them. Make sure your product stays up.
Also, please don't scorn people that disagree with you. Some times it's not them that "don't seem to get" it.
[0]: https://about.gitlab.com/devops-tools/github-vs-gitlab.html
[1]: https://about.gitlab.com/pricing/
[2]: https://about.gitlab.com/2018/06/03/movingtogitlab/
[3]: The report is redacted, but you can see the bounty at my HackerOne profile: https://hackerone.com/gilani
I think it's absolutely an appropriate response.
If only there was some standard for package hosting + publishing across all languages… stares at The Update Framework
I agree that the verbiage could be better; it looks like they tried hard not to poke fun, gloat, or otherwise prod the blue giant.
How GitLab is open source? It open sources a non-essential portion of its software, and so does GitHub.
Calling what it open sources "non-essential" is so ridiculously misinformed that I'm really wondering what your goal is here.
But EE, the product they are making money from, is not free, and not open source. Thus GitLab is not "Open Source company", as stated by arnieswap at the beginning of this thread.
I don't think this is a fair (or accurate) quantification.
While Gitlab's principal product probably has more open sourced code, Github makes tremendous contributions to open source. Atom is open source. They contribute significantly to projects like Rails (for example, the multiple database feature was extracted from their codebase). This doesn't even begin to address the dependency upon Github the entire open source ecosystem has. How many millions of dollars do they spend in infrastructure every month just to keep projects like RubyGems and npm viable?
I think Gitlab is a spectacular offering, and having a single source for your entire dev-ops story is extremely compelling. However, spinning a narrative that Gitlab is more open source than Github is extremely disingenuous.
I hope they can catch up before it becomes too tempting to bail.
The reason those things were never widely known is because GitHub never made whiny passive aggressive blogs posts about it. That's one thing Gitlab should have copied from GitHub.
> Now they're well in the dust and still don't have an open source version.
GitHub is massively larger than Gitlab. It's not even close. You're focussing on one relatively unimportant thing, and missing the bigger picture. I would wager a year from now, GitHub's lead in the market will have increased, not decreased.
I wager GitHub will be a significantly larger company, with more users both free and paid, hosting a significantly larger portion of notable open source projects.
[1] https://wrapbootstrap.com/theme/inspinia-responsive-admin-th...