Xfce switches to GitLab
simon.shimmerproject.org
simon.shimmerproject.org
I still have an issue where the system is not detecting when my laptop lid closing but at least it's not crashing every day or two.
There are some apps which I have to install outside the regular repositories (RStudio, Google Chrome, Zoom, etc.) but they all provide binaries specifically for Debian, and it seems this is becoming more commonplace. I recently installed Mattermost for a client on Debian Stable, and it was trivial given their provided binary and instructions. Time is valuable, folks.
More contributors are always needed and welcome.
Soon-ish™
If you want to investigate what you're executing in your system, as opposed to find what fedora does under the hood during install, you might find Arch install is nice an simple.
what use is that consistency if even all combined together they only support a percent of the consumer hardware support that the average Linux distro has though ?
The year of the Linux desktop will be 2021! /s
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.
I wouldn't call FreeNAS/TrueNAS and pfSense distros in the sense of a Linux dist (since they are non generic, I see them as an "application" that happens to include an operating system).
"All" "distro bsds" seem to follow FreeBSD very closely and building upon it rather than modifying it (providing installers and such while still being a true FreeBSD).
Dragonfly being the exception here, don't know enough about it.
Disclaimer: I'm no expert and do not mean to step on anyones toes.
E.g. you have some new-ish hardware where the most recent kernel (packaged in Arch) includes fixes.
I wish GitLab would improve their free-version of Merge Request reviews though, Github's is much much better right now.
If you're on GitHub Enterprise, availability will depend on the last time your company has installed updates.
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.
My decades-long complaint with every single code review system I've been forced to use at my workplaces (which no system I've seen fixes so far) is that they don't let you browse code and examine the diff in its native setting, so to speak.
'Cuz yeah, I've seen some nasty stuff sail past code review simply because it's so easy to accientally miss those files.
I feel like everything about the GitHub PR UI is targeted at reducing the code review job to being a human style checker. Minimal context, no code navigation, abysmal rename following.. it's really hard to review the design of a change.
Though it can certainly hide much more relevant-to-reviewers changes easily.
It could be a little while before global code search is available to non-paid users, according to their search roadmap documentation[1].
Although not at GitLab.com scale, I've worked on a few search-related projects (often using Elasticsearch) in the past and would consider offering some ideas.
Does GitLab have a policy for attribution/licensing of technical design input from external contributors? (this is partly out of curiosity in general -- I don't know for sure whether I'd have anything to add that your team wouldn't already have thought of themselves)
We always welcome the sharing of ideas and feedback. Just tag me on anything I should review. GitLab ID is @JohnMcGuire
We love external contributions. This page should help answer questions about contributing. https://about.gitlab.com/community/contribute/
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.
I'm always curious why open source projects don't embrace an open platform, although I get that GitHub is fantastic in a lot of ways. I'm guilty of it myself, but I've reached the 50/50 GL/GH split as I try using GL more.
Yes, GitHub absolutely has a bunch of annoyances, too. (I listed a bunch of them here on HN in response to a question by Nat, just the other day!) If everyone were using GitLab first, we'd probably find excuses to put off switching to GitHub, too.
To attract users, you've got to have a pull. If that's "open source", then it needs to be a way in which the closed-source nature of GitHub is hurting my daily workflow. If it's "user interface", you need to be such an improvement over GitHub that it's worth the cost of switching. If it's "cost", that's tough because GitHub dropped prices and is now $0 for many users, and you probably don't want to get in a price war with Microsoft (see: Netscape).
It doesn't have to be the same pull for every customer, but every customer needs at least one.
"We're just as good as that big popular project" isn't a pull. I've seen hundreds of projects try that, and it never works.
1) it had a message that tells you that the elastic search is so much better and that your admin can enable it (if he would only switch to enterprise)
2) it pretends to have functionality only to have it hidden behind an "available in ee" banner
3) it has a new functionality where it annoys everyone that has a new ip (24h disconnect anyone) that can't be disabled (only through patching) and suggests that enabling 2fa helps, but is send regardless of 2fa
And every function that gets cut out and hidden behind the enterprise banner iy forever lost to you, because even if you implement it yourself it will nevet get merged since the function exists, in enterprise...
Ps yeah there is a free enterprise license for universities, but it is not available for staff or external users (other universities) and the licensing model is so unflexible that you can't mix "free for students" and "pay for staff" or "students get enterprise" and "staff get basic features"
Pps I had to patch out more than one thing over the years this was just the first thing that came to mind
I'm really interested in the development of this issue so thank you again for reaching out.
GitLab doesn't serve ads it only pushes out messages to users that they could have a better product if only the admin would shill out some bucks.
It's ok if admin settings are greyed out with a remark like in old freewares to tell you features you could have in the enterprise product, but if the software tells any user that they are missing out it is more unnescessary work for the admin to explain that we don't have the money to pay for every single student, most of which only create an account without pushing any code, just so that the search can work over all wikis and not only the selected one.
So again it's more like the "buy winrar" or "go pro now" nag and _not ads_. Sorry for the confusion
I understand your frustration with FOSS pushing you toward buying proprietary software.
But your lede will mislead people into thinking CE gets revenue by serving up third-party ads because that is what "ads" mean for web services 99.99% time the term is used on HN.
On a positive note it got quite a bit more responsive in the last 4 or 5 five years since I started hosting it and even thought we got some regressions and bugs and problems with releases we didn't have any data loss (that we know of) or major security problems. Most of the security problems are in the enterprise functionality anyway (elasticsearch and grafana pop up regulary)
git remote set-url --add origin ...
Or, I would have, if the builtin GitLab mirroring feature wasn't broken for pushing to GitHub.
git checkout master
git pull github/master
git push gitlab/master
And you don't exactly want to pitch to them how you don't have your code on Github because you use this other "fringe" service which even if they look at it they are going to find unfamiliar.
I now host 50/50 on Gitlab / Github because I'm not really affected by this, but I'm conscious of it.
It's very easy to deploy, consumes few resources (you can run it on a low-end VPS). It even has Jenkins integration.
However I don't know how it scales to big teams and projects since I only use it for myself. And I'm not entirely convinced by its security track record, but it looks like things are improving.
It makes the modern web so much more pleasant, paradoxically by breaking it, now that user-hostile machinations are the norm.
And yes, gitlab's web interface is substantially more annoying than github, in my experience.
However, I think GitLab can only really shine when you host it yourself. In 2020, on-premise/self-managed anything is kind of a hard sell, but the reliability and performance of gitlab.com leaves a lot to be desired. (So much so, I often think about trying to work for GitLab so I could help from a reliability perspective.) I stuck my neck out for GitLab in a previous organization and we ended up migrating from github.com to gitlab.com. This set me up for some embarrassment for every outage they experienced last year which felt surprisingly frequent. But if you have the resources, self-managed GitLab is great!
tl;dr: gitlab.your.org > github.com > gitlab.com
I’ve been using Gitea for my personal hosting because it’s small, quick, and easy to grok. It isn’t nearly as fully featured as GitLab though, but I don’t mind. I’m not a team and I’m happy to glue different services together rather than use a large all in one (Gitea + Drone + Wekan).
When a website or service becomes too slow, it is on its way to an impending death. Then people wonder why some service fell apart? Put users and usability first and foremost before features.
Great news for open source software hosting.
[0] https://simon.shimmerproject.org/2020/05/10/gitlab-ci-is-up-...
Would anyone doubt that open source contributions, and individual contributers even more so, have grown by an order of magnitude or more in the last decade or so? And that GitHub's process improvements and standardisation were the major factor in this?
It used to be, you had to mail patches to some mailing list, with each projects having their own set of arcane rules, sometimes written and sometimes informal, but always enforced with that very special enthusiasm stale organisations devote to policing arbitrary norms because that's the sole remaining source of the old timer's power differential.
Or at least that's how it seemed to me, for I never felt courageous enough to try.
These days, I fire off smaller contributions several times a week, and contribute some medium-sized feature once or twice a year.
Meanwhile, the most impressive thing about GitLab keeps being this strange quirk of them, that among all the companies I know, they are closest to being a total clone of an existing product. Or at least they were in the beginning, when their CSS still had ".gh-wide-3" class names.
Yet despite this, or maybe because of it, they are also the only company that repeatedly lorded it over their competitor when they came late to implementing some minor feature. Seriously: I noticed it the first time because it's a level of pettiness not usually seen. And since then, there have been three or four more instances.
Why the same people that seem afraid of email, can however gratuitously accuse others of being on an ego trip on a public forum, I wonder.
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 repository (ie: knowing when a bug has been closed and which versions/branches it was dealt with).
This is something I struggle with even when working alone on a simple project. I've used both sd (simple defects) and bugs-everywhere, however it seems that development on these has pretty much stalled, which is A Great Shame. I keep using "be" in these cases.
However as soon as you have 2-3 devs, it's easier to fire up something like gitlab and have all features such as reviews/CI in a single shot than having to setup these separately.
Factor in that ease of reporting both for you and for your users should be in the top #3 reasons for using a specific bug tracker.
Bugzilla IMHO only works as an internal-only tracker for developers or testers directly involved with the code and decent overview/discipline of the triaging process.
Gitea does integrate with some external CI/CD services, but it's not a part of the core product: https://docs.gitea.io/en-us/ci-cd/. Gogs makes no mention of CI/CD in its documentation.
I've switched from Gitea to GitLab for that same reason for my personal projects, and I'd bet that's by far the largest selling point of GitLab when compared to other self-hosted solutions. You just do a "git push" and stuff gets automatically tested in a VM or even deployed in a live environment.
Yea, same with my Gitea + Drone servers.
It’s cool that GitLab has everything built in, but I don’t mind having distinct tools. Especially when both are very performance static binaries in a language I’m fond of working in (Golang) so that I can patch upstream.
Truth be told, if it weren’t for GitLabs sluggishness on my very cheap VPS, I’d probably give it more of a go so I’d have less to maintain.
Indeed, gitolite doesn't support anything except permissions on raw git repos, plus all the customisation features you may have seen in the docs.
There are plenty of good tools if you need issues, reviews, comments, etc.; no need for little old me to jump in there!
In fact, at one time I changed the topic of #gitolite on freenode to "Social coding. Without the social" :-)
Do forks introduce potential PR spam or something of that sort on GitLab?
I had not been surprised if Microsoft had ruined GitHub by "enhancing" the site with loads of Javascript and other things that would make the site worse, but this hasn't happened. GitHub has actually improved steadily since the acquisition. Ironically, it's the FOSS alternative that is slow and bloated this time.
That being said, anything taking away from GH's dominance is an improvement imho.
XFCE is awesome, and is my second most used desktop after, well, Awesome.
> Starting today, May 1, we’re switching from our _cgit/gitolite_ setup to GitLab.
It's in the first sentence :)
It's also high time we look at the motivation and principles when it comes to products and services from a company, not just their technical superiority.
- Savannah?
- FreshMeat?