Fedora People

Peter Czanik: The syslog-ng Insider 2026-03: 4.11.0 release; OpenSearch; ElasticSearch

2026-03-11T12:01:47+00:00

Remi Collet: 🎲 PHP version 8.4.19RC1 and 8.5.4RC1

2026-02-27T07:12:00+00:00

Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for parallel installation, the perfect solution for such tests, and as base packages.

RPMs of PHP version 8.5.4RC1 are available

as base packages in the remi-modular-test for Fedora 42-44 and Enterprise Linux ≥ 8
as SCL in remi-test repository

RPMs of PHP version 8.4.19RC1 are available

as base packages in the remi-modular-test for Fedora 42-44 and Enterprise Linux ≥ 8
as SCL in remi-test repository

ℹ️ The packages are available for x86_64 and aarch64.

ℹ️ PHP version 8.3 is now in security mode only, so no more RC will be released.

ℹ️ Installation: follow the wizard instructions.

ℹ️ Announcements:

Parallel installation of version 8.5 as Software Collection:

yum --enablerepo=remi-test install php85

Parallel installation of version 8.4 as Software Collection:

yum --enablerepo=remi-test install php84

Update of system version 8.5:

dnf module switch-to php:remi-8.5
dnf --enablerepo=remi-modular-test update php\*

Update of system version 8.4:

dnf module switch-to php:remi-8.4
dnf --enablerepo=remi-modular-test update php\*

ℹ️ Notice:

version 8.5.4RC1 is in Fedora rawhide for QA
EL-10 packages are built using RHEL-10.1 and EPEL-10.1
EL-9 packages are built using RHEL-9.7 and EPEL-9
EL-8 packages are built using RHEL-8.10 and EPEL-8
oci8 extension uses the RPM of the Oracle Instant Client version 23.9 on x86_64 and aarch64
intl extension uses libicu 74.2
RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
versions 8.4.19 and 8.5.4 are planed for March 12th, in 2 weeks.

Software Collections (php84, php85)

Base packages (php)

Fedora Magazine: How to rebase to Fedora Silverblue 44 Beta

2026-03-10T19:29:19+00:00

Silverblue is an operating system for your desktop built on Fedora Linux. It’s excellent for daily use, development, and container-based workflows. It offers numerous advantages such as being able to roll back in case of any problems. This article provides the steps to rebase to the newly released Fedora Linux 44 Beta, and how to revert if anything unforeseen happens.

NOTE: Before attempting an upgrade to the Fedora Linux 44 Beta, apply any pending upgrades to your current system.

Updating using the terminal

Because Fedora Linux 44 Beta is not available in GNOME Software, the whole process must be done through a terminal.

First, check if the 44 branch is available, which should be true now:

$ ostree remote refs fedora

You should see the following line in the output:

fedora:fedora/44/x86_64/silverblue

If you want to pin the current deployment (this deployment will stay as an option in GRUB until you remove it), you can do it by running:

# 0 is entry position in rpm-ostree status
$ sudo ostree admin pin 0

To remove the pinned deployment use the following command ( “2” corresponds to the entry position in the output from rpm-ostree status ):

$ sudo ostree admin pin --unpin 2

Next, rebase your system to the Fedora 44 branch.

$ rpm-ostree rebase fedora:fedora/44/x86_64/silverblue

The final thing to do is restart your computer and boot to Fedora Silverblue 44 Beta.

How to revert

If anything bad happens — for instance, if you can’t boot to Fedora Silverblue 44 Beta at all — it’s easy to go back. Pick the previous entry in the GRUB boot menu (you need to press ESC during boot sequence to see the GRUB menu in newer versions of Fedora Silverblue), and your system will start in its previous state. To make this change permanent, use the following command:

$ rpm-ostree rollback

That’s it. Now you know how to rebase to Fedora Silverblue 44 Beta and fall back. So why not do it today?

Known issues

PAM Lastlog change crashing gdm

FAQ

Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.

Question: Can I skip versions during rebase of Fedora Linux? For example from Fedora Silverblue 42 to Fedora Silverblue 44?

Answer: Although it could be sometimes possible to skip versions during rebase, it is not recommended. You should always update to one version above (42->43 for example) to avoid unnecessary errors.

Question: I have rpm-fusion layered and I got errors during rebase. How should I do the rebase?

Answer: If you have rpm-fusion layered on your Silverblue installation, you should do the following before rebase:

rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release

After doing this you can follow the guide in this article.

Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),…?

Yes, you can follow the Updating using the terminal part of this guide for every ostree edition of Fedora. Just use the corresponding branch. For example for Kinoite use fedora:fedora/44/x86_64/kinoite

Marcin Juszkiewicz: RISC-V is sloooow

2026-03-10T17:53:00+00:00

About 3 months ago I started working with RISC-V port of Fedora Linux. Many things happened during that time.

Triaging

I went through the Fedora RISC-V tracker entries, triaged most of them (at the moment 17 entries left in NEW) and tried to handle whatever possible.

Fedora packaging

My usual way of working involves fetching sources of a Fedora package (fedpkg clone -a) and then building it (fedpkg mockbuild -r fedora-43-riscv64). After some time, I check did it built and if not then I go through build logs to find out why.

Effect? At the moment, 86 pull requests sent for Fedora packages. From heavy packages like the “llvm15” to simple ones like the “iyfct” (some simple game). At the moment most of them were merged, and most of these got built for the Fedora 43. Then we can build them as well as we follow ‘f43-updates’ tag on the Fedora koji.

Slowness

Work on packages brings the hard, sometimes controversial, topic: speed. Or rather lack of it.

You see, the RISC-V hardware at the moment is slow. Which results in terrible build times — look at details of the binutils 2.45.1-4.fc43 package I took from koji (Fedora and RISC-V Fedora):

Architecture	Cores	Memory	Build time
aarch64	12	46 GB	36 minutes
i686	8	29 GB	25 minutes
ppc64le	10	37 GB	46 minutes
riscv64	8	16 GB	143 minutes
s390x	3	45 GB	37 minutes
x86_64	8	29 GB	29 minutes

That was StarFive VisionFive 2 board, while it has other strengths (such as upstreamed drivers), it is not the fastest available one. I asked around and one of porters did a built on Milk-V Megrez — it took 58 minutes.

Also worth mentioning is that the current build of RISC-V Fedora port is done with disabled LTO. To cut on memory usage and build times.

RISC-V builders have four or eight cores with 8, 16 or 32 GB of RAM (depending on a board). And those cores are usually compared to Arm Cortex-A55 ones. The lowest cpu cores in today’s Arm chips.

The UltraRISC UR-DP1000 SoC, present on the Milk-V Titan motherboard should improve situation a bit (and can have 64 GB ram). Similar with SpacemiT K3-based systems (but only 32 GB ram). Both will be an improvement, but not the final solution.

Hardware needs for Fedora inclusion

We need hardware capable of building above “binutils” package below one hour. With LTO enabled system-wide etc. to be on par with the other architectures. This is the speed-related requirement.

There is no point of going for inclusion with slow builders as this will make package maintainers complain. You see, in Fedora build results are released into repositories only when all architectures finish. And we had maintainers complaining about lack of speed of AArch64 builders in the past. Some developers may start excluding RISC-V architecture from their packages to not have to wait.

And any future builders need to be rackable and manageable like any other boring server (put in a rack, connect cables, install, do not touch any more). Because no one will go into a data centre to manually reboot an SBC-based builder.

Without systems fulfilling both requirements, we can not even plan for the RISC-V 64-bit architecture to became one of official, primary architectures in Fedora Linux.

I still use QEMU for local testing

Such long build times make my use of QEMU useful. My AArch64 desktop has 80 cores, so with the use of QEMU userspace riscv64 emulation, I can build the “llvm15” package in about 4 hours. Compare that to 10.5 hours on a Banana Pi BPI-F3 builder (it may be quicker on a P550 one).

btop shows 80 cores being busy

And LLVM packages make real use of both available cores and memory. I am wondering how fast would it go on 192/384 cores of Ampere One-based system.

Still, I used QEMU for local builds/testing only. Fedora, like several other distributions, does native builds only.

Future plans

We plan to start building Fedora Linux 44. If things go well, we will use the same kernel image on all of our builders (the current ones use a mix of kernel versions). LTO will still be disabled.

When it comes to lack of speed… There are plans to bring new, faster builders. And probably assign some heavier packages to them.

Tim Waugh: Searching Logseq by Concept, Not Keystrokes

2026-03-10T13:46:21+00:00

Logseq is great for dumping daily notes, but finding them again later can be a pain. If you’re looking for notes on a “connection timeout” but originally wrote “increasing the socket keepalive”, a standard keyword search will give you nothing. You end up having to guess the exact phrasing your past self used.

I wanted a way to search my graph by concept rather than exact text matches. That’s why I put together the Logseq Semantic Search plugin.

The upcoming database version of Logseq actually has semantic search built-in. But since I’m still using the standard Markdown version for my day-to-day workflow, I wanted to get that capability right now.

Indexing the hierarchy

The plugin uses text embeddings to find conceptually similar blocks. But just embedding individual bullet points doesn’t work well for outliners. A block that just says “needs refactoring” is useless on its own.

If you’ve seen my Logsqueak project, you’ll recognise the indexing approach here. Every block is indexed along with its complete structural lineage—the page name, properties, and the full chain of parent blocks above it.

Because it captures this nested context, the search index knows that a vague bullet point nested under billing-service → Database Connection Pool is actually about your Postgres setup. Searching for “optimizing billing db” will pull that specific child block right to the top of the results.

Running it locally

Since a Logseq graph is essentially a private brain dump, I wanted this to run entirely locally. By default, the plugin connects to Ollama using the lightweight nomic-embed-text model. It’s smart enough to only re-embed blocks that have changed, so it’s relatively fast even without a GPU. (If you prefer, you can also point it at any OpenAI-compatible endpoint in the settings).

I run Fedora Workstation and prefer to keep my host system clean, so I run Ollama via Podman. It’s incredibly straightforward to set up:

# Start the Ollama container, exposing the default port and persisting data
podman run -d -v ollama:/root/.ollama -p 11434:11434 --name ollama docker.io/ollama/ollama

# Pull the lightweight embedding model
podman exec -it ollama ollama pull nomic-embed-text

Because we mapped port 11434, the Semantic Search plugin can talk to the container seamlessly at http://localhost:11434 right out of the box. No dependency issues, just a private embedding server ready to run in the background.

Usage

You can grab the plugin directly from the Logseq Marketplace. Once it’s installed, hit Alt+K (or click the toolbar icon) to open the search modal. Try typing a natural language query—like “notes about debugging pipeline failures”—and it will surface the relevant blocks even if you didn’t use the word “debugging.”

The source code is up on GitHub if you want to poke around or contribute.

The post Searching Logseq by Concept, Not Keystrokes appeared first on PRINT HEAD.

Peter Czanik: New toy: Installing FreeBSD on the HP Z2 Mini

2026-03-10T12:13:13+00:00

Fedora Magazine: Announcing Fedora Linux 44 Beta

2026-03-10T08:00:00+00:00

On Tuesday, 10 March 2026, it is our pleasure to announce the availability of Fedora Linux 44 Beta! As with every beta release, this is your opportunity to contribute by testing out the upcoming Fedora Linux 44 Beta release. Testing the beta release is a vital way you can contribute to the Fedora Project. Your testing is invaluable feedback that helps us refine what the final F44 experience will be for all users.

We hope you enjoy this latest beta version of Fedora!

How to get the Fedora Linux 44 Beta release

You can download Fedora Linux 44 Beta, or our pre-release edition versions, from any of the following places:

The Fedora CoreOS “next” stream rebases to Fedora beta content on the same day as the beta release. To try out Fedora Linux 44-based CoreOS, try out the Fedora CoreOS “next” stream today.

You can also update an existing system to the beta using DNF system-upgrade.

The Fedora Linux 44 Beta release content may also be available for Fedora Spins and Labs.

Fedora Linux 44 Beta highlights

Like every Beta release, the Fedora Linux 44 Beta release is packed with changes. The following are highlights from the full set of changes for F44. They are ready for you to test drive in the Fedora Linux 44 Beta.

Installer and desktop Improvements

Goodbye Anaconda Created Default Network Profiles: This change impacts how Anaconda populates network device profiles. Only those devices configured during installation (by boot options, kickstart or interactively in UI) become part of the final system install. This behavior change addresses some long standing issues caused by populating network profiles for all network devices. These made it difficult to correctly reconfigure devices post-install.

Unified KDE Out of the Box Experience: This change introduces the post-install Plasma Setup application for all Fedora KDE variants. In the variants making use of this new setup application, the Anaconda configuration will be adjusted to disable redundant configuration stages that duplicate the functionality exposed in the setup application.

KDE Plasma Login Manager: This change introduced the Plasma Login Manager (PLM) for Fedora KDE variants instead of SDDM for the default login manager.

Reworked Games Lab: This change modernizes the Games Lab deliverable by leveraging the latest technologies. This offers a high quality gaming and game development experience. It includes a change from Xfce to KDE Plasma to take advantage of the latest and greatest Wayland stack for gaming.

Budgie 10.10: Budgie 10.10 is the latest release of Budgie Desktop. Budgie 10.10 migrates from X11 to Wayland. This ensures a viable long-term user experience for Fedora Budgie users and lays groundwork for the next major Budgie release.

LiveCD Improvements

Automatic DTB selection for aarch64 EFI systems: This change intends to make the aarch64 Fedora Live ISO images work out of the box on Windows on ARM (WoA) laptops. This will automatically select the right DTB at boot.

Modernize Live Media: This change modernizes the live media experience by switching to the “new” live environment setup scripts provided by livesys-scripts and leverage new functionality in dracut to enable support for automatically enabling persistent overlays when flashed to USB sticks.

System Enhancements

GNU Toolchain Update: The updates to the GNU Toolchain ensure Fedora stays current with the latest features, improvements, and bug and security fixes from the upstream gcc, glibc, binutils, and gdb projects. They guarantee a working system compiler, assembler, static and dynamic linker, core language runtimes, and debugger.

Reproducible Package Builds: Over the last few releases, we changed our build infrastructure to make package builds reproducible. This is enough to reach 90%. The remaining issues need to be fixed in individual packages. With this change, all package builds are expected to be reproducible in the F44 final release. Bugs will be filed against packages when an irreproducibility is detected. The goal is to have no fewer than 99% of package builds reproducible.

Packit as a dist-git CI: This change continues down the path of modernizing the Fedora CI experience by moving forward with the final phase of the plan to integrate Packit as the default CI for Fedora dist-git.

Remove Python Mock Usage: python-mock was deprecated with Fedora 34. However, it is still in use in many packages. We plan to go through the remaining usages and clean them up, with the goal of retiring python-mock from Fedora.

Adoption of new R Packaging Guidelines: This change introduces new rpm macros to help standardize and automate common R language packaging tasks resulting in a simplification of the rpm spec files.

Introduction of Nix Developer Tool: This change adds the nix package manager developer tool to Fedora.

Hardlink identical files in packages by default: With this change, all fedora packages will automatically hardlink files under /usr by default as a post install action. The mechanism introduced in this change is designed specifically to address reproducibility validation race conditions found in use by traditional hardlinking approaches.

Fedora Linux 44 Beta upgrades and removals

Golang 1.26: Fedora users will receive the most current and recent Go release. Being close to upstream allows us to avoid security issues and provide more updated features. Consequently, Fedora will provide a reliable development platform for the Go language and projects written in it.

MariaDB 11.8 as Distribution Default Version: The distribution default for MariaDB packaging will switch to 11.8. Multiple versions of the MariaDB packages will continue to be available. This change only impact which of the versioned packages presents itself as the unversioned “default”

IBus 1.5.34: Fedora users will benefit from better support of Wayland and Emoji features.

Django 6.x: Fedora Users can make use of the latest Django version; users who use Django add-ons that are not ready for 6.0 yet should be able to switch it out for python3-django5

TagLib 2: This change puts Fedora on the latest supported version, and it will benefit from improvements in future minor releases with a simple update.

Helm 4: Helm 4 has been released upstream with intentional backwards-incompatible changes relative to Helm 3. To ensure a smooth transition for Fedora, this Change introduces Helm 4 as the default helm package, while providing a parallel-installable helm3 package for users and tooling that still rely on Helm 3.

Ansible 13: Update from Ansible 11 and Ansible Core 2.18 to Ansible 13 and Ansible Core 2.20. This includes major robustness and security fixes to the templating engine which might break existing playbooks that had incorrect behavior. This was silently ignored in previous releases.

TeXLive 2025: With this change, we update to the latest version of TeXLive (2025). We also move to a modularized packaging system, which splits the “texlive” SPEC into a set of collection and scheme packages. This reflects the categorization that TeXLive upstream defines. Each collection package will package the immediate component dependencies as subpackages.

Drop QEMU 32-bit Host Builds: Fedora will stop building QEMU on i686 architecture. This change brings Fedora inline with the QEMU upstream project decision to deprecate support for 32-bit host builds. Upstream intends to start removing 32-bit host build support code in a future release and will assume 64-bit atomic ops in all builds.

Drop FUSE 2 libraries in Atomic Desktops: Remove FUSE 2 binaries and libraries from all Atomic Desktops

Drop compatibility for pkla polkit rules in Atomic Desktops: Remove support for deprecated pkla polkit rules from all Fedora Atomic Desktops

More information about Fedora Linux 44 Beta

Details and more information on the many great changes landing in Fedora Linux 44 are available on the Change Set page.

Editor’s Notes

Previously, it was noted that Fedora CoreOS “next” stream releases a week after the beta. This was a publishing error. The Fedora CoreOS “next” stream releases on the same day as the beta release. The article was edited to clarify this error.

Kushal Das: In the land of XML

2026-03-09T07:22:53+00:00

Miroslav Vadkerti: Silencing Alerts During OpenShift Cluster Upgrades with Prometheus and Alertmanager

2026-03-09T00:00:00+00:00

Kevin Fenzi: misc fedora bits first week of march 2026

2026-03-07T17:27:53+00:00

Here we are in the first week of March 2026 already. This was a pretty quiet week for me, partly due to the Fedora 44 Beta freeze and partly I think due to people traveling/being away. In any case it was welcome to me to have a chance to work on some planned work instead of day to day or fighting fires.

GPU machine

This week I finally got our gpu machine all setup, which has been a very long road. Last year we thought it would be very handy to have a machine that has desktop GPUs in it that we could use to test / build / explore things that could use those. We didn't want a server with fancy datacenter gpus, we wanted things that Fedora users might have. This of course is tricky, since that entails a desktop like machine in a datacenter.

After some looking around, we found the Dell Precision 7960 Rack, which is a rackmount machine, but sort of a desktop too.

We got a loaner to test things out with, and finally decided to buy it and use it. There have been so many little delays with this thing ( wrong network card, need a new one. Time of people involved to setup the testing. Drac license was wrong and I couldn't install it, and more).

But finally this week it's up. We will see how useful it becomes and what new exciting things it opens up.

Fedora 44 Beta is GO for release next tuesday

We had our Fedora 44 Beta go/nogo meeting on thursday and amazinly we were go for release on tuesday. The second beta candidate had no accepted blockers. I'm always a bit surprised when things go so smoothly, but I will take it!

Secure boot signing

I also made some more progress on my secure boot signing setup, but then i hit a blocker. I was able to sign grub and kernel for aarch64, but it doesn't actually boot. (I have my lenovo slim7x and also another aarch64 box that supports secure boot to test with). Hopefully we can get to the bottom of that soon so we can switch things on. I really hope we can have it running before Fedora 44 final freeze.

This also has been a long road.

Just missed it

I'm getting a solar system with batteries and home backup installed late this month, and I'm really looking forward to it.

Unfortunately, my electic coop just informed me that there is going to be a 4 hour power outage on monday for maint work. If it had only been next month, I could have just ignored it. Oh well, one more time for the generator! :)

comments? additions? reactions?

As always, comment on mastodon: https://fosstodon.org/@nirik/116189196834124254

Avi Alkalay: Ideal Laptop

2026-03-07T08:15:44+00:00

Do you remember the most important characteristics you should look for in a good laptop? In the following order:

1⃣ A high-resolution, high-density display: 3K or 4K, far beyond HD or Full HD
2⃣ A battery that lasts all day
3⃣ Fast storage (SSD)
4⃣ Light, thin, and elegant

It’s not the CPU.
It’s not AI.
It’s not having huge storage capacity.
It’s not a large physical size.
It’s not having more than 8 GB of memory (memory is not storage).
It’s not having a stylus, tablet convertible, or having a detachable or articulated keyboard.
And it’s definitely not having a numeric keypad on the side.

Until last week, the best and most affordable laptop on the market with these characteristics was the $1100 MacBook Air. But now Apple has launched the MacBook Neo, which delivers all these qualities — display, battery, storage, lightness, and elegance for 45% less: $600.

❝A laptop for me is just for browsing the internet, email, editing documents, messaging, watching movies, and relaxing with games like Solitaire or Roblox.❞

Congratulations, you’re like 99.9% of humanity. The MacBook Neo delivers the best value for you.

In the Windows laptop universe, these truly important characteristics (display quality, lightness, etc.) are usually found only in the most expensive product lines. To justify the high price, their marketing shifts the focus to things that are largely irrelevant: unnecessarily powerful CPUs, unnecessarily large storage, unnecessarily large memory, tablet modes, styluses, and so on.

All unnecessary for 99.9% of humanity.

And even in those expensive lines, the battery rarely lasts more than two hours, let alone all day. The reason: inefficient CPU.

Don’t be misled when choosing your next laptop. Pay attention to the characteristics that really matter: hires display, battery duration, fast storage, lightness, and elegance. General rule is to avoid laptops that use Intel CPUs.

This also applies to the laptops that companies give to their employees.

Also in my Instagram, Facebook and LinkedIn.

Avi Alkalay: Laptop ideal

2026-03-07T07:56:23+00:00

Lembra quais são as características mais importantes que você deve procurar num bom laptop? 1⃣ tela de alta resolução e densidade, 3K ou 4K, bem mais que HD ou full HD; 2⃣ bateria que dura o dia todo; 3⃣ armazenamento rápido (SSD); 4⃣ leve, fino e elegante.

Não é CPU. Não é IA. Não é armazenamento grande. Não é ter tamanho físico grande. Não é ter mais do que 8GB de memória (memória não é armazenamento). Não é ter caneta, virar tablet, teclado removível ou articulado. E definitivamente não é ter teclado numérico lateral.

Até semana passada, o melhor e mais barato laptop do mercado com essas características era o MacBook Air de $1100. Mas agora a Apple lançou o MacBook Neo que entrega todas essas características de tela, bateria, armazenamento, leveza e elegância, 45% mais barato: $600.

❝Laptop prá mim é só prá navegar na internet, e-mail, editar documentos, mandar mensagem, assistir filmes, me distrair jogando paciência e Roblox❞. Parabéns, você é como 99,9% da humanidade. O MacBook Neo entrega o melhor custo-benefício para você.

No universo dos laptops Windows, essas características importantes (tela, leveza etc), só se encontram nas linhas mais caras dos fabricantes. E para justificar o alto preço, seu marketing procura mudar o foco para coisas completamente irrelevantes, como CPU desnecessariamente poderosa, armazenamento desnecessariamente alto, memória desnecessariamente grande, virar tablet, ter caneta etc. Desnecessário para 99,9% da humanidade. E mesmo assim, nem nessas linhas mais caras a bateria dura mais do que 2 horas (motivo: CPU ineficiente), quanto menos o dia todo.

Não seja ludibriado ao escolher seu próximo laptop. Preste atenção nas características que realmente importam: tela, bateria, armazenamento rápido, leveza e elegância. A regra geral é evitar laptops com CPUs Intel.

Isso vale também para laptops que empresas dão a seus funcionários.

Também no meu Instagram, Facebook e LinkedIn.

Fedora Community Blog: Final Reminder: Flock 2026 Financial Assistance Applications Close Sunday, March 8th

2026-03-06T10:15:00+00:00

Do you want to join us for our annual contributor conference? We want to see you there! However, we know that traveling to a global event is a big trip. It costs real money. To help out, the Flock Organizing Team offers Flock 2026 financial assistance. We want to make sure money does not stop our active contributors from attending.

This is your final reminder. You must submit your form by Sunday, March 8th, 2026. The organizing team starts looking at the data on Monday morning. Because of this fast timeline, we cannot accept any late forms. Sunday is a hard stop.

What does this funding actually cover? We can help you pay for your travel. This includes your airfare or train tickets. We can also help cover your hotel room at the main event venue. We have a limited budget. Because of this, we cannot fully fund every person who applies. Your peers on the organizing team review all the forms. They look at your community impact to make these tough choices.

Note for Flock 2026 speakers

Are you giving a talk this year? We are excited to hear from you! But please remember one important rule. Being an accepted speaker does not give you guaranteed funding. You still need to ask for help. All speakers must fill out the Flock 2026 financial assistance form if they need travel support.

Apply for Flock 2026 financial assistance

Applying is easy. Just follow these steps:

Open the Google Form application.
Fill in your travel details and your estimated costs.
Explain your recent work and your impact in the Fedora community.
Submit the form before the end of the day on Sunday, March 8th.

We want to bring as many builders and contributors together as possible. Please do not wait until the last minute. If you need support to join us, fill out the application today!

The post Final Reminder: Flock 2026 Financial Assistance Applications Close Sunday, March 8th appeared first on Fedora Community Blog.

Fedora Community Blog: Community Update – Week 10 2026

2026-03-06T10:00:00+00:00

This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infrastructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project.

Week: 02 – 06 March 2026

Fedora Infrastructure

This team is taking care of day to day business regarding Fedora Infrastructure.
It’s responsible for services running in Fedora infrastructure.
Ticket tracker

Migrated remaining pagure.io repositories, there is one remaining, but needs to have private issues implemented
Provide DNS domain name for konflux (ticket)
Meeting with the IPA-tuura team to move forward with the Ipsilon replacement project

CentOS Infra including CentOS CI

This team is taking care of day to day business regarding CentOS Infrastructure and CentOS Stream Infrastructure.
It’s responsible for services running in CentOS Infratrusture and CentOS Stream.
CentOS ticket tracker
CentOS Stream ticket tracker

Release Engineering

This team is taking care of day to day business regarding Fedora releases.
It’s responsible for releases, retirement process of packages and package builds.
Ticket tracker

Still in Beta Freeze, we have had a couple of release candidate composes for Fedora 44 Beta.
GO/NO-GO call for the Beta Release is tentatively scheduled for Thursday, March 5th.

RISC-V

This is the summary of the work done regarding the RISC-V architecture in Fedora.

Continue to comb through the list of Fedora packages that need work — submit changes to Fedora / upstream, review patches from others, and submit builds as needed.
Build/test the RISC-V unified kernel.
Figured out logistics for 24-h remote access to SpacemiT ‘K3’ hardware (based on RVA230
Discussed with the RISC-V SIG and Fedora docs about migrating the Fedora RISC-V docs from the wiki to forge.
Figure out the prerequisites for F44 builds — toolchain dependencies are being sorted out.

AI

This is the summary of the work done regarding AI in Fedora.

Aurelien Bompard Worked on the AI-powered This Week in Fedora.
Claude helped Gordon Messmer develop an extension to glibc’s malloc API to solve a common problem with memory inflation, and produced some illustrations of the problem and solution. The write-up will be posted shortly. Draft at: https://codeberg.org/gordonmessmer/dev-blog/src/branch/main/memory-efficiency-with-arena-allocators.md
Quality Team workflow for AI code review in Forgejo — easily reused if you’re interested! https://forge.fedoraproject.org/quality/workflows/src/branch/main/.forgejo/workflows/ai-review.yml

QE

This team is taking care of quality of Fedora. Maintaining CI, organizing test days
and keeping an eye on overall quality of Fedora releases.

Fedora 44 RCs are now available and under heavy testing. The Go/NoGo is scheduled in a few days. Lots of blocker (and not blocker) bugs were discovered, discussed, voted on and resolved.
Kernel 6.19 test days are complete and Podman 5.8 test days are under way.
A new version of BlockerBugs bot was implemented and deployed to staging, which should allow us to migrate blocker voting repository from Pagure to Forge (ticket).
Our cloud automation now reports results to the production wiki for each new compose.
The refactoring of Fedora Easy Karma was merged to the main branch. All places with links were also updated wrt the recent transition to Forge, and the migration is now done for this repo.
Forge QA repos now has a reusable workflow for an AI review.
More bugs hitting OpenQA automated testing were resolved, some some particular ones are very hard to debug, e.g. an ibus hang or an xdg-desktop-portal crash.

Forgejo

This team is working on introduction of https://forge.fedoraproject.org to Fedora
and migration of repositories from pagure.io.

[Forgejo] New Organization and Teams Request: Fedora KDE [Followup]
[Forgejo] Participated in the Forge review, planning and retrospective meet with Rodney, Nils, Ryan and David [Board]
[Forgejo] New organisation for Fedora Code of Conduct committee + migration [Followup] [Namespace] [Followup]
[Forgejo] New repo for Security SIG [Followup] [Namespace] [Followup] [Followup]
[Forgejo] New Organization and Teams Request: Fedora Btrfs [Followup] [Namespace]
[Docs] Will be migrating Release Notes imminently + branching for F44, contributions welcome once the repo appears on Forgejo
Forgejo runners added for orgs mindshare and apps
Private Issues
- Unit tests for code ⇔ DB boundary (Issue & PrivateIssue: done, related types: ongoing)
- Verify, debug and fix DB migration

UX

This team is working on improving User experience. Providing artwork, user experience,
usability, and general design services to the Fedora project

Updated all references to Fedora Design ticket tracker to point to Forgejo [ticket], migration of tickets still wip, but significant progress made.

If you have any questions or feedback, please respond to this report or contact us on #admin:fedoraproject.org channel on matrix.

The post Community Update – Week 10 2026 appeared first on Fedora Community Blog.

Miroslav Vadkerti: How a Single Regex Stalled 30 Testing Farm Jobs for Hours

2026-03-06T00:00:00+00:00

Christof Damian: Friday Links 26-08

2026-03-05T23:00:00+00:00

Ben Cotton: You’d better start believing in supply chains because you’re in one (SCaLE 23x)

2026-03-05T19:53:01+00:00

At SCaLE 23x, I’ll debut “You’d better start believing in supply chains because you’re in one.” This is my first talk that started as a silly joke, but it covers a serious and timely topic.

Abstract: “I’m not a supplier!” open source maintainers correctly say. When a large company comes in making unfunded demands, it drives volunteer maintainers away. But supply chain attacks are a reality and they don’t just affect megacorps. As an open source maintainer, you have a supply chain, too.

Improving your security improves safety for everyone. But how can volunteer maintainers who aren’t security experts do this work? This talk introduces easy practices and tools to address common software supply chain concerns. Attendees will also learn how to address supply chain and regulatory concerns from their downstreams.

Date: 8 March 2026

Location: Pasadena, CA, US

Slides

Resources

Looking for links to the tools I mentioned in the talk, perhaps because you’re sitting in the audience right now?

The post You’d better start believing in supply chains because you’re in one (SCaLE 23x) appeared first on Duck Alignment Academy.

Akashdeep Dhar: Fedora Project Community Corner @ DevConf.IN 2026 - Day Two

2026-03-05T18:30:06+00:00

Returning early from the dinner on the previous day was the right call to make, given how packed we were expecting the second day of DevConf.IN 2026 to be. Since this was going to be on 14th February 2026, i.e., a Saturday (and, of course, Valentine's Day), we would most likely have a greater footfall of folks around the conference professing their eternal love for free and open source software that day. I found myself waking up before the scheduled alarm, and as I had some time, I started working on manually awarding the attendees the event badge. For an over-occupied booth like ours, it was especially important since many folks could not get the chance to scan the QR code, and the greater attention was, of course, taken up by the DevConf.IN 2026's visitor choice, Fedora Project Community Trivia.

Collection A (Akashdeep Dhar and Shounak Dey, CC BY-SA 4.0)

Learning from the previous day's mistakes, I also decided to give myself some time for breakfast before getting an Uber ride. Somehow, I was able to get one without having to go through more than a couple of cancellations at around 0900am Indian Standard Time. After picking up the swagpacks, Shounak Dey and I set the location directly to the Vyas Building of MIT World Peace University - thus removing the hauling efforts from the day before. I also checked with the likes of Yashwanth Rathakrishnan and Samyak Jain in the meantime, both of whom had their hotel bookings a lot closer to the conference venue. Yashwanth had to skip breakfast since an Uber ride was arranged for him before he could get some food, while Samyak took his time to get ready and head over to the conference venue.

Collection B (Akashdeep Dhar, CC BY-SA 4.0)

Funnily enough, it was Matthew Miller, this time around, who had arrived at the venue by around 1000am Indian Standard Time and was lounging at the Fedora Project Community Corner. Shounak and I chuckled at the photograph shared by Yashwanth while we were on the way, since our punctuality from the day before might have most likely rubbed off on him. After a smooth ride, we soon arrived at the venue entrance at around 1030am Indian Standard Time. Given that we had the lay of the land and our posters were already placed properly, we had more time to conveniently set up our swagpacks and exhibits at our booth. I checked in with Matthew about how his preparations for his talk were going, while Shounak and Yashwanth started arranging the swagpacks and exhibits on the booth desk.

Collection C (Shounak Dey, CC BY-SA 4.0)

Samyak decided to add a couple more tricky questions to the question list of the Fedora Project Community Trivia. That was a brilliant idea since it allowed visitors from the previous day to go out of their way to explore more about the Fedora Project and its dealings. As we were quite economical with handing out swagpacks the day before, and none of us was in the mood for taking them back home, we decided to be rather generous that day. I devised a plan for handing out our limited-edition Fedora Project magnet-and-clip combo to the attendees entering Matthew's talk to appreciate their presence there, while Matthew contemplated whether he should extend his talk to include 35 Fedora Linux releases instead of the previously planned 30 of them, since he had to manage the talk duration.

Collection D (Shounak Dey, CC BY-SA 4.0)

As his talk was scheduled for 0115pm Indian Standard Time, we had more than enough time before then to attend to the visitors. We also decided to temporarily shut down the Fedora Project Community Corner for those 45 minutes to allow a larger audience to attend Matthew's presentation instead. Unfortunately, just like the day before, visitors continued to confuse our booth with the DevConf.IN registration desk. We had a frustrated Samyak craft a handwritten note at our booth to guide folks to the actual DevConf.IN registration desk. His frustrations were well placed, as even though we loved interacting with visitors, we would rather spend time and energy talking about the Fedora Project and Red Hat than being punished for the booth's attendance by becoming glorified compasses.

Collection E (Akashdeep Dhar and Shounak Dey, CC BY-SA 4.0)

A quick catch-up with Sudhir Dharanendraiah allowed me to remind him of the community dinner that we were planning to have later that day at Ishaara, Viman Nagar, and also share some Fedora Project stickers with him for them to be shared by the Red Hat India Communities booth personnel. That not only helped out the staff there, but it also allowed the Fedora Project to be cross-promoted across multiple co-located booths. Following this, I headed over next to the DevConf.IN registration desk to avail myself of a couple of DevConf.IN-themed magnets and clips. To return the goodwill, I also shared some Fedora Project magnet-and-clip combos with them to be shared by the visiting attendees, a gesture that they not only appreciated but that also allowed us to further pursue cross-promotion.

Collection F (Akashdeep Dhar and Shounak Dey, CC BY-SA 4.0)

At around 1200pm Indian Standard Time, Shounak and Yashwanth took off to explore the booths around DevConf.IN 2026, leaving Samyak and me to tend to the booth visitors. While the footfall did drop by the time they left, it slowly started picking up pace about fifteen minutes later, with questions around .NET compatibility in Fedora Linux and security developments in the Fedora Project. There was another wave of quiz participants who checked in with us about the Fedora Project Community Trivia answer keys and verified where they got things wrong. It was rather refreshing to see that while there were a few visitors who were argumentative about their defeat, a greater number embraced getting to know the things that they did not previously know about the Fedora Project and its dealings.

Collection G (Akashdeep Dhar and Shounak Dey, CC BY-SA 4.0)

One of the learnings we took away from organising an interactive event that made the best use of visitors being there in person was to order more exclusive swagpacks in the future. With Samyak dropping another handcrafted note to inform visitors about the temporary shutdown and me wrapping things up at the booth desk, we were pleasantly surprised by Sayak Sarkar, who managed to make it to the venue early that day. Samyak set up a countdown timer on his iPad placed on the booth desk to expire at around 0100pm Indian Standard Time to let folks know the same. After a quick catch-up with both Sayak and Deepesh Nair, we had the returning Shounak and Yashwanth haul the swagpacks and exhibits to the first floor's VY0104 room, where Matthew's talk was scheduled to be organised.

Collection H (Shounak Dey, CC BY-SA 4.0)

As Matthew was getting prepared for the talk, Shounak made his way to the elevated back of the room with his fancy Canon DSLR camera. Yashwanth and I worked on arranging the swagpacks on one of the front desks so that attendees could help themselves. The room was soon filled to the brim, and the talk went well, albeit with some minor considerations, with Matthew having to speed up the delivery toward the end to accommodate five more releases. Matthew also ensured that there was some time left at the end for questions and feedback; a bunch of them were related to artificial intelligence, his experience, changing times, and newer responsibilities. With the talk getting wrapped up at around 0200pm Indian Standard Time, the Fedora Project Indian Crew made it back to the ground floor.

Collection I (Akashdeep Dhar and Shounak Dey, CC BY-SA 4.0)

We had to wash our plans of having lunch at around that time down the drain since the booth activities were planned to wrap up earlier that day. That would have essentially meant that we had to be around to declare the winners of the second day of the Fedora Project Community Trivia at around 0230pm Indian Standard Time. Samyak made himself busy populating the scores on the raffle service while Shounak unsuccessfully tried sharing the progress on the Fedora Badges Revamp Project with Sayak. The poor cellular data reception, along with the wireless downtimes, made it extremely difficult for us to connect to the outside world. Yashwanth and I instead decided to field other conversations around the use of Fedora Linux in the robotics field and other adjacent infrastructure uses.

Collection J (Shounak Dey, CC BY-SA 4.0)

Matthew joined us soon, asking for feedback, and I shared that it would have been best to cover the earlier releases quickly while spending more time on the recent ones, because it was his personal experience as the Fedora Project Leader that people were there for. Since we coincidentally had him around then, it just made sense for him to felicitate the lucky winners with the exclusive Fedora Project-themed sippers. With Kashyap Ekbote helping us with the pictures after we were through with the awarding ceremony, Rajan Shah appreciated us for putting up a great show of community engagement at the conference. At around 0330pm Indian Standard Time, we started wrapping up our booth operations, with many enthusiastic visitors returning to express just how much they liked us there.

Collection K (Akashdeep Dhar, CC BY-SA 4.0)

Samyak and I went around reminding Matthew and Sayak about the dinner that he had booked previously in the morning, before seeing them off. For the late lunch, though, Shounak and Samyak discovered the La Sicilia Bistro and Patisserie restaurant, which was barely under five kilometres away from the event venue. On our way out, we swiftly got ourselves some photographs at the DevConf.IN 2026 event entrance was before we booked an Uber ride to the meal place. While the likes of Sudhir and Kashyap could not join us for lunch, Avadhoot Dhere gracefully joined our little party, and we did end up having quite the delicacies while sharing the best moments of the day. We saw each other off at around 0500pm Indian Standard Time after a rather late lunch and returned home on a quiet Uber ride.

Collection L (Akashdeep Dhar, CC BY-SA 4.0)

Having had a brief respite, one hell of a confusing disaster struck when I checked with Sudhir to restate the location of the restaurant. It turned out that Samyak had prebooked the wrong branch of the Ishaara restaurant, which was about thirty kilometres on the outskirts of the city, i.e., in Wakad and not the one that was under approximately ten kilometres from all ends, i.e., in Viman Nagar. I checked in with Samyak, but after not hearing back from him, I decided to create a new booking under my name amidst the filled capacity due to the Valentine's Day evening. Thankfully, I was able to get one, and after hearing from Matthew and Karen Miller about them having gone to the wrong location, I asked them to go on without us because it would have taken at least a couple of hours just to get there.

Collection M (Akashdeep Dhar, CC BY-SA 4.0)

Even Samyak had to tap out since he was feeling under the weather after all the work from the day, so I checked in with the likes of Shounak, Yashwanth, and Sudhir to reconfirm the correct location at around 0730pm Indian Standard Time. It was quite the mess-up, but I was not going to let the Fedora Project's community presence at DevConf.IN 2026 end on a sour note. The four of us ordered light bites with hand gestures, as the restaurant employed specially-abled people, and it was an enlightening experience to witness the world from their perspective. After some interesting conversations and unpacking catchups, Sudhir and Yashwanth left first before Shounak and I were able to find ourselves an Uber ride, finally breathing a sigh of relief after having organised this throughout the last couple of long days.

Peter Czanik: New toy: Installing Fedora Linux on the HP Z2 Mini

2026-03-04T11:56:13+00:00

Tim Waugh: Logsqueak: Rescuing Insights from the Logseq Journal

2026-03-04T11:30:43+00:00

I’ve been using Logseq for a year now and it’s become the backbone of my workflow. I have pages dedicated to specific topics, concepts, projects, meetings… all sorts of things.

During my day, when I want to note something down or write something out to think about it, the daily Logseq journal is the obvious place for it to go. It has been an invaluable habit to build. But there’s a catch: the journal can easily become a black hole. It ends up as a chaotic mix of meeting notes, fleeting thoughts, random ideas, task lists and the occasional moment of genuine insight.

Most of the time, I try to link journal items to the relevant pages. Sometimes I remember to update those pages in light of new information. But other times I forget, and those insights get buried in the timeline, only resurfacing if I explicitly search for them.

All of those things belong in the journal, but some of them also belong in permanent pages. I wanted a way to filter the signal from the noise and capture things that I can integrate into my pages, in a way that makes them traceable back to the journal, without leaving the keyboard.

Enter Logsqueak: a proof-of-concept experiment to see if a local AI model can act as an automated gardener for a Personal Knowledge Management (PKM) system.

How Logsqueak Works

It’s a Python-based terminal UI built with Textual, using RAG (Retrieval-Augmented Generation) via Ollama. Because PKM data is highly personal, my aim was to be able to build a tool that can run entirely on a local GPU, meaning your private journal entries never have to leave your machine. (Though you can certainly connect it to much larger cloud models if you prefer.)

The workflow is broken down into 3 phases:

1: Extraction (Signal vs. Noise)

In this phase, Logsqueak reads your Logseq journal and helps identify which items are ephemeral daily noise (e.g., “Morning standup at 9am”) and which are actual knowledge or insight worth keeping.

2: Refinement (Making it Evergreen)

Temporal context is stripped away, and additional context from parent bullet points is added in.

Original Journal Entry:
- Working on the new analytics dashboard
  - Finally figured out why the main chart was double-fetching data on load. The useEffect hook was missing the empty dependency array.
Logsqueak Refinement:
- To prevent double-fetching data on load in the analytics dashboard, ensure the useEffect hook for the main chart includes an empty dependency array.

3: Integration (Filing it Away)

In this final phase, the most semantically relevant pages in your Logseq graph are tracked down, and the best insertion point is identified. Logsqueak will suggest exactly which page and heading the new insight belongs under.

Logseq is built around powerful block properties, so crucially this is where the traceability happens. When an insight is integrated, Logsqueak adds an extracted-to:: property to the original journal block, linking it directly to the new block. The new block on the target page gets an id:: property linking back. This means you can always jump from your polished knowledge base straight back to the original journal entry to see the full context of what you were doing that day.

All writes are performed using a custom engine specifically built for Logseq’s Markdown format, ensuring your notes stay safe. Because this is a proof-of-concept, all writes are guarded by explicit user approval—Logsqueak won’t change your files without you saying “yes.”

Try it out!

Logsqueak requires Python 3.11+ and an AI assistant. You can use Ollama to run everything locally.

If you’re on Fedora, getting the prerequisites running is incredibly straightforward. Since Fedora Workstation ships with recent Python versions out of the box, you’re already halfway there. You just need to grab Ollama to run the models locally, set up a virtual environment, and you’re good to go:

# Assuming you've installed Ollama
git clone https://github.com/twaugh/logsqueak.git
cd logsqueak
./setup-dev.sh
source venv/bin/activate
logsqueak init

Taming the Knowledge Graph

This tool can help you turn a pile of daily logs into a structured, searchable knowledge base. Although it can’t yet create new pages from scratch or be given custom instructions about how best to integrate things into the graph, it’s already useful enough for me to use in my daily routine.

It’s very much a proof-of-concept though, and I’d love to get some feedback from other developers and knowledge management enthusiasts. You can check out the code on GitHub.

Building Logsqueak made me realise just how much time I spend thinking about note-taking friction. While Logsqueak handles my fast, keyboard-driven daily logging, I actually do a lot of my deep thinking away from the screen on a Ratta Supernote e-ink tablet.

I recently found myself trying to solve a similar “black hole” problem over there. The result is Slipstream: a Zettelkasten framework to let you build infinitely nested idea networks by hand.

If you happen to be an e-ink user who prefers a stylus to a keyboard when you need to disconnect and focus, you might find it an interesting contrast. As a bonus, because Slipstream has a structured convention, exporting those handwritten notes to plain text makes them perfectly readable for the exact kind of LLM processing Logsqueak relies on. It’s analogue thinking, ready for the AI age.

The post Logsqueak: Rescuing Insights from the Logseq Journal appeared first on PRINT HEAD.

Peter Czanik: Syslog-ng 4.11.0 packaging status

2026-03-04T08:31:45+00:00

Avi Alkalay: Uniqlo T-Shirt Bash Script Easter Egg

2026-03-03T21:18:35+00:00

At Uniqlo flagship store in Ginza, Tokyo, there was this T-shirt with an encoded shell script.

Well, I had to decode it and see the result.

I took a photo with my iPhone and used its own OCR, which made a lot of confusion between 0 (zero), O (capital o) and 8, mixed 1 and l (small L), and yielded many chars as very similar glyphs but in advanced Unicode ranges, which are invalid for Base64 encoding. It took me some time to fix it all. The final corrected text is this:

#!/bin/bash
eval "$(base64 -d <<< 'IyEvYmluL2Jhc2gKCiMgQ29uZ3Jhd
HVsYXRpb25zISBZb3UgZm91bmQgdGhlIGVhc3RlciBlZ2chIOKdpO+4jwojIOOBiuO
CgeOBp+OBqOOBhuOBlOOBluOBhOOBvuOBme+8gemaoOOBleOCjOOBn+OCteODl+OD
qeOCpOOCuuOCkuimi+OBpOOBkeOBvuOBl+OBn++8geKdpO+4jwoKIyBEZWZpbmUgd
GhlIHRleHQgdG8gYW5pbWF0ZQp0ZXh0PSLimaVQRUFDReKZpUZPUuKZpUFMTOKZpV
BFQUNF4pmlRk9S4pmlQUxM4pmlUEVBQ0XimaVGT1LimaVBTEzimaVQRUFDReKZpUZ
PUuKZpUFMTOKZpVBFQUNF4pmlRk9S4pmlQUxM4pmlIgoKIyBHZXQgdGVybWluYWwg
ZGltZW5zaW9ucwpjb2xzPSQodHB1dCBjb2xzKQpsaW5lcz0kKHRwdXQgbGluZXMpC
gojIENhbGN1bGF0ZSB0aGUgbGVuZ3RoIG9mIHRoZSB0ZXh0CnRleHRfbGVuZ3RoPS
R7I3RleHR9CgojIEhpZGUgdGhlIGN1cnNvcgp0cHV0IGNpdmlzCgojIFRyYXAgQ1RS
TCtDIHRvIHNob3cgdGhlIGN1cnNvciBiZWZvcmUgZXhpdGluZwp0cmFwICJ0cHV0I
GNub3JtOyBleGl0IiBTSUdJTlQKCiMgU2V0IGZyZXF1ZW5jeSBzY2FsaW5nIGZhY3R
vcgpmcmVxPTAuMgoKIyBJbmZpbml0ZSBsb29wIGZvciBjb250aW51b3VzIGFuaW1hd
Glvbgpmb3IgKCggdD0wOyA7IHQrPTEgKSk7IGRvCiAgICAjIEV4dHJhY3Qgb25lIGN
oYXJhY3RlciBhdCBhIHRpbWUKICAgIGNoYXI9IiR7dGV4dDp0ICUgdGV4dF9sZW5nd
Gg6MX0iCiAgICAKICAgICMgQ2FsY3VsYXRlIHRoZSBhbmdsZSBpbiByYWRpYW5zCiA
gICBhbmdsZT0kKGVjaG8gIigkdCkgKiAkZnJlcSIgfCBiYyAtbCkKCiAgICAjIENhb
GN1bGF0ZSB0aGUgc2luZSBvZiB0aGUgYW5nbGUKICAgIHNpbmVfdmFsdWU9JChlY2
hvICJzKCRhbmdsZSkiIHwgYmMgLWwpCgogICAgIyBDYWxjdWxhdGUgeCBwb3NpdGl
vbiB1c2luZyB0aGUgc2luZSB2YWx1ZQogICAgeD0kKGVjaG8gIigkY29scyAvIDIpIC
sgKCRjb2xzIC8gNCkgKiAkc2luZV92YWx1ZSIgfCBiYyAtbCkKICAgIHg9JChwcmlu
dGYgIiUuMGYiICIkeCIpCgogICAgIyBFbnN1cmUgeCBpcyB3aXRoaW4gdGVybWluY
WwgYm91bmRzCiAgICBpZiAoKCB4IDwgMCApKTsgdGhlbiB4PTA7IGZpCiAgICBpZi
AoKCB4ID49IGNvbHMgKSk7IHRoZW4geD0kKChjb2xzIC0gMSkpOyBmaQoKICAgICM
gQ2FsY3VsYXRlIGNvbG9yIGdyYWRpZW50IGJldHdlZW4gMTIgKGN5YW4pIGFuZCAyM
DggKG9yYW5nZSkKICAgIGNvbG9yX3N0YXJ0PTEyCiAgICBjb2xvcl9lbmQ9MjA4CiA
gICBjb2xvcl9yYW5nZT0kKChjb2xvcl9lbmQgLSBjb2xvcl9zdGFydCkpCiAgICBjb
2xvcj0kKChjb2xvcl9zdGFydCArIChjb2xvcl9yYW5nZSAqIHQgLyBsaW5lcykgJSBj
b2xvcl9yYW5nZSkpCgogICAgIyBQcmludCB0aGUgY2hhcmFjdGVyIHdpdGggMjU2L
WNvbG9yIHN1cHBvcnQKICAgIGVjaG8gLW5lICJcMDMzWzM4OzU7JHtjb2xvcn1tIiQ
odHB1dCBjdXAgJHQgJHgpIiRjaGFyXDAzM1swbSIKCiAgICAjIExpbmUgZmVlZCB0b
yBtb3ZlIGRvd253YXJkCiAgICBlY2hvICIiCgpkb25lCgo= ')"

When base64-decoded, this bash script appears:

#!/bin/bash
# Congratulations! You found the easter egg! ❤
# おめでとうございます！隠されたサプライズを見つけました！❤
# Define the text to animate
text="♥PEACE♥FOR♥ALL♥PEACE♥FOR♥ALL♥PEACE♥FOR♥ALL♥PEACE♥FOR♥ALL♥PEACE♥FOR♥ALL♥"
# Get terminal dimensions
cols=$(tput cols)
lines=$(tput lines)
# Calculate the length of the text
text_length=${#text}
# Hide the cursor
tput civis
# Trap CTRL+C to show the cursor before exiting
trap "tput cnorm; exit" SIGINT
# Set frequency scaling factor
freq=0.2
# Infinite loop for continuous animation
for (( t=0; ; t+=1 )); do
    # Extract one character at a time
    char="${text:t % text_length:1}"
    # Calculate the angle in radians
    angle=$(echo "($t) * $freq" | bc -l)
    # Calculate the sine of the angle
    sine_value=$(echo "s($angle)" | bc -l)
    # Calculate x position using the sine value
    x=$(echo "($cols / 2) + ($cols / 4) * $sine_value" | bc -l)
    x=$(printf "%.0f" "$x")
    # Ensure x is within terminal bounds
    if (( x < 0 )); then x=0; fi
    if (( x >= cols )); then x=$((cols - 1)); fi
    # Calculate color gradient between 12 (cyan) and 208 (orange)
    color_start=12
    color_end=208
    color_range=$((color_end - color_start))
    color=$((color_start + (color_range * t / lines) % color_range))
    # Print the character with 256-color support
    echo -ne "\033[38;5;${color}m"$(tput cup $t $x)"$char\033[0m"
    # Line feed to move downward
    echo ""
done

The original encoded text, when executed in my Linux terminal gives a beatiful animation, similar to this:

After decoding and executing the script, I found other people doing the same:

But I swear I decoded it myself first, without any help.

Akashdeep Dhar: Fedora Project Community Corner @ DevConf.IN 2026 - Day One

2026-03-03T18:30:29+00:00

As the event owner for the Fedora Project’s community presence during the DevConf.IN 2026 conference, I had to ensure that I made it to the event venue as early as possible. The first day began with me getting ready by 0930am Indian Standard Time since I had returned from meeting the likes of Samyak Jain, Matthew Miller and Karen Miller late the day before. I had to put a pin on my plans to check the inventory of the swag packs that I had delivered at Shounak Dey’s house, as it was quite the struggle to get us Uber rides to the MIT World Peace University campus, Kothrud. While checking with Yashwanth Rathakrishnan, I also ensured that I packed the essential tooling that might come in handy while establishing and tearing down our booth at the DevConf.IN venue.

Collection A (Akashdeep Dhar, CC BY-SA 4.0)

After a couple of Uber cab cancellations, Shounak and I were finally on our way from Chandan Nagar to Kothrud. We seemed to have greatly underestimated the time it would take for us to get there, as not only was it thirty kilometres away from us, but the morning office-going traffic was also at its peak. We projected that it would take us around an hour to get there, but since the booth activities were to begin from 1100am Indian Standard Time onwards, we had ample time in our hands. I checked in with Yashwanth and Samyak on our organiser chatroom, who had reached there by around 1000am Indian Standard Time. They had joined the queue to pick up their badges and swag packs from the organiser’s desk, and also went ahead to visit where our Fedora Project Community Corner was located.

Collection B (Akashdeep Dhar, CC BY-SA 4.0)

To both Shounak’s and my chagrin, we figured out a little too late that the venue had been moved to the newly constructed Vyas Building of the MIT World Peace University campus. We realised it after our (rather friendly) Uber driver dropped us off, so the two of us had to walk around a kilometre hauling the heavy swag boxes and booth equipment. I did connect with Yashwanth and Samyak so that they could help carry those over from the entrance, but there must have been a disconnect, as Shounak and I had to sweat our way into the Vyas Building anyway. After passing a security check and a flight of wide stairs, our relief came in the form of one patient, Avadhoot Dhere, whom we met at the building’s entrance, who helped us carry our load to the Fedora Project Community Corner location.

Collection C (Akashdeep Dhar, CC BY-SA 4.0)

At around 1030am Indian Standard Time, we had about thirty minutes to get our community booth set up with exhibits and swag packs. I delivered a quick briefing to our on-site Fedora Project Indian Crew on what was expected of them and how they had to abide by the DevConf.IN Code of Conduct, when to take breaks after duly informing about the same, and how judicious they have to be regarding the swag distribution. We started drawing quite a huge crowd of early visitors to the booth while we were busy setting up the community booth, a bunch of whom confused our location with the registration desk. Huge kudos to Rajan Shah, who helped us secure a strategic location to allow for most (if not all) community conversations to come to us first before they seeped into other booths.

Collection D (Akashdeep Dhar, CC BY-SA 4.0)

While Samyak and Shounak got busy setting up the A3-sized posters that I had previously designed, Yashwanth and I worked on organising the swag stickers and swag magnets on our booth desk. I briefly paused to take in just how amazing a task the DevConf.IN 2026 organising committee did with arranging the booth backdrops and positioning the two desks at a right angle for us. With Samyak’s handspan calculations and Shounak’s accurate pasting, we soon had our four posters on topics like Matthew’s presentation, Flock To Fedora 2026, DevConf.IN 2026’s Fedora Badge and Fedora Project Community Trivia, ready to go. Since we had visitors lining up already before the scheduled beginning, we had to double-time addressing the people and setting up our Fedora Linux-powered laptops.

Collection E (Shounak Dey, CC BY-SA 4.0)

By around 1100am Indian Standard Time, we had already addressed approx 200 visitors at the booth, so you could imagine just how difficult the opening hours were for the on-site Fedora Project Indian Crew to handle that wave. Our economical yet outgoing approach towards handing out our limited swag packs allowed us to pace ourselves while dealing with a huge number of attendees. To add to that, our inclusive demeanour towards the visitors allowed them to bring their conversations and feedback about Fedora Linux and/or the Fedora Project to us. While the population numbers did not hold a candle against the likes that we usually get in places like FOSDEM, I extended those experiences to ensure that we did not stretch ourselves thin while answering questions and receiving feedback.

Collection F (Akashdeep Dhar, CC BY-SA 4.0)

We were also visited by Dorka Volavkova, who checked in with me about the situation regarding the availability of swag packs at our booth. While I was initially dependent on folks portering in swag packs from various other events due to logistical difficulties, I soon realised that the plan was not reliable. I informed her about my decision to extend the Fedora Mindshare budget request by about USD 150 to ensure that I could produce the swag packs locally with Rajan’s and Devang Parikh’s assistance. This not only allowed for deterministic representation at DevConf.IN 2026, but the same resources could also be used for organising more such Fedora Project events around India or APAC. Dorka was happy to note that we followed an ideal process of getting swag packs for events from local vendors.

Collection G (Shounak Dey, CC BY-SA 4.0)

As the footfall slightly slowed down, Shounak and I took that opportunity to leave for the registration desk to pick up our badges and swag packs. It had literally escaped our minds since we were occupied with setting up the Fedora Project Community Corner, but we did manage to get our DevConf.IN-themed backpack and ID badges on time. We fielded various questions from visitors wanting to know about what the Fedora Project is, how Fedora Linux differs from other distributions, how Fedora Linux shapes the future of enterprise distributions, and what one can do to get started with contributing. Yashwanth suggested rewarding more interesting conversations with our limited-edition Fedora Project magnet-and-clip combo, and that helped us drive the course of our conversations and shape an open narrative.

Collection H (Shounak Dey, CC BY-SA 4.0)

Matthew soon arrived at around 1200pm Indian Standard Time, and that not only gave us one more person to field interactions with, but the visitors could also avail themselves of the historical context about the Fedora Project that he could offer, having served in the Fedora Project Leader position for over a decade. This was also our opportunity to gather folks around us and promote his talk about “30/35 Fedora Linux Releases in 30/35 Minutes”, which was scheduled for the next day. The younger, college-going crowd looked up to us for working on free and open source software as our full-time employment and wanted to understand how they could begin doing the same. This was a great opportunity for us to showcase our onboarding pathways into the community through the Fedora Join SIG.

Collection I (Shounak Dey, CC BY-SA 4.0)

Among the curious questions that I fielded, a couple that I remember had to do with the incompatibility of Fedora Linux as a student base operating system for attempting CNCF certification examinations and the apparent lack of a long-term release in the Fedora Linux offerings. While I personally did not have any experience with those examinations, I elaborated on how Fedora Linux’s focus on innovation and the fast-moving release cycle could be something that could not be conveniently kept up with by the examination proctors. As for the question about the Fedora Linux long-term distribution release, I recommended that they use CentOS Stream and/or the Red Hat Enterprise Linux Developer Subscription for more serious workloads that require strict quality and uncompromising support.

Collection J (Shounak Dey, CC BY-SA 4.0)

As I was wearing a CentOS Linux-themed tee, I was also able to steer discussions into explaining how the Fedora Project’s decisions around technologies such as the systemd movement, PipeWire inclusion, Wayland defaults, etc., were seen as controversial in the past but ended up becoming industry standards just a couple of years later. I wanted our conversations with the visitors to be a gateway through which they could start exploring the space of open source enterprise distributions and potentially begin contributing to the projects of their interest. Amidst our conversations, the visitors were drawn to the Fedora Project Community Trivia that Samyak helped craft questions for, and the fact that it had an exclusive Fedora Project-themed sipper as an award prize only helped us farm more engagement.

Collection K (Akashdeep Dhar and Shounak Dey, CC BY-SA 4.0)

Shounak stayed busy photographing with his fancy Canon DSLR camera as we guided visitors to scan the QR code on our posters to do things like get themselves the associated Fedora Project event badge, learn more about the annual flagship contributor conference, Flock To Fedora 2026, and, of course, participate in the Fedora Project Community Trivia. A bunch of these visitors had experience using a GNU/Linux distribution, and with us sharing just how Fedora Linux allows them to build solutions for the consumers of today and tomorrow, with its packages being on the leading edge, they were eager to try it out on their personal devices. There were comparison conversations against the likes of Microsoft Windows and Apple macOS, too, on a more superficial level, among the younger folks there.

Collection L (Shounak Dey, CC BY-SA 4.0)

A DevConf.IN volunteer, Rahul Sharma, visited our booth to inform us about the catering being served on the eighth floor of the building at around 0100pm Indian Standard Time. Right around this time, we had a confusing conflict with a fellow speaker or booth participant who we found to be taking away Shounak’s swag pack, claiming it to be theirs since they had left it there for the restroom. While we could not verify the truthfulness of their claim, I sternly asked them to return the swag pack to Shounak and verify with his friends before pressing further. Since he did not bother informing any of the booth staff about leaving behind his objects, we could not be held responsible for any misplaced belongings. For all that trouble, it turned out that his friend indeed had his swag pack with him all along.

Collection M (Shounak Dey, CC BY-SA 4.0)

After reporting this awkward incident to an adjacent DevConf.IN volunteer, Shounak and I decided to head upstairs for lunch. With Matthew leaving, it was down to the four of us handling the booth, so we wanted to ensure that the booth was staffed by at least a couple of folks at any given time. Since both Samyak and Yashwanth mentioned that they were not feeling hungry enough, the two of us decided to scale through sixteen flights of stairs to make it to the eighth floor. It is not that the place did not have elevators, but they were jam-packed, and we would have ended up wasting time waiting for a vacant one to become available, given how popular DevConf.IN 2026 ended up being in terms of attendee count. We also connected with Avadhoot to check on his experience at the conference so far.

Collection N (Shounak Dey, CC BY-SA 4.0)

We did end up wasting our time, though, since we found a huge queue on the eighth floor at the dining establishment serving volunteers, speakers and staff. Actually, scratch that, it was not entirely a wasteful endeavour because I got to meet up with Brian Proffitt, whom I met after almost a year or so since the previous DevConf.IN. After a brief catch-up and a bio break, the two of us headed back to the booth, since waiting in the queue doing absolutely nothing before spending more time to have food would have been wasteful. Instead, Shounak and I decided to go across the place to see what other booths had to offer, which led me to meet a bunch of community friends and fellow employees. We met Sudhir Dharanendraiah while we were exploring, meeting after almost a couple of years.

Collection O (Akashdeep Dhar, CC BY-SA 4.0)

He remarked that the booth personnel from the Red Hat India Communities ran out of their swag during the first few hours of the event's commencement and praised how we kept visitors engaged throughout the day. He also said that not combining the Fedora Project community booth with the Red Hat India Communities was the right call, since that allowed us to be crystal clear in our messaging that the Fedora Project and Red Hat do indeed care about India and APAC users and contributors. We were even asked whether we had a regional community presence or meetup cadence, which gave us something to explore and consider from the Fedora Mindshare activity perspective. The two of us finally came back to the booth, letting Samyak and Yashwanth head away for lunch.

Collection P (Akashdeep Dhar, CC BY-SA 4.0)

The other major questions and feedback that came to us about Fedora Linux had to do with what we were planning to do around artificial intelligence. Being a Fedora Mindshare representative to the Fedora Council at the time, and also someone who proposed the creation of an AI-assisted contribution policy, I elaborated on how inclusive our community had recently become towards policy-abiding AI-assisted contributions. I also emphasised that with subprojects and SIGs around AI, ML, and PyTorch, our focus was to establish Fedora Linux as a general-purpose platform of choice for generalists, developers, sysadmins, or enthusiasts to build AI-powered technologies on, rather than have AI-based solutions that no one asked for enabled by default in our primary offerings.

Collection Q (Shounak Dey, CC BY-SA 4.0)

We met Pravin Satpute, who suggested that we have lunch at the cafeteria on the fifth floor, and after letting Samyak and Yashwanth return from their exploration, we headed there with Avadhoot. The dining choice was limited to a Vegetarian Biryani and Cold Coffee, but at around 0230pm Indian Standard Time, that felt like a divine serving. We were able to get ourselves an elevator this time around, and after a brief catch-up with the likes of Saumili Dutta and Kashyap Ekbote, both of whom I met previously during GNOME Asia 2024 in Bengaluru, we returned to the booth. I made it a point to remind the booth crew to stay hydrated now and then, given just how easy it could be for folks to forget about self-preservation after being overwhelmed by almost 600 visitors since we reached the conference.

Collection R (Shounak Dey, CC BY-SA 4.0)

Coincidentally, I met Harshavardhan Sharma from openSUSE, whom we had met in the past in another conference, along with Sahil Tah, a college senior from my alma mater. DevConf.IN 2026, did manage to bring like-minded individuals into one place, regardless of which industry they belonged to, showing that openness and innovation are indeed the way forward when it comes to technology. Rajan made a visit to the Fedora Project Community Corner around that time, and he admired how we kept visitors occupied while providing them with things to learn and swag to collect. We were also soon visited by the likes of Amita Sharma and Sudhir Menon, whom we caught up with after a long time, while offering them the warm embrace that the Fedora Project’s “Friends” foundation is known for.

Collection S (Shounak Dey, CC BY-SA 4.0)

I was also briefly visited by some folks who thought that we had mistaken the answer keys in the Fedora Project Community Trivia, but to their surprise, those were made tricky on purpose. I provided them with the context of how I planned those deceptively difficult questions while emphasising that we wanted the four winners each day of the conference to feel special about their victory. Since I had procured eight limited-edition Fedora Project-themed sippers for the winners, the attendees not only had to exhibit their community knowledge by getting full marks but also had to be lucky enough to emerge victorious in a raffle. We wanted folks to return to the booth thirty minutes before closing time for the announcements.

Collection T (Akashdeep Dhar, CC BY-SA 4.0)

While Samyak worked on populating the raffle with the high scorers on his laptop, I checked with Sayak Sarkar, who was visiting DevConf.IN, just like the year before. As the Vyas Building gave us very poor cellular reception, it was incredibly challenging to point him in the correct direction, especially since, while the venue remained the same as the previous year, the actual location had moved. For their first experience manning a community booth, I could not help but watch from a distance just how well both Shounak and Yashwanth did as volunteer contributors as I waited for Sayak to turn up at the Fedora Project Community Corner. At around 0430pm Indian Standard Time, I caught up with Sayak and introduced him to the Indian Crew as the curious crowd started gathering for the results.

Collection U (Akashdeep Dhar, CC BY-SA 4.0)

With the four winners being announced and felicitated by both Samyak and me, the visitors cheered for the winners as well as for the exciting activity. We clicked a few more pictures with Matthew before he went on his way to attend the dinner with the DevConf.IN speakers, organisers, and members. While I was invited to the dinner as well on behalf of the Fedora Project, it made little sense to me not to go out with the hardworking Fedora Project Indian Crew instead. In one of the conversations with Sayak and Shreyank Gupta, I was pleasantly surprised to learn that Shreyank was also a fellow Bengali, since I had always interacted with him in either English or Hindi for the past five years or so. After a few more pictures were taken by Shounak at the booth, we decided to start wrapping things up for the day.

Collection V (Akashdeep Dhar, CC BY-SA 4.0)

We unfortunately had to send some visitors back, and ask them to return the next day, who wanted a demonstration of Fedora Workstation at our exhibits. We had more than half of the swag packs left in our inventory, even after giving away a huge number of them to be cross-shared by the Red Hat India Communities booth personnel. After taking an inventory of all the belongings we had with us, we started looking for Uber rides back home. While we left the posters behind on the backdrops, we decided to take everything else with us to avoid misplacing them. It took a while for that to be confirmed, but after Samyak and Yashwanth got theirs, Shounak and I got ours, and we decided to leave for our homes around 0530pm Indian Standard Time, since we planned to reconvene for dinner later that day.

Collection W (Akashdeep Dhar, CC BY-SA 4.0)

After a rather uneventful but lengthy Uber drive, Shounak and I made it back to our homes. The evening went quite smoothly, with a pre-booking for dinner done at Wasabi15 under my name and Samyak and Yashwanth arriving early by 0800pm Indian Standard Time. Using the budget that I had previously requested from my management, we were able to have a great time unpacking from a busy day running operations at the Fedora Project Community Corner. Yashwanth sought advice on how he could take his contributions further, and Shounak shared how he got started in free and open source software contribution. With some great Asian cuisine and even greater conversations, we called it a night at 1000pm Indian Standard Time and went back to our places to prepare for the next day.

Fedora Community Blog: Fedora Documentation translations not available from March 4th, 2026

2026-03-03T10:00:00+00:00

Fedora Documentation translations will be put on hold from March 4th as the Fedora Localization Team has started the process of migration from pagure.io to the Fedora Forge. From the date, translation projects of the documentation (with ‘fedora-docs-l10n’ in name) will be gradually locked on the Fedora translation platform. Translation automation of the Docs website will also be stopped in the Fedora infrastructure. Consequently, there will be no translation updates available in the language versions on the Fedora Documentation.

The migration involves all repositories which support and ensure the availability of translations of the Fedora Documentation. There is no possibility the migration can be performed ‘on the fly’ as changes in the repositories, related scripts and continuous integration with the translation platform cannot be dealt with independently. Therefore the translation process of the Fedora Documentation is kept on hold.

We regrettably ask the Fedora contributors, our translation community, to pull back from translating of the Fedora Documentation and wait till the translation automation of the documentation is resumed again.

The progress of migration can be followed in the localization tracker as issue #52.

The post Fedora Documentation translations not available from March 4th, 2026 appeared first on Fedora Community Blog.

Brian (bex) Exelbierd: Jekyll Reads: the tooling behind my reading list

2026-03-03T07:50:00+00:00

In Rediscovering Reading (Without the Social Media Part) I wrote about stepping away from scrolling and building a slower, more deliberate reading habit. Part of that shift was making my reading log public without tying it to a dedicated social network.

The mechanics behind that were simple but fussy: keep a YAML file up to date, copy and paste links from Open Library, remember to grab cover images, and wire everything into Jekyll templates for the reading page and sidebar. None of it was hard, but it was just annoying enough that I knew future‑me would start skipping updates.

I built Jekyll Reads to make that workflow tolerable.

What Jekyll Reads actually does

Jekyll Reads is a small collection of pieces designed around a single idea: keep all the book data in one _data/reading.yml file and let everything else be presentation.

The core pieces are:

A shared Node.js library that talks to Open Library, picks a reasonable match, and produces a standard YAML snippet for a book
A command‑line tool that lets you search for a book and print the YAML to stdout, with options for indentation and auto‑selecting results
A Vim integration that shells out to the CLI and drops the YAML directly into your buffer at the right indentation level
A Visual Studio Code extension that does the same thing from inside the editor, with a proper search UI and update checks for the extension itself

All of this is intentionally boring: no external Node dependencies, just the built‑in modules and a bit of glue. The point is to make it slightly easier to keep the reading list current than to let it drift.

How it shows up on this site

On this site, the source of truth is _data/reading.yml. Entries that are still in progress, finished, or abandoned are all represented there with the same structure. The YAML includes things like start and finish dates, a link to more information (usually Open Library), an optional cover image, and a free‑form comment.

That data feeds two places:

The dedicated reading page, which separates currently‑reading, finished, and abandoned books and shows covers, dates, and comments
A small sidebar block on the home page that surfaces what I am currently reading, so the log is visible without needing a whole post for every book

Jekyll Reads does not try to be a general bookshelf app. It just reflects what I am already doing: writing short notes in YAML and publishing them along with the rest of the site.

Design constraints and trade‑offs

I made a few deliberate choices that might look odd if you are used to larger toolchains:

No external Node dependencies. The library and CLI only use built‑in modules like https and readline. That keeps installation simple and makes it easy to run in constrained environments.
Open Library as the primary data source. It provides book metadata, cover images, and stable URLs without requiring another account or scraping.
Plain YAML as the storage format. A static _data file is easy to version, review, and back up. It also plays nicely with Jekyll’s existing data pipeline.
Multiple small tools instead of one big one. The CLI, Vim integration, and VS Code extension all sit on top of the same library, so they stay in sync without each re‑implementing the logic.

If any of that stops being true in the future, I can replace or extend the pieces without touching the core data file.

If you want to use it

The repository README walks through how to set up your own _data/reading.yml, wire up a reading page and sidebar, and use the CLI or editor integrations. It is written so that you can follow it even if you are not using the same Jekyll theme I am.

The code is MIT‑licensed and shipped under Electric Pliers LLC. If you want a lightweight way to publish a reading log without standing up a whole social network, you might find it useful.

You can find the repository and full documentation here: https://github.com/ElectricPliers/jekyll-reads

Matthew Garrett: To update blobs or not to update blobs

2026-03-03T03:09:48+00:00

Tony Asleson: Honey, I Shrunk the Model (Maybe): blk-archive vs AI Data

2026-03-03T00:00:00+00:00

Kevin Fenzi: misc fedora bits last week of feb 2026

2026-02-28T17:10:26+00:00

The year is rolling along, and here we are at the end of Feb.

Lots of small day to day items

There were a lot of small day to day investigations and incoming requests, along with a pretty large amount of pull requests for our ansible repo. Since we are in Beta freeze some of them will have to wait, but some we can test out in staging now. It's great to see people submitting fixes and enhancements.

There were also some small fun to debug issues this week, including:

The https://whatcanidoforfedora.org/ site was sometimes alerting that it's ssl cert was expired. Turns out this was caused by that domain having old ip's for 2 proxies that had moved datacenters. So, sometimes it hit those, timed out and the ssl check just assumed it was bad. So, it was DNS. :)
The fedorapeople.org web server started being very slow to respond. Turns out the scrapers were hitting the cgit interface there and downloading xz snapshots of every commit. This caused the server to have to try and compress things over and over again. So, for now I just disabled those links and increased resources on the webserver. scrapers continue to keep on giving.

Secure boot signing work

Much of my time this week has been spent working on our new secure boot signing workflow. This is really really overdue and something I was hoping to finish mid last year, but things kept coming up and it kept getting pushed back.

The new setup leverages our existing signing infrastructure (sigul) so there's no need for special build hardware anymore. It also removes some constraints in the existing setup allowing us to do something we have wanted for a long time, namely sign aarch64 boot loader artifacts for secure boot.

Kudos to Jermey Cline for all his work on the code to make this possible. This uses the siguldry-bridge, rust based server to talk to sigul, and hopfully before too long we can replace the sigul server side with the new rust based server too.

I got everything deployed, I am now able to sign things, but in testing on my aarch64 laptop, there's still some issue with grub2 that needs to be sorted out. Hopefully it's something not too difficult to track down and we can move to this new setup after beta freeze once and for all.

comments? additions? reactions?

As always, comment on mastodon: https://fosstodon.org/@nirik/116149442549416772

Tim Waugh: Patchutils 0.4.5 released

2026-02-27T16:04:38+00:00

I have released version 0.4.5 of patchutils and also built it in Fedora rawhide. This is a stability-focused update fixing compatibility issues and bugs, some of which had been introduced in 0.4.4.

Compatibility Fix: Git Extended Diffs

Version 0.4.4 added support in the filterdiff suite for Git’s extended diff format. Git diffs without content hunks (such as renames, copies, mode-only changes and binary files) were included in the output. This broke compatibility with 0.4.3.

For 0.4.5 this functionality is now gated with a --git-extended-diffs=include|exclude parameter. The default for 0.4.x is to exclude files in Git extended diffs with no content. There were also some fixes relating to file numbering for these types of diffs.

Note: in 0.5.x this default will change to include.

Status Indictors for grepdiff

Previously grepdiff --status showed ! for all matching files, but now it correctly reports them as additions (+), removals (-) or modifications (!).

As always, bug reports and feature requests are welcome on GitHub. Thanks to everyone who reported issues and helped to test fixes!

The post Patchutils 0.4.5 released appeared first on PRINT HEAD.

Fedora Community Blog: Community Update – Week 9, 2026

2026-02-27T15:13:10+00:00

Week: 20 Feb – 27 Feb 2026

Fedora Infrastructure

This team is taking care of day to day business regarding Fedora Infrastructure.
It’s responsible for services running in Fedora infrastructure.
Ticket tracker

Migration of pagure.io repositories continues
Ansible repository now has CI running in runner
Resolved errors on dist-git that were spamming sysadmin-main mailbox – ticket

CentOS Infra including CentOS CI

Release Engineering

This team is taking care of day to day business regarding Fedora releases.
It’s responsible for releases, retirement process of packages and package builds.
Ticket tracker

Release engineering is currently in Beta Freeze.
Releng has provided the first beta release candidate after the QE request.
Request for creating detached signature has been handled by Samyak for ignition 2.26.0 release.

RISC-V

This is the summary of the work done regarding the RISC-V architecture in Fedora.

Continued to go through the list of packages to investigate (failing to build; requires patching, and more).
- Got a PR merged for ‘libkrunfw’ (a low-level library for process isolation) and built it in RISC-V Koji; Marcin (“hrw”) also got a couple more merged.
Work is progressing well on Fedora RISC-V unified kernels (Jason Montleon is doing most of the heavy-lifting here). Currently hosted in Copr.

AI

This is the summary of the work done regarding AI in Fedora.

Worked on the AI-powered This Week in Fedora.
Updated ai-code-review to use Gemini 3.1 Pro by default
Nexus team: interesting experience using Claude to refactor fedora-easy-karma, on review we found it made multiple unrequested functionality changes which complicated the review, after discussion decided to re-prompt it to avoid functionality changes

QE

This team is taking care of quality of Fedora. Maintaining CI, organizing test days
and keeping an eye on overall quality of Fedora releases.

Fedora 44 Beta testing in full swing
Kernel 6.19 test week in progress, please contribute
Help wanted: if anyone can help figure out why F44 boot occasionally just hangs for no very obvious reason that’d be great (details in bug)

Forgejo

This team is working on introduction of https://forge.fedoraproject.org to Fedora
and migration of repositories from pagure.io.

Create and present Fedora -> Forgejo efforts during FOSDEM 2026 Distributions Devroom [Video] [Followup]
Pagure migration doc: add follow-up checklist based on Nexus team’s [Review]
Create new organisation and namespace on Fedora Forge for Fedora Join [Followup] [Namespace]
Rename “translations” into “localization-docs” [Followup][Namespace]
- Remedy mapping after renaming translations to localization-docs [Commit]
Migrating NeuroFedora SIG [Followup][Namespace][Update]
- Perform mapping for NeuroFedora SIG teams and groups [Commit] [Followup]
New Organization and Teams Request: Fedora KDE [Followup][Triaged]
- Perform mapping for Fedora KDE teams and groups [Commit]
REST API: Create private issue & foundational work [Followup]
Runner for forge organization [Followup]
Refactor the ansible-role-forgejo-runner role task now configured and deploy the runners using ansible-pull
Clean out the spam from Pagure.io [Followup]
Refactor internal APIs for public vs. private issue identity [Followup][Feature]

EPEL

This team is working on keeping Epel running and helping package things.

Completed EPEL 10.2 mass branching in preparation for the upcoming RHEL 10.2 release (announcement)

UX

This team is working on improving User experience. Providing artwork, user experience,
usability, and general design services to the Fedora project

Madeline’s F45 Wallpaper Process Update: blog post / discussion post
The Fedora Design Team has switched to using Google Meet for our weekly meetings to utilise Gemini for note-taking. Discussion took place on this ticket and on our weekly call. Updated Fedocal entry can be found here.
Forgejo migration: Sprint board created, tickets currently being imported, remaining assets currently being imported / reorganised.

If you have any questions or feedback, please respond to this report or contact us on #admin:fedoraproject.org channel on matrix.

The post Community Update – Week 9, 2026 appeared first on Fedora Community Blog.

Guillaume Kulakowski: Mise en place d’Anubis sur l’instance Scaleway de Fedora-Fr

2026-02-27T11:22:00+00:00

Tim Lauridsen: INTERSECT - A nondestructive, time-stretching, and intersecting sample slicer

2026-02-27T06:00:00+00:00

Christof Damian: Friday Links 26-07

2026-02-26T23:00:00+00:00

Peter Czanik: New toy: Installing Ubuntu on the HP Z2 Mini

2026-02-26T14:06:13+00:00

Peter Czanik: Version 4.11.0 of syslog-ng is now available

2026-02-25T13:11:05+00:00

Ben Cotton: Trust in open source communities

2026-02-25T12:00:00+00:00

In chapter 3 of Program Management for Open Source Projects, I talk about the importance of trust. “Open source communities run on trust,” I wrote. I go on to talk about building trust by establishing relationships and credibility. This is fine when you’re coming into a defined role, perhaps if you got hired to fill a sponsored role in a community or if a project leader has asked you to apply your skills to the project.

Most people, of course, don’t come directly into a defined role. They start by making a small contribution: filing a bug, answering a question on a mailing list or forum, submitting a patch, and so on. Sometimes, they don’t even plan to stick around. They’re making one contribution and moving on. The kind of trust-building based on relationships doesn’t work as well in that case. But you still need trust to evaluate a contributor (and thus their contribution).

This issue has only grown more relevant as large language models become widespread. If the person who submitted a pull request didn’t write the code, do they understand it? Can they answer maintainers’ questions or address feedback? Is the code even worth a maintainer’s time to review or is it plausible-looking garbage?

In late January, GitHub product manager Camilla Moraes started a conversation seeking ideas for giving maintainers tools to address low-quality contributions. The conversation produced many good (and also some bad) ideas and highlighted the difficulty of a universal solution. Although the word “trust” only appears six times (as of this writing) in the whole thread, the conversation is basically a discussion of trust. “How can we slow the rate of un-trusted contribution without making life harder for the trusted contributors?” is a fair summary of the underlying issue.

Defining trust

Charles H. Green developed an equation of trustworthiness that includes credibility, reliability, and intimacy. Although it’s a smidge hokey, it’s fundamentally a reasonable representation of trust, so we can roll with it.

Importantly, trust is not a static characteristic of a person. Instead, it’s a dynamic measure that changes based on context and relationship. My coworkers (hopefully) think that I am competent in my work, deliver what I say I will, and am a fun guy to be around. There’s a high degree of trust because I rate highly in credibility, reliability, and intimacy. When I join a new project, I am the same person, but I am relatively or entirely unknown. The other people in the community need to interact with me for a period of time before they can develop trust in me.

Even if I’ve known someone for a long time, their trust in me may change when the context changes. The intimacy and reliability may be the same, but they don’t necessarily know if I’m credible in the new context. Just because I have experience in other languages, that doesn’t mean my Rust code is good. Someone who thinks I write competent Python (we’re pretending here!) would be well served reviewing a Rust contribution very closely, as I’ve written essentially none.

Trust in your community

As with many concepts, we often think about trust in open source communities without explicitly thinking about it. But most projects have some concept of a contributor ladder, where people get increased privileges and responsibilities based on the trust they’ve earned. It’s more important than ever to give deliberate thought to how trust is evaluated in your community.

This not only affects community management concerns but also security. Many projects have automated CI jobs that run on pull requests. These check for code style, run unit and integration tests, and so on. In the best case, bad code (intentional or accidental) can limit resources (including maintainer time). In the worst case, bad code can compromise the project and publish malware. For this reason, projects often require maintainers or other trusted users to grant permission for automated tests to run when the submitter is untrusted. Unfortunately, this still places a time burden on maintainers, which is a precious resource.

I suggest that projects explicitly consider what levels of trust are required to access certain resources (CI jobs, project emails, etc) and how that trust will be measured. The Discourse trust levels are an excellent starting point for building your project’s trust model. The specifics are designed for forum interaction, but you can extrapolate to your project’s activities.

The path to build trust has to be easy, or else you’ll drive away new contributors and your community will wither away over time. Trust levels are a safety measure, not a gatekeeping measure.

Tools to help

I am aware of a few tools to help with trust evaluation. I share them here as a reference, but I have not used them and do not endorse or renounce them. contributor-report is a GitHub Action that gives maintainers a report on a new contributor’s activity levels. This helps maintainers evaluate newcomers on the metrics that make sense for their specific project. vouch is a tool for marking users as vouched (or denounced) and taking action based on that. It can be used to provide a web of trust across projects and communities.

This post’s featured photo by Andrew Petrov on Unsplash.

The post Trust in open source communities appeared first on Duck Alignment Academy.

Peter Czanik: New toy: Installing openSUSE Tumbleweed on the HP Z2 Mini

2026-02-24T11:58:13+00:00

Remi Collet: 📝 Install PHP 8.5 on Fedora, RHEL, CentOS Stream, Alma, Rocky or other clone

2026-02-24T11:16:00+00:00

Here is a quick howto upgrade default PHP version provided on Fedora, RHEL, CentOS, AlmaLinux, Rocky Linux or other clones with latest version 8.5.

You can also follow the Wizard instructions.

Architectures:

The repository is available for x86_64 (Intel/AMD) and aarch64 (ARM).

Repositories configuration:

On Fedora, standards repositories are enough, on Enterprise Linux (RHEL, CentOS) the Extra Packages for Enterprise Linux (EPEL) and Code Ready Builder (CRB) repositories must be configured.

Fedora 44

dnf install https://rpms.remirepo.net/fedora/remi-release-44.rpm

Fedora 43

dnf install https://rpms.remirepo.net/fedora/remi-release-43.rpm

Fedora 42

dnf install https://rpms.remirepo.net/fedora/remi-release-42.rpm

RHEL version 10.1

dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm
dnf install https://rpms.remirepo.net/enterprise/remi-release-10.rpm
subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms

RHEL version 9.7

dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
dnf install https://rpms.remirepo.net/enterprise/remi-release-9.rpm
subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms

RHEL version 8.10

dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
dnf install https://rpms.remirepo.net/enterprise/remi-release-8.rpm
subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms

Alma, CentOS Stream, Rocky version 10

dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm
dnf install https://rpms.remirepo.net/enterprise/remi-release-10.rpm
crb install

Alma, CentOS Stream, Rocky version 9

dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
dnf install https://rpms.remirepo.net/enterprise/remi-release-9.rpm
crb install

Alma, Rocky version 8

dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
dnf install https://rpms.remirepo.net/enterprise/remi-release-8.rpm
crb install

PHP module usage

With Fedora and EL, you can simply use the remi-8.4 stream of the php module

With Fedora (dnf5 has partial module support)

dnf module reset php
dnf module enable php:remi-8.5
dnf install php-cli php-fpm php-mbstring php-xml

Other distributions (dnf4)

dnf module switch-to php:remi-8.5/common

PHP upgrade

By choice, the packages have the same name as in the distribution, so a simple update is enough:

dnf update

That's all :)

$ php -v
PHP 8.5.3 (cli) (built: Feb 10 2026 18:25:51) (NTS gcc x86_64)
Copyright (c) The PHP Group
Built by Remi's RPM repository  #StandWithUkraine
Zend Engine v4.5.3, Copyright (c) Zend Technologies
    with Zend OPcache v8.5.3, Copyright (c), by Zend Technologies

Known issues

The upgrade can fail (by design) when some installed extensions are not yet compatible with PHP 8.5.

See the compatibility tracking list: PECL extensions RPM status

If these extensions are not mandatory, you can remove them before the upgrade; otherwise, you must be patient.

Warning: some extensions are still under development, but it seems useful to provide them to upgrade more people and allow users to give feedback to the authors.

More information

If you prefer to install PHP 8.5 beside the default PHP version, this can be achieved using the php85 prefixed packages, see the PHP 8.5 as Software Collection post.

You can also try the configuration wizard.

This is also documented as the community way to install PHP 8.5 on the official PHP web site.

The packages available in the repository were used as sources for Fedora 44.

By providing a full feature PHP stack, with about 150 available extensions, 11 PHP versions, as base and SCL packages, for Fedora and Enterprise Linux, and with 300 000 downloads per day, the remi repository became in the last 21 years a reference for PHP users on RPM based distributions, maintained by an active contributor to the projects (Fedora, PHP, PECL...).

Remi Collet: 📝 Redis version 8.4

2025-11-04T12:48:00+00:00

RPMs of Redis version 8.4 are available in the remi-modular repository for Fedora ≥ 41 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

1. Installation

Packages are available in the redis:remi-8.4 module stream.

1.1. Using dnf4 on Enterprise Linux

# dnf install https://rpms.remirepo.net/enterprise/remi-release-<ver>.rpm
# dnf module switch-to redis:remi-8.4/common

1.2. Using dnf5 on Fedora

# dnf install https://rpms.remirepo.net/fedora/remi-release-<ver>.rpm
# dnf module reset  redis
# dnf module enable redis:remi-8.4
# dnf install redis --allowerasing

You may have to remove the valkey-compat-redis compatibilty package.

2. Modules

Some optional modules are also available:

RedisBloom as redis-bloom
RedisJSON as redis-json
RedisTimeSeries as redis-timeseries

These packages are weak dependencies of Redis, so they are installed by default (if install_weak_deps is not disabled in the dnf configuration).

The modules are automatically loaded after installation and service (re)start.

The modules are not available for Enterprise Linux 8.

3. Future

Valkey also provides a similar set of modules, requiring some packaging changes already proposed for Fedora official repository.

Redis may be proposed for unretirement and be back in the Fedora official repository, by me if I find enough motivation and energy, or by someone else.

I may also try to solve packaging issues for other modules (e.g. RediSearch). For now, module packages are very far from Packaging Guidelines, so obviously not ready for a review.

Akashdeep Dhar: Loadouts For Genshin Impact v0.1.14 Released

2026-02-23T18:30:40+00:00

Hello travelers!

Loadouts for Genshin Impact v0.1.14 is OUT NOW with the addition of support for recently released artifacts like Aubade of the Morningstar and Moon and A Day Carved From Rising Woods, recently released characters like Columbina, Zibai and Illuga and for recently released weapons like Nocturne's Curtain Call and Lightbearing Moonshard from Genshin Impact Luna IV or v6.3 Phase 2. Take this FREE and OPEN SOURCE application for a spin using the links below to manage the custom equipment of artifacts and weapons for the playable characters.

Resources

Installation

Besides its availability as a repository package on PyPI and as an archived binary on PyInstaller, Loadouts for Genshin Impact is now available as an installable package on Fedora Linux. Travelers using Fedora Linux 42 and above can install the package on their operating system by executing the following command.

$ sudo dnf install gi-loadouts --assumeyes --setopt=install_weak_deps=False

Installation command for Fedora Linux

Changelog

Automated dependency updates for GI Loadouts by @renovate[bot] in #486
Add the recently added character Columbina to the GI Loadouts roster by @sdglitched in #494
Add the recently added weapon Nocturne's Curtain Call to the GI Loadouts roster by @sdglitched in #495
Add the recently added artifact set A Day Carved From Rising Winds to the GI Loadouts roster by @sdglitched in #497
Add the recently added artifact set Aubade of Morningstar and Moon to the GI Loadouts roster by @sdglitched in #496
Update dependency pillow to v12.1.1 [SECURITY] by @renovate[bot] in #502
Add the recently added character Zibai to the GI Loadouts roster by @sdglitched in #501
Add the recently added character Illuga to the GI Loadouts roster by @sdglitched in #503
Add the recently added weapon Lightbearing Moonshard to the GI Loadouts roster by @sdglitched in #504
Remove the conditional substat calculation of weapon Harbinger of Dawn by @sdglitched in #505
Stage the release v0.1.13 for Genshin Impact Luna IV (v6.3 Phase 2) by @sdglitched in #506
Automated dependency updates for GI Loadouts by @renovate[bot] in #500

Artifacts

Two artifacts have debuted in this version release.

Aubade of the Morningstar and Moon

Bonus for Two Piece Equipment
Increases Elemental Mastery by 80.
Bonus for Four Piece Equipment
When the equipping character is off-field, Lunar Reaction DMG is increased by 20%. When the party's Moonsign Level is at least Ascendant Gleam, Lunar Reaction DMG will be further increased by 40%. This effect will disappear after the equipping character is active for 3s.

Aubade of the Morningstar and Moon - Workspace and Results

A Day Carved From Rising Winds

Bonus for Two Piece Equipment
ATK +18%.
Bonus for Four Piece Equipment
After a Normal Attack, Charged Attack, Elemental Skill or Elemental Burst hits an opponent, gain the Blessing of Pastoral Winds effect for 6s: ATK is increased by 25%. If the equipping character has completed Witch's Homework, Blessing of Pastoral Winds will be upgraded to Resolve of Pastoral Winds, which also increases the CRIT Rate of the equipping character by an additional 20%. This effect can be triggered even when the character is off-field.

A Day Carved From Rising Winds - Workspace and Results

Characters

Three characters have debuted in this version release.

Columbina

Columbina is a catalyst-wielding Hydro character of five-star quality.

Columbina - Workspace and Results

Zibai

Zibai is a sword-wielding Geo character of five-star quality.

Zibai - Workspace and Results

Illuga

Illuga is a polearm-wielding Geo character of five-star quality.

Illuga - Workspace and Results

Weapons

Two weapons have debuted in this version release.

Nocturne's Curtain Call

Ballad of the Crossroads - Scales on Crit DMG.

Lightbearing Moonshard

Legacy of Lang-Gan - Scales on Crit DMG.

Appeal

While allowing you to experiment with various builds and share them for later, Loadouts for Genshin Impact lets you take calculated risks by showing you the potential of your characters with certain artifacts and weapons equipped that you might not even own. Loadouts for Genshin Impact has been and always will be a free and open source software project, and we are committed to delivering a quality experience with every release we make.

Disclaimer

With an extensive suite of over 1550 diverse functionality tests and impeccable 100% source code coverage, we proudly invite auditors and analysts from MiHoYo and other organizations to review our free and open source codebase. This thorough transparency underscores our unwavering commitment to maintaining the fairness and integrity of the game.

The users of this ecosystem application can have complete confidence that their accounts are safe from warnings, suspensions or terminations when using this project. The ecosystem application ensures complete compliance with the terms of services and the regulations regarding third-party software established by MiHoYo for Genshin Impact.

All rights to Genshin Impact assets used in this project are reserved by miHoYo Ltd. and Cognosphere Pte., Ltd. Other properties belong to their respective owners.

Tim Lauridsen: Fedora Audio Production Ressources

2026-02-23T11:00:00+00:00

Brian (bex) Exelbierd: Phone a Friend: Multi-Model Subagents for VS Code Copilot Chat

2026-02-23T10:10:00+00:00

I wanted a way to stay inside Visual Studio Code, use Copilot Chat as the “orchestrator,” and still mix and match models for different parts of the work. Plan a change with one of the slower, more capable models, but let a smaller, faster model handle mechanical refactors. Edit a blog post with one model, but hand Jekyll plumbing or JSON/YAML munging to another. The friction was that the built-in Copilot Chat extension only lets subagents run on the same model as the parent conversation, while the Copilot CLI happily lets you pick any available model per run. Phone a Friend bolts that flexibility onto Copilot Chat, so I can keep the full VS Code experience - including gutter diffs - while dispatching subtasks to whatever model is best for the job.

The Problem

When you use GitHub Copilot Chat in VS Code, every subagent it spawns runs on the same model as the parent conversation. If you’re on Claude Opus 4.6, all subagents are Claude Opus 4.6. Sometimes you want a different model for a subtask - a faster one for simple work, or a different vendor for a second opinion.

GitHub Copilot CLI supports --model to pick any available model, but using it directly doesn’t help - changes made by the CLI don’t produce VS Code’s gutter indicators (the green/red diff decorations in the editor margin). You get the work done but lose the visual feedback that makes code review comfortable.

Phone a Friend is an MCP server that solves both problems. It dispatches work to Copilot CLI with the model of choice, captures a unified diff of the changes, and returns it to the calling agent - which applies it through VS Code’s edit tools. Gutter indicators show up as the changes were made natively.

How It Works

Copilot Chat calls the phone_a_friend MCP tool with a prompt, model name, and working directory
The MCP server creates an isolated git worktree from HEAD
It launches Copilot CLI in non-interactive mode in that worktree with the requested model
The subagent does its work and writes its response to a “message-in-a-bottle” file
The MCP server reads the response, captures a git diff, and cleans up the worktree
The MCP server then returns the response text and unified diff to the calling agent
The calling agent applies the diff using VS Code’s edit tools - gutter indicators appear

The “message in a bottle” pattern is worth explaining. Copilot CLI’s stdout mixes the agent’s response with progress output and is unreliable to parse. Rather than fighting noisy output, the tool instructs the subagent to write its final response to a file. The server reads the file. Clean separation.

Safety

Worktree isolation means your working tree is never modified directly. Push protection blocks git push at the tool level. Worktrees are cleaned up after every invocation, even on errors.

Setup

You install Phone a Friend like any other MCP server in VS Code: add the @bexelbie/phone-a-friend npm package through the MCP: Add Server... command, or point VS Code at it via your MCP configuration. The GitHub README details the exact JSON and prerequisites (Node.js, Copilot CLI, Git).

Usage

Once configured, you stay in Copilot Chat and describe the outcome you want; the calling agent decides when to route a subtask through Phone a Friend. The tool surface includes discovery hints, so natural phrasing like “get a second opinion from another model” is usually enough to trigger it. Any model that Copilot CLI exposes is available.

Known Limitations

A few trade-offs worth knowing:

Context cost. The unified diff lands in the calling agent’s context window. Large diffs eat context. I’ve got an issue open exploring ideas for improving this.
Message-in-a-bottle compliance. Most models follow the instruction to write their final response into the message-in-a-bottle file, but some may occasionally ignore it. When that happens, the calling agent still gets the diff of any file changes but not the response text.

Availability

The project is on GitHub under MIT license, and published on npm as @bexelbie/phone-a-friend. Written in TypeScript.

What Changed For Me

Since integrating this into my Copilot setup, the biggest shift is that I no longer have to choose between “the model I want to think with” and “the model I want to do the work” and I eliminated a bunch of copy/paste from manually emulating this. I keep the main conversation with a larger, more capable model for planning and review, and routinely:

send quick, mechanical refactors to a smaller, faster model
hand Jekyll front matter, Liquid, and config tweaks to a model that’s better at markup and templating
ask a different vendor’s model for a second opinion on changes or ideas, especially where that model may be better at the task

Because everything still lands back in the same VS Code buffer with normal gutter diffs, it feels like one coherent tool instead of a handful of loosely-connected ones.

The project also had an unexpected dynamic in the development process. Building an MCP server that mimics a capability already available to the model created a strange feedback loop. I could collaborate on the implementation with Opus, and then turn around and interview it as a subject matter expert on how it uses that very same capability. It was a weird feeling to use the model as both a partner in writing the code and a primary source for understanding the user requirements.

Fedora Magazine: Join Us for Fedora Hatch at SCaLE 23x!

2026-02-23T08:00:00+00:00

Fedora is heading back to sunny Southern California! As we gear up for SCaLE 23x, we are thrilled to announce a special edition of Fedora Hatch. This is taking place on Friday, March 6 as an embedded track at SCALE.

Whether you’re a long-time contributor, a curious user, or someone looking to make your very first pull request, Fedora Hatch is designed for you. This is our way of bringing the experience of Flock (our annual contributor conference) to a local level. It focuses on connection, collaboration, and community growth.

What’s Happening?

This year, Fedora has secured a dedicated track on Friday at SCALE. We’ve curated a line-up that balances technical deep dives with essential community initiatives.

When: Friday, March 6, 2026

Where: Room 208, Pasadena Convention Center

Who: You! (And a bunch of friendly Fedorans)

The Schedule Highlights

We have a packed morning featuring five talks and a hands-on workshop:

Getting Started in Open Source and Fedora (Amy Marrich): Are you new to the world of open source? Or are you looking to make your first contribution? This session will provide a guide for beginners interested in contributing to open source projects. It will focus on the Fedora project. We’ll cover a variety of topics, like finding suitable projects, making your first pull request, and navigating community interactions. Attendees will leave with practical tips, resources, and the confidence to embark on their open source journey.
Fedora Docs Revamp Initiative (Shaun McCance): The Fedora Council recently approved an initiative to revamp the Fedora docs. The initiative aims to establish a support team to maintain a productive environment for writing docs. It will establish subteams with subject matter expertise to develop docs in specific areas of interest. We’ll describe some of the challenges the Fedora docs have faced, and present the progress so far in improving the docs. You’ll also learn how you can help Fedora have better docs.
A Brief Tour of the Age of Atomic (Laura Santamaria): Ever wished to try a number of different desktop experiences quickly in your homelab? Maybe it’s time to explore Fedora Atomic or Universal Blue! The tour starts with what makes these experiences special. It will then review the options including Silverblue, Cosmic, Bluefin and Bazzite (yes, the gaming OS). We’ll briefly get under the hood to explore bootc, the technology powering Atomic. Finally, we’ll explore how you can contribute to the future of Fedora Atomic.
Accelerating Cen t OS with Fedora (Davide Cavalca): This talk will explore how CentOS SIGs are able to leverage the work happening in Fedora to improve the quality and velocity of packages in CentOS Stream. We’ll cover how the CentOS Hyperscale SIG is able to deliver faster-moving updates for select packages, and how the CentOS Proposed Updates SIG integrates bugfixes and improves the contribution process to the distribution.
Agentic Workloads on Linux: Btrfs + Service Accounts Architecture (David Duncan): As AI agents become more prevalent in enterprise environments, Linux systems need architectural patterns that provide isolation, security, and efficient resource management. This session explores an approach, using BTRFS subvolumes combined with dedicated service accounts, to build secure, isolated environments for autonomous AI agents in enterprise deployment.
RPM Packaging Workshop (Carl George): While universal package formats like Flatpak, Snap, and AppImage have gained popularity for their cross-distro support, native system packages remain a cornerstone of Linux distributions. These native formats offer numerous benefits. Understanding them is essential for those who want to contribute to the Linux ecosystem at a deeper level. In this hands-on workshop, we’ll explore RPM, the native package format used by Fedora, CentOS, and RHEL. RPM is a powerful and flexible tool. It plays a vital role in the management and distribution of software for these operating systems.

Don’t forget to swing by the Fedora Booth in the Expo Hall! Our team will be there all weekend (March 6–8) with live demonstrations of Fedora Linux 43, GNOME 49 improvements, and plenty of fresh swag to go around.

Registration Details

To join us at the Hatch, you’ll need a SCaLE 23x pass.

Location: Pasadena Convention Center, 300 E Green St, Pasadena, CA.
Tickets: Available at the official SCaLE website.

We can’t wait to see you there. Let’s make SCaLE 23x the best one yet!

Fedora Badges: New badge: SCaLE 23x Attendee !

2026-02-23T06:17:14+00:00

Tim Lauridsen: Plugin - OB-Xf

2026-02-22T17:00:00+00:00

Kevin Fenzi: misc fedora bits 3nd week of feb 2026

2026-02-21T19:27:52+00:00

Well, another saturday, time for another bit of longer form recapping what has been going on in fedora infrastructure and other areas for me.

Infrastructure Fedora 44 Beta freeze

We started the beta freeze in infrastructure. This is to make sure that we don't cause any problems for the release building and distributing pipeline. We require some acks for any changes to things that might impact those things until the day after the Beta is released.

I think this has served us fine over the years. Every once in a while I wonder if we could just stop doing it as we are usually pretty good about not breaking things day to day, but having the extra eyes on changes and slowing down a bit is a good thing I think.

Forge migrations

We have been busy working on migrating things from pagure.io to forge.fedoraproject.org. On tuesday just before the freeze we finally got our ansible repo moved over. I've really been looking forward to this as the review interface in forgejo is a good deal nicer than the pagure one. I've already used it to great effect.

We do still have a few more things to migrate, but overall it's moving along nicely.

Last bits of rdu2-cc move

We finally finished off the last things (at least that I am aware of) for things we moved in last december from rdu2-cc to rdu3.

There was a very strange and difficut to figure out problem for copr builders on ipv6 that I wasn't able to track down, but luckily Pavel worked with networking and finally did so! It seems to have been a odd caching bug in the switches. Hopefully it's now gone once and for all.

There was some hardware issues to sort out: some bad network cards that had to be replaced, a machine that didn't actually move when it was supposed to, etc.

Anyhow I hope all that work is all finally done.

signing work

Finally got back to deploying / testing the new signing path for secure boot signing. I got it all deployed, just need to get things tested now and hopefully we can switch over after the freeze.

This should hopefully allow us to sign aarch64 kernels for secure boot as well as removing reliance on an old smart card for signing.

comments? additions? reactions?

As always, comment on mastodon: https://fosstodon.org/@nirik/116110354434738317

Guillaume Kulakowski: Pourquoi j’ai basculé de Portainer vers Arcane pour gérer les conteneurs sur le NAS

2026-02-21T09:37:36+00:00

Avi Alkalay: Erradicando Preconceito

2026-02-20T16:25:50+00:00

Hoje fiz um curso online do RH da empresa, sobre preconceito e assédio, e abrange etnia, idade, sexo e deficiência. Eu achei ótimo o conteúdo, muito lúdico e bem estruturado, aprendi um monte de coisas. Hoje em dia todas as empresas exigem esses treinamentos. E fiquei pensando que a História da Humanidade, até bem pouco tempo atrás, ficaria orgulhosa em se olhar no futuro finalmente tratando esse assunto para o bem. Então, mesmo que estejamos ainda longe de erradicar preconceito neste Planeta, quero reconhecer e parabenizar todos nós pelos passos que estamos dando. Com a soma dos pequenos passos chegaremos longe.

Today I completed an online HR course at my company on prejudice and harassment, covering topics such as ethnicity, age, gender, and disability. I found the content excellent. Engaging, well-structured, and truly educational. I learned a great deal. These days, this kind of training is required in most organizations. It made me reflect on how, not so long ago, humanity might have looked to the future appreciating that we are finally addressing these issues constructively and consciously. Even though we are still far from eradicating prejudice on this planet, I want to acknowledge and congratulate all of us for the steps we are taking. It is through the accumulation of small steps that we will go far.

Publicado também no meu LinkedIn.

Vít Smolík: Offloading processes to NVidia GPU on Fedora

2026-02-20T12:22:46+00:00

Yashwanth Rathakrishnan: DevConf India 2026

2026-02-20T11:24:05+00:00

Fedora People

Peter Czanik: The syslog-ng Insider 2026-03: 4.11.0 release; OpenSearch; ElasticSearch

Remi Collet: 🎲 PHP version 8.4.19RC1 and 8.5.4RC1

Fedora Magazine: How to rebase to Fedora Silverblue 44 Beta

Updating using the terminal

How to revert

Known issues

FAQ

Marcin Juszkiewicz: RISC-V is sloooow

Triaging

Fedora packaging

Slowness

Hardware needs for Fedora inclusion

I still use QEMU for local testing

Future plans

Tim Waugh: Searching Logseq by Concept, Not Keystrokes

Indexing the hierarchy

Running it locally

Usage

Peter Czanik: New toy: Installing FreeBSD on the HP Z2 Mini

Fedora Magazine: Announcing Fedora Linux 44 Beta

How to get the Fedora Linux 44 Beta release

Fedora Linux 44 Beta highlights

Installer and desktop Improvements

LiveCD Improvements

System Enhancements

Fedora Linux 44 Beta upgrades and removals

More information about Fedora Linux 44 Beta

Kushal Das: In the land of XML

Miroslav Vadkerti: Silencing Alerts During OpenShift Cluster Upgrades with Prometheus and Alertmanager

Kevin Fenzi: misc fedora bits first week of march 2026

GPU machine

Fedora 44 Beta is GO for release next tuesday

Secure boot signing

Just missed it

comments? additions? reactions?

Avi Alkalay: Ideal Laptop

Avi Alkalay: Laptop ideal

Fedora Community Blog: Final Reminder: Flock 2026 Financial Assistance Applications Close Sunday, March 8th

Note for Flock 2026 speakers

Apply for Flock 2026 financial assistance

Fedora Community Blog: Community Update – Week 10 2026

Fedora Infrastructure

CentOS Infra including CentOS CI

Release Engineering

RISC-V

AI

QE

Forgejo

UX

Miroslav Vadkerti: How a Single Regex Stalled 30 Testing Farm Jobs for Hours

Christof Damian: Friday Links 26-08

Ben Cotton: You’d better start believing in supply chains because you’re in one (SCaLE 23x)

Resources

Akashdeep Dhar: Fedora Project Community Corner @ DevConf.IN 2026 - Day Two

Peter Czanik: New toy: Installing Fedora Linux on the HP Z2 Mini

Tim Waugh: Logsqueak: Rescuing Insights from the Logseq Journal

How Logsqueak Works

1: Extraction (Signal vs. Noise)

2: Refinement (Making it Evergreen)

3: Integration (Filing it Away)

Try it out!

Taming the Knowledge Graph

Peter Czanik: Syslog-ng 4.11.0 packaging status

Avi Alkalay: Uniqlo T-Shirt Bash Script Easter Egg

Akashdeep Dhar: Fedora Project Community Corner @ DevConf.IN 2026 - Day One

Fedora Community Blog: Fedora Documentation translations not available from March 4th, 2026

Brian (bex) Exelbierd: Jekyll Reads: the tooling behind my reading list

Why I needed more than a social reading site

What Jekyll Reads actually does

How it shows up on this site

Design constraints and trade‑offs

If you want to use it

Matthew Garrett: To update blobs or not to update blobs

Tony Asleson: Honey, I Shrunk the Model (Maybe): blk-archive vs AI Data

Kevin Fenzi: misc fedora bits last week of feb 2026

Lots of small day to day items

Secure boot signing work

comments? additions? reactions?

Tim Waugh: Patchutils 0.4.5 released