Live data from Hacker News

Dear open-source maintainers, a letter from GitLab

about.gitlab.com

151–160 of 325 posts

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

#151
post #134

Any chance you can support Mercurial? There was a highly voted issue that I saw sometime back.

We'll not support Mercurial, this would be an additional layer of indirection and limit us to features that are supported in both Git and Mercurial.

Maybe just support hg-git? All someone has to do is write some tests for Gitlab, and then you are all set?

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

#152
post #129

Please improve your mobile UI - phones have lesser horizontal space than vertical. You have put a cool looking sidebar on the left side which takes up a lot of space causing text layout to be funny on my 5.2 inch LG G2. Github OTOH has an extremely usable mobile UI.

You should be able to collapse the left sidebar. But we are the mobile UI has deteriorated in the last few releases and we plan to look into it in the coming months. If you want to get paid to contribute, we're hiring front-end engineers https://about.gitlab.com/jobs/

Thanks for that offer. Already have my hands full. Look for me on Bookface ;)

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

#153
post #147
post #136

Earlier quoted context omitted.

Thanks a lot for the answer and the proposal. But we do not want to have anything critical that is not open source. We try to promote OpenSource, so using non-open-source software is hard to do. 1. Thanks, but see above :) 2. As I said, custom labels are way too limited, as people on the open-letter-to-github said, so I will comment on the issue. 3. Will do. 4. same as 1 :) But thanks a lot. I will contact you :)

Thanks, I get that you don't want to be on proprietary code. I'm look forward to your email. And we're open to discussing open sourcing features if that is needed.

I don't know if that would apply to GitLab too, but maybe consider switching from the CE / EE model to just one "product" and a free for non-commercial model? Like e.g. http://3t.io/mongochef/download/ does it? I like that model way more than a feature-reduced version.

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

#154
post #147

Earlier quoted context omitted.

Thanks, I get that you don't want to be on proprietary code. I'm look forward to your email. And we're open to discussing open sourcing features if that is needed.

I don't know if that would apply to GitLab too, but maybe consider switching from the CE / EE model to just one "product" and a free for non-commercial model? Like e.g. http://3t.io/mongochef/download/ does it? I like that model way more than a feature-reduced version.

We considered that but we value having a completely open source version for all projects more. For more information about how we see the difference between CE and EE please see https://about.gitlab.com/about/#stewardship

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

#155
post #129

Earlier quoted context omitted.

You should be able to collapse the left sidebar. But we are the mobile UI has deteriorated in the last few releases and we plan to look into it in the coming months. If you want to get paid to contribute, we're hiring front-end engineers https://about.gitlab.com/jobs/

Thanks for that offer. Already have my hands full. Look for me on Bookface ;)

Sorry, I missed that you're YC too :)

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

#156
post #134

Earlier quoted context omitted.

We'll not support Mercurial, this would be an additional layer of indirection and limit us to features that are supported in both Git and Mercurial.

Maybe just support hg-git? All someone has to do is write some tests for Gitlab, and then you are all set?

Interesting, feel free to make a detailed technical feature proposal on https://gitlab.com/gitlab-org/gitlab-ce/issues and mention me.

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

#157
post #139
post #65

Somebody just spammed their Issues page[1]. The one they link to in the letter. I think the spammer is trying to make a point! For starters, there seems to be no rate limit applied. [1] https://gitlab.com/gitlab-org/gitlab-ce/issues

GitLab has rate limiting on the API http://doc.gitlab.com/ce/security/rack_attack.html but by default we set it pretty high.

We added recaptcha a week ago and will merge akismet and RBL support this week to reduce spam.

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

#158
post #127

Earlier quoted context omitted.

[videolan infra guy here] The whole idea of VideoLAN infrastructure migration from gitweb/trac/etc to gitlab and not to github was to use and promote free and open-source software. Using closed-source software there is out of question, really.

Gitlab EE is actually open source. https://gitlab.com/gitlab-org/gitlab-ee

If you need help on the difference between "publicly viewable" and "open source" see this answer to a related question on the Open Source Stack Exchange: http://opensource.stackexchange.com/questions/2338/can-i-use...

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

#159
post #22
post #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…

Have you tried using BitBucket?

We use BitBucket extensively at my company for two reasons: Mercurial support and Unlimited private repositories.

The mercurial support is great because of legacy code (I finally have come to admit that Git is superior for most purposes). The unlimited private repositories is great because we make loads of projects. I came from so many companies that would have this giant monolithic tree of tangled dependencies because they would check everything into one project. I fear this with GitHub's pricing model.

I find BitBucket's dashboard useless. It used to be decent but they changed it some years back. BitBucket's security was sort of disturbing as well but I believe they have added 2 factor authentication.

I will say that Atlassian's Jira used to be the best bug tracking but I have found that in the last couple of years it has become a complete bloated pig that is overly complex and slow. The hosted Jira is so awful that we contemplated just using BitBucket for bugs. We eventually switched to Youtrack and are loving it.

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

#160
post #70

This 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…

Since they have employees and apparently are an ongoing business concern I would be worried if they didn't try to get their name in the conversation. If they let this huge discussion go by the wayside silently then they would be incompetent business people.
Post reply on HN