Recent searches
Search options
Administered by:
We're excited to announce the official launch of the #Forgejo project, a community-driven fork of #Gitea under the stewardship of @Codeberg.
Check out https://forgejo.org/2022-12-15-hello-forgejo/ to learn more, including the motivation for the fork, as well as Codeberg's announcement at https://blog.codeberg.org/codeberg-launches-forgejo.html
Come and get involved at https://codeberg.org/forgejo/forgejo or in our Matrix room https://matrix.to/#/#forgejo-chat:matrix.org . We aim to be a fully inclusive community and everyone's participation is welcomed.
@HackerGeno @hostsharing @fsfe I am sad to hear about Gitea surrender to the dark side but same time I am glad to hear about @forgejo standing with the Resistance! #softwarefreedom
@dancesWithCycles @HackerGeno @hostsharing @fsfe @forgejo I'm curious what "the dark side" refers to in this context.
@jolheiser @HackerGeno @hostsharing @fsfe @forgejo I do not understand and it has a certain kind of taste that Gitea Ltd. choose a profit-oriented over a non-profit-oriented legal form. Everyone seeks to make money with FLOSS. That is fine. Sadly, there have been to many examples in the past and it is a rising business model to exploit FLOSS for commercial matters that limit people's freedom: #softwarefreedom
@dancesWithCycles @HackerGeno @hostsharing @fsfe Forgejo is a non profit community dedicated to the interest of the general public. Gitea Ltd is a for profit company that will put the interest of its shareholders first.
Very different... but they do not fight. There is a fruitful cooperation at a technical level.
A nice example is how a scaling bug discovered on Codeberg.org while publishing Forgejo container images was fixed by a Gitea contributor.
~ @dachary@mastodon.online
@forgejo Will you also provide ARMv6/ARMv7 binaries at your releases one day – for those currently running Gitea on e.g. BananaPis?
@IzzyOnDroid yes. There is a need for testers willing to verify the result works as intended. Would you like to be part of such a team?
~ @dachary@mastodon.online
@forgejo @dachary@mastodon.online I don't think I'll have much time to do real testing. On my end, it's indeed running on a BananaPi with Armbian, mostly mirroring my repos from different places but also being primary for my local stuff (configurations etc), so it would be bad if it "breaks things". But if the worst thing should "usually" be that the binary isn't starting up, or anything else that could be fixed by just replacing it with the previous Gitea, why not.
@padraic @Codeberg @IzzyOnDroid actually... the 1.18.0 will also include armv6/armv7 binaries if they can be automatically tested with qemu in the CI, which is likely.
An issue was created to track this work.
https://codeberg.org/forgejo/forgejo/issues/117
~ @dachary@mastodon.online
@forgejo that's ace, looking forward to it!
@padraic @Codeberg @IzzyOnDroid @dachary@mastodon.online Forgejo 1.18.0 will provide armv6 binaries. Those can also be used on armv7.
The Forgejo release process will include the generation of arm-6 binaries and a qemu based test that verifies it is functional.
If you are curious about how it is done checkout this (very short) pull request.
https://codeberg.org/forgejo/forgejo/pulls/118
~ @dachary@mastodon.online
@forgejo Thanks for the follow up. Woodpecker also looks like a nice tool!
#Forgejo is based on the #Esperanto word for "Forge" - #Forĝejo.
It has one single correct pronunciation, and here you can listen to it in the attached audio file 
Available now. It's #FOSS, always will be, and is built exclusively with free software and tools - no Google sheets, zoom conferences - ONLY FOSS - we're serious about #dogfooding our open source!
#tallship #Fediverse h/t to @onepict #git #We_Forge
.
