@xgqt @drj yeah, and #forgejo too. the #ForgeFed (https://forgefed.org/) stuff looks really interesting too: it makes sense to me that for distributed vcs, the quality of life features like bug tracking, code review and web interface should be distributed too. the dominance of gh in particular removes one of the main reasons git (and mercurial, bazaar, fossil, darcs, et al) chose to move away from the design of cvs/subversion

edit: it's not #FediForge…

I’m running #ForgeJo on a raspberry pi, but hitting weird stability issues. Shame, it’s very impressive otherwise.

Run #forgejo on #TrueNASScale ✅

Thanks that #gitea was added to community #truenasCharts and was easy to be adjusted to run #forgejo 😁

Ääääh, Ok. Mein git-Problem mit #Forgejo (ich konnte keine Branches pushen, in denen tgz-Dateien waren) hat sich gelöst, indem ich #traefik aktualisiert habe…

Manchmal muss ich's vielleicht einfach auch nicht verstehen.

\o/ my @forgejo now has a @WoodpeckerCI picking!

#forgejo #woodpecker #ci #selfhosted

re-reading this post by @zwol about the state of the art of the #Autotools

https://www.owlfolio.org/development/autoconf-swot/

it seems that the support of the servers for issue tracking and the paperwork for intellectual property issues are holding back the health of the Autotools

I was thinking

as for issue tracking, it'd be nice (and probably relatively easy) to host the Autools suite on #Forgejo

as it seems to be the most sensible FLOSS oriented solution (currently)

as for paperwork...

re-reading this post by @zwol about the state of the art of the Autotools

https://www.owlfolio.org/development/autoconf-swot/

it seems that the support of the servers for issue tracking and the paperwork for intellectual property issues are holding back the health of the Autotools

I was thinking

as for issue tracking, it'd be nice (and probably relatively easy) to host the Autools suite on #Forgejo

as it seems to be the most sensible FLOSS oriented solution (currently)

as for paperwork...

That didn't take as long to migrate as I thought!

Now running #forgejo @ https://git.starbeamrainbowlabs.com

I solved my problem with #Forgejo installation (see the attached screenshot). I had to mount and alter much more directories than I hoped for. And SSH is still broken.

During migration from old server I lost all metadata (descriptions, images, mirror configurations) which would be pain to reconfigure (why can't I do pull mirrors from UI?). I'm considering using @charmcli's soft-serve instead, with maybe cgit as a HTTP frontend.

Are there some #forgejo admins in the hood, who have some time to try to reproduce the OAuth2 bug, that i am facing on my instance?

Here's the description: https://codeberg.org/forgejo/forgejo/issues/1205

#Forgejo v1.20.3-0 was just released! This is a security release. It includes breaking changes related to storage and a safeguard to prevent data loss. This is very unusual for a point release because they are usually designed for unattended upgrades.

Check out the blog post to figure out if your Forgejo instance is impacted. If that is the case, detailed instructions are provided to help you perform the manual steps required before the upgrade can happen.

https://forgejo.org/2023-08-release-v1-20-3-0/

forges such as #github, #gitea, and #forgejo should remove stars since the concept of stars is the same as the concept of likes in social media. it will create a false sense of trust and legitimacy to that project. if you really like a project, you can just bookmark it from your browser or take note of it.

related article: https://the-guild.dev/blog/judging-open-source-by-github-stars
video link where i found the article: https://youtu.be/fi-QKFjC--M

good thing #sourcehut does not have concept of starring a project.

#codeberg #forgejo

I am a bit confused by the licenses offered on https://codeberg.org/ during repo creation. GPL-3.0-only and GPL-3.0-or-later don't show any difference.

dammit!
each week the #gitlab interface changes 🙄
you don't improve something by constantly moving shit around - i want to code, not constantly relearning the UI!
really thinking about moving to #codeberg or setting up my own #forgejo

The #Forgejo summer update was published ✨ It is a high level overview of the project activities.

Forgejo v1.20, was published and was 100% built with Forgejo Actions. Codeberg was upgraded 10 August and hit an unexpected issue. It was quickly resolved and the fix will be integrated in the next release. Meanwhile development continued on the code, the website, the documentaion etc. All signs of a healthy project that needs your help to keep going in the long run. 🙏

https://forgejo.org/2023-08-monthly-update/

#Codeberg now allows the pinning of issues so they show up right above the issue list in a special, more visible box. Nice!

#development #forgejo #git #workflow

Making sure that my Fish history doesn't contain any "git push --force" before giving a #Git introduction to students tomorrow 🫣😂 :git:

I will show them briefly how to work with Github, but the main introduction will be on #Codeberg because I have some morals.

The biggest open source platform is itself proprietary and exploits its users by feeding their code into closed AIs.

Are #FOSS communities ever going to wake up?
Maybe when federation landes in #Forgejo and therefore in Codeberg?

Let’s try to migrate a #forgejo container. 😬

Finally, it's there: Blocking users has recently been added to #Codeberg, thanks to the #Forgejo team.

You feel offended or disturbed? Getting rid of them is just one button away.

Please be reminded: If the users are likely also a problem for other users, save them the trouble and report them to abuse@codeberg.org or by mentioning @moderation in an issue.

So, Migration von #gitea nach @forgejo #forgejo ist durch: https://git.schmidl.dev/schtobia.
Das war mal _wirklich_ simpel!