Our University recently moved from SVN to self-hosted Gitlab for internal projects It integrates nicely with our LDAP server so that you can easily search for collegues and students to add them to projects. I totally love it. It's probably not a coincidence, as Gitlab used to be Utrecht-based if I recall correctly. Just want to thank you guys for not having to use SVN for my graduate project.
Choose GitLab for your next open source project
191–200 of 289 posts
Re: Choose GitLab for your next open source project
#192Earlier quoted context omitted.
Thanks for your question! We're a VC backed startup so we have to have a so called liquidity event at some point. As explained on https://about.gitlab.com/strategy/ our goal is to IPO instead of being aquired. This will ensure we can preserve our culture, mission and goals. There will always be an open source version of GitLab, more than 1000 people contributed and it the most popular self-hosted option, used on-prem…
> IPO > preserve our culture, mission and goals. Pick one. Or is there a historic precedent I'm unaware of? On a serious note, the shift in the latter parameters can be smaller than in an acquisition, but to "preserve" would imply actively managing employee (and founder) expectations in the build-up to IPO.
Re: Choose GitLab for your next open source project
#193Is there a way to port publicly viewable github issues and PRs over to gitlab automatically?
Re: Choose GitLab for your next open source project
#194Our local instance is only a version back but we find gitlab to be terrifically slow, and regularly have to kick the server as we find it stops tracking updates, then simply stops responding at all. Also, the diffing on merge requests is simply awful. It regularly shits itself on spacing changes and the like making most merge requests almost useless from a code review perspective. Searching just doesn't work. At all.…
I have to agree regarding the slowness, and although we do have many repositories (~100) and the machine only has 2GiB of RAM, it does feel slow for a service that sits idle 90% of the time, and almost never gets concurrent user access. We're on 8.0.0, so maybe it has gotten better. That said, are you sure you don't have a very old version? There is a simple path for accessing code in a branch, you can just click the…
Re: Choose GitLab for your next open source project
#195Earlier quoted context omitted.
I have a single concern about GitLab. Looking at https://about.gitlab.com/direction/ , I feel like there is way too much being labeled as EE only. I understand that GitLab has to make money to survive, however I see a lot of those features as things that are relevant to pure open source projects (private issues are something Open Source projects do actually need for security, think Chromium) and should probably be in…
Thanks for the feedback and for listing the features that you are concerned about. The squash functionality is likely to stay EE only since it is similar to rebasing. Rebasing is EE only because larger enterprises are more likely to have this workflow. Regarding the 'test the merge' functionality I've only heard requests from large organizations for that, can you detail the context in which you want to use it? The co…
'Test the merge' is something that we already get from GitHub. Travis CI tests both the merge and the branch itself. I think it only makes sense to test both, in fact, if I were to choose one way for a Merge Request, I would just test the merge result.
We have IoT Platform SDKs (See https://github.com/IOT-DSA/sdk-dslink-dart and https://github.com/IOT-DSA/sdk-dslink-java for examples) that at somepoint I would like to pitch the idea to move from GitHub to GitLab fully. We currently utilize GitLab for only a portion of our projects. We find it really helpful that Travis CI tests both the merge result and the branch, and even though I could look over it to switch GitLab (because let's face it, GitLab > GitHub), I would love to be able to tell the other developers that they will only be gaining functionality.
As for the code analytics, I have second guessed myself, and I completely agree with you now. This is definitely something that I see most useful in the enterprise setting.
Re: Choose GitLab for your next open source project
#196I for one am a very happy user of Github. Two mid size open source projects, dozens tiny ones and a few commercial private repos. Github has private repos you just need to pay for them and they are actually very affordable. I've seen developers who make >100 per hour choose bitbucket because they don't want to pay for private repos. How is that rational...? I like Github and I like paying them for a service I use eve…
I guess I could make some public, but not open source, but that seems like an odd solution too. And I don't want to be publishing homework assignments for others.
Re: Choose GitLab for your next open source project
#197Albeit, I am little disappointed because I have finally started getting into open source and being active on GitHub, and now it seems the development community is vying for a way out. GitHub may not be open, it may be centralized, but it does offer the advantages of uniformity and easy discovery.
Re: Choose GitLab for your next open source project
#198Earlier quoted context omitted.
> IPO > preserve our culture, mission and goals. Pick one. Or is there a historic precedent I'm unaware of? On a serious note, the shift in the latter parameters can be smaller than in an acquisition, but to "preserve" would imply actively managing employee (and founder) expectations in the build-up to IPO.
I agree that as a company grows the culture will always change, there is no standing still. But we're very active in spreading and prioritizing our values. For information about our values please see https://about.gitlab.com/handbook/#values
Re: Choose GitLab for your next open source project
#199Our local instance is only a version back but we find gitlab to be terrifically slow, and regularly have to kick the server as we find it stops tracking updates, then simply stops responding at all. Also, the diffing on merge requests is simply awful. It regularly shits itself on spacing changes and the like making most merge requests almost useless from a code review perspective. Searching just doesn't work. At all.…
Re: Choose GitLab for your next open source project
#200GitLab CEO here. Awesome to see this article! Ask me anything.
I am currently very happy with my self-hosted GitLab instance for my personal projects. But I would love to have some of the EE features (both for my workflow and experience working with enterprise tools) and I'm willing to put my money where my mouth is. However open source is very important to me so my question is do you think it would ever be possible to purchase a personal use EE instance without license keys, calling home, and under an open source license?