I am willing to maintain Yast2 myself

I know Ruby and I am willing to maintain Yast2 myself. How do I volunteer for that?

I simply can’t stand such an useful tool being abandoned.

6 Likes

You should get in touch with the current maintainers - there is a discussion on the factory mailing list (Re: Will YaST be deprecated in Tumbleweed? - openSUSE Factory - openSUSE Mailing Lists) that would be a good place to indicate your interest and get connected to the other person maintaining it.

This would be so great! Thank you.

1 Like

@darkhog Only 246 different modules to look after… should not be too bad…
https://github.com/orgs/yast/repositories?type=all

I believe that all of YAST should not be maintained.

YAST is mostly useful for newbees or for complex tasks that are relatively common but that a user occasionally performs.

A tool like YAST is important, not because of what it does, but because it reassures people who are hesitant to switch to Linux, and helps convince them to migrate, while helping them to get to know this OS.

The aim, of course, is for every new user to eventually be able to do without YAST.

In the “Network services” category, there are 13 modules, but I can’t think of any that would interest a user too unskilled to require YAST.

The “System configuration” category seems to me, containing the most interesting modules :

  1. yast-auth-client Configuration of various authentication methods for system like Kerberos, LDAP or SSSD.
  2. yast-bootloader Bootloader installation and configuration.
  3. yast-country Configuration of localization specific settings like language, keyboard layout, timezone, etc.
  4. yast-firewall Management of SUSE Firewall.
  5. yast-network Configures network devices.
  6. yast-nfs-client Configures mounts NFS directories from NFS servers.
  7. yast-ntp-client Time synchronization over network (NTP).
  8. yast-online-update Updates your SUSE with the latest patches from online repositories.
  9. yast-pam User authentication plug-ins configuration PAM
  10. yast-printer Local and remote printing configuration.
  11. yast-scanner Configures local (SCSI, USB) or network scanners.
    12 yast-security Security settings (password and login settings, kernel options…)
  12. yast-services-manager Configures system services started at boot (systemd services).
  13. yast-snapper Configures snapper (the Btrfs snapshotting tool), can browse snapshots.
  14. yast-sound Configures sound cards (usually needed just in some special cases, autoconfiguration should work out-of-box).
  15. yast-storage-ng Disk and partition management.
  16. yast-sudo Configures the sudo tool (to execute commands as another user or as root).
  17. yast-sysconfig Editor for /etc/sysconfig files.
  18. yast-tune Hardware detection and expert system tuning.
  19. yast-users Tool for managing system users and groups.

Even printers and scanners will became much easier to install and configure, thanks to openprinting.

1 Like

@darkhog So many of those things can be done in Cockpit (and more eg SELinux, File Browser, Terminal…)

My suggestion is you install the rpm version of cockpit and compare, then also the flatpak version (which is what I use) and compare.

If you want to look at YaST Bootloader, then it needs additional work for systemd boot to add options and also update the kernel config (eg pbl --add-option, sdbootutil add-all-kernels` or setting default loader config.

1 Like

I agree - I think we need to move forward, and time and effort can be put into making that as useful as required.

What about AutoYast? Is there a replacement for it ?

Moving this to Open Chat, as not a request for technical support.

1 Like