Migration from #gitea to #forgejo complete. Was a breeze using #nixos, really. Deployed forgejo to server, then stopped process, copied /var/lib/gitea to /var/lib/forgejo, fixed ownership and addressed a few small stateful data pitfalls: gitea database is named gitea.db, Forgejo is named forgejo.db so you need to move it. For repo origins using ssh, you'll need to update the origin to use ssh://forgejo@ instead of ssh://gitea@.
How clean is your #fork? #github, the place that #microsoft gets #openSource developers to provide it free #ai training data for use by proprietary products, is being attacked by bots making millions of malicious forks (copies) of projects and adding password stealing code.
Check your sources carefully before you #git clone!
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Forgejo started as a soft fork of Gitea, in reaction to governance changes within the project. Over time, it developed its own identity, adopted both development and governance practices - to ensure the stability, quality, and openness of the project - that made it more challenging to remain a soft fork. The decision was made to become a hard fork.
I think it's telling that #GitHub, #GitLab, and even #Forgejo all don't have a workflow for "renew an #OpenPGP key", i.e. extend its validity before (or after) expiry. On all of them, you have to delete and re-add the key. It's as if nobody is following OpenPGP best practices and everyone is using keys without an expiry date.
#Forgejo v1.21.6-0 was just released! This is a security release.
We strongly recommend that all installations are upgraded to the latest version as soon as possible. Read more in the companion blog post https://forgejo.org/2024-02-release-v1-21-6-0/.
There’s a special circle of hell for the “This file contains ambigious Unicode characters” overlay on @Codeberg
No, it doesn’t, it uses proper curly quotes and other typographically-correct punctuation in comments and strings.
Thought we’d fixed this in Forgejo but apparently not?
Really making me not want to link to my source code on Codeberg and I don’t want to migrate elsewhere right now when everything else is working so well.
Hot Take:
The "I'm new to Github guy" is an absolute asshole but is actually completely right, all the developers coping right now that Github is a dev platform are wrong. If you only release your app on Github it's no longer just a development platform it's also distribution one
Although I like the idea of the "not by AI" badge (https://notbyai.fyi/), if I was building a LLM crawler, then I’d definitely ingest pages with this badge first.
Don't think this will be coming for Codeberg any time soon, and it's a long shot, but you might have some energy for a hosted Forgejo / Gitea instance.
This means, I think, that I can get my home #forgejo instance to render notebooks - which I had no idea about.
"Forgejo is no longer bound to Gitea, and can forge its own path going forward, allowing maintainers and contributors to reduce tech debt at a much higher pace, and implement changes - whether they’re new features or bug fixes - that would otherwise have a high risk of conflicting with changes made in Gitea."
Forgejo started as a soft fork of Gitea. Over time, it developed its own identity, adopted both development and governance practices - to ensure the stability, quality, and openness of the project - that made it more challenging to remain a soft fork. In early 2024, a decision was made to become a hard fork, and for Forgejo to forge its own path going forward. This post explains the consequences this decision will have.
We are excited about @forgejo becoming a hard fork, and trust the maintainers to double down on their commitment to a secure and reliable software forge. It was a pleasure to work with #Forgejo in the past year, and we thank everyone involved for turning the fork into a successful project.
Not to rain on a parade of #GitLab and some #Fedora projects embracing #GitLabEE, but the official web UI and mobile apps (by enthusiasts) for surfacing it are in a sorry state.
Web: very JavaScript-heavy, not optimized for mobile.
Web (mobile): can't view comments without logging in.
Web: too many fields are immediately thrown into the mix, despite the lack of usage. Mobile apps: the complete absence thereof.
Web: issue tasks open either in a popup and as a separate page, but not easy to predict.
Web: you wanna click on the task - too bad, it's confused with drag-and-drop.
This all made me reminisce about #GitNex, #Codeberg, #Forgejo and plain ol' issues, without all that fluff. And then, there is #Pagure: it lets you work with issues and pull requests as #Git repos of their own. I have to wonder why fedorians resort to GitLab, when in-house solution (such as Pagure) exists. I assume, it's just that - a fluff. I simpathize it is hard to say no to these minute conveniences.
Agit means that you can open new PRs to a repository using git push origin HEAD:refs/for/<branch>..., without having to open the web UI, create a fork, create a new branch, create a new pull request and then choose the branch on your tree (as well as the target branch).
Bit messy because it's a bit late, but I hope that the improved documentation can raise some further awareness about that cool feature.
#Codeberg would not be here without all the free time volunteers donate to our platform and to upstream projects. However, we can give our project a rocket boost with your help. We have compensated a small share of time for their work in #Forgejo, and we have seen immense progress we would waited long for.
Can you help #translate#Codeberg's user interface into more languages? Consider joining the #localization team of #Forgejo and review or provide translations for your native language.
Turns out #Gitea was turned into a for-profit company two years ago. The software remains MIT-licensed, but it's now centered around enterprise solutions
However Gitea's community was not happy about this and created a soft fork that remains fully-compatible, community-driven. It's called #Forgejo and #Codeberg switched to using it in favor of Gitea.
Visited the #codeberg#woodpecker#forgejo stand at #FOSDEM and after just a few seconds I was recognised “Ah, yes! You definitely are jwildeboer, the guy that complains a lot about Codeberg Pages but still is nice” :)
@suruatoel We know of many users who migrated from #Gitea to #Forgejo. We never heard of anyone switching back (correct us if you know someone, would be interesting to learn why).
I think this is a sign, and we believe there is all reason to switch and not look back.