Karl Voit :emacs: :orgmode:@publicvoit@graz.social

Using docs.codefloe.com/usage/migrat I was able to easily migrate my #Codeberg projects to #CodeFloe, which is a permissive FOSS hosting service:
codefloe.com/publicvoit/

What should I do with my projects on Codeberg? Where should I put the link to the new project locations?

put in read-only mode with a note in README58%
remove code and replace with short README wit link23%
delete project and risk dead links on the web17%
other (please comment)0%

⁨17⁩ votes · Closed

CodeFloeMigrating from Other ForgesBulk-migrate repositories from GitHub, GitLab, Gitea, or another Forgejo into CodeFloe
en
Karl Voit :emacs: :orgmode:@publicvoit@graz.social

Replying to @⁨publicvoit@graz.social⁩

I went with option number 2: I removed my code from #Codeberg and replaced it with a notification message.

codeberg.org/publicvoit/ is history. 👋

Hail codefloe.com/publicvoit on a permissive #FOSS service: @codefloe 🙇

Background: social.tchncs.de/@codefloe/116

#CodeFloe

CodeFloe@codefloe@social.tchncs.de

Now that #codeberg has manifested their anti-AI view with a 70% in favor vote (codeberg.org/Codeberg/org/pull), we're happy to welcome (once again) all the people which have to/want to move their repositories off Codeberg but still want to stay on a Forgejo-based instance.

Bonus: on top you'll get better uptime, faster site responses and faster CI runners - all for free :)

tl;dr: after this ToU change, keeping AI-generated code on Codeberg would violate these and repositories will be in danger of deletion.

#codeberg #codefloe #giveUpGitHub