- cross-posted to:
- libre_culture@lemmy.ml
- cross-posted to:
- libre_culture@lemmy.ml
#Gitea is joining the fediverse 🎉 We can now announce we’ve been accepted into the #NLnet funding round that we applied to. https://nlnet.nl/project/Gitea/
You must log in or register to comment.
This is huge news. We need decentralized issue tracking and code yesterday, and all the previous tries have ended up at dead ends. Really hope this succeeds so all projects including lemmy can migrate off github / gitlab.
Oh my. I’m so, so happy! Thank you really much to all the people who have make this possible; you’re are really changing the world for the better.
Gitea presenting at Forgefriends federation webinar, 19 January
–> Forge federation: How forge friends want to liberate your code
On 19 January at 10.00 UTC+1 the Forgefriends community is organizing a webinar to introduce anyone that is interested to the importance and benefits of adding federation to code forges such as Gitea, Gitlab, Github and any other forge that implements Fediverse-based interoperability.
Gitea is the first project to be a true “forge friend”. Federation support allows FOSS projects to be liberated from proprietary platforms that lock people in by network effects and FOMO. Forge friends set your code free, and allows anyone to interact with it from their own platform of choice. Just like it works for email, you can choose your own favourite environment, and still interact with a project elsewhere on the web to file issues, merge code and track progress.
There’s an enormous amount of potential that this development unleashes. But whether opportunities are grasped and how fast the “forge friends” vision materializes depends on all of you. The forgefriends community needs your help, whether it is technical in nature or otherwise. Anyone can contribute.
Join the webinar and learn more!
I’m wondering how far the the federation is being planned. Is it just that an user on Gitea instance A can discover projects on instance B? Or can an user on instance A also open issues, pull-requests etc on a project on instance B, assuming the user has the required permissions?
If it is the latter, I believe that would be awesome. Right now, I feel like as a starting project, if you want to be discovered and get contributors you basically need to be on a large, centralised code platform such as codeberg, gitlab.com or github.com. I hope that it will lessen the barrier for people already on another Gitea instance to contribute to a project on another instance.
Discovery, like with all fediverse software, probably isn’t going to be very robust if present at all.
deleted by creator
This is really exciting! I think this is what’s going to get people to switch away from GitHub.
Is ForgeFed dead?
It is unmaintained. There’s discussion on whether it should become part of Forgefriends community, and how that may be organized. See:
Gitea produces something similar to gogs for thrice it’s size last I checked. gogs was 25MB and gitea was 76MB. Something must be done for removal of code too instead of just addition of code.
I guess this change in size is due to the fact that the Gitea fork of Gogs has been more actively developed and at this time contains more features than Gogs. Though I haven’t tried Gogs recently to know which they are, I appreciate what Gitea has to offer and I feel with them it becomes more and more attractive for people to consider a move away from Github. With these federation features being added, Gitea will be getting a lot of the same network effects that lead to FOMO and keeps people on Github. But in a decentralized manner.
It’s obviously better than GitHub. But between Gogs and Gitea, I think Gogs has more than enough features and using Gogs, you trust 1 person, whereas with Gitea, responsibility lies nowhere. Also, in such community projects, people never remove code, they just keep adding code which is a disaster!
I personally like cgit and stagit more than above 2 but Gogs lies at appropriate junction between ease of use, UX and features.
Yeah, there’s pros and cons to both approaches. Gitea team is very active and responsive, and I personally like a community approach to a BDFL project. I had some self-hosted Gitea’s, but nowadays I use Codeberg mostly. They are a Gitea instance and actively contributing to the project (one Codeberg member is a core team participant in Gitea). They have added cool features such as Codeberg Pages and soon Codeberg CI (based on Woodpecker CI integration, the FOSS fork of drone.io).
I guess that with Gitea and Forgefriends adding federation support, and this being implemented in Golang, it will be easy for Gogs to adopt that too, and then the choice of code forge wouldn’t matter all that much anymore. Choice would be fully up to personal preference.
Btw, after being blocked to do so, Gitea intends to move off Github soonish and dogfood their own project, which is quite cool when that happens.
Moving off GitHub is cool. They should do that definitely! I take immense interest in computer security and would trade such extra features easily for minimalism! People could easily learn using just those features! But yes, I get your point.
