Notices by Codeberg.org (codeberg@social.anoxinon.de)

The latest newsletter to Codeberg members is now also available on our blog. https://blog.codeberg.org/letter-from-codeberg-happy-new-year.html

@JustineSmithies Contributions in form of some time are also very appreciated.

Please note that Codeberg Pages and Codeberg itself are still separate services. A dowtime on Codeberg.org means that Pages is probably down, too, but the Pages Service also has some issues on its own, and there are not enough contributions to the code itself to solve them 😞

The hardest #scaling issue: https://blog.codeberg.org/the-hardest-scaling-issue.html

Some thoughts about how non-profit web services can have healthy growth and keeping up with proprietary competitors.

Do you love #selfhosting? What about providing service to the public via #Codeberg?

We are looking for maintainers that take on adding code search features to our #Forgejo instance to reduce the load on the existing infrastructure team and bring this project forward.

Please see https://codeberg.org/Codeberg/Community/issues/904 if you are interested.

We are looking forward to your contributions. Thank you a lot!

Are you running #Forgejo inside a container? Upgrades are now available to include the fix for the #Git #security issue.

If you are running from your distribution, please ensure you update the Git version.

Learn more at: https://forgejo.org/2023-01-18-release-v1-18-1-0/

(For anyone wondering: The Git version on Codeberg was already patched)

@rudi https://blog.codeberg.org/codeberg-launches-forgejo.html This is likely all you need to know. While Forgejo stays a soft-fork, it is a drop-in replacement, and you can go back at any time.

aaand we're officially migrated from #Gitea to #Forgejo. Nice!

Thanks to @forgejo, it was a pleasure :)

🔔 Heads-Up: We're deploying Forgejo 1.18 in a few minutes. We expect no unusual downtime.

@benjaminhollon
It is especially a priority for Forgejo. To our knowledge, (nearly?) all the developers involved with federation have moved to the #Forgejo soft-fork. There is also a new grant application to continue the federation implementation within Forgejo.

I'm sure that these features will be upstreamed if possible, so Gitea and Forgejo users can interact.
@forgejo

@insanePerlman Previously, Codeberg was just a hosted instance of Gitea with a small set of additional patches, mostly cosmetic. The bonus features of Codeberg was mostly the ecosystem (Pages, CI, Weblate integration, ...).

But for the actual software, we followed the Gitea development closely. Now, we are not sure if we can "blindly" deploy their code any more :)

s/Gitea/Forgejo: Although we need to get used to it, we’re happy that we can support the #Gitea soft-fork #Forgejo by our means.
It will remain independent of for-profit companies and is guaranteed to remain 100% free/libre forever.

Read more on our blog: https://blog.codeberg.org/codeberg-launches-forgejo.html

Or Visit https://forgejo.org

Do you fear moving to the #libre side of the web?

We have 6k followers on #Mastodon, 1k on #Twitter, and they are much less engaged.

Do you think this can't be true for your #GitHub or #GitLab.com projects?

If you dare to switch, a nice community is waiting for you on #Codeberg!

@danjones000
Forgejo is working on the 1.18 Gitea branch, so we can only do the switch once we're ready for that release. For the current Gitea stable (1.17), there is no Forgejo yet.
@gitea @forgejo

@smallcircles
We're planning to do this, and we have allocated resources for the index. The Gitea integration wasn't awesome, but we're in favour of investing resources for that.

Regarding the infrastructure part: We were looking into replacing elasticsearch with zinc https://github.com/zinclabs/zinc, but the activity decreased recently and we don't know if the company backing this is trustworthy.
@doctormo

@max
And there is a world outside #GitHub which won't contribute their either. Our recommendation: always allow at least two methods to receive contributions, e.g. by using email.
@timbray @Edent

Do you love what we do?

Consider a donation, or becoming a member of the non-profit Codeberg e.V. to support our mission!

https://docs.codeberg.org/improving-codeberg/#donate-to-codeberg
&
https://join.codeberg.org/

@astrojuanlu We're optimistic that we find a way to stay independent. 💙

@moonbolt
We will not take any sides too soon, but will carefully evaluate pro's and con's.

We are trying to be independent and do whatever is best for libre software hosting on Codeberg.

We somehow still hope that there is no need for a fork, but we'll see.
@dachary

@eludom
As suggested in the comment below, we think Gogs is not an option. Gitea has matured a lot since then.
@humanetech

The summary of our latest news, in case you missed any: https://blog.codeberg.org/letter-from-codeberg-hackathon-translation-service-more.html

#hackathon, hosted #weblate, Status Monitor & more