Before you think of switching to GitLab, look at their status Twitter account over the past few months. They've had a lot of down times. They run on Microsoft Azure.
> They run on Microsoft Azure. What does this have to do with anything? Are you suggesting that service run on Microsoft Azure are not stable?
Dear open-source maintainers, a letter from GitLab
81–90 of 325 posts
Re: Dear open-source maintainers, a letter from GitLab
#82This attempt by the Gitlab folks to ride the Github dissatisfaction wave seems a little low-brow. Why respond to a letter that's not addressed to you? I would have preferred them to simply post an honest "Why you should migrate from Github to Gitlab" article. The tone just seems a little devious to me. By the way, we're using self-hosted Gitlab at work and we love it. This isn't a knock against the actual product. In…
> This attempt by the Gitlab folks to ride the Github dissatisfaction
> wave seems a little low-brow.
There's a github dissatisfaction wave?Anyway, opening sentence of gitlab's open letter: "The letter of GitHub’s open source community is clearly not addressed to us, but we’re thinking a lot about the issues that were mentioned in it."
Does that cover your concerns?
I think if github was the free software entity, and gitlab had no free software edition available, then the tone would be, as you suggest, totally inappropriate. However given the arrangement is the other way around, it seems quite reasonable they would hop onto this issue at this time, especially given the very clear caveat quoted above.
Re: Dear open-source maintainers, a letter from GitLab
#83Re: Dear open-source maintainers, a letter from GitLab
#84Earlier quoted context omitted.
A good friend of mine likes to run https://gogs.io/ .. I havent used it heavily but Ive been impressed so far.
I was unaware of this. Thanks for the link. It seems just about everything is being re-written in Go these days...
Re: Dear open-source maintainers, a letter from GitLab
#85I don't think the fact that GitLab is free for basic users is very discoverable from the site. You've got the "features" tab, which leads to what seems to be the option of downloading a community edition, which makes it look like GitLab is only offering the code itself but not hosting from their, and the enterprise edition for some licensing fee (I suppose). Then you've got "sign in", but no "sign up", which leads me…
Visiting www.gitlab.com redirects me to https://about.gitlab.com/ . There are three big options: 1. Community edition 2. Enterprise edition 3. On our server The 3rd option has this text: Free hosting for private repos? Sign up to get unlimited repos and collaborators. Clicking on Sign up takes me to https://gitlab.com/users/sign_in which has clear options to sign in or sign up. It also has the text: GitLab.com offers…
Re: Dear open-source maintainers, a letter from GitLab
#86Earlier quoted context omitted.
> Is there a reason why you didn't use GitLab.com, which runs EE and thus has Repository Mirroring? 1. My hosting is way more reliable than yours :-) 2. I need to host the CI runners myself anyway, because you don't have the right config 3. I already have a private GitLab install, so it's no extra trouble 4. My repository mirroring is quite a lot better than yours, as it's instant, not hourly 5. I prefer to have a co…
> 1. My hosting is way more reliable than yours :-) You've got me there :) I'm sure your aware of our intention to greatly improve GitLab.com reliability and performance in Q1 2016: https://gitlab.com/gitlab-com/operations/issues > 4. My repository mirroring is quite a lot better than yours, as it's instant, not hourly Heh, care to share? :) Maybe we can take some pointers from your implementation. How does your repo…
Bingo. Full implementation, in Bash: http://faq.sealedabstract.com/gitlab_mirror/
> What are you afraid of?
Mostly, that you'll get bought by the likes of Oracle. In spite of my quibbles about CE features, I think you're doing a (mostly) fine job of CE right now. But your acquirer will see CE as a cost center (there's no revenue) and will want to "streamline" by focusing on enterprise (where your balance sheet is). GitLab.com will also look like a cost center, and will either shut down, turn into a datamining opportunity, or go through the bad PR of no longer being free. I fully anticipate, in 5-10 years time, that I will be running a CE fork to get out from under your acquirer, just like StarOffice, MySQL, Hudson, etc.
Contrast with GitHub, who makes a silly amount of money from people like me. Their acquirer would be mad to screw up a winning formula.
The good news is, GitLab is such a good product that I still hugely prefer it even after "pricing in" the risk (cough, certainty) that my days are numbered. It is an amazing tool, it really shows that you care about it. For now.
Re: Dear open-source maintainers, a letter from GitLab
#87Meanwhile, Phabricator has implemented all of these (and even more). Custom templates: https://secure.phabricator.com/book/phabricator/article/form... Votes: https://www.mediawiki.org/wiki/Phabricator/Tokens It's better in almost every aspect than GitLab and GitHub. See https://en.wikipedia.org/wiki/Phabricator for an (incomplete) list of open source projects using it.
Also, do they pride themselves for writing this in PHP? I consider this an anti-feature, but this might be highly opinionated.
Re: Dear open-source maintainers, a letter from GitLab
#88Earlier quoted context omitted.
I think they mean you can download the free community edition and host that. Why do you feel you need to pay for the EE version?
If I have to host myself, why won't I simply host Git? The point of these services is peace of mind. If I'm managing on-prem, it kind of kills the point.
Re: Dear open-source maintainers, a letter from GitLab
#89I still don't know how I feel about GitLab. My initial reaction was that they were an underhanded, cheap knockoff of GitHub. It felt kind of dirty, like they were stealing GitHub's thunder and giving it away for free. Then they started charging for enterprise features and turned it into a business, which felt even weirder. And then they raised a lot of money, which kind of made them seem more legitimate. And now this…
On EE, there's nothing that we miss from the EE version, although we might end up going with EE after the team will grow. We also have dedicated dev-ops, otherwise having support for it would sounds good. And the pricing for EE if you go that route is much better than for GitHub Enterprise.
Personally I have mixed feelings about the "open core" model, as many times it's just a marketing stunt. But for now that's not the case with GitLab.
Re: Dear open-source maintainers, a letter from GitLab
#90This attempt by the Gitlab folks to ride the Github dissatisfaction wave seems a little low-brow. Why respond to a letter that's not addressed to you? I would have preferred them to simply post an honest "Why you should migrate from Github to Gitlab" article. The tone just seems a little devious to me. By the way, we're using self-hosted Gitlab at work and we love it. This isn't a knock against the actual product. In…
That's basically what they did. They said "hey, you have these issues with GitHub, we're covering them, AND we listen to the community".
I think it's great that they responded to it, since it proves they actually listen and care about what their audience thinks.