G
Gitea Blog
blog.gitea.io · Company blog · on HN since 2016
The Gitea project's blog announces releases and governance news for the self-hosted Git service forked from Gogs.
What HN saysHN commenters cite it for release notes like Gitea Actions and for the Gitea Ltd. announcement, which one commenter criticizes over crypto ties.
38HN people shared it
20linked it in comments
21stories submitted
741story points
3 years agolast shared
2016people per year2026
Most-shared posts
- 1Welcome to Gitea12 people · 6 points · first shared 2016 · 1 comments on HN
- 2Open source sustainment and the future of Gitea6 people · 157 points · first shared 2022 · 182 comments on HN
- 3Feature Preview: Gitea Actions4 people · 2 points · first shared 2022 · discussion on HN
- 4A Message from Lunny on Gitea Ltd. and the Gitea Project3 people · 106 points · first shared 2022 · 90 comments on HN
- 5Gitea 1.17.0 is released – includes package registry support2 people · 235 points · first shared 2022 · 72 comments on HN
- 6Gitea 1.13.0 Released2 people · 4 points · first shared 2020 · discussion on HN
- 7Gitea 1.15.0 Is Released2 people · 2 points · first shared 2021 · discussion on HN
- 8Gitea 1.192 people · 1 points · first shared 2023 · discussion on HN
- 9Gitea 1.10.0 Released1 people · 107 points · first shared 2019 · 16 comments on HN
- 10Gitea 1.11.0 Is Released1 people · 62 points · first shared 2020 · discussion on HN
- 11Gitea 1.7.0 is released1 people · 41 points · first shared 2019 · 4 comments on HN
- 12Gitea 1.2.0 released1 people · 4 points · first shared 2017 · discussion on HN
- 13Gitea 1.15.2 Is Released1 people · 3 points · first shared 2021 · discussion on HN
- 14Gitea 1.5.0 Released – Lightweight Git Self-Hosting1 people · 3 points · first shared 2018 · discussion on HN
- 15Gitea 1.17.3 Is Released1 people · 3 points · first shared 2022 · discussion on HN
What HN people wrote when they linked it
Deukhoofd · 2022-03-22
The major releases generally change quite a lot in one go, for example:
https://blog.gitea.io/2022/02/gitea-1.16.0-and-1.16.1-released/
https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/
But I'm sure Github changes a lot more. However, the question is if those changes are worth the instability. For my workflow I just want my repos to be accessible, have my source, issues, and wiki accessible, and of course my basic git operations working. If that core functionality is actually not working at times, I'd definitely consider changing the git provider.
mbertschler · 2017-01-13
Instead of Gogs it is now recommended to use Gitea, since it has more activity (~400 more commits last time I checked) and is community driven: https://gitea.io/
According to their Blog: Gitea is a community fork of the popular self-hosted Git service Gogs. We’re a growing group of former Gogs users and contributors who found the single-maintainer management model of Gogs frustrating and thus decided to make an effort to build a more open and faster development model. https://blog.gitea.io/2016/12/welcome-to-gitea/
melony · 2023-06-22
The Gitea team is full of crypto shillers.
https://blog.gitea.io/2022/10/a-message-from-lunny-on-gitea-ltd.-and-t…
Their founder claims to have invented Gogs (he was one of the early committers) when the original author is another engineer
https://en.m.wikipedia.org/wiki/Gitea
> Gitea was created by Lunny Xiao, who was also a founder of the self-hosted Git service Gogs.
https://about.sourcegraph.com/blog/three-years-at-sourcegraph
> About the author
Joe Chen is Software Engineer and maintainer of the open source project Gogs, a painless self-hosted Git service. You can chat with Joe on Twitter @jc_unknwon or our community Discord
aojdwhsd · 2023-03-30
They've actually just rolled out an early version of Gitea Actions in the most recent release, which are mostly compatible with GitHub actions.
https://blog.gitea.io/2023/03/gitea-1.19.0-is-released/#-gitea-actions…
jacooper · 2023-03-14
Personally I only care about GitLab because its open source with a good CI and because of Copilot.
If the supreme court says the copilot is fully legal, I would probably just revert to using Github for personal projects(their free tier is just unbeatable), i still use it more than anything else, because everything is on Github.
I am excited about Gitea Actions[1], as I feel gitea is generally only missing a decent CI system, and codeberg is growing fast.
1. https://blog.gitea.io/2022/12/feature-preview-gitea-actions/
e12e · 2023-03-02
Wow, that's quite impressive:
https://blog.gitea.io/2022/12/feature-preview-gitea-actions/
Looks like there's still more work planned, though:
https://github.com/go-gitea/gitea/issues/13539
This is interesting - as I understand it gitea supports work flows from the github marketplace - and I had just made a note to try and figure out how the ruby/setup-ruby[1] action actually works/is implemented - and from the looks/claims here - I guess it should just work with gitea?
[1] https://github.com/ruby/setup-ruby
jrop · 2022-11-26
https://blog.gitea.io/2022/10/open-source-sustainment-and-the-future-o…
Yeah looks like they are selling support, which I have no problem with. I actually recently set up Gitea and Drone together and it is a match made in heaven. I don't have a problem if open source developers try to monetize their work. I will likely try to do the same with a few projects in the future, lol
aargh_aargh · 2022-10-28
This is in response to:
https://blog.gitea.io/2022/10/open-source-sustainment-and-the-future-o…
as discussed here:
https://news.ycombinator.com/item?id=33339421
dachary · 2022-10-28
The Gitea Open Letter has links to the two documents that have the facts you ask for, at the bottom of the page. And with links within the text. They are:
https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#owners
https://blog.gitea.io/2022/10/open-source-sustainment-and-the-future-o…
frfl · 2018-11-10
https://gitea.io/en-us/ is a fork with some additional functionality and more open to outside contribution[1]
[1] https://blog.gitea.io/2016/12/welcome-to-gitea/
partycoder · 2018-06-06
This is the announcement of Gitea, which is a fork of Gogs.
https://blog.gitea.io/2016/12/welcome-to-gitea/
"We’re a growing group of former Gogs users and contributors who found the single-maintainer management model of Gogs frustrating and thus decided to make an effort to build a more open and faster development model."
This is a guide to run it with Docker
https://docs.gitea.io/en-us/install-with-docker/
gvx · 2018-05-06
I've not used either, but reading their forking announcement (https://blog.gitea.io/2016/12/welcome-to-gitea/), it seems the main difference is that Gogs is maintained by a single person and Gitea by a team of people.
The comments on that post suggest that Gitea is more actively developed, at least shortly after the fork, but I haven't checked to see if that's still the case.
connorshea · 2017-09-22
My understanding was that the maintainer of Gogs had stopped replying to any issues/PRs for a period of a few weeks and refused to add any other maintainers to the project, so people wanted to fork and ensure that it'd always have an active maintainer.
https://blog.gitea.io/2016/12/welcome-to-gitea/
cristaloleg · 2017-05-29
Gitea[1] is a fork of Gogs without 'single-maintainer management model'[2]
[1] https://github.com/go-gitea/gitea
[2] https://blog.gitea.io/2016/12/welcome-to-gitea/
nfriedly · 2017-01-22
What's different between Gitea and Gogs?
I just setup the Gogs docker image the other day to play with, and it seemed pretty painless to me.
Edit: I just found https://blog.gitea.io/2016/12/welcome-to-gitea/ which somewhat answers this - essentially a different governance model and more development, but not any major functional differences.
secure · 2017-01-21
Gitea is a fork of Gogs, the reasons for the fork are explained at https://blog.gitea.io/2016/12/welcome-to-gitea/
sairamkunala · 2017-01-13
Gitea is a community fork of the popular self-hosted Git service Gogs. We’re a growing group of former Gogs users and contributors who found the single-maintainer management model of Gogs frustrating and thus decided to make an effort to build a more open and faster development model.
This happened not before trying to convince @Unknwon about giving write permissions to more people, among the community. He rightly considered Gogs his own creature and didn’t want to let it grow outside of him, thus a fork was necessary in order to set that code effectively free.
source: https://blog.gitea.io/2016/12/welcome-to-gitea/
dqv · 2017-01-01
It was forked because they wanted a different management model that included more people.
https://blog.gitea.io/2016/12/welcome-to-gitea/
ricardobeat · 2022-12-16
Background story seems to be that a portion of Gitea maintainers formed a for-profit company, and transferred all the trademarks to it, going against former promises made, and blowing up their own community as a consequence. They go over the now-traditional "companies are using our free software without paying us" discourse here: https://blog.gitea.io/2022/10/open-source-sustainment-and-the-future-o…
> we’re planning on establishing a fund to be able to provide support to contributors who not only contribute features, but also bug fixes, performance enhancements, and important refactors.
Sounds like any other for-profit company building commercial software. What stopped them from doing that while keeping the original OSS software copyrights intact?
Also curious to see their plan to pay out all the developers working on the OSS that underpins Gitea itself. The list is pretty long.
forgotpwd16 · 2022-11-01
A takeover was announced a week ago (https://blog.gitea.io/2022/10/open-source-sustainment-and-the-future-o… ; discussed in https://news.ycombinator.com/item?id=33339421). This got a negative response by the community (https://gitea-open-letter.coding.social/ ; discussed in https://news.ycombinator.com/item?id=33372471) but the owners disregarded them (https://blog.gitea.io/2022/10/a-message-from-lunny-on-gitea-ltd.-and-t… ; discussed in https://news.ycombinator.com/item?id=33394280). The reason behind the response being that Gitea was a community-led project with an electionary process. A fork is eminent.