Learning Devuan GNU/Linux - Roadmap & Community

#Introduction

Devuan is a living community project — not just a static release. Episode 21 covers Devuan's roadmap and community: the Excalibur 6.1.x point releases, the development of the testing and ceres suites, the development of the installer and init tooling, and the places users and developers gather — the forum, mailing lists, and IRC.

Understanding the roadmap helps you decide which suite to use (episode 4), while getting to know the community gives you a place to ask questions when you hit problems not covered by documentation. Both matter for your long-term growth as a Devuan sysadmin.

#Release Roadmap

#Excalibur Point Releases

After Excalibur 6.0 became stable, development continues through point releases 6.1.x, which bring security updates, bug fixes, and installer refinements. Point releases follow the Debian point release pattern — stable users just run apt full-upgrade to get them:

sudo apt update
sudo apt full-upgrade
apt-cache policy | head

apt-cache policy | head shows the available package versions — after updating, base packages will point to the 6.1.x versions. A point release doesn't change the suite, only refreshes its contents.

#Testing and Ceres

The next release takes shape in two moving suites:

excalibur   - stable, basis Debian Trixie
testing     - menuju rilis berikutnya (Freia)
ceres       - basis Debian Sid, rolling

Freia is the code name for the next candidate release, developed in the testing suite. Ceres keeps receiving Sid packages on a rolling basis. Both play a key role: packages that stabilize in ceres and testing will "become" the next release.

#Tooling Development

#Installer and Init

The Devuan development team keeps improving devuan-installer and init tooling. The main focus: making the init choice during installation work smoothly for sysvinit, OpenRC, and runit; improving hardware detection through eudev; and refining the migration from Debian.

You can contribute without writing code: test the testing and ceres releases, report bugs with detail, and translate documentation. This is the kind of support the project needs most.

For those who want to write code, a beginner-friendly entry point is fixing init scripts — you only need to understand shell scripting and the /etc/init.d/ pattern from episode 5. Other areas like installer documentation and the eudev packages are also open to contribution. Start small, get to know the active maintainers on the mailing list, and follow the contribution guidelines the project publishes.

#Community and Learning Resources

#Official Site and Documentation

Devuan's information hub is devuan.org:

curl -s https://www.devuan.org/ | grep -oiE 'release[^<]{0,40}' | head

curl -s https://www.devuan.org/ fetches the homepage. The get-devuan page handles ISO downloads (episode 0), FAQ covers common questions, and devuan-releases documents each release.

#Forum, Mailing Lists, and IRC

Devuan's main discussion places:

devuan-forums.com  - forum diskusi pengguna
Mailing lists      - diskusi teknis lewat email
IRC #devuan        - obrolan real-time di OFTC

The forum is the best place for "how-to" questions, the mailing lists for development discussions, and IRC for quick responses from active developers.

A common pattern in the community: post your question on the forum with a clear title like "Excalibur 6.1: Wi-Fi not detected after kernel update", then link your diagnostic output. For quick discussion, the IRC channel is active during certain hours of European time. Don't hesitate to join — new users are always welcome.

#The Etiquette of Asking Good Questions

Before asking, do the basic steps: check the documentation, search the forum, and gather diagnostic information like uname -r, the output of service --status-all, and relevant logs. Complete questions get answers faster and help the community stay productive.

A good forum question usually looks like this: state the release version (for example Excalibur 6.1), name the init you use (sysvinit, OpenRC, or runit), include the output of relevant commands, and explain what you've already tried. This narrows down the possible causes dramatically and lets volunteers help immediately instead of asking for the same data repeatedly.

#Using the Community to Learn

#A Continued Learning Plan

With the roadmap and community you now know, put together a continued plan:

dpkg --list | wc -l
ls /etc/init.d/ | wc -l
apt list --upgradable | wc -l

dpkg --list | wc -l tells you how many packages are installed — a picture of your system's size. Use this number to compare your system with other users' on the forum and understand configuration differences. It's also useful when asking about performance problems: a larger system with many extra services will behave differently from a minimal install.

In addition, make it a habit to follow release news and official changelogs. Devuan's roadmap can shift with the community's needs, and what's written in this episode is only a snapshot at the time of writing — always verify current information against the official sources on devuan.org.

#Conclusion

Episode 21 covered Devuan's roadmap and community: the 6.1.x point releases, the testing and ceres development lines with the Freia candidate release, the installer and init tooling focus, and the community channels — forum, mailing lists, and IRC.

Key takeaways:

• Point releases 6.1.x come through a regular apt full-upgrade.
• testing heads toward Freia; ceres mirrors Sid on a rolling basis.
• Developers focus on the installer and init tooling.
• devuan.org is the hub for official news and downloads.
• Forum, mailing lists, and IRC are the main community channels.
• Include complete diagnostic information when asking questions.

In the next episode — episode 22, the last one — we'll cover ecosystem, alternatives, and final reflection: comparing Devuan with Artix, Void, Alpine, and Debian; when to choose each; and a full recap of episodes 0 through 21 plus a production checklist.