I organize a weekly office hour, for questions about Radicle CI, distributed CI, local-first CI, or related topics, in https://meet.ffmuc.net/radicleciofficehour (Jitsi, only needs browser, mic and webcam optional but helpful).

This week on Wednesday 16:00 UTC (18 CEST, 19 EST). I can do a live demo of setting up a CI node on Debian.

cc @radicle

https://radicle-ci.liw.fi/

#Radicle #RadicleCI #ContinuousIntegration #officeHour

ETA UTC timestamp

Jitsi Meet

Join a WebRTC video conference powered by the Jitsi Videobridge

State of Radicle CI and where it's going: June 2026

One unexpected benefit from migrating away from self-hosted #GitLab Enterprise to #Radicle : the temperature in the #HardenedBSD server room at my home hasn't reached 70F, even though it's over 90F outside.

I organize a weekly office hour, for questions about Radicle CI, distributed CI, local-first CI, or related topics, in https://meet.ffmuc.net/radicleciofficehour (Jitsi, only needs browser, mic and webcam optional but helpful).

This week on Wednesday 07:00 UTC (09 CEST, 10 EST). I can do a live demo of setting up a CI node on Debian.

cc @radicle

https://radicle-ci.liw.fi/

#Radicle #RadicleCI #ContinuousIntegration #officeHour

ETA UTC timestamp

Jitsi Meet

Join a WebRTC video conference powered by the Jitsi Videobridge

Verification complete with a successful result!

My next project will be a #Radicle orchestrator process that can mirror our repos to third-party resource (like our read-only presence on GitHub).

While I find #Rust easy to read, I haven't written much #Rustlang code yet. This will be a good exercise in learning Rust. :-)

The main idea is to implement bunches of features in this orchestrator (the first being the aforementioned repo mirroring support.) The next feature will likely be per-commit emails and issue/patch notifications via #Pushover.

Very productive day today:

  • Volunteered at the #Pride parade, representing #COSAARPR
  • Got the #HardenedBSD auto-sync re-enabled with "the #Radicle way"
  • Fixed our home's front storm door
  • Laundry and dishes
  • If it wasn't after 5pm, I'd look to add in a nap. But instead, I'll take our dog Vader for a walk.

    @ff0x oh, nice!! 😎

    Do you already know about the radicle-ci-broker and the #Ambient CI engine that @liw has written?

    Or are you already self-hosting another CI engine (e.g. Jenkins, etc.) that you'd like #radicle to integrate with?

    #HardenedBSD goal for this weekend: Radicle-ify our auto-sync.

    #Radicle

    I know it's old news but I still find it really funny that Gitea still hasn't bootstrapped yet.

    - #radicle is developed on Radicle
    - #forgejo is developed on Forgejo
    - #gitlab is developed on GitLab
    - #github is developed on Github
    - #git is developed on git (using emails for issues & etc.)

    Gitea though? #Gitea is developed on Github. By their own admission they aren't good enough yet. Apparently #dogfooding isn't a priority.

    Context (an issue locked to collaborators): https://github.com/go-gitea/gitea/issues/1029

    Gitea hosted Gitea · Issue #1029 · go-gitea/gitea

    For the first big stage, we would like Gitea's development could be based on a Gitea hosted and github will only a mirror. This will maybe completed in v1.x. So that this issue will list all the fe...

    GitHub
    @adingbatponder I don't, but that's a good idea. I do plan on writing an in-depth article on our #Radicle journey so far. When I get to doing that (will take another few weeks as I clear higher priority items off my plate), I'll make sure to record a "#HardenedBSD release engineering" video, showing how we use Radicle and how I perform the release engineering process.