Why use gitea over gogs ? #133

New Issue

GiteaMirror · 2025-11-02T03:10:13-06:00

GiteaMirror commented

2025-11-02 03:10:13 -06:00

Originally created by @lenormf on GitHub (Dec 20, 2016).

Hi,

The README lacks explanations as to how gitea is better than gogs, could you please expand on that? I see the features list, but that's not very helpful to someone who isn't familiar with everything that gogs do in the first place.

Thanks.

Originally created by @lenormf on GitHub (Dec 20, 2016). Hi, The README lacks explanations as to how `gitea` is better than `gogs`, could you please expand on that? I see the features list, but that's not very helpful to someone who isn't familiar with everything that `gogs` do in the first place. Thanks.

GiteaMirror added the type/question label 2025-11-02 03:10:13 -06:00

GiteaMirror closed this issue

2025-11-02 03:10:13 -06:00

GiteaMirror commented

2025-11-02 03:10:13 -06:00

@strk commented on GitHub (Dec 20, 2016):

The current goal is shipping a 1.0.0 version which has no new feature,
so from a user point of view there should be nothing that gitea does
and gogs doesn't.

Moreover, Gitea doesn't have an official release yet, so the user does
not even have the choice.

The only reason for using Gitea over Gogs at this moment is to contribute
in making it better, as acceptance of contributions in Gitea should be
easier to make. In the long run, our belief is that this ease of contribution
would make Gitea reacher in terms of features, and safer in terms of bugs.

@strk commented on GitHub (Dec 20, 2016): The current goal is shipping a 1.0.0 version which has no new feature, so from a user point of view there should be nothing that gitea does and gogs doesn't. Moreover, Gitea doesn't have an official release yet, so the user does not even have the choice. The only reason for using Gitea over Gogs at this moment is to contribute in making it better, as acceptance of contributions in Gitea should be easier to make. In the long run, our belief is that this ease of contribution would make Gitea reacher in terms of features, and safer in terms of bugs.

GiteaMirror commented

2025-11-02 03:10:14 -06:00

@lenormf commented on GitHub (Dec 20, 2016):

Aren't those principles shared by the gogs project as well? Or is that why the project was forked.

@lenormf commented on GitHub (Dec 20, 2016): Aren't those principles shared by the `gogs` project as well? Or is that why the project was forked.

GiteaMirror commented

2025-11-02 03:10:14 -06:00

@strk commented on GitHub (Dec 20, 2016):

Gogs is managed by a single person, who is the original author.
The community asked many times to share responsibility but this
was never accepted. So yes, this is the reason why the project
was forked.

Read more on https://blog.gitea.io/2016/12/welcome-to-gitea/

@strk commented on GitHub (Dec 20, 2016): Gogs is managed by a single person, who is the original author. The community asked many times to share responsibility but this was never accepted. So yes, this is the reason why the project was forked. Read more on https://blog.gitea.io/2016/12/welcome-to-gitea/

GiteaMirror commented

2025-11-02 03:10:14 -06:00

@lenormf commented on GitHub (Dec 20, 2016):

Great, thanks for your quick answers.

@lenormf commented on GitHub (Dec 20, 2016): Great, thanks for your quick answers.

GiteaMirror commented

2025-11-02 03:10:14 -06:00

@ptman commented on GitHub (May 7, 2018):

https://github.com/go-gitea/website/issues/40

@ptman commented on GitHub (May 7, 2018): https://github.com/go-gitea/website/issues/40

GiteaMirror referenced this issue

2025-11-02 11:40:29 -06:00