Thank you GitLab for being yet another option, and for at least maintaining one Open Source version of your software at the very least.
You're very welcome!
Dear open-source maintainers, a letter from GitLab
261–270 of 325 posts
Re: Dear open-source maintainers, a letter from GitLab
#262Earlier quoted context omitted.
GitLab.com is completely free, and has both unlimited private repositories and unlimited collaborators!
Except that it's unreliable, the website says so. Let me ask again, is there any plan without $390 onboarding provided by Gitlab that gives me following features: 1. Hosted Git. 2. Reliability. There is none. I don't know why you seem to be trying to deny it. Your business obviously works with Enterprise. If I was a big corp, I'd be all over you. I'm not sure with Gitlab's compulsion with trying to make everyone happ…
If you want reliable hosted Git right now consider https://githost.io/ (single tenant)
And we're working hard to make GitLab.com reliable, fast and free too.
Re: Dear open-source maintainers, a letter from GitLab
#263Earlier quoted context omitted.
GitLab.com is completely free, and has both unlimited private repositories and unlimited collaborators!
Ignoring the name... are there any plans to make GitLab Mercurial capable? We still have Mercurial repositories and still sort of like Mercurial.
We'll not support Mercurial like we support Git, doing both would limit us to the features that are supported in both.
Re: Dear open-source maintainers, a letter from GitLab
#264Earlier quoted context omitted.
That's great to hear. Any way we can improve web hooks for you?
Arguments from the project/push add to url would be great! A page outlining why you are better than gitblit would help with clients :-) (who are all possible future EE users)
Thanks! I created an issue here [0], I'd love it if you could clarify it a bit there.
I think we can do better in our comparisons with competitors. I created an issue [1]. I haven't heard someone asking before about a comparison with Gitblit. Please feel free to email me at job at companyname dotcom if you'd like me to discuss it with your clients.
[0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/10860
[1]: https://gitlab.com/gitlab-com/www-gitlab-com/issues/514
Re: Dear open-source maintainers, a letter from GitLab
#265My 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. Go…
> one of the reason is that I fear that Github contains too many projects and gains too much control over OSS I don't understand this fear. All repositories on GitHub can be hosted elsewhere. Moving metadata (e.g. issues, milestones, PRs, etc.) is more difficult but mostly possible. Disclaimer: I like that GitHub is the "central" place for OSS, it makes my life much easier. I know how to use the product very well and…
> Moving metadata (e.g. issues, milestones, PRs, etc.) is more difficult but mostly possible.
I'm curious as to how people tend to go about doing this. Any recommendations?
Re: Dear open-source maintainers, a letter from GitLab
#266Earlier quoted context omitted.
> one of the reason is that I fear that Github contains too many projects and gains too much control over OSS I don't understand this fear. All repositories on GitHub can be hosted elsewhere. Moving metadata (e.g. issues, milestones, PRs, etc.) is more difficult but mostly possible. Disclaimer: I like that GitHub is the "central" place for OSS, it makes my life much easier. I know how to use the product very well and…
> Moving metadata (e.g. issues, milestones, PRs, etc.) is more difficult but mostly possible. I'm curious as to how people tend to go about doing this. Any recommendations?
GitLab has an importer for GitHub repo's, issues, pull requests and in 8.4 (out on Jan 22) wiki's.
Re: Dear open-source maintainers, a letter from GitLab
#267GitLab could differentiate their service by offering IPv6 support, which GitHub has so far declined to do.
Cool, I created an issue https://gitlab.com/gitlab-com/operations/issues/43
Thanks, subscribed. When Google Code shut down, I migrated the IPvFoo[1] source code to GitHub, but it felt dirty using an IPv4-only service for that purpose; I'll probably move again to GitLab if they follow through.
Re: Dear open-source maintainers, a letter from GitLab
#268Earlier quoted context omitted.
By the way, I don't want to troll you, but at my company we use Gitlab 6 self hosted version and I wasn't able to do a simple git push origin master the repo I held in my machine was barely 5MB and still remote server closed connection HTTP 500 I solved it by increasing the POST buffer. I never had this issue with github, maybe you can check why it was an issue with gitlab? it might help to advance your product!
Thank you for feedback. We improved git push a lot since version 6. So when you update to recent version it should not be a problem anymore.
cool
Re: Dear open-source maintainers, a letter from GitLab
#269Earlier quoted context omitted.
> If this is essential for you we'll give you a free lifetime license for GitLab EE. While I get the sentiment, I don't think this helps. If you want to help the Open Source community, give us what we need in the form of open source. If I don't care about vendor lock-in I can go ahead and use GitHub. GitLab counts because its open source, and its open source version is the only thing the open source community should…
That makes sense and we want to make sure GitLab CE is a great solution for open source projects. If there is an EE feature that is would come up frequently in these conversations we would not hesitate to open source it.
I'm seeing you post this a lot, which is great. I hope the people you are responding to are doing their part!
Re: Dear open-source maintainers, a letter from GitLab
#270Earlier quoted context omitted.
To be clear, it doesn't support issue tracking because it is an Atlassian project. Issue tracking is done through Jira, another product they offer.
Umm no, you are incorrect. Bitbucket does have its own issue tracker like GitHub.. (but it is not turned on by default) and what I am referring to is NOT JIRA Software. https://confluence.atlassian.com/bitbucket/enable-an-issue-t...
That looks to be for Bitbucket Cloud. We were discussing Bitbucket Server, the hosted solution.