Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Gogs, the project Gitea has been forked off, works just as well. As far as I can see there's no technical reason to prefer the fork over the original.

Judging from Github stars, Gogs is also vastly more popular.



I compared them yesterday. There seems to be more development activity and more contributors for Gitea (check the pulse tool on github for the last month). I haven’t got a stake in this whatsoever, but I recall the rationale for the fork being that PR’s would remain unmerged for months without comment due to the inactivity of the original author, who nevertheless wanted to retain control?


Gogs has many issues that no one want to fix.


Find the 7 differences...

- https://github.com/go-gitea/gitea/commits/master

- https://github.com/gogs/gogs/commits/master

gogs is mostly maintained by a single developer, and has less activity than gitea.


A frantic commit free for all isn't necessarily better. I count nine different developers committing to the project's master branch in a single day. That has tradeoffs too.


Comparing commits is mostly pointless anyway. Some people commit very often any little change (like some indentation change) while others commit only when a feature is done.

Compare releases and features.


Gitea requires peer review for pull requests, a healthy process that promotes quality. Cogs is managed exclusively by its BDFL.


The best way to compare the features could be https://docs.gitea.io/en-us/comparison/ which is a really fair comparision.

Edit: This list have been created on best efford, if you find any wrong information a pull request is always welcome.


Online Gogs demo here: https://gogs.io/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: