51–60 of 112 posts
Wow. Almost feels like a bait and switch. GitLab is now completely uncompetitive with GitHub in terms of price structure. 4-5x on monthly cost.
Github is deeply subsidized by Azure's marketing budget and benefits from larger scale. Gitlab can't compete head-to-head; they'll have to pivot or partner soon.
Earlier quoted context omitted.
What about Bitbucket?
I don't know. But I am desperate to find a good github alternative, so thanks for the suggestion. But at the same time isn't it quite easy to set up a github server?
I'm unsure of how big the divide on features is.
Earlier quoted context omitted.
We have an entire team of people responding on social and I wanted them to be the DRI https://about.gitlab.com/handbook/people-group/directly-resp... I think the blog post with me as the author https://about.gitlab.com/blog/2021/01/26/new-gitlab-product-... and the FAQ https://about.gitlab.com/pricing/faq-new-product-subscriptio... answer most questions. But happy to answer any other questions.
That was not the point. I was commenting on my perception of your different level of engagement. And a quick search with algolia justifies that : there are very little Gitlab threads where you have been absent.
Because of the expected volume we had a different process for responding on social yesterday and I wasn't part of that group.
We're currently using the starter edition for exactly one reason, ldap integration. Now we're supposed to pay $240 / employee for an ldap integration?! Not sure what we'll do but I suspect scripting some ldap integration into our gitlab will be one of the best spent times in terms of ROI for me this year.
$240 a year (per engineer) to keep your engineers focusing on providing product value is beyond paying for itself. Building custom in house tooling always costs 5x more than engineers believe, and ultimately doesn't improve your end product. This kind of tooling would probably require at least 100 engineers to justify the innate cost of building and maintaining it.
Realistically that takes a lot less than a fulltime engineer to support.
Of course this assumes no other value is acquired from the license, but if we take the comment at face value it seems worthwhile to just add it yourself.
This means they have no doubt in this particular case.
I guess we also can doubtlessly deduce what to think then.
Earlier quoted context omitted.
What about Bitbucket?
I don't know. But I am desperate to find a good github alternative, so thanks for the suggestion. But at the same time isn't it quite easy to set up a github server?
> But at the same time isn't it quite easy to set up a github server?
I suspect a typo here - is on premise github a thing? [ed: judging by other comments github enterprise allows self-hosting - but unlike gitlab there's no Free software version]. Fwiw setting up a gitlab server is indeed quite straightforward.
Everyone who are finding the pricing too high: care to share why you're not hosting/running your own gitlab instances?
Everyone who are finding the pricing too high: care to share why you're not hosting/running your own gitlab instances?
Earlier quoted context omitted.
$240 a year (per engineer) to keep your engineers focusing on providing product value is beyond paying for itself. Building custom in house tooling always costs 5x more than engineers believe, and ultimately doesn't improve your end product. This kind of tooling would probably require at least 100 engineers to justify the innate cost of building and maintaining it.
At 1000 engineers, that's a fulltime engineer to support the "ldap+gitlab community fork"... Realistically that takes a lot less than a fulltime engineer to support. Of course this assumes no other value is acquired from the license, but if we take the comment at face value it seems worthwhile to just add it yourself.