Learn Void Linux - Roadmap & Community

#Introduction

Before closing this journey in episode 22, let's look ahead. Episode 21 covers the roadmap of Void Linux — where XBPS, runit, and the installer are heading — as well as the community and documentation that will accompany you after this series ends. Learning doesn't stop at the last episode; it actually starts here.

Understanding the development direction helps you judge when a feature arrives in the repository and how to react to changes. Knowing the community helps you find answers when the documentation isn't enough.

Let's look at Void's development direction.

#The Development Roadmap

#XBPS Evolution and runit Integration

XBPS development continues with a focus on precise package management and clean integration with runit. Improvements like better transaction handling, more thorough dependency checks, and broader architecture support are always under observation:

xbps-query -l | grep xbps
xbps-query -p version xbps

The output of xbps-query -p version xbps shows the installed XBPS version. Following XBPS releases gives you a sense of how fast this tooling evolves.

#Kernel and Installer

Void always follows the latest upstream kernel and the LTS kernel. Improvements to the void-installer are also ongoing, especially for new hardware support and the TUI user experience. To follow these changes:

xbps-query -l | grep -E 'linux-(lts|zen|@)'

#Community and Learning Resources

#Official Documentation

The main source for learning Void is the official documentation at docs.voidlinux.org. The handbook there covers installation, XBPS, runit, all the way to xbps-src. Read it directly in your browser or download an offline version:

xdg-open https://docs.voidlinux.org

#Wiki and Forum

Besides the documentation, the community maintains a wiki and a forum. The Void forum is the main place for discussion and questions. Before asking, get into the habit of searching the documentation and forum first — most questions have already been answered.

#IRC and Matrix Channels

For real-time discussion, Void is active on IRC and Matrix. Some relevant channels:

#voidlinux    : general discussion on IRC
#voidlinux-dev: package and template development
Matrix bridge : connects IRC and Matrix

Etiquette in community channels: read the documentation first, ask clearly, and include the relevant command output. This approach will be welcomed much more warmly.

#How to Contribute

#Non-Technical Contributions

Not every contribution has to be code. Things that help a lot:

• Reporting bugs found in the repository.
• Writing and translating documentation.
• Testing packages waiting for review.
• Answering questions from new users on the forum.

#Technical Contributions

For those ready to write package templates, the path was covered in episode 15:

git clone https://github.com/void-linux/void-packages.git
cd void-packages
./xbps-src binary-bootstrap
./xbps-src pkg <package-name>

#Keeping the System Healthy

#Routine Maintenance Habits

As a practical wrap-up for this episode, summarize the habits that keep Void healthy:

sudo xbps-install -Su
sudo xbps-pkgdb -a
sudo sv status /var/service/*

The xbps-pkgdb -a command checks the health of the package database. The combination of regular upgrades, database checks, and service audits is the minimum that keeps the system stable.

#Conclusion

Episode 21 opened a view into Void's future: the evolution of XBPS and runit integration, a kernel policy that always follows upstream, and continuous installer improvements. You also got to know the official documentation, forum, IRC, Matrix, and how to contribute.

Key takeaways:

• XBPS and runit keep evolving with a focus on precision.
• Void always follows the latest kernel and the LTS kernel.
• docs.voidlinux.org is the main learning resource.
• The Void forum and IRC/Matrix channels are active for discussion.
• Contributions aren't always code: report bugs, write documentation, test packages.
• Routine maintenance keeps the system stable.

In the next episode, episode 22, the final episode of this series, we will cover ecosystem, alternatives, and final reflection — comparing Void with Artix, Devuan, Alpine, and Arch, when you should choose Void, plus a recap and production checklist from the entire Learn Void Linux journey.