/rss20.xml">

Fedora People

End of OpenID authentication in Fedora Account System

Posted by Fedora Community Blog on 2025-03-20 10:00:00 UTC

On the latest Fedora Infrastructure weekly meeting we decided on a date of OpenID authentication sunset. The date is 20th May 2025.

Why the change?

The OpenID is being replaced by OpenIDConnect (OIDC) in most of the modern web and most of the Fedora infrastructure is already using OIDC as the default authentication method. OIDC offers us better security by handling both authentication and authorization. It also allows us to have more control over services that are using Fedora Account System (FAS) for authentication.

What will change for you?

With the End Of Life of OpenID we will switch to OIDC for everything and no longer support authentication with OpenID. If your web or service is already using OIDC for authentication nothing will change for you. If you are still using OpenID open a ticket on Fedora Infrastructure issue tracker and we will help you with migration to OIDC. For users using FAS as authentication option there should be no change at all.

What will happen now?

We will be reaching to services we identified as using OpenID directly, but as we don’t have control over OpenID authentication we can’t identify everyone.

If you are interested in following this work feel free to watch this ticket.

The post End of OpenID authentication in Fedora Account System appeared first on Fedora Community Blog.

Facilitating decisions is more important than making them

Posted by Ben Cotton on 2025-03-19 12:00:00 UTC

When asked about her leadership philosophy, Cate Huston came up with “My job is to make it easier for people to make good decision.” While that’s a great philosophy for leadership in a company, it’s even more critical in leading an open source community. Even with a “benevolent dictator for life” governance model, communities are largely self-directed. Contributors won’t just do whatever tasks they’re assigned, they’ll do the work that they find interesting.

Self-direction means that people will have different ideas. Sometimes those ideas will be at odds with each other. Sometimes they’ll be mostly complimentary with minor differences. Sometimes they’ll be entirely unrelated and the community will have to figure out which of the ideas to work on first.

You cannot decide on behalf of the community if you want to continue having a community. Your input is probably valuable, but it’s not the only valuable input. Helping the community come to its own decision is how you build a community that wants to stick around.

In chapter four of Program Management for Open Source Projects, I talk about how to guide your community’s decision-making process.

This post’s featured photo by Sophia Kunkel on Unsplash.

The post Facilitating decisions is more important than making them appeared first on Duck Alignment Academy.

How to rebase to Fedora Silverblue 42 Beta

Posted by Fedora Magazine on 2025-03-18 18:00:00 UTC

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

Before attempting an upgrade to the Fedora Linux 42 Beta, apply any pending upgrades.

Updating using terminal

Because the Fedora LInux 42 Beta is not available in GNOME Software, the whole upgrade must be done through a terminal.

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

$ ostree remote refs fedora

You should see the following line in the output:

fedora:fedora/42/x86_64/silverblue

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

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

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

$ sudo ostree admin pin --unpin 2

Next, rebase your system to the Fedora 42 branch.

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

Finally, the last thing to do is restart your computer and boot to Fedora Silverblue 42 Beta.

How to revert

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

$ rpm-ostree rollback

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

Known Issues

FAQ

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

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

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

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

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

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

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

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

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

Introducing the develop branch of the syslog-ng git repo

Posted by Peter Czanik on 2025-03-18 17:46:32 UTC

For many years, the development of syslog-ng happened on the master branch in Git. However, if you follow that branch, you might have noticed that there has not been much activity on it lately. That is because we introduced a new branch in git called “develop”.

https://www.syslog-ng.com/community/b/blog/posts/introducing-the-develop-branch-of-the-syslog-ng-git-repo

syslog-ng logo

Announcing Fedora Linux 42 Beta

Posted by Fedora Magazine on 2025-03-18 14:05:00 UTC

The Fedora Project is pleased to announce the availability of Fedora Linux 42 Beta! We have lots to share with you about our upcoming release of Fedora Linux 42, and we want to give you a sneak preview of what’s in this release in the beta version that is out now.

Get the the pre-release of any of our editions from our project website:

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

Beta Release Highlights

New Edition Alert

KDE Plasma Desktop has been promoted to edition status starting with Fedora Linux 42 Beta! You can expect to continue to enjoy the same level of quality from Fedora KDE Plasma Desktop that you always have. In addition, Fedora KDE Plasma Desktop is now supported on Power Systems (ppc64le). Also the full KDE stack (including KDE PIM) is now available on Power and we have installable live images for OpenPOWER based systems like the Talos Workstation from Raptor Systems.

Fedora COSMIC Spin

We also have a brand new Spin in Fedora Linux 42 Beta – introducing the Fedora COSMIC spin! This new Rust-based desktop environment developed by System76, makers of Pop!_OS. COSMIC has many unique features, such as hybrid per-workspace window/tiling management, window stacks with tabs to switch between windows, and robust customization features that integrate with GTK and (later on) Qt!

Anaconda Changes

Anaconda has some pretty significant changes in Fedora Linux 42 Beta. They have introduced a new Web UI that is now the default for Fedora Workstation. This means that users can enjoy a smooth installation experience, with features such as an installation progress indicator, built in help, configuration review and more. This new feature also includes Wizard which will allow users to skip what they don’t need during installation. 

The Anaconda team has launched a new web UI for partitioning in Fedora Linux 42 Beta. With this new feature, the biggest benefit to Fedora users is the new guided partitioning function. This provides a more powerful automatic partitioning, where the user will select a goal and have additional customizations possible. This change also comes with a new “Reinstall Fedora” option which allows users to easily reinstall their system if something goes wrong. It also adds support for dual-boot installation. Users just need to create some free space and don’t have to understand other details.

Some updates to enjoy in Fedora Linux 42 Beta

This release will include the latest upstream release of python-setuptools. Setuptools is a package development process library designed to facilitate packaging Python projects. It enhances the former Python standard library distutils (distribution utilities).

There is also a DNF5 improvement that includes new logic that will remove expired and obsolete repository keys from the system. This means users can enjoy the automatic management of repository keys during software installation or upgrades.

We are also including the newest version of Ruby with this beta release. Ruby 3.4 is the latest stable version of Ruby. Many new features and improvements are included for the increasingly diverse and expanding demands for Ruby. With this major update from Ruby 3.3 in Fedora Linux 41 to Ruby 3.4 in Fedora Linux 42, Fedora Linux becomes the superior Ruby development platform.

In Fedora Workstation, we have also introduced the SDL3 transition and Wayland-by-default for SDL apps, and included the new GNOME well-being feature.

There are a lot more changes coming in Fedora Linux 42. The above is just a snippet! Please check out the Fedora Linux 42 Change Set page for a complete list of the changes included with this OS release.

Testing needed

As with any beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora Quality team via the test mailing list or in the #quality channel on Fedora Chat. As testing progresses, common issues are tracked in the “Common Issues” category on Ask Fedora.

For tips on reporting a bug effectively, read how to file a bug.

What is the beta release?

A beta release is code-complete and bears a very strong resemblance to the final release. If you take the time to download and try out the beta, you can check and make sure the things that are important to you are working. Every bug you find and report doesn’t just help you, it improves the experience of millions of Fedora Linux users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can. Your feedback improves not only Fedora Linux, but the Linux ecosystem and free software as a whole.


Comments are welcome on discussion.fedoraproject.org. For tech support, please use ask.fedoraproject.org.

Announcing Fedora Asahi Remix 42 Beta

Posted by Fedora Magazine on 2025-03-18 14:03:53 UTC

We are happy to announce the availability of Fedora Asahi Remix 42 Beta. This pre-release will bring the freshly announced Fedora Linux 42 Beta to Apple Silicon Macs. We expect to announce general availability of Fedora Asahi Remix 42 in about a month. This will coincide with the overall Fedora Linux 42 release.

Fedora Asahi Remix is developed in close collaboration with the Fedora Asahi SIG and the Asahi Linux project. Fedora Asahi Remix 42 Beta includes all of the Changes from Fedora Linux 42. One change of note for Apple Silicon Macs is the integration of FEX in Fedora Linux. This provides an easier way to run x86 and x86-64 binaries out of the box via emulation.

You can try out Fedora Asahi Remix 42 Beta today by following our installation guide. Existing systems, running Fedora Asahi Remix 40 or 41, can be updated following the usual Fedora upgrade process. Upgrades via Fedora Workstation’s Software application are unfortunately not supported and DNF’s System Upgrade plugin has to be used.

Since this is a beta release, we expect that you may encounter bugs or missing features. Please report any Remix-specific issues in our tracker. You may also reach out in our Discourse forum or our Matrix room for user support.

What hardware, software, and cloud services do we use?

Posted by Vedran Miletić on 2025-03-17 09:09:09 UTC

What hardware, software, and cloud services do we use?


green and black computer motherboard

Photo source: Patrik Kernstock (@pkernstock) | Unsplash


Our everyday scientific and educational work relies heavily on hardware, software, and, in modern times, cloud services. The equipment that we will mention below is specific to our group; common services used by university and/or faculty employees will not be specifically mentioned here.

Publishing (Material for) MkDocs website to GitHub Pages using custom Actions workflow

Posted by Vedran Miletić on 2025-03-17 09:09:09 UTC

Publishing (Material for) MkDocs website to GitHub Pages using custom Actions workflow


blue and black penguin plush toy

Photo source: Roman Synkevych (@synkevych) | Unsplash


As you can probably see, this website is built using the Material theme for MkDocs, which we have been happily using for over one year after using Sphinx for many years prior to that. GitHub Pages offers built-in support for Jekyll, but not for MkDocs and therefore it requires the manual building and deployment of our website. However, it automates many other things, including HTTPS certificate provisioning on our domain via Let's Encrypt.

There are several somewhat related approaches using GitHub Actions for automating the deployment of MkDocs-generated sites, usually with the Material theme, to GitHub Pages. These guides are not only found on blogs written by enthusiasts; the official Getting started section of the Material for MkDocs documentation describes the usage of GitHub Actions for deployment and provides a generic YAML file for that purpose.

moment of zen

Posted by Frank Ch. Eigler on 2025-03-16 18:51:10 UTC

Fellow human animals, contemplate these two photos. What's going on?

Here's a Tesla, fully self-driving itself on & off of a local highway, working through an intersection, on its way to a friend. The driver hasn't touched the controls since leaving the home driveway. Beneath the car's screen, an ipad mini, streaming a live video of the SpaceX launch of four astronauts to the ISS via Twitter. Since cell phone reception is crappy here, it's using a Starlink mini dish mounted to the ceiling glass of the Tesla to talk to internet satellites and give us an island of wifi.

In other words, an Elon car is driving us, while we are watching an Elon social media video service, with internet traffic coming through Elon satellites, all to watch an Elon rocket go into space. It's Elon all the way down.

Cross-building and cross-testing GROMACS for Windows on Linux with MinGW and Wine

Posted by Vedran Miletić on 2025-03-16 00:00:00 UTC

Cross-building and cross-testing GROMACS for Windows on Linux with MinGW and Wine


opened brown wooden window

Photo source: Katerina (@kat_katerina) | Unsplash


GROMACS 2025.1 (doi:10.5281/zenodo.15006630) bugfix release came out on Tuesday with a few bugfixes. Among them is a fix for energy correction map (CMAP) parsing code, a feature which I introduced in 2025 release in preparation for adding a converted version of Amber ff19SB force field (doi:10.1021/acs.jctc.9b00591) to GROMACS.

The fix for the issue also added several tests to avoid future regressions. I like developing free and open-source software in general and GROMACS in particular; it feels a lot like the postdoc years in Heidelberg again. However, that was not the only change I proposed that got merged for the bugfix release.

Unlocking the Power of GridTracker for Amateur Radio Operators

Posted by Piju 9M2PJU on 2025-03-15 23:14:06 UTC

What is GridTracker?

Originally introduced in February 2018, GridTracker began as a simple tool designed to listen to traffic from WSJT-X and display it on a map. Over the years, it has evolved into a comprehensive and powerful amateur radio tool, extending beyond FT8 to serve a wide range of functions. From live traffic decodes and logbook management to real-time spot reports, weather conditions, and solar activity tracking, GridTracker has become an indispensable asset for radio enthusiasts.

gridtracker-1024x574 Unlocking the Power of GridTracker for Amateur Radio Operators

Features of GridTracker

GridTracker offers a wealth of features that enhance the amateur radio experience. Here are some of its key capabilities:

1. Advanced Mapping & Real-Time Contact Tracking

GridTracker provides highly detailed and customizable maps that allow users to visualize both real-time and historical contacts. It supports multiple overlays, including Greyline, Moon position tracking, award tracking, and reception reports (Spots). Grid and county hunters will appreciate the instant access to detailed location data directly from the map interface.

2. Customizable Alerts

Users can set up personalized audio and visual alerts, ensuring they never miss an important signal, QSO opportunity, or propagation event.

3. Comprehensive Callsign Lookup

GridTracker integrates seamlessly with popular callsign databases, making it easy to retrieve detailed operator information quickly.

4. Call Roster for Live Activity Monitoring

The Call Roster is a table-based view of live activity, allowing users to track ongoing QSOs in a highly customizable format. This feature is particularly useful for award chasers and special event operators, enabling them to initiate contacts with a single click.

5. Seamless Logging Integration

GridTracker works with many popular logging programs and web-based logbook systems, providing up-to-the-minute tracking for awards such as DXCC and Worked All States.

6. Complete DXCC, Country, and Prefix Recognition

Whether you’re chasing DXCC or monitoring global activity, GridTracker offers comprehensive recognition for countries, prefixes, and DXCC entities.

7. Offline Mode for Portable Operations

Field-day, Parks on the Air (POTA), Summits on the Air (SOTA), Islands on the Air (IOTA), or mobile operators will appreciate GridTracker’s 100% offline mode, ensuring uninterrupted functionality even in remote locations.

8. Off-Air Messaging System

GridTracker allows users to send messages to potential QSO partners over the Internet, bridging communication gaps beyond traditional RF propagation.

9. Real-Time Spotting Integration

The software supports real-time spotting for other GridTracker and Log4OM users, enhancing situational awareness for radio operators.

Why Use GridTracker?

GridTracker is more than just a mapping tool—it is an all-in-one amateur radio companion that simplifies QSO tracking, enhances logging capabilities, and provides essential propagation data. Whether you are a DX chaser, an award hunter, or simply looking to optimize your radio experience, GridTracker offers the features and flexibility needed to take your operations to the next level.

Final Thoughts

For amateur radio operators looking for a feature-rich, intuitive, and powerful software tool, GridTracker is a must-have. It enhances the ability to track signals, visualize activity, and manage logbooks efficiently, making it a valuable asset in the modern ham radio landscape.

Visit https://gridtracker.org/

The post Unlocking the Power of GridTracker for Amateur Radio Operators appeared first on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Mid March infra bits 2025

Posted by Kevin Fenzi on 2025-03-15 17:52:50 UTC
Scrye into the crystal ball

AI Scraper scourge

The AI scraper (I can only assume thats what they are) scourge continued, and intensified in the last week. This time they were hitting pagure.io really quite hard. We blocked a bunch of subnets, but it's really hard to block everything without inpacting legit users, and indeed, we hit several cases where we blocked legit users. Quickly reverted, but still troublesome. On thursday and friday it got even worse. I happened to notice that most of the subnets/blocks were from .br (Brazil). So, in desperation, I blocked .br entirely and that brought things back to being more responsive. I know thats not a long term solution, so I will lift that block as soon as I see the traffic diminish (which I would think it would once they realize it's not going to work). We definitely need a better solution here. I want to find the time to look into mod_qos where we could at least make sure important networks aren't blocked and other networks get low priority. I also added a bunch more cpus to the pagure.io vm. That also seemed to help some.

F42 Beta on the way

Fedora 43 Beta is going to be released tuesday! Shaping up to be another great release. Do download and test if you wish.

Datacenter Move

The datacenter move we are going to be doing later this year has moved a bit later in the year. Due to some logistics we are moving to a mid June window from the May window. That does give us a bit more time, but it's still going to be a lot of work in a short window. It's also going to be right after flock. We hope to have access to new hardware in a few weeks here so we can start to install and setup things. The actual 'switcharoo' in June will be over 3 or so days, then fixing anything that was broken by the move and hopefully all set before the F43 Mass rebuild.

comments? additions? reactions?

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

Replacing ls with eza

Posted by Christiano Anderson on 2025-03-15 13:06:11 UTC
Eza is a modern replacement for ls, it’s written in Rust, small, fast and just a single binary. How to replace in Fedora with Fish Shell sudo dnf install eza alias --save ls eza Done!

Reticulum: The Future of Secure and Resilient Networking

Posted by Piju 9M2PJU on 2025-03-14 19:21:46 UTC

In a world where digital communication is often subject to surveillance, censorship, and centralized control, Reticulum stands as a revolutionary solution. Designed as a cryptography-based networking stack, Reticulum empowers individuals and communities to build local and wide-area networks using readily available hardware. Unlike traditional networking technologies, Reticulum operates efficiently even under extreme conditions, such as high latency and ultra-low bandwidth.

Reticulum is more than just a network—it is a tool for creating thousands of independent and autonomous networks that interconnect seamlessly. These networks are designed to function without kill-switches, external control, or centralized oversight, allowing users to communicate freely and securely. Reticulum enables sovereign, censorship-resistant, and decentralized communication, making it a game-changer for those seeking privacy, security, and resilience in their networks.

Unlike conventional network stacks, Reticulum does not rely on the IP protocol or higher layers. However, it can still be encapsulated over IP networks, allowing users to tunnel Reticulum traffic through the Internet or private IP infrastructures when necessary. By eliminating dependencies on traditional networking protocols, Reticulum optimizes performance and security. The stack is built directly on cryptographic principles, ensuring stable and resilient functionality even in trustless and adversarial environments.

One of the most remarkable aspects of Reticulum is its ease of deployment. It requires no kernel modules or special drivers, making it incredibly lightweight and accessible. Running entirely in user space, Reticulum can be installed on virtually any system that supports Python 3, from personal computers and embedded devices to large-scale infrastructure. This versatility ensures that users can establish secure and sovereign communication networks without specialized or expensive hardware.

Reticulum: A New Era of Secure Networking

Reticulum is the cryptography-based networking stack for building local and wide-area networks with readily available hardware. It can operate even with very high latency and extremely low bandwidth. Reticulum allows you to build wide-area networks with off-the-shelf tools, and offers end-to-end encryption and connectivity, initiator anonymity, autoconfiguring cryptographically backed multi-hop transport, efficient addressing, unforgeable delivery acknowledgements and more.

The vision of Reticulum is to allow anyone to be their own network operator, and to make it cheap and easy to cover vast areas with a myriad of independent, inter-connectable and autonomous networks. Reticulum is not one network. It is a tool for building thousands of networks. Networks without kill-switches, surveillance, censorship and control. Networks that can freely interoperate, associate and disassociate with each other, and require no central oversight. Networks for human beings. Networks for the people.

Reticulum is a complete networking stack, and does not rely on IP or higher layers, but it is possible to use IP as the underlying carrier for Reticulum. It is therefore trivial to tunnel Reticulum over the Internet or private IP networks.

Having no dependencies on traditional networking stacks frees up overhead that has been used to implement a networking stack built directly on cryptographic principles, allowing resilience and stable functionality, even in open and trustless networks.

No kernel modules or drivers are required. Reticulum runs completely in userland, and can run on practically any system that runs Python 3.

Reticulum: The Unstoppable, Sovereign Networking Stack

A Vision for Sovereign Communication

Reticulum is more than just a network—it’s a framework for building thousands of independent networks. Unlike traditional systems, Reticulum eliminates the need for central control, allowing anyone to operate their own sovereign communication infrastructure. The key vision behind Reticulum is to empower individuals and communities to create networks that are free from surveillance, censorship, and external control.

With Reticulum, users can establish highly secure communication channels, ensuring that their data remains private and tamper-proof. This is particularly crucial in regions where communication restrictions are imposed, or in emergency scenarios where traditional networks fail.

What Makes Reticulum Different?

While Reticulum serves the same fundamental purpose as other networking stacks—moving data reliably from one point to another—it does so in a completely different way. Here are some notable characteristics that set Reticulum apart:

Privacy & Security by Default

  • Reticulum does not use source addresses in transmitted packets, making it impossible to trace the origin of communication.
  • All encryption keys are ephemeral and provide forward secrecy, ensuring that past communications remain secure even if future keys are compromised.
  • It is impossible to send or receive unencrypted packets within Reticulum, eliminating vulnerabilities associated with unprotected data transmission.

Decentralization & Sovereignty

  • There is no central authority controlling address allocations; users can create addresses as needed.
  • Once an address is generated, it remains globally reachable and portable, meaning it can be moved across different locations in the network while staying accessible.
  • Networks built on Reticulum are self-configuring and resilient, adapting to various communication mediums seamlessly.

Interconnectivity & Versatility

  • Reticulum supports a wide range of communication hardware, including LoRa radios, AX.25 packet radio TNCs, WiFi, Ethernet, serial devices, and even free-space optical links.
  • It allows seamless integration over existing IP networks (TCP/UDP), meaning it can function over wired and wireless infrastructure while maintaining security and decentralization.
  • By combining multiple communication mediums, Reticulum enables the creation of dynamic, self-healing mesh networks that are highly resistant to disruptions.

Supported Hardware & Interfaces

Reticulum is designed to work over virtually any medium that can sustain a half-duplex connection with at least 500 bits per second throughput. Some of the supported hardware and interfaces include:

  • Ethernet and WiFi devices
  • LoRa radios using RNode
  • Packet radio TNCs (AX.25 and KISS-compatible)
  • Any serial-based communication device
  • TCP and UDP over IP networks
  • Custom hardware via standard input/output (stdio) and pipes

For example, a simple Raspberry Pi setup connected to a LoRa radio, a packet radio TNC, and a WiFi network would allow devices on each of these mediums to communicate seamlessly, thanks to Reticulum’s self-configuring architecture.

How to Get Started with Reticulum

Getting started with Reticulum depends on your intended use case. However, installation is straightforward using Python’s package manager:

pip install rns

Once installed, you can start Reticulum manually or set it up as a system service using the rnsd utility. The first time Reticulum runs, it automatically generates a configuration file that helps you connect with local peers and expand the network from there.

For more details, consult the Getting Started Fast section of the Reticulum Manual.

Included Utilities for Network Management

Reticulum comes with several built-in utilities to simplify network setup and maintenance:

  • rnsd – Runs Reticulum as a background service.
  • rnstatus – Displays real-time information about network interfaces.
  • rnpath – Manages and views routing paths.
  • rnprobe – Diagnoses connectivity to specific destinations.
  • rncp – Transfers files securely between nodes.
  • rnx – Executes remote commands over Reticulum networks.

These tools ensure that even networks operating over extremely low-bandwidth mediums, such as LoRa or packet radio, function efficiently and reliably.

Applications Built on Reticulum

Reticulum powers several innovative applications that demonstrate its capabilities:

  • Nomad Network – An off-grid, encrypted, and resilient mesh communication platform.
  • Sideband – A user-friendly graphical messaging app for Linux, Android, and macOS.
  • LXMF – A distributed, delay-tolerant messaging protocol designed for asynchronous communication.

These projects showcase Reticulum’s ability to facilitate secure and decentralized digital interactions without reliance on traditional internet infrastructure.

Performance & Future Development

Reticulum is optimized for a broad range of performance scenarios, with speeds ranging from 150 bits per second to 40 megabits per second across different mediums. While development continues, the focus remains on expanding functionality for low-bandwidth networks, ensuring long-term resilience and adaptability.

Join the Reticulum Community

If you’re interested in exploring Reticulum, the community offers multiple channels for support and discussion:

  • GitHub Discussions
  • Matrix Channel: #reticulum
  • Reticulum Subreddit

Since Reticulum is still in beta, users should be aware of potential bugs or security improvements in future releases. However, its current stability and effectiveness make it a compelling choice for those seeking secure, decentralized communication solutions.

Conclusion

Reticulum represents a paradigm shift in digital communication, offering a powerful, censorship-resistant alternative to traditional networking protocols. Whether you’re building an off-grid messaging system, a disaster-resilient infrastructure, or simply seeking an alternative to centralized networks, Reticulum provides the tools to create truly sovereign and unstoppable communication systems.

Are you ready to take control of your own network? Install Reticulum today and start building the future of decentralized, autonomous communication!

For more info, visit https://github.com/markqvist/Reticulum

The post Reticulum: The Future of Secure and Resilient Networking appeared first on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Infra and RelEng Update – Week 11 2025

Posted by Fedora Community Blog on 2025-03-14 10:00:00 UTC

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

Week: 10 – 14 March 2025

Infrastructure & Release Engineering

The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues

Fedora Infra

CentOS Infra including CentOS CI

Release Engineering

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

If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.

The post Infra and RelEng Update – Week 11 2025 appeared first on Fedora Community Blog.

🛡️ PHP version 8.1.32, 8.2.28, 8.3.19 and 8.4.5

Posted by Remi Collet on 2025-03-14 06:26:00 UTC

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

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

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

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

ℹ️ The packages are available for x86_64 and aarch64.

⚠️ PHP version 8.0 has reached its end of life and is no longer maintained by the PHP project.

These versions are also available as Software Collections in the remi-safe repository.

🛡️ These Versions fix 6 security bugs (CVE-2024-11235, CVE-2025-1217, CVE-2025-1734, CVE-2025-1861, CVE-2025-1736, CVE-2025-1219), so the update is strongly recommended.

Version announcements:

ℹ️ Installation: use the Configuration Wizard and choose your version and installation mode.

Replacement of default PHP by version 8.4 installation (simplest):

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

Parallel installation of version 8.4 as Software Collection

yum install php84

Replacement of default PHP by version 8.3 installation (simplest):

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

Parallel installation of version 8.3 as Software Collection

yum install php83

And soon in the official updates:

⚠️ To be noticed :

  • EL-10 RPMs are built using RHEL-10.0-beta
  • EL-9 RPMs are built using RHEL-9.5
  • EL-8 RPMs are built using RHEL-8.10
  • intl extension now uses libicu74 (version 74.2)
  • mbstring extension (EL builds) now uses oniguruma5php (version 6.9.10, instead of the outdated system library)
  • oci8 extension now uses the RPM of Oracle Instant Client version 23.7 on x86_64 and aarch64
  • a lot of extensions are also available; see the PHP extensions RPM status (from PECL and other sources) page

ℹ️ Information:

Base packages (php)

Software Collections (php83 / php84)

Unleash Sonic Perfection: Configuring PipeWire with an RT Kernel for Low Latency Audio

Posted by Piju 9M2PJU on 2025-03-13 13:22:25 UTC

For audio enthusiasts, musicians, and producers seeking the absolute pinnacle of audio performance on Linux, combining PipeWire with a real-time (RT) kernel is a game-changer. This dynamic duo delivers remarkably low latency, ensuring your audio experience is smooth, responsive, and crystal clear. Let’s dive into a step-by-step guide to unlock this sonic potential.

Why an RT Kernel and PipeWire?

  • RT Kernel: Designed for time-critical applications, an RT kernel minimizes latency by prioritizing real-time tasks, crucial for audio processing.
  • PipeWire: A modern multimedia framework that excels at handling audio and video streams, offering superior performance and flexibility compared to older solutions.

Step-by-Step Guide

1. Verify Your RT Kernel is Running:

Before anything else, confirm your RT kernel is active. Open your terminal and run:

Bash

uname -r

You should see “rt” in the output, indicating a successful installation (e.g., 5.15.0-xanmod1-rt).

2. Install PipeWire and Essential Packages:

Install PipeWire and its necessary components using your distribution’s package manager:

  • Debian/Ubuntu:

Bash

sudo apt install pipewire pipewire-audio-client-libraries pipewire-pulse pipewire-jack wireplumber
  • Fedora:

Bash

sudo dnf install pipewire pipewire-pulseaudio pipewire-jack-audio-connection-kit wireplumber
  • Arch Linux:

Bash

sudo pacman -S pipewire pipewire-pulse pipewire-jack wireplumber

3. Grant Real-Time Privileges:

To allow PipeWire to operate in real-time, configure the audio group:

  • Edit the limits file:

Bash

sudo nano /etc/security/limits.d/99-audio.conf
  • Add these lines:
@audio   -  rtprio     95
@audio   -  memlock    unlimited
  • Add your user to the audio group:

Bash

sudo usermod -aG audio $USER
  • Log out and back in for the changes to apply.

4. Fine-Tune PipeWire Configuration:

  • Create a custom configuration directory:

Bash

mkdir -p ~/.config/pipewire
  • Copy default configurations:

Bash

cp /usr/share/pipewire/pipewire.conf ~/.config/pipewire/
cp /usr/share/pipewire/pipewire-pulse.conf ~/.config/pipewire/
  • Edit ~/.config/pipewire/pipewire.conf:
    • Add desired sample rates to default.clock.allowed-rates (e.g., 44100, 48000, 96000).
    • Set default.clock.quantum to your preferred buffer size (e.g., 256 for low latency).
    • Set default.clock.min-quantum to your minimum buffer size (e.g., 32).

5. Optimize for Low Latency:

  • Create a low-latency configuration file:

Bash

mkdir -p ~/.config/pipewire/pipewire.conf.d
nano ~/.config/pipewire/pipewire.conf.d/99-low-latency.conf
  • Add these settings:
context.properties = {
    default.clock.rate = 48000
    default.clock.quantum = 256
    default.clock.min-quantum = 32
    default.clock.max-quantum = 8192
}

48000 Hz is perfectly adequate, 192000 Hz is generally only relevant in professional audio production or for audiophiles with very high-end equipment. Most people would not be able to tell the difference between the two.

6. Enable Real-Time Priority:

  • Create a real-time priority file.

Bash

mkdir -p ~/.config/pipewire/pipewire.conf.d
nano ~/.config/pipewire/pipewire.conf.d/10-rt-priority.conf
  • Add these setting.
context.modules = [
{   name = libpipewire-module-rt
    args = {
        nice.level = -11
        rt.prio = 88
        rt.time.soft = 200000
        rt.time.hard = 200000
    }
    flags = [ ifexists nofail ]
}
]

7. Restart PipeWire:

Apply the changes by restarting PipeWire:

Bash

systemctl --user restart pipewire pipewire-pulse

8. Verify Low-Latency Operation:

  • Check latency settings:

Bash

pw-top
  • Verify real-time priorities:

Bash

ps -eo pid,cls,pri,cmd | grep pipewire

Troubleshooting:

  • Xruns (audio dropouts): Increase default.clock.quantum.
  • High CPU usage: Use htop to identify problematic processes.
  • CPU frequency scaling: Consider disabling it: sudo cpupower frequency-set -g performance.

Important Notes:

  • Finding the optimal settings requires experimentation based on your hardware.
  • For advanced usage, consider CPU core isolation, and the realtime-privileges package.

By following these steps, you’ll be well on your way to achieving exceptional audio performance with PipeWire and an RT kernel. Happy listening!

The post Unleash Sonic Perfection: Configuring PipeWire with an RT Kernel for Low Latency Audio appeared first on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

The syslog-ng Insider 2025-03: EPEL 10; Elasticsearch; Active Roles

Posted by Peter Czanik on 2025-03-13 07:33:13 UTC

The March syslog-ng newsletter is now on-line:

  • Test syslog-ng on EPEL 10!

  • Collecting Active Roles logs centrally using the syslog-ng Windows Agent

  • syslog-ng OSE 4.8.1 is now in EPEL 10, quick fix for Elasticsearch

It is available at https://www.syslog-ng.com/community/b/blog/posts/the-syslog-ng-insider-2025-03-epel-10-elasticsearch-active-roles

syslog-ng logo

🛡️ PHP version 8.1.31, 8.2.26 and 8.3.14

Posted by Remi Collet on 2024-11-21 08:46:00 UTC

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

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

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

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-important-2-24.pngPHP version 8.0 has reached its end of life and is no longer maintained by the PHP project.

These versions are also available as Software Collections in the remi-safe repository.

security-medium-2-24.pngThese Versions fix 6 security bugs (CVE-2024-11233, CVE-2024-11234, CVE-2024-11236, CVE-2024-8929, CVE-2024-8932), so update is strongly recommended.

Version announcements:

emblem-notice-24.pngInstallation: use the Configuration Wizard and choose your version and installation mode.

Replacement of default PHP by version 8.3 installation (simplest):

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

Parallel installation of version 8.3 as Software Collection

yum install php83

Replacement of default PHP by version 8.2 installation (simplest):

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

Parallel installation of version 8.2 as Software Collection

yum install php82

And soon in the official updates:

emblem-important-2-24.pngTo be noticed :

  • EL-10 RPMs are built using RHEL-10.0-beta
  • EL-9 RPMs are built using RHEL-9.4
  • EL-8 RPMs are built using RHEL-8.10
  • EL-7 repository is closed
  • intl extension now uses libicu74 (version 74.2)
  • mbstring extension (EL builds) now uses oniguruma5php (version 6.9.9, instead of the outdated system library)
  • oci8 extension now uses the RPM of Oracle Instant Client version 23.6 on x86_64, 19.24 on aarch64
  • a lot of extensions are also available, see the PHP extensions RPM status (from PECL and other sources) page

emblem-notice-24.pngInformation:

Base packages (php)

Software Collections (php81 / php82 / php83)

⚙️ PHP version 8.2.27, 8.3.15 and 8.4.2

Posted by Remi Collet on 2024-12-20 05:26:00 UTC

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

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

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

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-notice-24.pngThere is no security fix this month, so no update for version 8.1.31.

emblem-important-2-24.pngPHP version 8.0 has reached its end of life and is no longer maintained by the PHP project.

These versions are also available as Software Collections in the remi-safe repository.

Version announcements:

emblem-notice-24.pngInstallation: use the Configuration Wizard and choose your version and installation mode.

Replacement of default PHP by version 8.4 installation (simplest):

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

Parallel installation of version 8.4 as Software Collection

yum install php84

Replacement of default PHP by version 8.3 installation (simplest):

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

Parallel installation of version 8.3 as Software Collection

yum install php83

Replacement of default PHP by version 8.2 installation (simplest):

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

Parallel installation of version 8.2 as Software Collection

yum install php82

And soon in the official updates:

emblem-important-2-24.pngTo be noticed :

  • EL-10 RPMs are built using RHEL-10.0-beta
  • EL-9 RPMs are built using RHEL-9.5
  • EL-8 RPMs are built using RHEL-8.10
  • intl extension now uses libicu74 (version 74.2)
  • mbstring extension (EL builds) now uses oniguruma5php (version 6.9.9, instead of the outdated system library)
  • oci8 extension now uses the RPM of Oracle Instant Client version 23.6 on x86_64, 19.25 on aarch64
  • a lot of extensions are also available, see the PHP extensions RPM status (from PECL and other sources) page

emblem-notice-24.pngInformation:

Base packages (php)

Software Collections (php81 / php82 / php83)

⚙️ PHP version 8.3.17 and 8.4.4

Posted by Remi Collet on 2025-02-14 06:59:00 UTC

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

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

ℹ️ The packages are available for x86_64 and aarch64.

ℹ️ There is no security fix this month, so no update for version 8.1.31 and version 8.2.27.

⚠️ PHP version 8.0 has reached its end of life and is no longer maintained by the PHP project.

These versions are also available as Software Collections in the remi-safe repository.

Version announcements:

ℹ️ Installation: use the Configuration Wizard and choose your version and installation mode.

Replacement of default PHP by version 8.4 installation (simplest):

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

Parallel installation of version 8.4 as Software Collection

yum install php84

Replacement of default PHP by version 8.3 installation (simplest):

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

Parallel installation of version 8.3 as Software Collection

yum install php83

And soon in the official updates:

⚠️ To be noticed :

  • EL-10 RPMs are built using RHEL-10.0-beta
  • EL-9 RPMs are built using RHEL-9.5
  • EL-8 RPMs are built using RHEL-8.10
  • intl extension now uses libicu74 (version 74.2)
  • mbstring extension (EL builds) now uses oniguruma5php (version 6.9.10, instead of the outdated system library)
  • oci8 extension now uses the RPM of Oracle Instant Client version 23.7 on x86_64, 19.25 on aarch64
  • a lot of extensions are also available, see the PHP extensions RPM status (from PECL and other sources) page

ℹ️ Information:

Base packages (php)

Software Collections (php83 / php84)

Understanding Public NTP Servers: A Vital Tool for Time Synchronization

Posted by Piju 9M2PJU on 2025-03-12 12:17:54 UTC

In the world of networking and communications, precise time synchronization is crucial. Whether it’s ensuring that distributed systems operate in harmony or keeping logs accurate, time synchronization is fundamental. This is where the Network Time Protocol (NTP) comes into play, offering a way to synchronize clocks across computer networks. In this post, we’ll explore the origins and history of NTP, how it works, its practical applications, a list of top public NTP servers, the best NTP server software, and its benefits for amateur radio enthusiasts.

The Origin and History of NTP

NTP was designed by Dr. David L. Mills in 1985, making it one of the oldest Internet protocols still in use today. Developed at the University of Delaware, it was created to address the need for precise timekeeping in early computer networks. Over the decades, NTP has evolved, with various enhancements improving its accuracy, security, and resilience. Today, it is widely used in industries ranging from finance to telecommunications and even space exploration.

How NTP Works

NTP operates using a hierarchical structure, where highly accurate Stratum 1 servers (directly synchronized with atomic clocks or GPS time sources) provide time to Stratum 2 servers, which in turn distribute the time to lower-tier systems. This cascading model ensures minimal load on primary time sources while maintaining high accuracy.

NTP uses the UDP protocol on port 123 to communicate and follows a complex algorithm to measure and correct time discrepancies. It continuously adjusts system clocks by calculating round-trip delays and clock offsets, ensuring highly accurate synchronization over a network. Modern NTP implementations also support security features like NTS (Network Time Security) to prevent tampering and spoofing attacks.

Practical Uses of NTP

NTP serves a critical role in various fields, including:

  • Computer Networks: Synchronizing timestamps in distributed systems to prevent errors in transaction logging and event tracking.
  • Financial Transactions: Ensuring accurate timestamps for stock exchanges, banking operations, and digital payments.
  • Telecommunications: Keeping voice and data networks in sync to prevent latency and synchronization issues.
  • Cybersecurity: Validating cryptographic timestamps to enhance security and integrity.
  • Space and Scientific Research: Ensuring precision timing in astronomical observations and experiments.
  • Amateur Radio: Essential for digital modes, log synchronization, and accurate APRS positioning.

List of Top Public NTP Servers

There are many public NTP servers available for worldwide use. Some of the most reliable include:

  1. pool.ntp.org – A global cluster of NTP servers providing redundancy and availability.
  2. time.google.com – Google’s high-accuracy NTP service.
  3. time.windows.com – Microsoft’s default NTP service.
  4. time.apple.com – Apple’s time synchronization service.
  5. time.nist.gov – The U.S. National Institute of Standards and Technology’s official time server.
  6. ntp.ubuntu.com – Canonical’s NTP server for Ubuntu users.
  7. time.cloudflare.com – Cloudflare’s secure and highly accurate NTP service.
  8. time.macos.apple.com – Apple’s macOS-specific NTP service.

These servers ensure that users worldwide have access to precise and reliable time synchronization.

Best NTP Server Software

For those looking to set up their own NTP servers, here are some of the best available NTP server software solutions:

  1. ntpd (Network Time Protocol Daemon) – The most widely used NTP implementation, included in most Linux and Unix distributions.
  2. Chrony – A lightweight and highly accurate alternative to ntpd, ideal for systems with intermittent network connectivity.
  3. OpenNTPD – A simpler and more secure NTP daemon developed by the OpenBSD project.
  4. Windows Time Service (w32time) – The built-in NTP service for Windows operating systems.
  5. Meinberg NTP – A robust NTP distribution for Windows, based on the original ntpd.
  6. GPSD and NTPsec – Specialized solutions that provide precise time synchronization using GPS time sources.

Each of these options has its own strengths and is suited for different use cases, from enterprise-level deployments to personal and embedded applications.

Why NTP Matters for Amateur Radio

For amateur radio operators, accurate timekeeping is more than just a convenience—it’s a necessity. Here’s why:

1. Digital Modes and Weak Signal Communications

Many modern digital communication modes, such as FT8, JT65, and WSPR, require tight time synchronization. A clock drift of just a few seconds can lead to failed decodes or missed transmissions.

2. Accurate APRS Positioning

The Automatic Packet Reporting System (APRS) relies on timestamps to properly relay position and telemetry data. A misaligned clock can cause packets to be out of sync, leading to errors in location reporting.

3. Logbook Accuracy for Contests and QSOs

In amateur radio contests, accurate timestamps are crucial for log entries. Organizations like the ARRL and CQ Magazine require precise time records to verify QSOs and prevent disputes.

4. Satellite and Moonbounce Communications

When working with satellite communications and Earth-Moon-Earth (EME) contacts, precise timing ensures that transmissions and receptions are correctly aligned for optimal signal propagation.

5. Emergency Communications and Coordination

During emergencies, ARES, RACES, and other ham radio emergency networks rely on accurate logs and coordinated transmissions. A well-synchronized network ensures efficient communication between operators.

Conclusion

Public NTP servers play an essential role in time synchronization for a vast array of applications, including amateur radio. Whether you’re a network administrator, a financial analyst, or a ham radio operator, ensuring precise time synchronization improves reliability, accuracy, and efficiency. Leveraging public NTP services can significantly enhance digital communications, log accuracy, and overall operational effectiveness in the amateur radio world.

If you’re an amateur radio operator, take a moment to configure your system to use a reliable NTP server—you’ll notice the benefits immediately!

References

The post Understanding Public NTP Servers: A Vital Tool for Time Synchronization appeared first on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Helping your project survive the loss of core contributors

Posted by Ben Cotton on 2025-03-12 12:00:00 UTC

Work is not divided evenly across open source projects. A small number of contributors do the majority of the work. Sometimes these people have a formal designation as a core contributor and sometimes they don’t. In either case, they’re clearly load-bearing. But people’s interest in — or capacity to contribute to — a project can vary over time. Even the most committed contributor will need to take a step back sometimes.

So how can you help your project survive when a core member of the team steps away? Research by Olivier Nourry and colleagues offers some insight.

  • Grow the community. It seems obvious, but more contributors means a lower risk that the project dies. The larger the community — in particular, the larger the team of core contributors — the less the project depends on any one person.
  • Be older. Admittedly, there’s not much you can do about this. Still, the longer a project has been around, the more likely it is to survive the loss of a core contributor. My suspicion is that this is related to the previous point: a project that’s been around longer has had more opportunity to grow the community. But there’s also a higher likelihood that someone relies on it, which means they’re more likely to step up if the project is in danger of collapse. This is less likely to be the case for a new project that might be interesting, but isn’t relied upon yet.
  • Be active. “Activity begets activity” is a core idea behind the Flywheel Theory of Community Engagement. It’s not enough to have a lot of people sitting around, they need to be doing something. Nourry et al found that a higher number of commits at the time a core member left the project corresponds to a higher likelihood of survival.

Nourry et al also found that a smaller number of files correlated to survival rate. I didn’t include this in the list above because I’m not entirely sure what to make of it. There’s something to be said for simpler projects being easier to pick up on, but that may or may not be what’s happening here.

Building on what’s in the paper, I have a few extra tidbits.

  • Provide mentoring. Help contributors gain new skills and responsibilities and give them a ladder to climb. Not everyone will climb to the top, but the more rungs that people advance, the more resilient your community will be.
  • Plan for departures. Everyone is going to leave the project one way or another. Have a plan in advance for how to handle it. The mentoring you do will be a big part of that.
  • Foster a culture of documentation. Research by Lin et al found that contributors who primarily focus on documentation stick around for less time than those who primarily focus on code. Unless you want to constantly churn through docs contributors, make documentation everyone’s job. When people do work primarily on documentation, make sure they are recognized and given an incentive to stick around.
  • Encourage maintenance. The same work by Lin et al found that contributors who mostly modify files stick around longer that those who mostly create files. Once a project is beyond the initial phases, the bulk of the work is maintenance. Recognize and reward the maintainers.
  • Be important. The more people who depend on your project, the more likely someone is to step up when needed. Sadly, this happens far less than it should.

No matter what you do, the odds aren’t particularly great. Nourry et al found that nearly 90% of projects lose their core developers at least once, and only 27% of projects that do are able to survive. Despite the long odds, you can take steps to give your project its best chance.

This post’s featured photo by Jan Canty on Unsplash.

The post Helping your project survive the loss of core contributors appeared first on Duck Alignment Academy.

🎲 PHP version 8.3.18RC1 and 8.4.5RC1

Posted by Remi Collet on 2025-02-28 06:03: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 a parallel installation, the perfect solution for such tests, and also as base packages.

RPMs of PHP version 8.4.5RC1 are available

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

RPMs of PHP version 8.3.18RC1 are available

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

ℹ️ The packages are available for x86_64 and aarch64.

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

ℹ️ Installation: follow the wizard instructions.

ℹ️ Announcements:

Parallel installation of version 8.4 as Software Collection:

yum --enablerepo=remi-test install php84

Parallel installation of version 8.3 as Software Collection:

yum --enablerepo=remi-test install php83

Update of system version 8.4:

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

Update of system version 8.3:

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

ℹ️ Notice:

  • version 8.4.4RC2 is in Fedora rawhide for QA
  • EL-10 packages are built using RHEL-10.0-beta and EPEL-10.0
  • EL-9 packages are built using RHEL-9.5
  • EL-8 packages are built using RHEL-8.10
  • oci8 extension uses the RPM of the Oracle Instant Client version 23.7 on x86_64 or 19.25 on 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.3.18 and 8.4.5 are planed for March 13th, in 2 weeks.

Software Collections (php83, php84)

Base packages (php)