#Gitea is joining the fediverse 🎉 We can now announce we've been accepted into the #NLnet funding round that we applied to. nlnet.nl/project/Gitea/

Thank you to @NGIZero @dachary @forgefriends and so many others for getting us to this point.

We are very much looking forward to many wonderful things that federation within forges can support.

Follow

@gitea @NGIZero @dachary @forgefriends Cool! Looking forward for that :)

Are there any thoughts about changing to a more sustainable licence like the ? With federation this gets especially important. The MIT licence makes 'embrace, extend, extinguish' extremely easy: Company X creates a proprietary Gitea fork, federates with the existing instances, makes significant improvements/offers to lure people into their product. Changing to their instance is smooth thanks to federation.

@gitea @NGIZero @dachary @forgefriends
... I assume (but don't know) that many people who invest their time into Gitea would be quite pissed with something like that happening.
If that's the case, then the AGPL is the better choice.

Corporations are maybe not yet after the Fediverse, but they will once it grows.

Of course, the MIT is a better choice if you want to work for future corporations instead of future users :)

@vovanium @NGIZero @dachary @gitea @forgefriends
I'm not talking about improvements in the federation protocol. I mean other improvements in Gitea which make it more attractive: integration with some other cloud platform, etc.

But you got the point:

You get the improvements if you move to the improved instance. But not the other way. You can move without much costs, you can still communicate with the other instance as you did before. But the other instances don't have the improvements.

@t0k@social.tchncs.de @NGIZero@mastodon.xyz @dachary@mastodon.online @gitea@social.gitea.io @forgefriends@mastodon.online Non-federated features? I think there's already github for this. (i more afraid it got federated, as XMPP was nearly killed similar way)
Anyway, i don't see a reason to name EEE strategy 'super-easy' even with source code readily available, as it involves months to years of marketing.

@t0k @gitea @NGIZero @forgefriends the forgefriends codebase is published under #AGPL. It would make sense to me that #Gitea is published under #AGPL but that's a different discussion that needs to happen with the maintainers.

github.com/go-gitea/gitea/blob

@dachary @gitea @NGIZero @forgefriends Nice :) Yes, I agree, this involves the team. Unfortunately I don't know them and their motivations. But as a user I'd welcome the AGPL because it's like a promise of good intentions :)

Also it seems quite a successful approach when looking at the fediverse and projects like Nextcloud. People start appreciating the guarantee that they won't be trapped with a change towards a proprietary licence.

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!