Live data from Hacker News

Gitea: Open source, self-hosted GitHub alternative

gitea.io

231–240 of 241 posts

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

#231
post #182
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…

I had a class last semester that submitted everything through Gitlab and when we tried to run unit tests to test for the correct code, it would hang for 7-8 minutes. Very frustrating. Happened on all the assignments so was not just a one time thing.

I had a similar class that used Gigs instead and never had any performance issues. It didn't feel as polished as GitLab though.

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

#232

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…

Except for the features list, how good really are stars and issue counts indicators for anything? Gogs has been around for longer and has received much more publicity, so it's bound to have more stars. Similarly, Gitea has more contributors whereas Gogs is mostly a one man job, so Gitea users might feel more likely to receive an answer than from Gogs. It really feels more like you're comparing the community there than the product.

That said, I agree that Gitea should publish a features list and list the differences between the versions.

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

#233
I'm not a user of LFS, but I use phabricator and I find that it meets all my needs even on slower hardware, and it's pretty simple to debug. Has all your typical LAMP stack debuging techniques and when it breaks, it's pretty straight forward what needs to be fixed.

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

#234
Does it manage issues, pull requests, etc modeled in a distributed way? I was always dumbfounded as to why you'd take a great distributed collaboration tool like Git and then centralize it around issues, pull requests, comments, etc.

To me all of those things should be Git objects as well either tracked inside the same repo on another branch or something or tracked in a parallel Git repo.

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

#235

Earlier quoted context omitted.

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 y…

I think you're missing the point as well; "dearth" is a lack of. A lack of counter-productive features is a good thing.

I think you've misunderstood who is responding to who. A "dearth of somewhat counterproductive features" is being described as a bad thing in the OP, using an incorrect/nonexistent definition of "dearth" as "there are too many somewhat counterproductive features".

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

#236
post #222
post #203

Earlier quoted context omitted.

There is a milestone system setup on github which tracks when features will be introduced into master and such, so I wouldn't call it a lack of a vision statement. I don't think a vision statement is necessary either since I'm a fan of developing software primarly for dogfooding, fixing problems you have is probably a good way to improve the software for others.

It isn't though. People will make stupid demands, not because they are stupid, but because they don't incorporate previous decisions taken and they don't incorporate how their desired solution affects other users of the whole system. Last but not least having a 1000 feature blobb doesn't help anybody.

That doesn't mean that the maintainers of a community fork will have to follow every demand of the userbase.

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

#237

Earlier quoted context omitted.

I don't read it that way. How do you get that impression?

> The owner of the Gogs repo doesn't accept pull requests that won't fit his roadmap or quality standards, he is also not the most responsive during times this is why some people created Gitea. I am still using Gogs personally. Let's break it down: > The owner of the Gogs repo doesn't accept pull requests that won't fit his roadmap That generally sounds bad. Like, in an ideal world, you would be open to changing your…

You shouldn't try to interpret my words too much. I am not a native speaker.
Post reply on HN