Live data from Hacker News

Dear open-source maintainers, a letter from GitLab

about.gitlab.com

11–20 of 325 posts

Re: Dear open-source maintainers, a letter from GitLab

#11
post #7
post #5

Just for this, I'm tempted: One issue that was raised several times was the ability to not create merge commits. In GitLab you can, as an alternative to the merge commits, use fast-forward merges or have merge requests be automatically rebased. The main thing keeping me from actually doing it is the network effect... and this: Disadvantages Right now GitLab.com is really slow and frequently down. This is because of f…

Only in the enterprise edition though.

No the efforts are for .com https://gitlab.com/gitlab-com/operations/issues/42

Re: Dear open-source maintainers, a letter from GitLab

#12
post #7
post #5

Just for this, I'm tempted: One issue that was raised several times was the ability to not create merge commits. In GitLab you can, as an alternative to the merge commits, use fast-forward merges or have merge requests be automatically rebased. The main thing keeping me from actually doing it is the network effect... and this: Disadvantages Right now GitLab.com is really slow and frequently down. This is because of f…

Only in the enterprise edition though.

GitLab.com runs GitLab EE. So - if you compare features of github hosted and gitlab hosted, it's best to compare EE. (For example, GitLab.com hosts private repos, for free, and it's EE.)

Re: Dear open-source maintainers, a letter from GitLab

#13
My company with ~300 developers are moving to Gitlab in the next few months. Today our CTO/PM shared opinion about Gitlab and he was very happy we're doing it, even better I recommended it to him :)

I'm a Gitlab users for a few years now, personally I like it much more than Github, one of the reason is that I fear that Github contains too many projects and gains too much control over OSS, I also dislike their CoS.

Good luck Gitlab!

Re: Dear open-source maintainers, a letter from GitLab

#14
I 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 letter, which changed my perspective quite a lot. I didn't know that had features like voting on issues, and issue templates.

So now it even feels like they're doing Git hosting the right way, making the core software open source, and charging for enterprise features.

On the other hand, I would have probably never paid for GitHub if they followed this model. So I don't think GitHub would have been as successful.

Re: Dear open-source maintainers, a letter from GitLab

#17
Both products are really good, but Github needs to realise that they have to be more open and listen more to their users.

There is an opportunity for Gitlab here and I'm happy that they decided to make this announcement.

The community is the actual winner of this healthy competition.

Re: Dear open-source maintainers, a letter from GitLab

#18
post #5

Just for this, I'm tempted: One issue that was raised several times was the ability to not create merge commits. In GitLab you can, as an alternative to the merge commits, use fast-forward merges or have merge requests be automatically rebased. The main thing keeping me from actually doing it is the network effect... and this: Disadvantages Right now GitLab.com is really slow and frequently down. This is because of f…

Just wanted to point out the disadvantage statement came from https://about.gitlab.com/gitlab-com/

At GitLab we are honest about issues, and transparent about what we're working on. HTH!

Re: Dear open-source maintainers, a letter from GitLab

#19
post #5

Just for this, I'm tempted: One issue that was raised several times was the ability to not create merge commits. In GitLab you can, as an alternative to the merge commits, use fast-forward merges or have merge requests be automatically rebased. The main thing keeping me from actually doing it is the network effect... and this: Disadvantages Right now GitLab.com is really slow and frequently down. This is because of f…

Just wanted to point out the disadvantage statement came from https://about.gitlab.com/gitlab-com/ At GitLab we are honest about issues, and transparent about what we're working on. HTH!

Thank you for your transparency, it means a lot! :)

Re: Dear open-source maintainers, a letter from GitLab

#20
> "Right now GitLab.com is really slow and frequently down. This is because of fast growth in 2015. We are working to improve it in the first quarter in 2016. For now please consider downloading GitLab and using it on-premise for a fast experience."

Is this a joke? I mean for people looking for free private Git hosting, there is Bitbucket. This statement is like saying "free, but not really, really." The fact is if I want hosted Git hosting from Gitlab, I cannot reliably get it without paying at least $390 upfront for their EE plan. Too much smokescreen, too less actually on offer.

Post reply on HN