61–70 of 148 posts
I find Gitlab UI quite a bit bloated and slow compared to Github. They have some amazing features but I can't get past how many (2-5 seconds) to load a page and sometimes upto 10 seconds (analytics). I hope that's being addressed in future. Usually, I spend at least 2 hours on Github in a given day - and probably access the website about 50 times a day or more. These UI issues add up tremendously.
Earlier quoted context omitted.
This past year, on my Thinkpad P50, I've switched between Ubuntu, Fedora, and Arch; Arch has by far been the least buggy. With Ubuntu, things would go haywire when docking/undocking. With Fedora, putting it to sleep was always a risk because after putting it to sleep I would sometimes I would open up my laptop to a black screen that I couldn't recover from. I was fine with that and just wouldn't put my laptop to slee…
This fragmentation between what works on what dists makes me sad. Philosophically I've always admired BSD for the consistency, considering how there's just 3-ish of them, realistically I'm a Manjaro user as I don't have enough Linux-fu to set Arch up.
Earlier quoted context omitted.
GL is not browsable with JavaScript disabled while GH is.
Why is this a hard sell? How many people does this really affect? And why disable JS on GL?
Great news :) We switched to Gitlab at Arch Linux recently as well: https://gitlab.archlinux.org/ (well, we're still migrating projects and users, it's a long process)
Earlier quoted context omitted.
This past year, on my Thinkpad P50, I've switched between Ubuntu, Fedora, and Arch; Arch has by far been the least buggy. With Ubuntu, things would go haywire when docking/undocking. With Fedora, putting it to sleep was always a risk because after putting it to sleep I would sometimes I would open up my laptop to a black screen that I couldn't recover from. I was fine with that and just wouldn't put my laptop to slee…
This fragmentation between what works on what dists makes me sad. Philosophically I've always admired BSD for the consistency, considering how there's just 3-ish of them, realistically I'm a Manjaro user as I don't have enough Linux-fu to set Arch up.
At one CCC event there was a talk about a security vulnerability and it was interesting to see how the response times of the different BSDs was and how they tackled the security fix.
Is there any resource somewhere explaining why they migrated away from gitolite ? Not trying to sound negative, I'm just interested in the reasoning behind and see what really differentiates the two in this kind of usage.
My first hot guess would be: "issues". Gitolite is just managing raw git repositories. I'm using gitolite for personal (read: non-public) projects, and I wouldn't want to use anything else. I love how minimal it is, and the way it works. However, how do you manage issues? Bugzilla is, IMHO, horrible. You can replace it with something much more lean, such as Mantis, but you still lack true integration with the reposit…
Earlier quoted context omitted.
This fragmentation between what works on what dists makes me sad. Philosophically I've always admired BSD for the consistency, considering how there's just 3-ish of them, realistically I'm a Manjaro user as I don't have enough Linux-fu to set Arch up.
Honestly you don't need any particular skills to install Arch. Just time and access to the instructions. It's a neat way to spend an afternoon once, but I just switched to Manjaro too on future installations,
Soon-ish™
Earlier quoted context omitted.
I'd love to hear more about what you dislike about merge request reviews. At work we've been talking about migrating looking for alternatives to GitHub over dissatisfaction with its code review interface, and, of course, GitLab is on the list of ones to check out.
In my experience, GitLab's MR UI really lacks performance when the diffs pass a certain length. Similarly sized diffs in GitHub don't seem to have this problem, though. I think of it as additional incentive to maintain smaller patches for ease of review, but sometimes changes are necessarily large due to complexity. It can be obnoxious to be hamstrung like this.
Great to see GitLab gain momentum in FOSS. It's a great fit for small teams too, it's easy to setup and keep updated. It's more important than ever to help GitLab gain adoption with GitHub making it free for private repos. I love GitHub as much as any developer, but I believe having a free, open alternative to it is important. I wish GitLab would improve their free-version of Merge Request reviews though, Github's is…
I'd love to hear more about what you dislike about merge request reviews. At work we've been talking about migrating looking for alternatives to GitHub over dissatisfaction with its code review interface, and, of course, GitLab is on the list of ones to check out.
My git-fu is average level so its possible that I’m missing something obvious here. For me the easy solution is to just merge on the command line.
Earlier quoted context omitted.
This fragmentation between what works on what dists makes me sad. Philosophically I've always admired BSD for the consistency, considering how there's just 3-ish of them, realistically I'm a Manjaro user as I don't have enough Linux-fu to set Arch up.
Honestly you don't need any particular skills to install Arch. Just time and access to the instructions. It's a neat way to spend an afternoon once, but I just switched to Manjaro too on future installations,