Live data from Hacker News

Gitea: Open source, self-hosted GitHub alternative

gitea.io

51–60 of 241 posts

Re: Gitea: Open source, self-hosted GitHub alternative

#51
post #18

I've been using Gogs for a team of 40 people for over two years. This is the second time I've heard about Gitea, and I know it is a popular fork of Gogs. Can anyone sell me on why it's better than Gogs and why I should switch?

The biggest difference is the community around them, Gogs is more or less the brainchild of Unknwon and he used to have a tendency to just drop of the planet and Gogs would sit still for weeks (or even months) at a time without anyone being able to do anything about it. Gitea was a community response to this, nearly all the major contributors switched over and I think it shows in terms of features and fixes. Gitea now has well over a thousand more commits than Gogs and a lot more manpower behind it. You can see this by looking at the contributor graph for both projects, Gitea has had a steady supply of contributors and commits in the last release while Gogs has a few spikes of activity.

Also, if you look at the release notes for both of them I think it's fairly easy to see that Gitea is developing at a much faster rate and has more features than Gogs already with a lot of nice features coming in 1.5.

However, I'm fairly biased, I used Gogs for a long time but switched as soon as Gitea popped up for the reasons above. Since then I've contributed a few fixes and features to Gitea as well.

Re: Gitea: Open source, self-hosted GitHub alternative

#52
post #18

I've been using Gogs for a team of 40 people for over two years. This is the second time I've heard about Gitea, and I know it is a popular fork of Gogs. Can anyone sell me on why it's better than Gogs and why I should switch?

Don't switch.

Long story short: Gogs was slow in committing pull requests. The maintainer says it's because he has specific standards, the community sees it as just slowness. Anyway Gogs was forked into a new version that is supposed to be more active and well maintained.

Well the forking lit a fire under the ass of the Gogs maintainer and he has since become much more active than he was. For a month there there was reason to switch to Gitea as it was adding features that Gogs did not have at a rapid pace, but Gogs is now mostly caught up and there is reason to prefer it. I personally would go with Gogs. 1 passionate person > design by committee of people with shared low responsibility.

Re: Gitea: Open source, self-hosted GitHub alternative

#53
post #51
post #18

I've been using Gogs for a team of 40 people for over two years. This is the second time I've heard about Gitea, and I know it is a popular fork of Gogs. Can anyone sell me on why it's better than Gogs and why I should switch?

The biggest difference is the community around them, Gogs is more or less the brainchild of Unknwon and he used to have a tendency to just drop of the planet and Gogs would sit still for weeks (or even months) at a time without anyone being able to do anything about it. Gitea was a community response to this, nearly all the major contributors switched over and I think it shows in terms of features and fixes. Gitea no…

What's some stuff worth getting excited about in 1.5?

Re: Gitea: Open source, self-hosted GitHub alternative

#54

Was trying to figure out why it looked almost identical to Gogs, until I read it was a fork. So, what does this give me over using the main Gogs? I see it is managed differently, but what features does it offer that are not in Gogs?

Precisely, have a look at this: https://news.ycombinator.com/item?id=17006848

Re: Gitea: Open source, self-hosted GitHub alternative

#55

Quick comparison from GitHub stats and READMEs: Gogs: 24,564 stars, 602 issues, has a features list. https://github.com/gogits/gogs Gitea: 5,971 stars, 733 issues, doesn't have a features list. https://github.com/go-gitea/gitea Gogs features (from README): Activity timeline SSH and HTTP/HTTPS protocols SMTP/LDAP/Reverse proxy authentication Reverse proxy with sub-path Account/Organization/Repository management Add/Re…

Gitea is a fork of Gogs, so it has everything on that list and more. Sadly Gitea suffers from the usual problem that open source projects has, poor documentation. If you really want to compare feature lists, here's the one listed on their website (https://docs.gitea.io/en-us/).

Why compare two products by their README and not their website? Heck, why not compare them by using their test instances that are there for you to try.

Re: Gitea: Open source, self-hosted GitHub alternative

#56

Quick comparison from GitHub stats and READMEs: Gogs: 24,564 stars, 602 issues, has a features list. https://github.com/gogits/gogs Gitea: 5,971 stars, 733 issues, doesn't have a features list. https://github.com/go-gitea/gitea Gogs features (from README): Activity timeline SSH and HTTP/HTTPS protocols SMTP/LDAP/Reverse proxy authentication Reverse proxy with sub-path Account/Organization/Repository management Add/Re…

Gitea is a fork of Gogs.

> Are users expected to install and find out?

Some due diligence and going to the gitea website could also do the trick. https://docs.gitea.io/en-us/

Re: Gitea: Open source, self-hosted GitHub alternative

#57
post #18

I've been using Gogs for a team of 40 people for over two years. This is the second time I've heard about Gitea, and I know it is a popular fork of Gogs. Can anyone sell me on why it's better than Gogs and why I should switch?

Don't switch. Long story short: Gogs was slow in committing pull requests. The maintainer says it's because he has specific standards, the community sees it as just slowness. Anyway Gogs was forked into a new version that is supposed to be more active and well maintained. Well the forking lit a fire under the ass of the Gogs maintainer and he has since become much more active than he was. For a month there there was…

+1. About two years ago I switched to gitea but then switched back. gogs has (had?) slightly less features but seemed more polished. No issues since then, I'm glad to run again the original.

Re: Gitea: Open source, self-hosted GitHub alternative

#58
post #51

Earlier quoted context omitted.

The biggest difference is the community around them, Gogs is more or less the brainchild of Unknwon and he used to have a tendency to just drop of the planet and Gogs would sit still for weeks (or even months) at a time without anyone being able to do anything about it. Gitea was a community response to this, nearly all the major contributors switched over and I think it shows in terms of features and fixes. Gitea no…

What's some stuff worth getting excited about in 1.5?

Personally:

- Issue due dates (https://github.com/go-gitea/gitea/pull/3794)

- Approval/comments on pull requests (https://github.com/go-gitea/gitea/pull/3748)

- Multiple assignees on issues (https://github.com/go-gitea/gitea/pull/3705)

- Dependencies for issues (https://github.com/go-gitea/gitea/pull/2531)

- CI status on pull requests (https://github.com/go-gitea/gitea/pull/2519)

Re: Gitea: Open source, self-hosted GitHub alternative

#59
post #39

devops sysadmin here. I started with gitlab about a year ago and can honestly say I wish I had taken gogs/gitea instead. The main problem for me is gitlabs utter dearth of somewhat counterproductive features. Git LFS support is almost a cruel joke in gitlab as git operations under the hood now take inexorably more ram to complete. In turn im rewarded with more traditional RCS programmers asking why git has problems w…

Pedantic notice: an utter dearth of counterproductive features would seem to be a good thing rather than a problem.

As another systems engineer, I'd much rather have clearly delineated features and how to interconnect them, rather than a cornucopia of disparate and badly documented "features".

I'm thinking of the class of "Does:X, Y, Z" but Z requires unstated dependency of A and C, and C requires you to have a specific database organization type that was asked at the initialization of the system. And there would be no hint that you had to choose the DB type, and how that would have ramifications 10 steps down the line.

Going back, what I'd rather have is more in line with the Unix philosophy. Do something and do it well. Let me connect somethings to other somethings. But Gitlab is a cathedral, and disorganized at that.

Re: Gitea: Open source, self-hosted GitHub alternative

#60
post #39

devops sysadmin here. I started with gitlab about a year ago and can honestly say I wish I had taken gogs/gitea instead. The main problem for me is gitlabs utter dearth of somewhat counterproductive features. Git LFS support is almost a cruel joke in gitlab as git operations under the hood now take inexorably more ram to complete. In turn im rewarded with more traditional RCS programmers asking why git has problems w…

> [...] and implement competent things like competent CI [...]

I've got an OSX build box with a bunch of virtualbox VMs so I can build for Gnu/Linux (i386, x86_64, and arm), OSX, and Windows. Single slow box, so one runner at a time. It has to be running OSX because I haven't found any way to run an OSX VM on any other platform.

I want to trigger CI on Gitlab merge requests.

What does $competent_CI expand to?

Post reply on HN