/rss20.xml">

Fedora People

Fedora Asahi Remix 44 is now available

Posted by Fedora Magazine on 2026-04-28 14:05:33 UTC

We are happy to announce the general availability of Fedora Asahi Remix 44. This release brings Fedora Linux 44 to Apple Silicon Macs.

Fedora Asahi Remix is developed in close collaboration with the Fedora Asahi SIG and the Asahi Linux project. This release incorporates all of the exciting improvements brought by Fedora Linux 44.  Fedora Asahi Remix 44 also retires our vendored Mesa and virglrenderer packages. Users who have not already manually done so will be automatically transitioned to the upstream Mesa and virglrenderer packages provided by the upstream Fedora repositories.

Fedora Asahi Remix offers KDE Plasma 6.6 as our flagship desktop experience, with all of the new and exciting features brought by Fedora KDE Plasma Desktop 44Plasma Setup replaces the previous Calamares-based setup wizard, providing a Plasma-native experience for user account creation and system setup. Additionally, Plasma Login Manager is now the default greeter and session manager, replacing SDDM. This applies to new installs only; users upgrading from previous versions of Fedora Asahi Remix will not have their configuration changed.

A GNOME variant is also available, featuring GNOME 50, with both desktop variants matching what Fedora Linux offers. Fedora Asahi Remix also provides a Fedora Server variant for server workloads and other types of headless deployments. Finally, we offer a Minimal image for users that wish to build their own experience from the ground up.

You can install Fedora Asahi Remix today by following our installation guide. Existing systems running Fedora Asahi Remix 42 or 43 can be updated following the usual Fedora upgrade process. Upgrades via GNOME’s Software application are unfortunately not supported; either KDE’s Plasma Discover or DNF’s System Upgrade command must be used.

Please report any Remix-specific issues in our tracker, or reach out in our Discourse forum or our Matrix room for user support.

What’s New in Fedora KDE Plasma Desktop 44

Posted by Fedora Magazine on 2026-04-28 14:04:00 UTC

Fedora has released Fedora KDE Plasma Desktop Edition 44 to the public.

The Fedora KDE Plasma Desktop Edition is suitable for many needs.  It combines the reliable and trusted Fedora Linux base with the KDE Plasma Desktop environment.  It provides a selection of KDE applications that are simple by default, but powerful when needed.

KDE Plasma 6.6

The KDE community makes your life easier with the latest release of KDE Plasma. It builds upon the foundations of Plasma 6 to provide a seamless, friendly, and familiar experience.

Fedora KDE 44 ships with Plasma 6.6.4 featuring:

  • Custom global theme creation by saving the current theme setup
  • More options for using color accent in windows with tint intensity for window frames
  • Support for connecting to Wi-Fi networks by scanning QR codes
  • Per-application volume adjustment from the task manager
  • New grayscale filter for colorblindness correction
  • New screen magnifier feature that tracks the mouse pointer
  • New “Slow keys” and “reduced motion” settings
  • Spectacle can do OCR scanning of images to capture text
  • Per-window filter from screencast through the menu in the title bar

There’s so much more detail available in the Plasma 6.6 release announcement.

Fedora KDE 44 specific updates

Beyond just the updates included in KDE Plasma 6.6, there are some major new features with Fedora KDE on Fedora Linux 44.

  • Fresh installations now use the brand-new Plasma Setup and Plasma Login Manager. These provide a more cohesive and integrated experience from the moment the computer is powered on the first time. The installation process has been simplified. It now enables you to easily set up Fedora KDE Plasma Desktop for a computer for a friend or a loved one.
  • The on-screen keyboard uses the new Plasma Keyboard, providing a fresh and future-forward implementation for keyboard input.

Fedora Linux 44 general updates

Some broader changes in Fedora Linux also directly impact Fedora KDE Plasma Desktop Edition, notably:

  • PackageKit now uses version 5 of the DNF package manager as the backend.
  • Support for select Qualcomm-based laptops.
  • The /etc/pki/tls/cert.pem file no longer exists by default. This may impact some programs that expect this file to provide system CA certificates instead of leveraging behaviors built into cryptographic security libraries to offer this information.

Fedora Ready is ready for Fedora KDE

The Fedora KDE Plasma Desktop 44 edition is fully supported within the Fedora Ready program. Fedora KDE is actively engaging with hardware vendors to support Fedora KDE Plasma Desktop on their devices.

We are pleased to announce that Star Labs offers preinstalled Fedora KDE Plasma Desktop as an option for their portfolio of devices. As makers of computers with an open source ethos embedded into the core of their products with even open source firmware powered by Coreboot, they share many of the same principles the Fedora community values. This is a very exciting moment for Fedora KDE and we look forward to deepening our collaboration with Fedora Ready participants and extending to other vendors. If you are a vendor potentially interested in Fedora Ready, please reach out!

Wrap-up

The Fedora KDE SIG hopes that you’ll find the Fedora KDE Plasma Desktop 44 to be a wonderful experience. When you’re ready to try it, click here for download links and verification instructions. If you’d like to learn more, check out the Fedora KDE Plasma Desktop website.

Sealed Fedora Atomic Desktop bootable container images

Posted by Fedora Magazine on 2026-04-28 14:03:00 UTC

I’m happy to announce that we have sealed bootable container images ready for testing for the Fedora Atomic Desktops!

What are sealed bootable container images?

Sealed bootable container images include all the components needed to create a fully verified boot chain, from the firmware to the operating system composefs image. This relies on Secure Boot and thus only supports system booting with UEFI on x86_64 & aarch64.

The components are:

  • systemd-boot as bootloader
  • a Unified Kernel Image (UKI) which includes the Linux kernel, an initrd and the kernel command line
  • a composefs repository with fs-verity enabled. This is managed by bootc.

Both systemd-boot and the UKI are signed for Secure Boot. The images are test images so the components are not signed with the official keys from Fedora.

The main direct benefit that we will get from this support is that we will be able to enable passwordless disk unlocking using the TPM in a way that will be reasonably secure by default.

How do I test those images?

See the instructions at github.com/travier/fedora-atomic-desktops-sealed on how to give the pre-built container and disk images a try and how to build your own.

We welcome testing and feedback! Please see the list of known issues and report new issue at github.com/travier/fedora-atomic-desktops-sealed. We’ll redirect them as needed to the right upstream projects.

Beware, those are testing images. The root account does not have a password set and sshd is enabled, by default, to make debugging easier. The UKI and systemd-boot are signed for Secure Boot but, since those are test images, they are not signed with the official keys from Fedora. Don’t use those images in production.

Where can I get more details about how this works?

If you want to know more about how sealed images work (i.e. how we make bootable containers, UKI and composefs work together to create a verified boot chain), see the following presentations and documentation:

Thanks to all the contributors that made this possible, notably (but non exhaustively) from the following projects: bootc & bcvk, composefs & composefs-rs, chunkah, podman & buildah and systemd.

What’s New for Fedora Atomic Desktops in Fedora Linux 44

Posted by Fedora Magazine on 2026-04-28 14:02:00 UTC

Fedora Linux 44 has been released! 🎉 So, let’s see what is included in this new release for the Fedora Atomic Desktop variants (Silverblue, Kinoite, Sway Atomic, Budgie Atomic and COSMIC Atomic).

Changes for all Atomic Desktops

Issue tracker moved to the new Fedora forge

We have moved the cross-variants issue tracker to the new Fedora forge. This is the best place to file issues that impacts all variants or to coordinate work between all of them. If you have issues specific to a given desktop environment then we usually prefer to track them in each respective SIG trackers. These are available on the README for the atomic-desktops organization.

Unified documentation, hosted on the new forge

The unified documentation for all Atomic Desktops is finally live! Unfortunately the translations have not been migrated so we will need help to re-translate everything again, once the translation setup is ready with the new forge. It should be mostly copy/paste from the previous docs and this time we will only have to translate the docs once and not for every (new) variant.

See the tracking issue atomic-desktops#10.

Removal of FUSE version 2 libraries

FUSE version 2 has been deprecated and unmaintained for a while so we have removed it from the images. In practice, this means two things:

  • If you are using AppImages, some of them may not work anymore.
  • If you are using legacy backends with Plasma Vault on Kinoite, you need to migrate your data.

See the Fedora Change and the tracking issue atomic-desktops#50. The implications are detailed below.

AppImages and the FUSE 2 libraries

Some AppImages are still using an old AppImage runtime that relies on FUSE 2 libraries being available on the host. See the Discussion thread for examples on how to check the runtime of an AppImage.

If some of your AppImages do not work on Fedora Atomic Desktops 44, we recommend:

  • Looking for a Flatpak for the application and giving it another try. Consider helping upstream package their application as a Flatpak.
  • Reporting the issue upstream so that they are aware that they should use a newer runtime. Consider helping upstream with this as well.

EncFS or CryFS backends for Plasma Vaults are removed

KDE upstream no longer recommends using the EncFS nor CryFS backends for Plasma Vaults, notably because they rely on the FUSE 2 libraries. If you are using one of those backends, you should migrate your data to a new vault using the only maintained backend (gocryptfs). Ideally this should occur before the update to Fedora Linux 44. If you have already updated to Fedora Linux 44 and need access to your data, you can layer the needed packages (cryfs or fuse-encfs) using rpm-ostree install <package>, then migrate your data and finally reset the layers with rpm-ostree reset.

Dropping compatibility for pkla Polkit rules

Support for the legacy pkla Polkit rules format has been removed. It is unlikely that you were relying on support for those rules as most of the ecosystem has moved on to the new JavaScript based format.

See the Fedora Change and the tracking issue atomic-desktops#102.

What’s New in Silverblue

GNOME 50

Fedora Silverblue comes with the latest GNOME 50 release. For more details about the changes that occur alongside GNOME 50, see What’s New in Fedora Workstation 44 on the Fedora Magazine.

What’s New in Kinoite

KDE Plasma 6.6

Fedora Kinoite ships with Plasma 6.6, Frameworks 6.24 and Gear 25.12.

See also What’s New in Fedora KDE Plasma Desktop 44 in the Fedora Magazine.

KDE Plasma Login Manager replaces SDDM

The brand new Plasma Login Manager replaces SDDM to provide a more integrated experience with systemd and the KDE Plasma session.

See the Fedora Change.

Unified out of the box experience with KDE Plasma Setup (OEM installation)

Thanks to the new Plasma Setup, it is now possible to install the system with Anaconda with minimal configuration and then complete the installation on the first boot by creating a new user and selecting the timezone. This is great when you want to install Fedora Kinoite on a computer and don’t want to setup a user in advance.

See the Fedora Change.

What’s New in Sway Atomic

Nothing specific for this release.

What’s New in Budgie Atomic

Fedora Budgie Atomic comes with the latest 10.10.2 Budgie release. This release brings Wayland support to Budgie Atomic. See the 10.10 release announcement for more details.

What’s New in COSMIC Atomic

Fedora COSMIC Atomic comes with the latest 1.0.8 release of the COSMIC desktop. This is now considered stable.

Universal Blue, Bluefin, Bazzite and Aurora

Our friends in the Universal Blue project (Bazzite, Bluefin, Aurora) have prepared the update to Fedora Linux 44. Look for upcoming announcements in their Discourse.

As always, I heavily recommend checking them out, especially if you feel like some things are missing from the Fedora Atomic Desktops and you depend on them (NVIDIA drivers, extra media codec, out of tree kernel drivers, etc.).

What’s Next

Helping us with a few nasty bugs

If you have an interest in contributing to Fedora Atomic Desktops, here are some bugs that we will have to fix in the short term. We would greatly appreciate help with:

  • Fixing root mount options (atomic-desktops#72): This is a long standing and mostly invisible bug that impacts performance.
  • Moving away from nss-altfiles (atomic-desktops#108): This is another long standing source of issues that new users regularly face.

Sealed Fedora Atomic Desktop bootable container images

Sealed images are now ready for testing! See the other article for all the details.

Road map to Bootable Containers

A lot of work is happening to make the transition to Bootable Containers as smooth as possible for our existing users. You can look at the road map for this transition at atomic-desktops#26.

One of the tasks is to move away from our unmaintained installation ISO building scripts to the new image-builder tooling. This is planned for Fedora Linux 45 for the ostree variants and support for Bootable Container will follow right after.

Another task is to start building the Fedora Atomic Desktops Bootable Container images using the Fedora Konflux instance.

Where to reach us

We are looking for contributors to help us make the Fedora Atomic Desktops the best experience for Fedora users.

How to Rebase to Fedora Linux 44 on Silverblue

Posted by Fedora Magazine on 2026-04-28 14:01:00 UTC

Fedora 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. If you want to rebase to Fedora Linux 44 on your Fedora Silverblue system, this article tells you how. It not only shows you what to do, but also how to revert things if something unforeseen happens.

Update your existing system

Prior to actually doing the rebase to Fedora Linux 44, you should apply any pending updates. Enter the following in the terminal:

$ rpm-ostree update

or install updates through GNOME Software and reboot.

Note

rpm-ostree is the underlying atomic technology that all the Fedora Atomic Desktops use. The techniques described here for Silverblue will apply to all of them with proper modifications for the appropriate desktop.

Rebasing using GNOME Software

GNOME Software shows you that there is new version of Fedora Linux available on the Updates screen.

First thing to do is download the new image, so select the Download button. This will take some time. When it is done you will see that the update is ready to install.

Select the Restart & Upgrade button. This step will take only a few moments and the computer will restart when the update has completed. After the restart you will end up in a new and shiny release of Fedora Linux 44. Easy, isn’t it?

Rebasing using terminal

If you prefer to do everything in a terminal, then this part of the guide is for you.

Rebasing to Fedora Linux 44 using the terminal is easy. First, check if the 44 branch is available:

$ ostree remote refs fedora

You should see the following in the output:

fedora:fedora/44/x86_64/silverblue

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

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

To remove the pinned deployment use the following command:

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

Next, rebase your system to the Fedora Linux 44 branch.

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

Finally, the last thing to do is restart your computer and boot to Fedora Linux 44.

How to roll back

If anything bad happens (for instance, if you can’t boot to Fedora Linux 44 at all) it’s easy to go back. At boot time, pick the entry in the GRUB menu for the version prior to Fedora Linux 44 and your system will start in that previous version rather than Fedora Linux 44. If you don’t see the GRUB menu, try to press ESC during boot. To make the change to the previous version permanent, use the following command:

$ rpm-ostree rollback

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

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 a rebase of Fedora Linux? For example from Fedora Silverblue 41 to Fedora Silverblue 44?

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

Question: I have rpm-fusion layered and I get 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 blog post.

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 Rebasing using the terminal part of this guide for every Fedora Atomic Desktop. Just use the corresponding branch. For example, for Kinoite use fedora:fedora/44/x86_64/kinoite

What’s New in Fedora Workstation 44

Posted by Fedora Magazine on 2026-04-28 14:00:00 UTC

This article highlights a few noteworthy changes in the latest release of Fedora Workstation that we think you will love. Upgrade today from the official website, or upgrade your existing install using GNOME Software or through the terminal with dnf system-upgrade.

GNOME 50

Fedora Linux 44 Workstation ships with the latest GNOME release, GNOME 50. This comes with a long list of refinements to your desktop, including everything from accessibility, to color management and remote desktop.

As part of the Digital Wellbeing initiative, new native Parental Controls let you set screen time limits and bedtimes directly from Settings.

Many of the applications that are installed by default on the Fedora Workstation have also seen improvements, from the Document Viewer to the File Manager and the Calendar.

To learn more about these and other changes, you can read the GNOME 50 release notes.

Wrap-up

Be sure to check out the Fedora Linux 44 Change Set wiki for even more details about all the features and changes that went into Fedora Linux 44. Use the Fedora Discussion forum or Fedora’s Matrix chat server if you want to converse with the Fedora community about this new release!

The Fedora Linux 44 Release is Here!

Posted by Fedora Magazine on 2026-04-28 13:59:00 UTC

I’m excited to announce that Fedora Linux 44 is here! Keep reading to discover highlights of Fedora Linux 44, or if you are ready, just jump right in and give Fedora Linux 44 a try!

Thanks to everyone who helped!

Thank you and congrats to everyone who has contributed to this release. And thanks to everyone who showed up for the virtual release party last Friday. We celebrated a little early this year, just after the go/no-go meeting made the release official. If you weren’t able to join us live, you can watch the recording and hear about some of the great work from the contributors involved.

Looking to upgrade?

If you have an existing system, Upgrading Fedora Linux to a New Release is easy. In most cases, it’s not very different from just rebooting for regular updates, except you’ll have a little more time to grab a coffee.

Ready to Fresh Install?

If this is your first time running Fedora Linux, or if you just want to start fresh with Fedora, download the install media for our flagship Editions (Workstation, KDE Plasma Desktop, Cloud, Server, CoreOS, IoT), or one of our Atomic Desktops (Silverblue, Kinoite, Cosmic, Budgie, Sway), or alternate desktop options (like Cinnamon, Xfce, Sway, or others).

What’s new?

As usual with Fedora Linux, there are just too many individual changes and improvements to go over in detail. You’ll want to take a look at the release notes for that.

Notable User Visible Changes

Anaconda

For those of you installing fresh Fedora Linux 44 Spins, you may notice a change in how Anaconda handles network devices. Anaconda now only creates network profiles for devices configured during installation (by boot options, kickstart, or interactively in UI) instead of providing default profiles for all devices. This change will simplify post-installation network configuration for users who need to customize after installation.

Workstation

Fedora Linux 44 Workstation ships with the latest GNOME release, GNOME 50. This comes with a long list of refinements to your desktop, including everything from accessibility to color management and remote desktop. Many of the applications that are installed by default on Fedora Workstation have also seen improvements, from Document Viewer to File Manager and Calendar. To learn more about these and other changes, you can read the GNOME 50 release notes.

KDE Plasma Desktop

KDE Plasma Desktop: If you are a KDE user, you should also notice a couple of very obvious changes. Fedora KDE Plasma Desktop 44 is based on the latest Plasma 6.6, which includes the new Plasma Login Manager and Plasma Setup to provide a more cohesive and integrated experience from the moment the computer is powered on for the first time. The installation process has been simplified, enabling you to easily set up Fedora KDE Plasma Desktop for a computer for a friend or a loved one.
 

Plumbing Upgrades

Beyond the user-visible changes, there are some important plumbing changes user should be aware of.

OpenSSL Cert File Handling Improvements

The loading time of OpenSSL has been improved by making use of directory-hash support for ca-certificates. This improvement required changes to where some certificate bundles are stored on the filesystem. You can read the specific Change details for more information.

The MariaDB default version is now 11.8

MariaDB packages use a versioned package layout, which allows Fedora to deliver both, mariadb-10.11 and mariadb-11.8 for users.  The “distribution default” unversioned MariaDB packages now install the 11.8 versions in Fedora Linux 44. User doing upgrades to Fedora Linux 44 won’t notice the change in the default. For new users installing MariaDB for the first time, unless you specify the version, you’ll now get 11.8 by default.

Wine NTSYNC

The NTSYNC kernel module is enabled for select packages by package recommendation (notably Wine and Steam), which can improve compatibility and performance when running Windows applications (especially games).  When packages that recommend the wine-ntsync package are installed, the package recommendation ensures NTSYNC is configured automatically on subsequent boots, so that users don’t have to manually enable NTSYNC.

Fedora Cloud boot partition using Btrfs

The /boot partition has been replaced with a Btrfs subvolume for Fedora Cloud images that support it.  This results in better space utilization and smaller images.

If you hit a snag

If you run into a problem, visit our Ask Fedora user support forum. This forum includes a category where we collect common issues and solutions or work-arounds.

Just drop by and say “hello”

Drop by our “virtual watercooler” on Fedora Discussion and join a conversation, share something interesting, and introduce yourself. We’re always glad to see new people!

Support for OpenSSL 4.0?

Posted by Peter Czanik on 2026-04-28 13:20:56 UTC

Although OpenSSL 4.0 released just two weeks ago, the syslog-ng project has already received a GitHub issue complaining that we do not support it. So, before we would allocate too much effort on it: what should we expect?

OpenSSL 4.0 was announced on April 14: https://openssl-library.org/post/2026-04-14-openssl-40-final-release/ However, this announcement mentions that it is NOT a long-term support (LTS) release.

This raises the question that if it is not an LTS release, then can we stay on version 3.x and skip 4.x altogether? When will Linux distributions start using it? Looking at Repology, there are already a few places where OpenSSL 4.0 is available. This includes Gentoo, the community where the GitHub issue originated from, and also various FreeBSD ports. The current list is available at: https://repology.org/project/openssl/versions

Fedora is planning to use OpenSSL 4.0 as default starting from the next release: https://fedoraproject.org/wiki/Changes/OpenSSL40 However, OpenSSL 3.x will most likely stay supported for backwards compatibility.

I am also curious if there are any other projects which have added support for OpenSSL 4.0. If so, then what are your experiences? Was porting your code to use OpenSSL 4.0 difficult?

I am all in for supporting the latest technologies, but currently, even if we have an open request for OpenSSL 4.0 support, I do not feel that I have enough information to prioritize its development.

Share your thoughts with us in this syslog-ng GitHub discussion: https://github.com/syslog-ng/syslog-ng/discussions/5685 or reach out to me on Twitter / Mastodon / LinkedIn.

syslog-ng logo

Originally published at https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

Throwing Random Arguments at System Binaries: Real Segfaults vs. Ticket Noise

Posted by Fedora Community Blog on 2026-04-28 12:00:00 UTC

Why Would Anyone Do This?

Two and half reasons:

  1. Smoke testing – You want to know if your system commands actually work, not just when you run them the way the docs say, but when users (or their scripts) feed them garbage.
  2. AI is excellent at generating potential edge cases, and tracking systems are already all too eager to collect new tickets. I’m being careful not to dump every AI finding into Bugzilla; I don’t want to clutter the backlog and mainly waste developer time on theoretical bugs. Or Should I?

Plus, segfaults don’t lie – either the system crashed or it didn’t, and those are the issues that actually deserve the ticket.

Throwing Random Arguments at System Binaries Until They Crash

Script to do the work:

A pretty straightforward bash script, vibing with AI-generated chaos.

  1. Grab all binaries from /usr/bin and /usr/sbin
  2. Parse --help for flags (--whatever, -x, you know the drill)
  3. Pick random combos of those flags (1-4 per run)
  4. Feed them garbage: broken JSON/XML, binary junk, path traversal attempts, format strings, absurdly long lines

Only logs actual crashes – SIGSEGV, SIGABRT, SIGILL, SIGBUS. Exit code 1 from bad args gets ignored.

Core logic looks like this:

# Extract flags from --help                                            
  flags=$(timeout 3s "$bin" --help 2>&1 |                   
      grep -aoE -e '--[a-zA-Z0-9_-]+' -e '-[a-zA-Z]' |                                                    
      grep -avE 'help|version|usage')                                                                     
                                                                                                          
  # Pick random flags (1-4 of them)                                                                       
  chosen=$(echo "$flags" | shuf -n $((1 + RANDOM % 4)))                                                   
                                                                                                          
  # Add a random test file                                                                                
  fuzz_file="$WORKSPACE/$(random_pick: bad.json, random.bin, longline.txt, ...)"                          
                                                                                                          
  # Run it                                                  
  timeout 5s "$bin" $chosen $fuzz_file                                                                    
  

Script skips the obvious no go zones – package managers, rm, network tools, editors. I’m glad to see the script finish with the machine still answering.

Try It Yourself!

Source: run-them-all

Run via Testing Farm (how-to):

testing-farm-public request --test-type fmf \                                                
    --git-url https://forge.fedoraproject.org/quality/fmf-tests.git \                                     
    --git-ref main \
    --compose Fedora-Cloud-Base-AmazonEC2.x86_64-44-1.3 \                                                 
    --arch x86_64 \                                                                                       
    --test run-them-all \                                                                                 
    --context "force=yes" \                                                                               
    --plan /plans/all                                                                                     
  

Run locally: Just use the try-all.sh binary from the test, no requirement needed, run:

curl -sSLO https://forge.fedoraproject.org/quality/fmf-tests/raw/branch/main/system-in-use/run-them-all/try-all-binaries-help-options.sh && bash try-all-binaries-help-options.sh

My results: Testing Farm Artifacts (Fedora 44 RC compose 1.3, ~950 binaries tested)

What I Found

grub2-mkrescue (bootloader utilities), perl (half the system depends on it), eqn from groff (man pages break without it).

What coredumpctl caught:

TIME                           PID UID GID SIG     COREFILE EXE                      SIZE
  Mon 2026-04-20 12:08:09 UTC  52378   0   0 SIGABRT present  /usr/bin/edgepaint      80.7K               
  Mon 2026-04-20 12:08:22 UTC  58926   0   0 SIGSEGV present  /usr/bin/eqn            57.8K
  Mon 2026-04-20 12:08:41 UTC  77687   0   0 SIGSEGV present  /usr/bin/gdbm_dump      23.9K               
  Mon 2026-04-20 12:09:01 UTC  97901   0   0 SIGSEGV present  /usr/bin/grub2-mkrescue 64.7K
  Mon 2026-04-20 12:09:08 UTC 106904   0   0 SIGSEGV present  /usr/bin/gtshapprox     48.3K               
  Mon 2026-04-20 12:10:15 UTC 161697   0   0 SIGABRT present  /usr/bin/perl5.42.1       94K               
  

Breakdown:

  • edgepaint (graphviz) – 4× SIGABRT
  • gtshapprox (graphviz) – 3× SIGSEGV
  • perl – 4× SIGABRT
  • eqn (groff) – 1× SIGSEGV
  • gdbm_dump (gdbm) – 1× SIGSEGV
  • grub2-mkrescue (grub2) – 1× SIGSEGV

Reproducers

Run it on your side to see the reproducers in action. I’m curious to hear your thoughts on these major findings.

MY CRASHES:
COMMAND: /usr/bin/edgepaint -s -o --random_seed --angle --lightness -v --accuracy --share_endpoint 
COMMAND: /usr/bin/edgepaint -v -s --accuracy --color_scheme -o  /root/fuzz_lab/empty.dat
COMMAND: /usr/bin/edgepaint --share_endpoint -o --angle -v -s --random_seed --accuracy --color_scheme  -
COMMAND: /usr/bin/edgepaint -s --lightness --share_endpoint -o -v --angle --random_seed 
COMMAND: /usr/bin/efibootdump --guid -g -f  /root/fuzz_lab/large.dat
COMMAND: /usr/bin/eqn -C -f -M -d -v -m -T -s  /root/fuzz_lab/fake.png
COMMAND: /usr/bin/gdbm_dump --format  -
COMMAND: /usr/bin/grub2-file --is-x86-knetbsd  /root/fuzz_lab/longline.txt
COMMAND: /usr/bin/grub2-file --is-x86-knetbsd  /root/fuzz_lab/bad.json
COMMAND: /usr/bin/gtshapprox --flat -c  /root/fuzz_lab/fake.jpg
COMMAND: /usr/bin/gtshapprox -v -f --verbose -c  /root/fuzz_lab/cmd.txt
COMMAND: /usr/bin/gtshapprox -n -h --flat -l --closed -v  /root/fuzz_lab/gzip.dat
COMMAND: /usr/bin/gtshapprox --flat --number --log --cost --closed  -
COMMAND: /usr/bin/gtshapprox --log -l -f --keep  -
COMMAND: /usr/bin/mkfs.xfs -q  /root/fuzz_lab/bad_utf8.txt
COMMAND: /usr/bin/mkfs.xfs -K -L -m  /root/fuzz_lab/paths.txt
COMMAND: /usr/bin/perl -V -F -T -S -u -p -f -E -W -I  /root/fuzz_lab/bad.json
COMMAND: /usr/bin/perl -F -e -n -a -l -u -c  -
COMMAND: /usr/bin/perl -S -u -s -E -I -l 
COMMAND: /usr/bin/perl -s -p -n -u -D -E -d 
COMMAND: /usr/bin/tree -P --filelimit --matchdirs --hyperlink -i  /root/fuzz_lab/paths.txt

Look, these are edge cases. Nobody’s actually running edgepaint --wtf malformed.json in prod. But segfaults are segfaults – the binary should bail with “invalid option” or “bad input”, not dump core.

Now What?

So I’ve got a pile of crashes. Some in critical components. All reproducible.

File bugs for all of them? That’s a lot of BZ tickets for “yes hm this crashes if you feed it random garbage with weird flags”. Developers have better things to do.

Ignore them? They’re real bugs. And some of these are in grub2 and perl – not exactly throwaway packages.

Still figuring that out.


My Dilemma During Testing on Fedora 44 RC compose 1.X

The post Throwing Random Arguments at System Binaries: Real Segfaults vs. Ticket Noise appeared first on Fedora Community Blog.

What’s new for Fedora Atomic Desktops in Fedora 44

Posted by Timothée Ravier on 2026-04-27 22:00:00 UTC

Fedora 44 has been released! 🎉 So let’s see what is included in this new release for the Fedora Atomic Desktops variants (Silverblue, Kinoite, Sway Atomic, Budgie Atomic and COSMIC Atomic).

Note: You can also read this post on the Fedora Magazine.

Changes for all Atomic Desktops

Issue tracker moved to the new Fedora forge

We have moved the cross-variants issue tracker to the new Fedora forge. This is the best place to file issues that impacts all variants or to coordinate work between all of them. If you have issues specific to a given desktop environment then we usually prefer to track them in each respective SIG trackers. They are listed on the README for the atomic-desktops organization.

Unified documentation, hosted on the new forge

The unified documentation for all Atomic Desktops is finally live! Unfortunately the translations have not been migrated so we will need help to re-translate everything again, once the translation setup is ready with the new forge. It should be mostly copy/paste from the previous docs and this time we will only have to translate the docs once and not for every (new) variant.

See the tracking issue atomic-desktops#10.

Removal of FUSE version 2 libraries

FUSE version 2 has been deprecated and unmaintained for a while so we have removed it from the images. In practice, this means two things:

  • If you are using AppImages, some of them may not work anymore.
  • If you are using legacy backends with Plasma Vault on Kinoite, you need to migrate your data.

See the Fedora Change and the tracking issue atomic-desktops#50.

The implications are detailed below.

AppImages and the FUSE 2 libraries

Some AppImages are still using an old AppImage runtime that relies on FUSE 2 libraries being available on the host. See the discussion thread for examples on how to check the runtime of an AppImage.

If some of your AppImages do not work on Fedora Atomic Desktops 44, we recommend:

  • Looking for a Flatpak for the application and giving it another try. Consider helping upstream package their application as a Flatpak.
  • Reporting the issue upstream so that they are aware that they should use a newer runtime. Consider helping upstream with this as well.

EncFS or CryFS backends for Plasma Vaults are removed

KDE upstream no longer recommend using the EncFS nor CryFS backends for Plasma Vaults, notably because they rely on the FUSE 2 libraries. If you are using one of those backends, you should migrate your data to a new Vault using the only maintained backend (gocryptfs). Ideally this should occur before the update to Fedora 44. If you have already updated to Fedora 44 and need access to your data, you can layer the needed packages (cryfs or fuse-encfs) using rpm-ostree install <package>, then migrate your data and finally reset the layers with rpm-ostree reset.

Dropping compatibility for pkla polkit rules

Support for the legacy pkla polkit rules format has been removed. It is unlikely that you were relying on support for those rules as most of the ecosystem has moved on to the new Javascript based format.

See the Fedora Change and the tracking issue atomic-desktops#102.

What’s new in Silverblue

GNOME 50

Fedora Silverblue comes with the latest GNOME 50 release.

For more details about the changes that alongside GNOME 50, see What’s new in Fedora Workstation 44 on the Fedora Magazine.

What’s new in Kinoite

KDE Plasma 6.6

Fedora Kinoite ships with Plasma 6.6, Frameworks 6.24 and Gear 25.12.

See also What’s new in Fedora KDE Plasma Desktop 44 on the Fedora Magazine.

KDE Plasma Login Manager replaces SDDM

The brand new Plasma Login Manager replaces SDDM to provide a more integrated experience with systemd and the KDE Plasma session.

See the Fedora Change.

Unified out of the box experience with KDE Plasma Setup (OEM installation)

Thanks to the new Plasma Setup, it is now possible to install the system with Anaconda with minimal configuration and then complete the installation on the first boot by creating a new user and selecting the timezone. This is great when you want to install Fedora Kinoite on a computer and don’t want to setup a user in advance.

See the Fedora Change.

What’s new in Sway Atomic

Nothing specific for this release.

What’s new in Budgie Atomic

Fedora Budgie Atomic comes with the latest 10.10.2 Budgie release. This release brings Wayland support to Budgie Atomic. See the 10.10 release announcement for more details.

What’s new in COSMIC Atomic

Fedora COSMIC Atomic comes with the latest 1.0.8 release of the COSMIC desktop. This is now considered stable.

Universal Blue, Bluefin, Bazzite and Aurora

Our friends in the Universal Blue project (Bazzite, Bluefin, Aurora) have prepared the update to Fedora 44. Look for upcoming announcements in their Discourse.

As always, I heavily recommend checking them out, especially if you feel like some things are missing from the Fedora Atomic Desktops and you depend on them (NVIDIA drivers, extra media codec, out of tree kernel drivers, etc.).

What’s next

Helping us with a few nasty bugs

If you are interested in contributing to Fedora Atomic Desktops, here are some bugs that we will have to fix in the short term. We would greatly appreciate help with:

  • Fixing root mount options (atomic-desktops#72): This is a long standing and mostly invisible bug that impacts performance.

  • Moving away from nss-altfiles (atomic-desktops#108): This is another long standing source of issues that new users regularly face.

Sealed Fedora Atomic Desktop bootable container images

Sealed images are now ready for testing! See the other article for all the details.

Roadmap to Bootable Containers

A lot of work is happening to make the transition to Bootable Containers as smooth as possible for our existing users. You can look at the roadmap for this transition at atomic-desktops#26.

One of the tasks is to move away from our unmaintained installation ISO building scripts to the new image-builder tooling. This is planned for Fedora 45 for the ostree variants and support for Bootable Container will follow right after.

Another task is to start building the Fedora Atomic Desktops Bootable Container images using the Fedora Konflux instance.

Where to reach us

We are looking for contributors to help us make the Fedora Atomic Desktops the best experience for Fedora users.

Sealed Fedora Atomic Desktop bootable container images

Posted by Timothée Ravier on 2026-04-27 22:00:00 UTC

I’m happy to announce that we have sealed bootable container images ready for testing for the Fedora Atomic Desktops!

Note: You can also read this post on the Fedora Magazine.

What are sealed bootable container images?

Sealed bootable container images include all the components needed to create a fully verified boot chain, from the firmware to the operating system composefs image. This relies on Secure Boot and thus only supports system booting with UEFI on x86_64 & aarch64.

The components are:

  • systemd-boot as bootloader,
  • a Unified Kernel Image (UKI) which includes the Linux kernel, an initrd and the kernel command line,
  • a composefs repository with fs-verity enabled. This is managed by bootc.

Both systemd-boot and the UKI are signed for Secure Boot. The images are test images so the components are not signed with the official keys from Fedora.

The main direct benefit that we will get from this support is that we will be able to enable passwordless disk unlocking using the TPM in a way that will be reasonably secure by default.

How do I test those images?

See the instructions at github.com/travier/fedora-atomic-desktops-sealed on how to give the pre-built container and disk images a try and how to build your own.

We welcome testing and feedback! Please see the list of known issues and report new issue at github.com/travier/fedora-atomic-desktops-sealed. We’ll redirect them as needed to the right upstream projects.

Beware, those are testing images. The root account does not have a password set and sshd is enabled, by default, to make debugging easier. The UKI and systemd-boot are signed for Secure Boot but, since those are test images, they are not signed with the official keys from Fedora. Don’t use those images in production.

Where can I get more details about how this work?

If you want to know more about how sealed images work (i.e. how we make bootable containers, UKI and composefs work together to create a verified boot chain), see the following presentations and documentation:

Thanks to all the contributors that made this possible, notably (but non exhaustively) from the following projects: bootc & bcvk, composefs & composefs-rs, chunkah, podman & buildah and systemd.

A git sign bug

Posted by Kushal Das on 2026-04-26 08:58:55 UTC

While working on the new git signing feature for tumpa-cli I noticed that some of the commits can not be verified. For a moment I freaked out and then thought it must be a problem in my code. But, I could not dig enough. Opus 4.7 helped me to find the eaxct commit in git's history and a reproducer. I reported the issue to the maintainers and they are working on a fix.

\xc2\xa7 aka § was the cause for me.

msg.txt bodysign stdin (tee'd)stored commit bodyverify
git 2.43 (host)... 20 a7 0a... 20 c2 a7 0a... 20 c2 a7 0aOK
git 2.53 (CI, docker)... 20 a7 0a... 20 a7 0a... 20 c2 a7 0aBAD

git 2.43 transcoded the message to UTF-8 BEFORE calling the signer; signer and storage saw the same bytes (c2 a7). git 2.53 hands the signer the RAW bytes (a7) and transcodes only on the way to the commit object (c2 a7). The invariant "bytes fed to gpg.program at sign time equal the bytes a verifier sees when it reads the commit back" is broken.

git config i18n.commitEncoding iso-8859-1 is supposed to be the configuration if we have non UTF-8 characters. But, I never knew about this configuration before I found the bug.

I want to thank my friends in Anthropic for letting me use the tools and techonology to keep building.

git config am.threeWay

Posted by Michael Catanzaro on 2026-04-24 22:57:22 UTC

If you work with patches and git am, then you’re probably used to seeing patches fail to apply. For example:

$ git am CVE-2025-14512.patch
Applying: gfileattribute: Fix integer overflow calculating escaping for byte strings
error: patch failed: gio/gfileattribute.c:166
error: gio/gfileattribute.c: patch does not apply
Patch failed at 0001 gfileattribute: Fix integer overflow calculating escaping for byte strings
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

This is sad and frustrating because the entire patch has failed, and now you have to apply the entire thing manually. That is no good.

Here is the solution, which I wish I had learned long ago:

$ git config --global am.threeWay true

This enables three-way merge conflict resolution, same as if you were using git cherry-pick or git merge. For example:

$ git am CVE-2025-14512.patch
Applying: gfileattribute: Fix integer overflow calculating escaping for byte strings
Using index info to reconstruct a base tree...
M	gio/gfileattribute.c
Falling back to patching base and 3-way merge...
Auto-merging gio/gfileattribute.c
CONFLICT (content): Merge conflict in gio/gfileattribute.c
error: Failed to merge in the changes.
Patch failed at 0001 gfileattribute: Fix integer overflow calculating escaping for byte strings
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

Now you have merge conflicts, which you can handle as usual. This seems like a better default for pretty much everybody, so if you use git am, you should probably enable it.

I’ve no doubt that many readers will have known about this already, but it’s new to me, and it makes me happy, so I wanted to share. You’re welcome, Internet!

Modernize your Bash prompt colors

Posted by Tadej Janež on 2026-04-24 16:52:00 UTC

Do you still use the default green-colored Bash prompt?

Then it's time to upgrade to a much improved shell UX using the Bash Color Prompt (bcp).

Results:

Before
Before
After
After

Motivation: dealing with multiple Toolbox containers

Lately, I've been getting annoyed by my current Bash prompt offering me a poor UX when dealing with multiple Toolbox containers. The prompt lacked crucial information: to which of the running containers a given shell belongs to?

I did a quick search to see if there's an easy fix I'm missing out but it turned out there is a long-standing desire to improve Toolbox's UX in this respect and multiple approaches have been discussed/tried. Here are some relevant tickets:

Discovering the old and new version of Bash Color Prompt

After looking around on how to update my Bash prompt to become "container name"-aware, I came across Fedora's shell-color-prompt package which was conveniently just a dnf install bash-color-prompt away (strangely, the source package is named shell-color-prompt while the binary package is named bash-color-prompt, see also RHBZ #2291024).

My attempts at configuring the Bash prompt to be "container name"-aware with the help of shell-color-prompt didn't look very promising.

I had a little epiphany when discovering that shell-color-prompt's maintainer, Jens Petersen, recently wrote a replacement for it: namely Bash Color Prompt (bcp). Jens describes it as having a cleaner declarative approach for creating one's custom Bash prompt.

Setting up the new version of Bash Color Prompt

Seeing how easy Bash Color Prompt (bcp)'s example.bashrc.sh looked like, I decided to give it a try.

It worked and its declarative approach at creating a custom Bash prompt was really easy to follow and tailor to my needs.

Currently, until the new version of Bash Color Prompt (bcp) is packaged in Fedora (and other distributions), a simple way to install it is to just grab the bash-color-prompt.sh file directly from its GitHub repository and put it somewhere in your home directory.

Afterwards, just source and configure it in your .bashrc file. Here is how I've done it:

# Use the new Bash Color Prompt (bcp) by Jens Petersen (Red Hat) to handle PS1.
# NOTE: Temporarily, I've just copied the script from:
# https://github.com/juhp/bash-color-prompt/blob/main/bash-color-prompt.sh
if [ -f $HOME/bash-color-prompt.sh ]; then
    source $HOME/bash-color-prompt.sh
fi
# Configure bcp.
bcp_layout() {
    local exit_code=$1

    # hexagon
    bcp_container

    # opening [
    bcp_append "["

    # user@host or user@container(host)
    local user_color="green"
    if [[ $EUID -eq 0 ]]; then user_color="red"; fi
    local machine="\h"
    if [ -f /run/.containerenv ]; then
        container_name=$(grep -oP '(?<=name=")[^"]+' /run/.containerenv)
        machine="$container_name(\h)"
    fi
    bcp_append "\u@$machine " "$user_color;bold"
    bcp_title "\u@$machine:\w"

    # directory
    bcp_append "\w" "blue"

    # git status
    bcp_git_branch " " "magenta" "yellow"

    # status indicator
    if [[ $exit_code -ne 0 ]]; then
        bcp_append " ✘$exit_code" "red;bold"
    fi

    # actual prompt char
    bcp_append "]\$ " "default"
}
# Initialize bcp.
bcp_init

Community Update – Week 17 2026

Posted by Fedora Community Blog on 2026-04-24 12:00:00 UTC

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: 20 – 24 April 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

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

  • Fedora 44 Final release preparation

RISC-V

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

  • F44 rebuild: we’re halfway through; getting through about 300 builds/day.   (NB: This is still pretty decent, given the reduced builders we have.  Fedora also has a non-trivial number of ‘noarch’ packages; they can get imported into RISC-V Koji without a rebuild.)
  • Tried out an upcoming server hardware called  SpacemiT K3.  I got 24h remote access (with some limitations). Uploaded some basic data. Ran an initial benchmark of building ‘binutils’:
    • K3 is ~6.5x faster at compiling ‘binutils’ compared to our current build horse P550. (NB: this is not a 100% apples-to-apples comparison, as P550 is on Fedora, while the K3 is on some FrankenLinux, so the default compiler flags from the host differ.)
  • Started a thread with a few folks on a backup plan to improve reliability of builder hardware. Roughly: until server-grade hardware is widely accessible, see if we can get a few of the current “workhorse” (SiFive P550), and make them available somewhere so that they can be easily hooked to RISC-V Koji.
  • Conferences: RISC-V EU Summit schedule preparation is done.

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.

Forgejo

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

  • [Forgejo] Participated in the Fedora Forge Sprint Planning meeting call
  • [Forgejo] Strategized the collaboration on the private issues feature inclusion
  • [Forgejo] Private Issues, Web UI: List the private issues in its separate section [Followup A] [Followup B] [Followup C]
  • [Forgejo] Private Issues, Web UI: Show the private issue ticket contents [Followup A] [Followup B] [Followup C]
  • [Forgejo] Private Issues, Web UI: Investigate and implement the milestone changes on a private issue [Triaged]
  • [Forgejo] Private Issues, Web UI: Investigate and implement the project changes on a private issue [Triaged]
  • [Forgejo] Private Issues, Web UI: Investigate and implement the assignee changes on a private issue [Triaged]
  • [Forgejo] Private Issues, Web UI: Investigate and implement the dependency changes on a private issue [Triaged]
  • [Forgejo] Private Issues, Web UI: Push the foundational private issues frontend codebase implementation [Triaged] [Followup]
  • [Forgejo] Private Issues, Web UI: Investigate and implement the content changes on a private issue [Triaged]
  • [Forgejo] Private Issues, Web UI: Investigate and implement the content changes on a private issue [Triaged]
  • [Forgejo] Foundational private issues frontend codebase implementation [Opened][Followup]

EPEL

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

  • Updated EPEL minor EOL SOP, to be used next month during the retirement of EPEL 10.1
  • Routine packaging work, including CVE work and filing FTI bugs

List of new releases of apps maintained by I&R Team

COPR 2026-04-16 – Highlights

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 17 2026 appeared first on Fedora Community Blog.

🎲 PHP version 8.4.21RC1 and 8.5.6RC1

Posted by Remi Collet on 2026-04-24 04:58:00 UTC

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.6RC1 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.21RC1 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)

New badge: Let's have a party (Fedora 44) !

Posted by Fedora Badges on 2026-04-24 01:25:45 UTC
LetYou attended the F44 Virtual Release Party!

Friday Links 26-14

Posted by Christof Damian on 2026-04-23 22:00:00 UTC
Girona at dusk, with the cathedral and colourful riverside houses reflected in the Onyar

A bit of a mixed bag today. Good reads are the Agents and the Era of Overproduction and AI reshaping values at Enode blog posts. Podcast-wise, give Driverless World and the Pedro Sánchez episode a listen.

Quote of the Week
“It’s like the free puppy,” I continue. “It’s not the upfront capital that kills you, it’s the operations and maintenance on the back end.”
The Phoenix Project
Gene Kim, Kevin Behr, George Spafford

Leadership

TBM 418: Campfires, Trails, and Quests - collection of how AI affects teams.

Day Two - FOSSAsia 2026

Posted by Akashdeep Dhar on 2026-04-23 18:30:20 UTC
Day Two - FOSSAsia 2026

Before I knew it, I found myself already at the second day of the FOSSAsia 2026 conference on 10th March 2026 after a rather eventful previous day. While I did plan to wake up a little later, I realized that I had to prepare for my presentation on the Fedora Badges Revamp Project that was scheduled later that day. This was the only proposal that got selected, and the other one on the Fedora Forgejo Migration Project did not make it, so I had to ensure that I was well prepared for this. After some rounds of talk rehearsals and some quick bites of breakfast, Samyak Jain and I exited Lumen Bangkok Udomsuk Hotel to be greeted by comparatively cooler weather on that day. Since it was more of the same choices on the breakfast menu, we were able to leave the hotel as early as 0945am Indochina Time. Climbing the long escalator to finally make it to the FOSSAsia 2026 event venue, we noticed just how much the community booth layouts had changed that day. For instance, the GNOME Foundation community booth was now positioned beside those of the Debian Project and the TeaLinuxOS Project.

Day Two - FOSSAsia 2026
Manifest #1

I had a mixed feeling about this, while this did allow for the corridor to be widened, the space for volunteer staffing at the community booths of the GNOME Foundation, Debian Project, and TeaLinuxOS Project was severely restricted. This meant that it was quite a struggle for folks who had to move away from or into the booth locations, as that required the folks around them to be moved as well. Just like the day before, we decided to assist Aaditya Singh with booth operations, all while trying to finish off the last hundred Fedora Project stickers that we had saved up from our participation at DevConf.IN 2026. While we had previously signed up for the ExpressVPN-sponsored FOSSAsia hackathon on Internet Security Development Using Artificial Intelligence, we ultimately decided to give away our designated slot to other younger participants who could not register in time. We discussed just how important this hackathon participation was for budding folks who were getting started with free and open source software, but not so much for us, since we have been around the scene for a long while now.

Day Two - FOSSAsia 2026
Manifest #2

This opened us up further for many impromptu conversations, ideation discussions, booth visits, and of course, scheduled presentations. After leaving Samyak at the hallway track, I headed into a newer arrangement of community booths in the second corridor. Since my work laptop had malfunctioning cooling, which made screeching loud noises, I had to use his laptop to deliver my presentation later that day. Not only did I ensure that I downloaded my slide deck and speaker notes onto his computing device well in advance, but I also took care to avoid display inactivity suspensions and ensure an ample laptop battery charge. After a quick round through the community booths, I headed into the hall where the ExpressVPN-sponsored FOSSAsia hackathon was taking place, purely out of curiosity. Informing one of the co-located volunteers about my involvement as a visitor and not as a participant, they allowed me into the room to chat with the fellow participants. Since the hackathon was duration gated, I took extra care to curb my nosiness and allow the teams to work their magic.

Day Two - FOSSAsia 2026
Manifest #3

Out of all the participating groups that I interacted with in the competition hall, my conversations with the likes of Saksham Sirohi and Arnav Angarkar about their ideas stayed with me. They knew how they had to limit their actual implementation and were focused on delivering an MVP (Minimum Viable Product) that could be expanded upon. I also took some time to have a quick conversation with ExpressVPN employees who were serving as competition moderators there to understand what they look for in a certain implementation. Getting myself a cup of boba tea (and skipping it because I did not like it), I met up with the likes of Ajinkya R. and Dakshita Thakkar at the hallway track. On returning to the collective, I decided to lend my assistance to Pongsakorn S. at the KDE e.V. community booth as well, besides helping Aaditya at the GNOME Foundation community booth. I learned that he was using OpenSUSE Leap on his personal laptop and was interested in RPM packaging, while I was placing some of the last fifty Fedora Project stickers on the booth table.

Day Two - FOSSAsia 2026
Manifest #4

In contrast to the unoccupied booths from yesterday, it was endearing to see how the likes of Aaditya and Pongsakorn stood their ground at their respective booths, even when the footfall on the second day was noticeably smaller than the day before. Amidst our conversations, I connected them with each other, and Aaditya even took the chance to showcase the GNOME Foundation community quiz application that he had been working on. Following the community quiz activity idea from the Fedora Project Community Presence at DevConf.IN 2026, he wanted to use the remaining GNOME-styled tee-shirts as prizes for folks who attempted the quiz and got all the answers right at the hardest difficulty. Needless to state explicitly, I gave the quiz a try, not because I wanted another tee, but because I wanted to appreciate what he had been working on. A part of me also wanted to take on this hardest-difficulty question challenge to understand how much I knew about the GNOME Foundation and to see if I could learn things I did not know about the community and its activities in the process.

While I got most questions correct on the first attempt, it took me three attempts to get the satisfaction of having all the answers right. Departing from the booth and weaving through a thin collection of mostly booth attendants, event volunteers, and talk presenters, I made it to Mitchell Yue's talk on the Lynx Framework and how it could be used to move from web development to native applications at around 1000am Indochina Time. I was intrigued to learn about this development library, which made use of native bindings for impressive performance. I was even more taken aback (but positively) when I was gifted a ByteDance tee-shirt for asking how it differed from the usual QtWebEngine bindings, as I was well-versed in Qt. This act of brand advocacy definitely seemed to have encouraged the audience to share more feedback or ask more questions during the talk. Heading back to the Debian Project community booth, I shared my experiences from my splurge at Animate Store from the previous day with Ananthu CV before helping Abhijit PA get some cold coffee from the reception desk.

We were also joined by Shreenivas at the GNOME Foundation community booth, which allowed us to pace ourselves while tending to questions and feedback from booth visitors. During a brief visit from Daniel J Blueman, he connected with Aaditya to understand where he could report bugs and improvements for the GNOME desktop. He seemed to have been plagued by problems with the use of external monitors on his ARM-based (Advanced RISC Machines) SoC-powered (System on Chips) laptop on his fresh Debian Linux installation. Meanwhile, I wasted no time unofficially promoting my presentation on the Fedora Badges Revamp Project to the enthusiastic folks from the day before who visited our booth. Meanwhile, I also gave a quick demonstration on how RPM packaging works to a relentlessly curious Pongsakorn, who wanted to package their Rust application for Fedora Linux. Using one of my own hobby projects, Loadouts for Genshin Impact, I showed him how to write an RPM specfile and how programming-language-specific macros could help make things easier.

Day Two - FOSSAsia 2026
Manifest #5

As I was not sure if something like the PyProject RPM Macros for Rust existed, I wanted our conversation to be an entry point for them into the RPM packaging tooling ecosystem. While answering his question about Linux kernel package versioning on Fedora Rawhide, I also fielded a question about conflicting packages from Abhijit. Since he was experienced with how the Debian Linux packaging process would handle this, he was curious to know how RPM package management tools would address the situation. Using various examples of how software packages are related to one another, I explained how this linking not only mapped dependencies but conflicts as well. At around 1230pm Indochina Time, I wrapped up my lunch and connected with Simon Strohmenger, who was visiting the community booth then. He shared how he worked on funding free and open source software events across Europe and supporting critical engineering ecosystem resources and was also curious to know more about what I had to share regarding the AI-assisted Contribution Policy from the Fedora Project.

Day Two - FOSSAsia 2026
Manifest #6

After sharing contact details with each other, he also checked in with me on whether I would be willing to present a proposal on best practices in contributor onboarding and retention in free and open source software communities. In our conversations, we realized just how crucial it had become to discuss governance policies among grassroots collaborators to ensure that their implementation does not come off as a negative surprise. I also shared my approaches to using LLM (Large Language Model) tooling to assist project maintainers and budding contributors by automatically addressing various low-hanging fruits. Empathizing with how stressful and overwhelming it ends up being for the maintainers and newcomers, respectively, AI tooling could be utilized for these positive purposes instead of worrying about its popularized contemporary taboo perspective. While I could not get him to participate in my Fedora Badges Revamp Project talk later that day, he said that he would send over some of his engineering friends, as he found the general idea of awarding contributions fascinating.

Day Two - FOSSAsia 2026
Manifest #7

Since there were not a lot of folks present at the event apart from those who had some activity to participate in, Aaditya struggled to distribute the remaining GNOME-styled tee-shirts. On the other hand, we had been extremely successful in distributing the stickers, so we were able to advocate for our projects from the community booth. At around 0130pm Indochina Time, I checked in with the event volunteers about the allegedly malfunctioning livestreaming functionality in one of the presentation halls. Amidst my attempts to have that fixed before my talk began in about three hours, I briefly met up with Saksham again in the hallway, who mentioned his plans to expand the hackathon project, and I shared the idea of "releasing (software) fast and releasing often." It was an absorbing sight to see how the participants at the ExpressVPN-sponsored FOSSAsia Hackathon were helping each other with a gargantuan variety of problem statements. Such a sight (and evidence of friendly competition) is something one would rarely get to see outside of free and open-source software communities.

Day Two - FOSSAsia 2026
Manifest #8

I was thankfully able to get myself caffeinated at around 0330pm Indochina Time, as with the activities moving slowly throughout that that day, I found myself zoning out every now and then. After addressing the livestreaming issue, I met up with some folks from AWS (Amazon Web Services) who were visiting our trinity community booth lineup and had previously worked with the likes of David Duncan and Rich Bowen. Since they had experience with Amazon Linux, they reflected on how Fedora Linux provided them with an innovation-driven upstream distribution to build upon. After that one last conversation with them, Aaditya decided to start packing up the booth at around 0430pm Indochina Time, while I kept myself busy helping him with the tooling. With the time being barely fifteen minutes away from my presentation's commencement, Samyak returned to the GNOME Foundation community booth. Pongsakorn also found his companion back when Tomas returned to the KDE e.V. community booth, and I was ready for my talk to be delivered at the tail end of the event.

As the presentation designated training room had my slide deck already fetched, I did not have to bother with sharing my screen. There were some technical issues with the clicker device, though, as it failed to switch slides when the window was in fullscreen mode. I decided not to settle for windowed mode to save time, while Norbert Preining introduced me in the speaker area at around 0445pm Indochina Time. For a presentation scheduled at the tail end of the conference, it was reassuring to see that I still had around twenty attendees in the hall who were curious to know what I had to offer. Being the deciding moment that I had been practicing regularly for, I wanted to ensure that I was doing justice to their time (and attention) and that of the remote attendees. Thanks to Samyak's laptop and the regular touchups, the fifteen-minute-long presentation went largely well, and I also addressed some feedback and questions from both the in-person attendees and the hall host, Norbert. After finishing my talk, we headed into the competition hall where the four judges had assembled, by then.

After briefly waiting for the participating teams to propose their project ideas and for the judges to complete their evaluations, our collective made our way into the main hall to witness the winner announcements at around 0530pm Indochina Time. As the winners were announced and the event concluded, Samyak and I deliberated on our evening plans, as we did not intend to continue our stay with the FOSSAsia 2026 attendees at the Night Market. After his proposal was turned down by the folks he was planning to invite, we formed a group of four, including him, Soundarya Rangarajan, Aaditya, and myself, to visit Bangkok Chinatown. This idea felt strategically sound as it had become a little too late to visit the riverside for a calming evening boat ride dinner, and coincidentally, Soundarya was staying at the same hotel as Samyak and me. After making a quick drop of Aaditya's belongings at my hotel room and taking some time to re-energize ourselves after the long second day, we started looking for cabs using the Grab application at around 0700pm Indochina Time.

Amidst the heavy Bangkok evening traffic, we struggled to get a ride until we finally secured one after about thirty minutes of waiting through the Bolt service. I was not a fan of the service, as the toll expenses were not accounted for in the final billing, thus resulting in us having to pay for them separately. What I was a fan of, though, was the taxi driver assigned to us, as the cheerful person did not let the piling traffic and the linguistic barrier prevent him from having a friendly chat with us. With the use of Google Translate, he graciously helped us plan our course and described what we could expect in Bangkok Chinatown. And he could not have been more right - because when we got off the Bolt ride, the view of the neon filled, slightly humid hustle and bustle of Chinatown was a scene that nothing could even compare to. Weaving through the visitor crowd at the periphery, our first stop was, of course, a stall selling the world-famous Mango Sticky Rice for just 100 Thai Baht per plate. We finally got to experience firsthand just how true the people were who sang nothing but praises of this exclusive snack!

We dove deeper into our little roadside dining adventure with some Coconut Egg Sweet Crepes and Japanese Fried Octopus Balls before deciding to split into groups of two, as it did not sit right by Aaditya and myself, since the cuisines there were mostly non-vegetarian. As Samyak and Soundarya headed their way at around 0830pm Indochina Time, him and I decided to get even more creative by digging into some Shrimp Meat Dimsum Dumplings and Fried Crab Meat Rolls. After finishing off with some Fried Sweet Maple Fish and Ripe Alphonso Mango Slices, all for amazing bargains, we navigated the confusing pathways to reach Jam Jam Eatery Chinatown. As Aaditya's belongings were in my room, we left for the hotel at around 0915pm Indochina Time without waiting much longer. It was not that I had my fill of exploration, but I felt responsible to ensure he made it back safely at BTS Punnawithi to his hotel room. After hanging out in my hotel room and discussing industrial mentorship ideas, I decided to see him off and call it a day at around 1200am Indochina Time.

mTLS avec Cloudflare : mise en œuvre et intégration avec Prometheus

Posted by Guillaume Kulakowski on 2026-04-23 06:33:26 UTC
Dans cet article, je détaille la mise en place d’une authentification mTLS avec Cloudflare afin de sécuriser l’accès à mes métriques Prometheus. Un cas concret avec reverse proxy Apache et intégration dans Grafana.

RasterLab: Building an Image Editor with Claude Code

Posted by Tony Asleson on 2026-04-23 00:00:00 UTC

The question was simple enough: How good of an image editor can you build with $20 worth of Claude Code Pro subscription?

The answer, after one month and roughly that budget, is: surprisingly good, occasionally wrong about performance, and frustratingly confident about things it hadn’t measured.

RasterLab is a non-destructive RAW image editor written in Rust, built almost entirely by Claude Code. Not prototyped by it, not scaffolded by it — actually built by it, with me driving direction and reviewing the output. One month, four weekly usage blocks, one image editor.

New performance tuning possibilities in syslog-ng

Posted by Peter Czanik on 2026-04-22 10:57:45 UTC

On April’s fool’s day, I shared that syslog-ng can reach 7 million EPS. This test lab result was in part possible thanks to a few performance enhancements coming to syslog-ng version 4.12.

How 7 million EPS is possible? Before diving deeper, let me repeat it: 7 million EPS is just a lab testing result, not (yet) possible in the real world. However, the technologies enabling this are already available on the development branch of syslog-ng, or have been available for ages, just not tested or promoted enough.

Read more at https://www.syslog-ng.com/community/b/blog/posts/new-performance-tuning-possibilities-in-syslog-ng

syslog-ng logo

Forge runners maintenance

Posted by Fedora Infrastructure Status on 2026-04-22 09:00:00 UTC

Scheduled maintenance work on Forge Runners. Runners will be offline. Scheduled jobs or event triggered actions should be picked up when service is back running, however it's not completely excluded that some actions might need to be retriggered. forge.fedoraproject.org will not be affected.

Contact: #fedora-forgejo:fedoraproject.org

You’re Invited: Celebrate the Fedora Linux 44 Release Party!

Posted by Fedora Magazine on 2026-04-22 08:00:00 UTC

Fedora Linux 44 is almost officially here! While our release engineering team and packagers focus on the final touches for F44, it is nearly time for the usual tradition of a Global Virtual Release Party! It is almost time to celebrate! For this release, we will celebrate Fedora Linux 44 slightly ahead of its actual final release.

Regardless of the final calendar date of any Fedora Linux release, every release represents months of hard work, testing, and collaboration from our global community. Whether you are a long-time package maintainer, a dedicated documentation writer, a creative graphic artist, or a brand-new user firing up a Fedora Atomic Desktop for the very first time, this release belongs to you.

To mark the occasion, we are hosting the Fedora Linux 44 Virtual Release Party this Friday, April 24, 2026.

Join us for a half-day of live sessions, recorded deep-dives, and community socialization. We have packed the schedule with updates from the Fedora Project Leader, behind-the-scenes looks at new features like Nix integration and DNF5, and a sneak peek at our upcoming Flock conference!

🎟 How to Attend

The event is 100% free and open to everyone, but registration is required to access the virtual venue. We are also happy to continue using our chat communication provider, Element Creations, as the virtual venue for the Global Virtual Release Parties. Thanks Element & Matrix.org for providing us the great tools to bring our global community together!

👉 Register for the Fedora Linux 44 Release Party live event on Matrix! 👈

🗓 Event Schedule

All times are listed in US Eastern (UTC-4) and UTC.

Time (EDT)Time (UTC)SessionSpeaker(s)Description
09:00 AM13:00Opening RemarksJef Spaleta, Justin WheelerJoin the Fedora Project Leader and Community Architect as we kick off the celebration, look back on the last release cycle, and share news from around the project.
09:15 AM13:15FPL UpdateJef SpaletaJef Spaleta shares his reflections on Fedora Linux 44, what this release means for the project, and his vision for what lies ahead.
09:30 AM13:30Packit as Fedora dist-git CIFrantišek Lachman, Laura Barcziova, Maja Massarini, Matej Focko, Nikola ForroThe Packit team walks through how Packit is taking over Fedora dist-git CI, what this change means for contributors, and what’s next.
09:45 AM13:45Adding Nix to Fedora: we did a thingJens PetersenA behind-the-scenes look at bringing the Nix package tool to Fedora 44 — what it took, what it unlocks, and what it means for reproducible environments.
10:00 AM14:00PackageKit with DNF5 and KDE IntegrationNeal GompaDive into the integration of PackageKit with DNF5 and KDE in F44, what changed under the hood, and what it means for the desktop experience.
10:15 AM14:15Server WGPeter BoyAn overview of the Server Working Group’s initiative to create a dedicated home server spin, driven by community home lab feedback.
10:30 AM14:30BreakNoneTake a screen break, grab some coffee, or merge that Pull Request. We will be back with more programming soon!
11:00 AM15:00Fedora DocsPetr Bokoc, Peter BoyAn update on the state of Fedora Docs and the ongoing Docs Initiative — where things stand today, and how you can get involved.
11:15 AM15:15What’s new and what’s next for the Fedora Atomic DesktopsTimothée RavierDiscover what is new across the Fedora Atomic Desktops family (Silverblue, Kinoite, Sway, Budgie, COSMIC) and the roadmap toward Bootable Containers.
11:30 AM15:30Flock PreviewJustin WheelerWith Flock just weeks away, get an early look at what to expect — sessions, highlights, and reasons to get excited about this June’s event.
11:45 AM15:45TBATBAStay tuned!

See you there!

Don’t miss out on the chance to connect with the people who build Fedora. Grab your ticket, share the link with your friends, and get ready to celebrate Fedora Linux 44.

Claim your free ticket now!


The author of this article utilized generative AI (Google Gemini 3.1 Pro) to assist in part of the drafting and editing process.

Day One - FOSSAsia 2026

Posted by Akashdeep Dhar on 2026-04-21 18:30:33 UTC
Day One - FOSSAsia 2026

After kicking off the FOSSAsia 2026 proceedings with the "choose-your-adventure-flavoured" Community Day, the first day on 09th March 2026 began for me at around 0730am Indochina Time. It took me quite a lot of strength to get myself moving out of bed, but I knew that I had to make it to the conference venue by 1000am Indochina Time to appear in the group photo. I rang up Samyak Jain and we planned to rendezvous downstairs at the hotel reception in about ninety minutes from then. While I had my talk on the Fedora Badges Revamp Project scheduled for the next day, I wanted to ensure that I was able to find some time to rehearse it at least twice per day leading up to the scheduled time. Fifteen minutes were not enough for the number of topics I wanted to cover as a part of my presentation, and as such I wanted to use it as an appetizer or an entry point for those interested to explore the project by themselves. I headed downstairs to get some breakfast bites after having connected with my friends and family from back home. The choices were more or less the same as yesterday, but this time around, I elected to stick with the greens as much as possible, just as Samyak did.

Day One - FOSSAsia 2026
Manifest #01

This change in my dietary preference gave me a first-person perspective on just how difficult it ends up being for someone who is vegetarian. While Samyak had his collection of "just-pour-warm-water" packaged food, I had to stick mostly with noodles and salad for the most part. When it came to the origin of the meat products, you would not want your guesses to go wrong, and the language barrier could pose a real problem for the specifics. After an okayish refueling, we stepped out of the hotel premises into a humid Thailand at around 0945pm Indochina Time and were able to reach True Digital Park West in about ten minutes from then. Thankfully, the venue was a whole lot more crowded than the previous day, with a variety of community booths either getting placed or attended by visitors. While this day (and the next day) were exclusive to ticketed personnel, the crowd was definitely a whole lot more than the free-of-charge Community Day (of the day before). I split from Samyak as he left with one of the FOSSAsia 2026 community volunteers to obtain his attendee badge. As I already had the speaker badge, I could dive in headfirst into all the booths and friends that we had on the ground there.

Day One - FOSSAsia 2026
Manifest #02

One of the first folks I met up with was, of course, Aaditya Singh from the GNOME Foundation, who was setting up the community booth by himself. With one more pair of hands, we made quick work of the booth setup as we placed both the Fedora Project stickers beside the GNOME Foundation stickers on display there for picking. Aaditya mentioned that he had been still rocking the Fedora Workstation installation that he had set up during the GNOME Asia 2024 event, where I gave away flash drives with distributions having the premier GNOME desktop environment. As he set up his exhibition laptop, he wanted to promote the vanilla GNOME desktop experience which, in his opinion, could not be done better than it was on Fedora Workstation. Funnily enough, we had the KDE e.V. community booth a corridor apart from the GNOME Foundation community booth. Trying not to read too much into the poetically inclined booth arrangements, I decided to visit them next once I was done setting up the operations with Aaditya. Amidst all the upcoming developments there, Tomas was pleased to share his work on the Konsole KDE terminal emulator with various advancements.

Day One - FOSSAsia 2026
Manifest #03

From live previews of image thumbnails and semantic colors to proactive sharing of directory layouts and drag-and-drop operations, Tomas' improvements felt really impactful in the quality-of-life areas for any general terminal emulator user. This put the Konsole KDE terminal emulator miles ahead of the container-first terminal emulator, Ptyxis, in my personal opinion. I did have questions about the security of this approach, as some files could be malicious in nature (especially SVG files when it came to image assets), but since Konsole relied on pre-generated thumbnails, this was not a problem. No files were executed in the attempt to make the proactive previews available to the users, and that gave me peace of mind to top off my already excited overall feeling about the feature improvements. After meeting up with Pongsakorn S., another KDE e.V. community member, and picking up some stylish badges, I left a portion of the Fedora Project stickers to be shared from their community booth as well. It was important to commemorate the fact that since the release of Fedora Linux 42, the KDE Plasma variant of Fedora Linux had stepped up to become an actual edition instead of just being a spin.

Day One - FOSSAsia 2026
Manifest #04

With Samyak returning to the GNOME Foundation community booth, Aaditya was no longer staffing by himself, so I went ahead to have a conversation with the folks at the Debian Project and the TeaLinuxOS Project community booths. It was interesting to note that they had their ground operations set up as early as 0830am Indochina Time. Chatting with the likes of Ananthu CV and Harry LBI from both the community booths respectively gave me distinctive perspectives on their projects and their involvements. While the stalwart Debian Project community has been around for a while, my interest was piqued to see just how TeaLinuxOS made the Arch Linux distribution usable by normal users with the use of the Calamares Installer and curated OOBE tooling. On being requested for advice from our steadfastly evolving Fedora Linux operating system, I emphasized just how important it is for the documentation to have clarity and to be accessible. A lot of contributors to a free and open source software project come from its pool of users, so it cannot be understated just how important it is to ensure that users are treated as first-class citizens and that their issue statements are taken seriously.

Day One - FOSSAsia 2026
Manifest #05

I departed further into the wider collective of community booths after having taken some pictures with these folks at their community booths. I was halted at the entrance by Wendy Ha, who was just arriving at the conference venue then and wanted me to meet a CNCF ambassador from Japan. Our (rather, short-lived) conversation was put to an end by Rajan Shah, who was seeking out folks from Red Hat and IBM Corp for a group photo. I pulled in Samyak, and with the likes of Shivraj Patil, Veerkumar Patil, Deepesh Nair, and Gaurav Kamathe from Red Hat and a bunch of others from IBM Corp, we had photographs both in front of the FOSSAsia conference venue entrance and in front of the long escalator. This is where I met Soumyadip Choudhury, another colleague from Red Hat, from my hometown, and we spent some time chatting before we headed into the large hall for the FOSSAsia community group photo. I was glad to note that, in an attempt to avoid large commotion, the participants could stay right where they were in their seats and the photo would be taken from the event stage, while only those who were at the extreme periphery were requested to make it to the middle part of the hall.

Day One - FOSSAsia 2026
Manifest #06

As most of our Red Hat collective was already together at the center, all we had to do was enjoy the event hosts' excellent oration while we put out our best poses for the cameraman. We also did not miss the opportunity to take some selfies by ourselves while we were at it, because the audience population was only going to get thinner from here on out for the day. Once we were through with those pictures, Samyak and I ran into the likes of Pritesh Kiri and Dakshita Thakkar, who happened to be attending the event for the first time just like us. Heading out to visit the community booths together, we began by interacting with folks working on ESP32x-powered 2D robotic drawing computers and 3D-printer-powered accessibility-focused appliance designs. Not only did we get to see the demonstration, but we also got to experience how a differently abled person could use a Sony DualShock 4 controller with just one hand and how a pencil-triggered nail cutter could prevent folks from getting hurt. This was followed by a visit to the VideoLAN Project community booth, consisting of what looked to me like mostly disinterested staff members tending to the booth visitors as and when they saw fit.

Day One - FOSSAsia 2026
Manifest #07

After helping ourselves to the postcard prints featuring the famous VideoLAN Project's parodies of famous movies, we moved over to the Matrix Project and database-related community booths. With their booth placements also made beside one another, it was interesting to know from them what they had to offer that their alternatives did not. Skipping through the dishearteningly unoccupied FLOSS Fund community booth, I met Samyak again at the Google Summer of Code community booth. It was great to catch up with Stephanie Taylor after having met her during FOSDEM 2025, and she also graciously provided us with some swag for having participated in the program as a mentee (for Samyak) and as a mentor (for myself). We returned to the GNOME Foundation community booth while being surrounded by an enthusiastic group of folks who were contributors to both the GNOME Foundation (through donations) and the Fedora Project (through contributions). Not only were they thrilled to find us there, but they also went a step ahead by proudly showing off their Fedora Linux installations (most prominently of which were Fedora Silverblue and Fedora Kinoite) from their laptops.

Stellar moments like these always end up re-energizing my resolve to support free and open source software in ways that I could. Getting to interact with folks like these who were just as resolute about the Fedora Project as I was made this trip already worthwhile, even though we had a couple of days ahead of us. They mentioned just how they regularly organized their local Fedora Linux installfest events to help with the adoption of our Fedora Project's primary offerings and also participated in the regularly organized testing events in our engineering community. While I could not provide them with the means to make donations as they wanted to contribute further, I requested them to propose their event through the officially ratified Fedora Mindshare event process. Being the model open source citizens that they were, I wanted to ensure that they did not have to spend out of their own pockets to organize Fedora Project events while ensuring that they were well equipped to host one in the already underrepresented APAC region. Increasing the Fedora Project's APAC representation was already at the top of my list, and this interaction only ended up centering my commitment towards this mission.

Day One - FOSSAsia 2026
Manifest #09

They magically had the intrinsic understanding of just how badly we need contributors to be onboarded and retained within the community to ensure the longevity of a project. A lot of times, it eventually ends up falling on the shoulders of a flywheel person when someone from the community has to depart for some reason. We did not even have to share what was upcoming in Fedora Linux, as they even had an alternate Fedora Rawhide installation handy for development purposes. As the event owner for the Fedora Project's community presence at FOSSAsia 2026, a part of me still felt bad to have missed out on having a dedicated separate community booth at the conference. Sure—we felt right at home with the folks from the GNOME Foundation and KDE e.V., but we could very well have taken advantage of being the prominent RPM-based distribution there on site. A great deal of the community conversations would have then made their way directly to our community booth instead of us having to seek them out as event prospectors in all of our interactions. Instead of dwelling on this situation, I wanted to interact with the booth visitors from a Fedora Project governance member's perspective.

Day One - FOSSAsia 2026
Manifest #10

As I was both a part of the Fedora Mindshare and the Fedora Council governance bodies at the time, I used my event presence to hear more about potential opportunities as well as possible approaches towards community outreach from grassroots contributors. Depending on the matter at hand, I could either choose to address the same or pass it over to the teams responsible as a conduit. Finishing off with this heartfelt interaction, I headed over to the OpenKylin Project community booth to connect with the folks working on this downstream distribution of Debian Linux. Apart from its absolute resemblance to the Windows 11 user interface, this provided folks with a pleasant slope of technical learning while they executed their departure from Microsoft's popular operating system. On my technical suggestion, they made it a point to reach out to the downstream packagers because, from the Fedora Project packaging perspective, their packages were either wildly outdated or simply broken, thus hurting their adoption in the RPM-based universe. I also proposed the utilization of Fedora Linux for the development of the project's codebase, as we provided a speedy-moving development toolchain with updates that they could utilize.

Day One - FOSSAsia 2026
Manifest #11

While there were presentations and workshops scheduled throughout the first day, I still found myself spending most of my time in the hallway track. It was so easy to find someone I knew (or wanted to connect with) or something I knew (or wanted to know about) in all of the conversations. I also appreciated just how my fellow colleagues from Red Hat participated as volunteers for the event, all while sharing goodwill for potential long-term collaboration with the FOSSAsia organizers. This was around the time that the queue for availing lunch started forming at around 1200pm Indochina Time, so Samyak and I ended up joining in. Unfortunately, we had to push our lunch plans for later to make it to Praveen Kumar's interactive talk on Creating Custom Linux Images Using Bootc Technology and Podman Desktop. Delaying our lunch meals by about fifteen minutes or so allowed us to skip waiting in a long queue, but we did end up getting disappointed to notice that the menu had not changed for that day too. Do not get me wrong - the meal was okay for an obligatory refueling, but it left a lot to be desired when it came to ensuring that whatever ended up on our palate tasted good.

Day One - FOSSAsia 2026
Manifest #12

Finishing our meals allowed us to obtain some more energy to visit the community booths that seemed to have popped up later or had absent attendants. We started off with the MapConductor Project community booth, staffed by Masashi Katsumata, who briefed us about how they worked towards unifying all mapping APIs (Application Programming Interfaces) for mobile application map SDKs (Software Development Kits). It was rather intriguing to know how these APIs could be integrated with MCPs (Model Context Protocols) to allow mobile applications to have a semantic understanding of the navigation utility. Using the puzzle question about the number of post offices in Japan was a fascinating way to draw a picture of the important purpose of this community project. We sifted through the ARM Project and RISC-V Project community booths with our discussions around the necessity of an alternative architecture for desktop computing amidst the exorbitant prices of the year 2026. The demos were made using a custom AlmaLinux distribution image flashed on a Raspberry Pi 500 Plus, which had the SBC (Single Board Computer) inside a mechanical keyboard.

Day One - FOSSAsia 2026
Manifest #13

This reminded me of the SyncStar Project that I worked on a couple of years back, when the Raspberry Pi computers were still generally accessible and not prohibitively expensive, as they had become by then. Returning to Aaditya allowed us to meet Rich Bowen, who was just heading out from the workshop at around 0100pm Indochina Time. It was delightful to catch up with him after having met him the last time during CentOS Connect 2025, and he was just as surprised to meet me here, since I was attending FOSSAsia for the first time. Wrapping up our conversations here, Samyak and I headed over to attend Shivani Bhardwaj's demonstration of Hands-on Network Security With Suricata. As someone who primarily works on infrastructure architecture, it was compelling to see just how the project worked both as an intrusion detection system as well as an intrusion prevention system. While her presentation was plagued with a bunch of technical issues related to the presenter's laptop inadvertently suspending, Shivani kept the audience engaged with her admirable showpersonship and funny jokes, giving me something to learn about too when it came to speaking.

Day One - FOSSAsia 2026
Manifest #14

We stayed back in the same hall to attend Peter Membrey's talk on Open Sourcing Secure GPU Workloads in Enclaves as it shared a similar cybersecurity-inclined theme. As he was the Chief Research Officer of ExpressVPN, an organization that was also one of the primary sponsors of the conference, I wanted to understand just how bought in they were with the free and open source software mission. Having gotten a satisfactory answer, I left to get a FOSSAsia tee-shirt and necessary caffeine, since I did not have to join the queue for the identification badge that morning. I was pleasantly corrected when they declined my payment for the FOSSAsia tee-shirt and informed me that this was available at zero extra cost for the event participants. The lack of a proper lunch did manage to keep me awake, but a proper shot of cold coffee was able to finally get me back into the game once I was done exchanging the participant coupons. I hung out with my fellow Red Hat colleagues at the OpenEuler Project community booth before going back to Aaditya's place. Since he had kept a medium-sized GNOME tee-shirt aside for me, it only made sense for me to pledge a certain amount to the community.

Day One - FOSSAsia 2026
Manifest #15

And might I add just how attractive of a bargain 100 Thai Baht was in exchange for a white GNOME round-necked tee-shirt, all while supporting the great work that they did! It could not be understated just how often free and open source software communities end up giving you friendships that you cherish for your lifetime. At around 0215pm Indochina Time, we attended Dakshita's presentation on Observability for Backend Developers before reaching out to the FOSSAsia volunteers regarding my concerns about the absence of speaker desks in various smaller-sized halls. While my concerns were accounted for by the staffing volunteers there, it was only when Rajan entered the scene that it was not only resolved for the training room that I had my presentation planned for the day after, but also for other associated halls. He mentioned to me how my preemptive concern about my deferred presentation allowed others to benefit too, since it had become unwieldy to use a lower-height general table. After having attended Joe Blubaugh's talk on SQL Expressions in Grafana Dashboards at around 0240pm Indochina Time, I decided to return to the hallway track to have some more conversations.

Day One - FOSSAsia 2026
Manifest #16

One discussion on internet technologies with the likes of Ananthu and Deepesh at the Debian Project community booth later, we were joined by an extremely enthusiastic Daniel J Blueman at the GNOME Foundation community booth. Since he had presented his talk about Linux on ARM (Advanced RISC Machines) Laptops earlier that day, he wanted to have a comparative study of how different both the architectures were on a quantitative level. While our collective had a qualitative understanding of just how efficient ARM-based SOCs (System On Chips) were as compared to the widely available x86-based CPUs (Central Processing Units), stress-ng testing (as requested by him) could help paint an accurate picture. While the tests were running on both Aaditya's power-deprived laptop and Daniel's cool-running laptop, he was appreciative of the attempts made to make Fedora Linux work on ARM-powered Apple MacBooks and general-purpose ARM-powered laptops. Although the initial tests gave us an idea about the performance per wattage across both the architectures, we had to dispose of the results as the x86-based laptop was not getting power from the wall, unlike the ARM-based one.

Of course, we had to have a rematch - not specifically for getting different-looking results but getting genuinely computed ones, and this time around it was the turn for Samyak's Lenovo ThinkPad P16v Gen 1. After making sure that both of these devices were getting enough juice from the power outlet and shutting down the unnecessary applications, we were able to obtain an anecdotal result that put the AMD (Advanced Micro Devices) Ryzen 7 Pro 7840HS CPU miles ahead of the Qualcomm Snapdragon X Elite SoC. This kind of unstructured research was able to draw quite a huge crowd in the second half of the day, and we deduced that while Samyak's laptop was drawing at most about 100 watts from the wall, Daniel's laptop was barely pulling at most around 25 watts. With improved compatibility across various applications and additional efforts in hardware enablement, the ARM-based SoCs could very well be the future of sustainable domestic general computing. After sharing contact details, Ananthu and I had a quick discussion on exploring places that exhibited (or franchised) anime-related swag, especially those from the popular Genshin Impact brand at around 0400pm Indochina Time.

With Samyak on his way back to the hotel room, Aaditya, Ananthu, and Shreenivas (who began hanging out with us at around that time) and I decided to stay back to attend the FOSSAsia Evening Social Event. I seemed to have chosen wisely, as I ended up running into Harish Pillay shortly after in the hallway track, whom I had last met during CHAOSScon EU 2024. In our friendly exchange, he shared how he used Anthropic Claude to generate slide decks based on the speaker notes that he had manually prepared, a process that felt flipped to me, but I was captivated to see the results that he had on display. I noted the effective learning for times with a shorter timeline for proposal submissions without having to compromise on the overall quality. After a couple of photographs with him, I joined back our little gang for a quick round of instant photoshoots with a hilarious set of props. Aaditya and I decided to split from the likes of Shreenivas and Ananthu for the day to have our snack bites at around 0700pm Indochina Time. We enjoyed the Thai cultural performance presented by the event volunteers before I decided to depart swiftly for the newly discovered Animate Store at the MBK Center.

Day One - FOSSAsia 2026
Manifest #19

Coordinating with Samyak again, I dropped off my stuff in my hotel room before leaving for the BTS SkyTrain at around 0715pm Indochina Time. Since MBK Center was around a ten-minute walk away from BTS Siam, and so was the Jain temple that he wanted to visit, we decided to travel together. Having one of those rare moments where Samyak was ready to leave before I was, we headed to an ATM to withdraw some money. Just like my arrival day, we had to cough up around 250 Thai Baht besides the actual amount, but that had nearly become something that we had gotten used to. Cash was indeed king in Thailand, and we had to ensure that we had enough money to not require another round of ATM withdrawals. After a forty-five-minute-long journey from BTS Udomsuk, we split at BTS Siam after deciding to meet up there at around 0930pm Indochina Time. Getting local Thailand SIM cards proved to be extremely beneficial, as that allowed us to stay connected with our friends and families while we were navigating the hustle and bustle of Bangkok. We did not worry about the possibility of getting lost during transit, as we could always find our way back to each other.

Day One - FOSSAsia 2026
Manifest #20

I was able to make it to Animate Store on the seventh floor of the sprawling MBK Center mall by around 0830pm Indochina Time, giving me roughly half an hour before the shop shuttered. Connecting remotely with Shounak Dey from back home, I made the best use of the time to collect some Genshin Impact collectibles for us. After making quite a lot of purchases from the official miHoYo swag catalog, I decided to be on my way back to BTS Siam right when Animate Store closed down for the day at around 0900pm Indochina Time. An uneventful BTS SkyTrain journey later, we found ourselves at BTS Udomsuk at around 1015pm Indochina Time with few choices for Indian cuisine, as most adjacent shops were closed and the farther restaurants would be closed by the time we would have gotten there. After a quick trip to an adjacent SevenEleven outlet and helping Samyak with packaged mineral water bottles from the day before, we decided to order some Indian cuisine takeaways from the Grab application. We decided to call it a day at around 1130pm Indochina Time after sharing a light dinner of some homestyle Indian meal together in my hotel room and going through a round of presentation prep.



Fedora Verified: Help Shape a New Way to Recognize Fedora Contributors

Posted by Fedora Community Blog on 2026-04-21 12:02:00 UTC

The Fedora Project is proposing a new contributor status called “Fedora Verified” to better recognize all forms of community contribution, and we need your feedback. Following the Fedora Council 2026 Strategy Summit, Fedora leadership is reflecting on how we recognize, support, and empower the people who make Fedora possible. Please read through our proposal below and share your thoughts in the Fedora Verified community survey.

As the global open source community grows, the Fedora Project needs to ensure that our systems for recognizing contributors keep pace. Historically, open source recognition has leaned heavily on easily-quantifiable systems such as git repository commits and Pull Requests. But Fedora is built on much more than just code. We want to implement a more human-centered approach that equally values all forms of contribution including mentoring, documentation, design, event organization, and community support.

To help us get there, we are proposing a new contributor status called “Fedora Verified” (Name TBD – feedback welcome!). But before we finalize this model, we need your feedback.

What is the “Fedora Verified” Status? 

“Fedora Verified” is a proposed membership-driven approach for the Fedora Account System that distinguishes highly engaged, committed contributors from tens of thousands of standard registered accounts.

How is “Fedora Verified” different from a standard account? Anyone can create a new account in the Fedora Account System (FAS) to begin their journey, file bugs, or make initial contributions. A FAS account is the equivalent of a digital passport to access various Fedora-hosted applications and services for users and contributors alike. “Fedora Verified” represents the next step: a mutual commitment between the contributor and the project, recognizing a sustained track record of positive impact and adherence to our core principles as a community: the Four Foundations (Freedom, Friends, Features, First).

What are the proposed benefits? The primary motivation behind “Fedora Verified” is to build trust-based recognition that grants elevated, privileged rights within the project. Most notably, this status would determine eligibility for strategic governance activities, such as:

  • Voting in Fedora community elections.
  • Running for leadership or decision-making roles within the project (i.e., Fedora Council, FESCo, Mindshare Committee, EPEL Steering Committee).
  • (Potential, unplanned) Accessing specific shared project resources or educational opportunities (e.g., Red Hat training credits).

Proposed Baseline Metrics for Fedora Verified

To ensure fairness and transparency, we are proposing a set of baseline metrics that a contributor must meet before their request for “Fedora Verified” status goes to a human review. The proposed baseline includes:

  • Sustained Activity: Active involvement in the Fedora community for a minimum of two Fedora release cycles (i.e., sustained participation between 6-12 months at minimum).
  • Consistent Contributions: A measurable track record of contributions across any recognized area (code, documentation, design, community support, etc.) in the current and previous Fedora release cycle.
  • Good Community Standing: The contributor is in good standing in the community and does not have a history of behavior that is contradictory to the Fedora Code of Conduct.

Unanswered Questions for the Fedora Community

While we have a framework, there are several major questions we need the community to answer before we move forward. Specifically, we want to know:

  • Validation: Should applicants be approved by grassroots peer vouches, or an elected committee?
  • Fairness: Does this model truly value non-code contributions equally?
  • Progression: How strictly structured should the path to becoming “Verified” be?
  • Maintenance: Should the status expire after 12 months of inactivity?

Share Your Voice on the Proposal

We want to make sure this proposed membership model is fair, sustainable, and truly represents what our contributors value. Your feedback will directly influence how this policy is drafted and implemented.

Take the Fedora Verified Community Survey!

The survey will be open until Sunday, 5th May 2026 at 23:59 UTC. Thank you for taking the time to share your perspective, and for everything you do to make Fedora an amazing community!

The post Fedora Verified: Help Shape a New Way to Recognize Fedora Contributors appeared first on Fedora Community Blog.

Community Day - FOSSAsia 2026

Posted by Akashdeep Dhar on 2026-04-19 18:30:18 UTC
Community Day - FOSSAsia 2026

The FOSSAsia 2026 event prioritized the friendly community interaction aspect of a free and open source software event by frontloading it on 08th March 2026 as a freely accessible event. This was surely a great example to learn from and implement at our flagship annual community conference, Flock To Fedora. I started the day by waking up as early as 0700am Indochina Time and giving Samyak Jain a wake-up call. As the timezone offset from Indian Standard Time was ninety minutes, I had to wait for some time before I could connect back home with my family members. Thankfully, the breakfast meal provided at Lumen Bangkok Udomsuk Station was a lot more flavourful and distinctive as compared to those that I was habituated to having at hotels in Europe. While there was a lot to be had for my dietary preferences, it was a tough time for Samyak in a mostly non-vegetarian selection of meals, so he had to request a custom vegetarian meal. Once we were through with breakfast, we started off for the FOSSAsia 2026 conference venue, True Digital Park West, at around 0930am Indochina Time.

Community Day - FOSSAsia 2026
Checkpoint A

As the venue was barely under a kilometer away from our stay, we were able to make it to the event on foot. While the summer season had not arrived in Thailand, it was still extremely humid, and we wanted to head indoors as soon as possible. Skipping the first couple of early sessions allowed us to get enough respite after a long yesterday, and that would mean that we could also last longer that day. After skipping through some floors of the True Digital Park Campus and connecting with the folks from the FOSSAsia Community Cycling Trip in the Telegram chat, we were finally able to make it to the right location. Following Mishari Muqbil's advice, we took the long escalator that skipped a couple of floors entirely to get us right in front of the event reception. The one thing that took me by surprise in Thailand was the fact that the ground floors were counted as the first floor, and there was no concept of a zero level. It was a pretty interesting observation that we had to mentally train ourselves to get used to, if we wanted to not get lost while visiting most (if not all) multi-storeyed buildings in Bangkok.

Walking through the premises, which astonishingly enough consisted of both student laboratories and shopping stores in equal measure, we entered the hall selection where FOSSAsia 2026 was organized. Surely, the volunteers could have done better at pointing folks to the correct place, but this feeling was quickly overridden when I ran into a bunch of acquainted and recent community friends. Getting to meet these people, mostly from APAC, at the event felt like making a victory lap to celebrate all the connections that I had painstakingly built throughout the last five years or so. Trying not to get swept away in all the interesting conversations, we were guided by an adjacent volunteer to get ourselves the badges, wristbands, and swag kits from the event reception. I was able to get those for myself as I was also participating in the conference as a speaker, but Samyak had to wait until the next day to obtain his badge. While we had the agency to join one of the running workshops at the time, we still decided to hang out at the hallway track a little longer to discuss open source strategies with the community.

After a brief catch-up with Ananthu CV from the Debian Project, whom I was meeting here after having done so during GNOME Asia 2024 and FOSDEM 2025, Samyak and I made it into the Eventyay Developer Workshop room at around 1045am Indochina Time. Although we initially thought that we were late, Norbert Preining, Srivastav Auswin, and Mario Behling were just getting started conducting a round of introductions for the folks present there. Since I was representing the Fedora Infrastructure in this workshop, I presented the case of how we used a similar event service platform, Pretalx, for our use case and how I was interested in learning all the various things EventYay had to offer. Amidst the feature run-through and tooling integrations, the workshop organizers had an interest in how the Fedora Project used Pretalx for running events like CentOS Connect and Flock To Fedora. Amidst the lack of proper seating in the room, I also got to meet Deepesh Nair briefly before agreeing to connect with Mario later for deeper discussions on how we could further collaborate in the future.

Hong Phuc Dang entered sometime later with an announcement for refreshments and some more seats for the workshop hall. This allowed the hall to be filled up a whole lot more as we headed back to the hallway track to meet with the likes of Aqsa Aqeel from DigitalOcean and Leon Nunes, who had begun his open source contribution journey. It was interesting to notice how the Fedora Project was the only RPM-based distribution on the scene there apart from our reliable downstream, Red Hat Enterprise Linux representatives. The distribution aspect of the event felt mostly occupied by the folks from Canonical and Debian, thus giving us the chance to capture some relevance. I briefly met up with Anuvrat Parashar and Shivani Parashar before having a conversation with Hong, who was surprised to note that the Fedora Project did not have a community booth. It turned out that there was another Call For Proposal form that was opened up closer to the commencement timeline, apart from the one for presentations and workshops, that I, as the event owner from the Fedora Project, was not even aware of.

Community Day - FOSSAsia 2026
Checkpoint B

This was also hinted at by Mishari in one of our conversations from the day before about the community booths being made available for free while the commercial booths were being charged a reasonable payment. In our discussions, Hong assured community support, and I discussed strategic collaboration before we had some quick photograph clicks to end the conversation. While not being able to have a community booth during FOSSAsia 2026 felt like a missed chance, I wanted to make the most of my participation as a community prospector for the Fedora Project's future participation in the event. We did not really have concrete plans on which workshops we would want to attend that day and were making our agenda on the fly. Making it back to the hallway track at around 1100am Indochina Time, I met up with the likes of Rajan Shah, Shivraj Patil, Veerkumar Patil, and Gaurav Kamathe from Red Hat, who were just arriving at the conference venue. It was hilarious to catch up with them here barely a couple of weeks after meeting them at the DevConf.IN 2026 conference in Pune, India.

At around 1130am Indochina Time, Samyak and I headed back into the rooms to attend presentations delivered not just in English but in a variety of languages. It was interesting to see just how open the FOSSAsia conference was to folks wanting to present their work in their own language, and when paired with a technology that live-transcribes it to a more generally known language, this could significantly lower the barrier of entry for these conferences. Most sessions, if not all, were bite-sized portions of fifteen minutes, and depending on who you are, the time management aspect of the presentation could be difficult. After exchanging the coffee coupon for a Dunkin-branded cold coffee and the meal coupon for a packed lunch, we headed out to chat with one of Samyak's friends from the Debian Project. We were able to make it back to Wendy Ha's talk on her experiences as an APAC Kubernetes Community Contributor, followed by Punsiri Boonyakiat's talk on balancing motherhood responsibilities with open source, which became a key highlight for International Women's Day.

On the second half of the community day, the host was doing absolutely terrific work keeping the audience entertained while the volunteer team looked into the technical problems that had crept in. Her fantastical oration with a deadpan expression did not allow our spirits to sour when the fixes were taking a little while longer. Contrary to my belief, the community day was not as occupied as I thought it would be due to its free-of-charge participation, but we were able to make the best of whoever was present on the ground. We also ran into Aaditya Singh from the GNOME Foundation and Mishari, who were just arriving at the conference venue in the afternoon, both of whom we were quite pleased to catch up with. After a quick conversation with Tamhant about the technological industry, I met up with Mario again to discuss how the Fedora Project evolved from a fragile ticket-based system to a robust dedicated event platform. It helped me understand how EventYay's Developer Preview Service could be accessed without having to establish the project environment locally.

As the Fedora Infrastructure's CommuniShift Project allowed for getting these deployments up and running in no time, I suggested the same to the EventYay developers, as they could find it handy to demonstrate this to the Fedora Project community. After running into Hong again, Samyak and I talked about how we could further push the adoption of the community day using interactive activities for folks hanging out on the hallway track. This would allow for greater participation on the community day, not just by those who have their talks planned but also by visitors. At around 0120pm Indochina Time, we made it to Peter Zaitsev's talk on Percona Project's attempts to make MySQL Community stronger. Apart from the obligatory jabs hurled at Oracle, there were also some tricky questions around the choice between MariaDB and MySQL if PerconaDB was not an option, addressed. We went on to attend Michael Meskes' talk on Open Source Business Models, which felt quite at home for us working with the Fedora Project as part of our responsibilities.

Community Day - FOSSAsia 2026
Checkpoint C

The "free" in a free and open source software project always comes with an asterisk marked hidden condition about the price being paid by someone else. The price is also usually not in the form of monetary payment, and that is what ends up hurting the longevity of these communities the most. After an insightful conversation on onboarding and retaining contributors, we headed out at around 0200pm Indochina Time to get another round of caffeine. We had discussions around the state of the warring world and how multiple cancelled flights through the Middle East affected selected speakers at FOSSAsia 2026. Aaditya welcomed us to station Fedora Project folks at the GNOME Foundation community booth since there would be enough space for both. As Samyak had stickers saved up from DevConf.IN 2026's Fedora Project community representation, we could use those here. Unfortunately, we could not meet Asmit Malakannawar, who planned to tag along with Aaditya, as his flights through the Middle East were also cancelled, and there were zero provisions made for remote talks.

Samyak and I headed back into the presentation rooms to attend Louis Yoong's talk on Building AI-Powered Interactive Maps with Open Data at around 0300pm Indochina Time, before attending a series of lightning talks from the Women In Tech category. After attending Velia Dang's informative talk on the reviewer's point of view when using EventYay and obtaining learnings to apply for Flock To Fedora, we decided to depart from the conference after the closing notes. While there were some activities planned at Lotus' Eatery for the Pre-Event Community Gathering, we wanted to use the remaining time of the day to explore what Bangkok had to offer. We were able to make it back to Lumen Bangkok Udomsuk Station by 0445pm Indochina Time before leaving again for the BTS SkyTrain after around forty-five minutes. With a rigid agenda to go with, we planned to visit Masaru, an anime collectible franchise store located near BTS Phra Khanong, which was barely four stops away from BTS Udomsuk. Ten minutes of train ride and five minutes of walking got us where we wanted to be.

We spent a little too long there than we could care to admit as Samyak got himself busy finding figurines while I was hunting for some Genshin Impact branded collectibles. Surprisingly enough, I was able to get a brokered change for the 1000 Thai Baht note that I was carrying while we were booking BTS SkyTrain tickets from BTS Phra Khanong to BTS Siam once we were done with our purchases at Masaru. It was going to be a comparatively longer ride with around eight stops and then a ten-minute walk to the world-famous MBK Center. At around 0800pm Indochina Time, we made it to BTS Siam station, but we kept getting sidetracked by the sprawling independent weekend market that we wanted to explore. With Samyak and me splitting again to find our pickings, I could not help but purchase some gifts for my family, including Hawaiian shirts, tourist hats, ornamental pendants, and much more. I was glad to have my wits about me while driving a hard bargain for making all these purchases because that would allow me to eventually purchase some more things in the end.

The humidity was making it tough, but we were finally able to push through to the indoors of the MBK Center by around 0845pm Indochina Time. Coincidentally, this is where we ended up finding one of the best independent handicraft stores, where Samyak and I got ourselves a wide assortment of personalized keychains and magnets for our friends and families. As our order was a massive one, with six for myself and six for him, we decided to depart after placing the order to see if we could make it to the anime café in time. The sprawling layout of the MBK Center only made it difficult for us to find our way - apart from, of course, getting sidetracked into purchasing Thailand incenses and local handicrafts. Splitting from Samyak again, who got busy with his purchases, I was able to make it to the place. To my utter disappointment, the shop had already closed by 0830pm Indochina Time, and I reached almost an hour late. I backtracked to where I last saw him, and we decided to head back to the handicraft store as we had to retrieve our orders right before the operations wrapped up for the day.

Community Day - FOSSAsia 2026
Checkpoint D

The enormous mall could be a treasure trove for those who know what they are looking for, but for the two of us exploring, it felt like an overwhelming labyrinth with similar looking pathways and deeply confusing corridors. We were finally able to make it to the handicraft store by around 0945pm Indochina Time, right at the time of the last handicraft being finalized. Since we had already cleared the bill, we headed back to BTS Siam while clicking pictures and discussing plans, only to end up boarding a rather crowded BTS SkyTrain on a weekend. By around 1045pm Indochina Time, we made it back to BTS Udomsuk, but after exploring the surrounding places to see where we could dine, we decided to order some food from the convenience of our hotel rooms using the Grab application. I got myself freshened up after requesting the hotel reception to retain the order, and I was glad to have ordered a carton of mineral water too. After a quick bite for dinner, I decided to call it a day with multiple precautionary alarms enabled to ensure that I woke up early the next day for the group photo.

misc fedora bits mid april 2026

Posted by Kevin Fenzi on 2026-04-18 16:10:38 UTC
Scrye into the crystal ball

Another frozen week before the Fedora 44 release, just a few notable things:

openssl4

Openssl4 landed in rawhide and caused some issues and then was pulled back out by FESCo. We definitely do need to move to it for Fedora 45, but hopefully we can land it in a way that doesn't break as many things as this last time.

Folks are working on it and I expect we will see it soon.

builder news

We had a aarch64 builder virthost fail to reboot with memory errors a few weeks ago. Finally got someone onsite to pull and reseat all it's memory and that seems to have done the trick. We are back to full on aarch64 builders again. Of course we had enough that I doubt anyone actually noticed that some were down.

I also brought up 3 more big x86_64 builders. They should be added after freeze/sometime soon. Nice to have extra capacity there even thought we aren't hurting for x86_64 builders.

Bots found the wiki

Yesterday our wiki was up and down in the morning. Seems scrapers not only found the wiki, but also found that they could query time ranges for changes in Special:RecentChanges.

We put in some blocking and then increased a bunch of cpu on the backend and everything seems to be back to 'normal' now.

Until the next time...

vacation!

I will be out on a family vacation next week. Our plane leaves super stupid early on tuesday morning and I will be packging and such on monday. So, please don't ping me: file tickets or ask others to take care of any fedora issues you might have.

Hopefully when I am back we will be go for Fedora 44 release!

comments? additions? reactions?

As always, comment on the fediverse: https://fosstodon.org/@nirik/116426624580451263

Arrival Day - FOSSAsia 2026

Posted by Akashdeep Dhar on 2026-04-17 18:30:12 UTC
Arrival Day - FOSSAsia 2026

As my arrival flight to Bangkok was scheduled to depart at around 0700am Indian Standard Time, I had to wake up as early as 0230am Indian Standard Time on 07th March 2026. The packing had already been taken care of previously, so all I had to take care of was ensuring that I got myself an Uber ride to the Pune International Airport in time. Thankfully, unlike my experiences from DevConf.IN 2026, I was able to get one pretty quickly, and at around 0400am Indian Standard Time, I reached the airport. The check-in process went smoothly, since I was not carrying much luggage anyway to begin with on my Air India Express flight. With my physical boarding pass in hand, I headed upstairs to wait for the immigration booths to open for the day. After forty-five minutes of waiting, the gates finally opened up, and I made it to the security check after smooth processing. The fact that I had my Thailand Digital Arrival Card registration done in advance helped me get through to the designated gate 1A without much hassle. I ended up having a lot of time left on my hands, so I decided to connect with the Egencia service about the troubled accommodation booking while I waited for boarding to begin.

Moving away from two noisy groups of travellers - one with senior citizens and one with rowdy men - I got myself a place to sit as I rang up the Egencia customer care helpline. Since 0530am Indian Standard Time was still a little early for their working hours, it took me a while to connect with a human representative. A helpful attendant attempted to connect with the Lumen Bangkok Udomsuk Station hotel employees, but that did not work out. I decided to board the flight anyway at around 0645am Indian Standard Time and leave the concerns about the troubled accommodation booking for when I would have reached Bangkok. There was not much that I could have done at that time to help the situation, and besides the issues that we had with Egencia regarding the flight confirmation, this worry would most likely have soured my entire experience. After a quick switch of seats from 7A to 6A, on a fellow passenger's request, I decided to watch some movies, such as Code 3 (2025) and Zootopia 2 (2025), on my phone. The Kebab Platter was soon served, and that allowed me to catch up on some rest that I was lacking due to having to wake up early in the morning just to make it to the airport.

The flight soon landed at the Suvarnabhumi Bangkok International Airport at around 1230pm Indochina Time, and after connecting with my family to let them know about my safe arrival, I headed swiftly into the immigration queue. The overcrowded traveller collective took me about forty-five minutes to make it through to the other side, where I found that the designated luggage belt #21 had finished delivering all of its luggage. After crossing a big group of Chinese travellers, I got myself a data plan from True 5G at the airport exit. 599 Thai Baht for 8 days of unlimited service was a great deal, and that allowed me to stay connected with both my family and friends, and with Samyak Jain, with whom I was representing the Fedora Project APAC community at FOSSAsia 2026. The humidity I faced after stepping out of the airport took me by surprise because it was even warmer there than it was in India. After unsuccessfully looking for a Grab ride that I had booked for about thirty minutes or so, I finally got one whose driver did a great job crossing over the language barrier and explaining where to find them amidst a rather crowded station of rides available for hire and buses that went into the city.

I connected with Samyak while I started off on the road at around 0230pm Indochina Time to instruct him about Airport Gate #4, where he could avail himself of a Grab ride, and that way he could avoid wasting that thirty minutes like I did. While connecting with my family during the Grab ride, I also commended the driver for just how clear they were with their communication while making the best utilization of the Grab application's live message translation feature for international travellers. I did not realize how swiftly I managed to reach the hotel at about 0315pm Indochina Time after all the immigration and cabbing troubles. Thankfully, the folks at the Lumen Bangkok Udomsuk Station gave me no trouble with the booking, and I was able to check into my room #703 rather swiftly. In contrast to the experience that I thought I would have, they also topped off their welcoming gesture with a cool popsicle-like snack as I headed downstairs to fetch the passport that I had left at the reception. With one less thing to worry about, Samyak and I still had to make it to the BTS Chit Lom station by 0430pm Indochina Time to meet up and join the FOSSAsia Community Cycling trip.

As Samyak touched down at around 0230pm Indochina Time, I had to proceed by myself to meet up with Mishari Muqbil after a quick changeover in my hotel room. After a brief struggle with finding an ATM and then losing about 250 Thai Baht for the international conversion, I made it back to the BTS Udomsuk station, which only accepted cash (and did not even provide receipts to track expenses!) but was thankfully situated right in front of my hotel. It took me thirty minutes to make it to the BTS Chit Lom station at around 0415pm Indochina Time, but I had to spend the remaining thirty minutes chasing Mishari's waypoint on Google Maps. As I flew in my bicycle helmet all the way from Pune, I had no plans of skipping the FOSSAsia Community Cycling Trip, and while it was my first time visiting Thailand, I did find myself audaciously picking trains and walking through as if I was exploring my backyard. I think I might have to credit the hotel reception and the BTS security for their welcoming behaviour, which made me want to leave the hotel room right after arrival because I genuinely wanted to experience more of what Bangkok had to offer, even when I was dead tired from the travels.

I was finally able to make it to the river jetty, where I met up with Mishari, Michael Christen, Anuvrat Parashar, Shivani Parashar, and others. The adventurous ordeal of catching up with them was rewarded with a scenic boat ride to the starting point of the FOSSAsia Community Cycling Trip. I managed to learn more about what Michael does with his work on YaCy and shared what I do as a part of the Fedora Council, the Fedora Mindshare, and the Fedora Infrastructure teams in the Fedora Project community activities. There were folks there for the first time like myself, and there were also those who had attended FOSSAsia since its beginning, so it was enlightening to know their experiences from this conference. During a brisk walk-and-talk with Anuvrat and other participants to the starting point of the cycling trip, I got to know about his frequent involvement in the PyCon organization and DGPLUG communities. Once we were joined by a couple of Mishari's friends and Wendy Ha, we began unlocking the rental bicycles using our HelloRide application, and Mishari gave us a quick orientation about street safety regulations at around 0530pm Indochina Time.

And there began our slow-paced ride through the alleys and streets of Bangkok! With Mishari and his friends leading our collective, I found myself at the start of our sequence, discussing with Bee about his involvement in technology. As a proving ground for their cartographic skills, we wove through a lot of parks, and I noticed a great number of cats along the various pathways we took. Since the cycling trip did not have many elevation changes to deal with, I took the liberty of falling behind in the sequence to chat with the likes of Wendy and Michael every now and then. At around 0630pm Indochina Time, we made our first stop at an independent family-owned chocolate store where we sampled many chocolates and purchased some beverages too. We were able to keep our rental bicycles safe using Mishari's (as Shivani hilariously named) "CYCLE-ogical protection," which mostly consisted of a loosely placed rope. This first stop also allowed Samyak to finally catch up with our collective, as I discovered him coincidentally heading in the opposite direction when we were on our way out. Tracking his location over WhatsApp's location sharing definitely seems to have been the right choice.

It was rather funny to finally catch up with Samyak on a random Bangkok evening street after having missed the chance at the airport and at the hotel. Our collective made the next stop at another independent family-owned ice cream parlour located in a deep alleyway at around 0700pm Indochina Time. While the location was tucked away in a seemingly long-forgotten corner of Bangkok, the place definitely had a very home-like feeling to it. We, of course, got busy sampling undiscovered flavours and ordering favourite ones for the break. After spending another thirty minutes there with my Butterfly Pea cold cone (and some obligatory badly written jokes by Mishari), we had a bunch of photographs clicked. Once we departed from the ice cream parlour, we found ourselves pausing every now and then due to certain cartographically inclined confusions, but our "vibe-riding" (as I hilariously named our fun experience) never had a dull moment. Through the riverside pathways to a restricted university, we seemed to be in the front seat of exploring what stories these streets and alleys of Bangkok had to offer—and as tired as I was, it still felt like we were just getting started and there was more to discover!

While we did have a bunch of registrations for the FOSSAsia community cycling trip, we barely had half of them turn up, so Mishari decided that it would be best if we found ourselves a dining place. After he quickly helped Samyak with his bicycle height, we caught up with the remaining group for yet another round of photographs - this time in front of a Bumblebee statue at a cross-section, if you can believe it. We also halted in front of the Royal Palace for a quick shoot before inching closer to the nearest drop-off point for the HelloRide rental bicycle center. Thankfully, I was able to take Bee's sweet custom ride for a quick spin before leaving, as it was filled to the brim with all the bells and whistles for an exhilarating street cycling experience. With about 80 Thai Baht spent for the HelloRide trip, some of us made it to the KemKon Vegan Experience Restaurant. As both Samyak and I had skipped lunch and exerted ourselves since the morning, we were starving. I was glad to note that while the menu was completely vegan, I still ended up liking the Make-believe Fried Fish Fritters that I had ordered for myself, both for the delicious taste and the quick service.

Apart from the nutritional values, of course, it was astonishing to notice just how close the vegan dish ended up tasting like a non-vegetarian one. Adding some spicy chili-flavoured oil on top of it all made it taste like heaven, and I could not see a better way to end the night than with this amazing meal. After clearing our bills, Shivani and Anuvrat stayed back at the market to explore some more, while Samyak, Mishari, and I headed back to the main road to catch a Grab ride to the hotel. It was magical just how we felt at home connecting with folks from various free and open-source software communities, all while doing activities like riding bicycles or sharing meals. The two of us were soon back in our hotel rooms, and apart from one misadventure of requiring the hotel staff's assistance to unlock the heavily jammed bathroom door, our arrival in Bangkok was super awesome. After a quick message to Julia Bley to inform her about our safe arrival at the conference and to conclude our saga of troubled travels, I called it a day at around 1130pm Indochina Time. There was so much to look forward to at the Community Day in FOSSAsia 2026, and I wanted to ensure that I was rested enough to experience the same.

Wiki struggling against bot attack

Posted by Fedora Infrastructure Status on 2026-04-17 15:00:00 UTC

The Fedora wiki is under very heavy load due to a large number of requests from bots.

  • Wiki services

Community Update – Week 16

Posted by Fedora Community Blog on 2026-04-17 10:00:00 UTC

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: 13 – 17 Apr 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

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

  • Producing release candidates for Fedora 44 Final release.
  • F44 GO/NO-GO meeting is tentatively scheduled for Thursday, April 16th.
  • Some work related to the migration to Forgejo..
  • OpenH264 RPMs are now published for F44 and Rawhide (F45).
  • Otherwise business as usual operations.

RISC-V

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

  • F44 rebuild in full swing:
    • GCC 16 builds slowed down some progress, but a workaround version was used to compensate.
    • The diff with F43 is about 1K packages
  • Discussed setting up Pungi for “compose’ artifacts (installation & kickstart trees, ISOs, etc)
  • RISC-V “omni kernels” (formerly “unified kernel”)
    • kernel 7.0 is in the mainline repository and work is proceeding normally (Jason)
    • A new f44-omni tag and target will be in Koji to support a single omni kernel.

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.

Forgejo

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

EPEL

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

  • Routine packaging work, including backporting multiple CVE fixes to tinyproxy and python-cbor2.  Also filed eight FTI (fail-to-install) bugs and updated three packages.
  • Refinement work on EPEL minor EOL SOP, which will be used next month when EPEL 10.1 reaches EOL.
  • Continued collaboration with RHEL Lightspeed team on goose packaging work.

UX

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

  • Emma was on the Fedora Podcast with Justin to talk about Flock 2026 and the branding! [Youtube link]
  • Continuing working with contributor on poster about getting involved with Fedora community [Ticket link]
  • Some progress on Flock designs [Ticket link]

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 16 appeared first on Fedora Community Blog.

Browser wars

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Browser wars


brown fox on snow field

Photo source: Ray Hennessy (@rayhennessy) | Unsplash


Last week in Rijeka we held Science festival 2015. This is the (hopefully not unlucky) 13th instance of the festival that started in 2003. Popular science events were organized in 18 cities in Croatia.

I was invited to give a popular lecture at the University departments open day, which is a part of the festival. This is the second time in a row that I got invited to give popular lecture at the open day. In 2014 I talked about The Perfect Storm in information technology caused by the fall of economy during 2008-2012 Great Recession and the simultaneous rise of low-cost, high-value open-source solutions. Open source completely changed the landscape of information technology in just a few years.

The follow-up

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

The follow-up


people watching concert

Photo source: Andre Benz (@trapnation) | Unsplash


When Linkin Park released their second album Meteora, they had a quote on their site that went along the lines of

Musicians have their entire lives to come up with a debut album, and only a very short time afterward to release a follow-up.

Open-source magic all around the world

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Open-source magic all around the world


woman blowing sprinkle in her hand

Photo source: Almos Bechtold (@almosbech) | Unsplash


Last week brought us two interesting events related to open-source movement: 2015 Red Hat Summit (June 23-26, Boston, MA) and Skeptics in the pub (June 26, Rijeka, Croatia).

Joys and pains of interdisciplinary research

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Joys and pains of interdisciplinary research


white and black coffee maker

Photo source: Trnava University (@trnavskauni) | Unsplash


In 2012 University of Rijeka became NVIDIA GPU Education Center (back then it was called CUDA Teaching Center). For non-techies: NVIDIA is a company producing graphical processors (GPUs), the computer chips that draw 3D graphics in games and the effects in modern movies. In the last couple of years, NVIDIA and other manufacturers allowed the usage of GPUs for general computations, so one can use them to do really fast multiplication of large matrices, finding paths in graphs, and other mathematical operations.

What is the price of open-source fear, uncertainty, and doubt?

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

What is the price of open-source fear, uncertainty, and doubt?


turned on red open LED signage

Photo source: j (@janicetea) | Unsplash


The Journal of Physical Chemistry Letters (JPCL), published by American Chemical Society, recently put out two Viewpoints discussing open-source software:

  1. Open Source and Open Data Should Be Standard Practices by J. Daniel Gezelter, and
  2. What Is the Price of Open-Source Software? by Anna I. Krylov, John M. Herbert, Filipp Furche, Martin Head-Gordon, Peter J. Knowles, Roland Lindh, Frederick R. Manby, Peter Pulay, Chris-Kriton Skylaris, and Hans-Joachim Werner.

Viewpoints are not detailed reviews of the topic, but instead, present the author's view on the state-of-the-art of a particular field.

The first of two articles stands for open source and open data. The article describes Quantum Chemical Program Exchange (QCPE), which was used in the 1980s and 1990s for the exchange of quantum chemistry codes between researchers and is roughly equivalent to the modern-day GitHub. The second of two articles questions the open-source software development practice, advocating the usage and development of proprietary software. I will dissect and counter some of the key points from the second article below.

On having leverage and using it for pushing open-source software adoption

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

On having leverage and using it for pushing open-source software adoption


Open 24 Hours neon signage

Photo source: Alina Grubnyak (@alinnnaaaa) | Unsplash


Back in late August and early September, I attended 4th CP2K Tutorial organized by CECAM in Zürich. I had the pleasure of meeting Joost VandeVondele's Nanoscale Simulations group at ETHZ and working with them on improving CP2K. It was both fun and productive; we overhauled the wiki homepage and introduced acronyms page, among other things. During a coffee break, there was a discussion on the JPCL viewpoint that speaks against open-source quantum chemistry software, which I countered in the previous blog post.

But there is a story from the workshop which somehow remained untold, and I wanted to tell it at some point. One of the attendants, Valérie Vaissier, told me how she used proprietary quantum chemistry software during her Ph.D.; if I recall correctly, it was Gaussian. Eventually, she decided to learn CP2K and made the switch. She liked CP2K better than the proprietary software package because it is available free of charge, the reported bugs get fixed quicker, and the group of developers behind it is very enthusiastic about their work and open to outsiders who want to join the development.

AMD and the open-source community are writing history

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

AMD and the open-source community are writing history


a close up of a cpu chip on top of a motherboard

Photo source: Andrew Dawes (@andrewdawes) | Unsplash


Over the last few years, AMD has slowly been walking the path towards having fully open source drivers on Linux. AMD did not walk alone, they got help from Red Hat, SUSE, and probably others. Phoronix also mentions PathScale, but I have been told on Freenode channel #radeon this is not the case and found no trace of their involvement.

AMD finally publically unveiled the GPUOpen initiative on the 15th of December 2015. The story was covered on AnandTech, Maximum PC, Ars Technica, Softpedia, and others. For the open-source community that follows the development of Linux graphics and computing stack, this announcement comes as hardly surprising: Alex Deucher and Jammy Zhou presented plans regarding amdgpu on XDC2015 in September 2015. Regardless, public announcement in mainstream media proves that AMD is serious about GPUOpen.

I believe GPUOpen is the best chance we will get in this decade to open up the driver and software stacks in the graphics and computing industry. I will outline the reasons for my optimism below. As for the history behind open-source drivers for ATi/AMD GPUs, I suggest the well-written reminiscence on Phoronix.

I am still not buying the new-open-source-friendly-Microsoft narrative

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

I am still not buying the new-open-source-friendly-Microsoft narrative


black framed window

Photo source: Patrick Bellot (@pbellot) | Unsplash


This week Microsoft released Computational Network Toolkit (CNTK) on GitHub, after open sourcing Edge's JavaScript engine last month and a whole bunch of projects before that.

Even though the open sourcing of a bunch of their software is a very nice move from Microsoft, I am still not convinced that they have changed to the core. I am sure there are parts of the company who believe that free and open source is the way to go, but it still looks like a change just on the periphery.

All the projects they have open-sourced so far are not the core of their business. Their latest version of Windows is no more friendly to alternative operating systems than any version of Windows before it, and one could argue it is even less friendly due to more Secure Boot restrictions. Using Office still basically requires you to use Microsoft's formats and, in turn, accept their vendor lock-in.

Put simply, I think all the projects Microsoft has opened up so far are a nice start, but they still have a long way to go to gain respect from the open-source community. What follows are three steps Microsoft could take in that direction.

Free to know: Open access and open source

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Free to know: Open access and open source


yellow and black come in we're open sign

Photo source: Álvaro Serrano (@alvaroserrano) | Unsplash


!!! info Reposted from Free to Know: Open access & open source, originally posted by STEMI education on Medium.

Q&A with Vedran Miletić

In June 2014, Elon Musk opened up all Tesla patents. In a blog post announcing this, he wrote that patents "serve merely to stifle progress, entrench the positions of giant corporations and enrich those in the legal profession, rather than the actual inventors." In other words, he joined those who believe that free knowledge is the prerequisite for a great society -- that it is the vibrancy of the educated masses that can make us capable of handling the strange problems our world is made of.

The movements that promote and cultivate this vibrancy are probably most frequently associated with terms "Open access" and "open source". In order to learn more about them, we Q&A-ed Vedran Miletić, the Rocker of Science -- researcher, developer and teacher, currently working in computational chemistry, and a free and open source software contributor and activist. You can read more of his thoughts on free software and related themes on his great blog, Nudged Elastic Band. We hope you will join him, us, and Elon Musk in promoting free knowledge, cooperation and education.

The academic and the free software community ideals

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

The academic and the free software community ideals


book lot on black wooden shelf

Photo source: Giammarco Boscaro (@giamboscaro) | Unsplash


Today I vaguely remembered there was one occasion in 2006 or 2007 when some guy from the academia doing something with Java and Unicode posted on some mailing list related to the free and open-source software about a tool he was developing. What made it interesting was that the tool was open source, and he filed a patent on the algorithm.

Celebrating Graphics and Compute Freedom Day

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Celebrating Graphics and Compute Freedom Day


stack of white and brown ceramic plates

Photo source: Elena Mozhvilo (@miracleday) | Unsplash


Hobbyists, activists, geeks, designers, engineers, etc have always tinkered with technologies for their purposes (in early personal computing, for example). And social activists have long advocated the power of giving tools to people. An open hardware movement driven by these restless innovators is creating ingenious versions of all sorts of technologies, and freely sharing the know-how through the Internet and more recently through social media. Open-source software and more recently hardware is also encroaching upon centers of manufacturing and can empower serious business opportunities and projects.

The free software movement is cited as both an inspiration and a model for open hardware. Free software practices have transformed our culture by making it easier for people to become involved in producing things from magazines to music, movies to games, communities to services. With advances in digital fabrication making it easier to manipulate materials, some now anticipate an analogous opening up of manufacturing to mass participation.

Enabling HTTP/2, HTTPS, and going HTTPS-only on inf2

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Enabling HTTP/2, HTTPS, and going HTTPS-only on inf2


an old padlock on a wooden door

Photo source: Arkadiusz Gąsiorowski (@ambuscade) | Unsplash


Inf2 is a web server at University of Rijeka Department of Informatics, hosting Sphinx-produced static HTML course materials (mirrored elsewhere), some big files, a WordPress instance (archived elsewhere), and an internal instance of Moodle.

HTTPS was enabled on inf2 for a long time, albeit using a self-signed certificate. However, with Let's Encrpyt coming into public beta, we decided to join the movement to HTTPS.

Why we use reStructuredText and Sphinx static site generator for maintaining teaching materials

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Why we use reStructuredText and Sphinx static site generator for maintaining teaching materials


open book lot

Photo source: Patrick Tomasso (@impatrickt) | Unsplash


Yesterday I was asked by Edvin Močibob, a friend and a former student teaching assistant of mine, the following question:

You seem to be using Sphinx for your teaching materials, right? As far as I can see, it doesn't have an online WYSIWYG editor. I would be interested in comparison of your solution with e.g. MediaWiki.

While the advantages and the disadvantages of static site generators, when compared to content management systems, have been written about and discussed already, I will outline our reasons for the choice of Sphinx below. Many of the points have probably already been presented elsewhere.

Fly away, little bird

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Fly away, little bird


macro-photography blue, brown, and white sparrow on branch

Photo source: Vincent van Zalinge (@vincentvanzalinge) | Unsplash


The last day of July happened to be the day that Domagoj Margan, a former student teaching assistant and a great friend of mine, set up his own DigitalOcean droplet running a web server and serving his professional website on his own domain domargan.net. For a few years, I was helping him by providing space on the server I owned and maintained, and I was always glad to do so. Let me explain why.

Mirroring free and open-source software matters

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Mirroring free and open-source software matters


gold and silver steel wall decor

Photo source: Tuva Mathilde Løland (@tuvaloland) | Unsplash


Post theme song: Mirror mirror by Blind Guardian

A mirror is a local copy of a website that's used to speed up access for the users residing in the area geographically close to it and reduce the load on the original website. Content distribution networks (CDNs), which are a newer concept and perhaps more familiar to younger readers, serve the same purpose, but do it in a way that's transparent to the user; when using a mirror, the user will see explicitly which mirror is being used because the domain will be different from the original website, while, in case of CDNs, the domain will remain the same, and the DNS resolution (which is invisible to the user) will select a different server.

Free and open-source software was distributed via (FTP) mirrors, usually residing in the universities, basically since its inception. The story of Linux mentions a directory on ftp.funet.fi (FUNET is the Finnish University and Research Network) where Linus Torvalds uploaded the sources, which was soon after mirrored by Ted Ts'o on MIT's FTP server. The GNU Project's history contains an analogous process of making local copies of the software for faster downloading, which was especially important in the times of pre-broadband Internet, and it continues today.

Markdown vs reStructuredText for teaching materials

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Markdown vs reStructuredText for teaching materials


blue wooden door surrounded by book covered wall

Photo source: Eugenio Mazzone (@eugi1492) | Unsplash


Back in summer 2017. I wrote an article explaining why we used Sphinx and reStructuredText to produce teaching materials and not a wiki. In addition to recommending Sphinx as the solution to use, it was general praise for generating static HTML files from Markdown or reStructuredText.

This summer I made the conversion of teaching materials from reStructuredText to Markdown. Unfortunately, the automated conversion using Pandoc didn't quite produce the result I wanted so I ended up cooking my own Python script that converted the specific dialect of reStructuredText that was used for writing the contents of the group website and fixing a myriad of inconsistencies in the writing style that accumulated over the years.

Don't use RAR

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Don't use RAR


a large white tank

Photo source: Tim Mossholder (@ctimmossholder) | Unsplash


I sometimes joke with my TA Milan Petrović that his usage of RAR does not imply that he will be driving a rari. After all, he is not Devito rapping^Wsinging Uh 😤. Jokes aside, if you search for "should I use RAR" or a similar phrase on your favorite search engine, you'll see articles like 2007 Don't Use ZIP, Use RAR and 2011 Why RAR Is Better Than ZIP & The Best RAR Software Available.

Should I do a Ph.D.?

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Should I do a Ph.D.?


a bike is parked in front of a building

Photo source: Santeri Liukkonen (@iamsanteri) | Unsplash


Tough question, and the one that has been asked and answered over and over. The simplest answer is, of course, it depends on many factors.

As I started blogging at the end of my journey as a doctoral student, the topic of how I selected the field and ultimately decided to enroll in the postgraduate studies never really came up. In the following paragraphs, I will give a personal perspective on my Ph.D. endeavor. Just like other perspectives from doctors of not that kind, it is specific to the person in the situation, but parts of it might apply more broadly.

Alumni Meeting 2023 at HITS and the reminiscence of the postdoc years

Posted by Vedran Miletić on 2026-04-17 08:00:21 UTC

Alumni Meeting 2023 at HITS and the reminiscence of the postdoc years


a fountain in the middle of a town square

Photo source: Jahanzeb Ahsan (@jahan_photobox) | Unsplash


This month we had Alumni Meeting 2023 at the Heidelberg Institute for Theoretical Studies, or HITS for short. I was very glad to attend this whole-day event and reconnect with my former colleagues as well as researchers currently working in the area of computational biochemistry at HITS. After all, this is the place and the institution where I worked for more than half of my time as a postdoc, where I started regularly contributing code to GROMACS molecular dynamics simulator, and published some of my best papers.