Codeberg.org

If you are reading this, we recommend that you also read ketanjoshi.co/2024/04/19/you… Then unfollow us here and move your account somewhere else. Thanks.

If you still follow us on X, you might not be aware that we fully moved to the libre M network in the meantime. Please check out our website to learn about how you can stay up to date with Codeberg.

A small but notable change on Codeberg? References to #Twitter are now gone. We believe in independent networks. Drop #GitHub, drop #Twitter, drop all the #proprietary clouds and embrace true freedom.

If you want to stay up to date with Codeberg, please stop following us on X and join M instead. This account will stop sharing relevant information for the time being.

Did you know that "pushing your #code to #GitHub" is not how to #OpenSource a project? It is about adding a Free #License, and you can push anywhere you want, including #Codeberg, for example :) #FreeSoftware #ServiceTweet

We try to reply to platforms on the libre side of the web. A platform that is not available to everyone is definitely not the place we should be active on.

Since our thread on T is no longer visible to the public, our main instance for information is definitely on M. Please ensure to follow us on libre socialmedia, see our homepage for links.

I think you can run cronjobs, I do not know if you can choose not to run them if nothing changed. You might be able to use workarounds, though.

What about #CI on #Codeberg? We are providing access to our #WoodpeckerCI instance to those who need it, some caveats still apply. Also, you can read about the upcoming #ForgejoActions. Check out our docs to learn more about the state of CI on Codeberg: docs.codeberg.org/ci/

#NotOnGitHub: Tell us about your favourite #OpenSource / #FreeSoftware projects that are not available on mainstream platforms, whether on a self-hosted cgit or available as an archive download only. The #FLOSS world is more than #GitHub and #GitLab.

The hardest #scaling issue: blog.codeberg.org/the-hardes… Some thoughts about how non-profit web services can have healthy growth and keeping up with proprietary competitors.

Yes, that does make sense, but does not solve the problem on a systemic level. The big question is: How much effort should self-hosters do? Is it enough to open registrations on git.example.com and share it to friends, or do you need to become a full-time sysadmin?

Forgejo is supposed to stay a soft-fork, and we also aim to upstream most relevant changes.

Read why we think that Blocklists defeat a safe and decentralized Internet: blog.codeberg.org/how-blockl… #Infosec #PiHole #eblocker #spamhaus #abuse #centralization

Dealing with current #malware waves makes us mad. Mostly at #blocklist­s, which are often unmaintained, or selling a commercial product, even asking you to pay for delisting. This is far from allowing for a free and decentralized Internet. [... Read on ↓]

Dear followers, please note ...

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: blog.codeberg.org/codeberg-l…

Do you fear moving to the #libre side? We have 6k followers on #Mastodon, 1k much less engaged on #Twitter. 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 in the #Fediverse and on #Codeberg!

Big thanks to: #Gitea + #Forgejo, #Debian #GNU/#Linux and all these nice people in the #FLOSS community. You rock! 💙