I don’t think there will be changes regarding Tumbleweed and its development. If you are a factory contributor, rpm, OBS should be around the corner and continue to work like they are now.

What’s different from now is Leap, which is based on SLE, would be based on ALP in the future. But looking at the above discussion it looks like oS can build an ALP-based Leap which looks similar to the one we are using? If I didn’t get it wrong, ALP core+community packages=future Leap. RPM and OBS wouldn’t disappear in future Leap either if that’s the way.

Regards,

Charlie

From: Atri Bhattacharya <badshah400@opensuse.org>
Sent: Thursday, April 20, 2023 2:55 AM
To: factory@lists.opensuse.org <factory@lists.opensuse.org>
Subject: Re: openSUSE ALP: Current Status & A Starting Point for Future Discussions

Dear Richard,

On Tue, 2023-04-18 at 17:49 +0200, Richard Brown wrote:
> Hello everyone,
>
> I wanted to write this mail to let everyone know the current status
> of
> SUSE's ALP (Adaptable Linux Platform) efforts and hopefully get the
> ball
> rolling with openSUSE making use of these efforts.

Many thanks for your mail explaining SUSE's approach to ALP and the
consequences thereof for the openSUSE distro and its community at
large.

Over the last year or so, I have followed the discussions around ALP
with great interest and have tried my best to understand, unfortunately
in vain, the concrete ways by which this potential evolution of the
distro would have an impact on me with respect to two of my most basic
use-cases:

* As a user: I buy/have a laptop/desktop, if needed reduce the Windows
   to its deserved 20 GiB disk-space, and install openSUSE on the rest.
   This is sometimes Tumbleweed, sometimes (very rarely these days,
   admittedly) Leap. How would my work-flow in downloading and
   installing the distro — currently involving downloading an iso
   image, dd-ing it to USB stick, booting up, and enjoying YaST's
   installer do its thing — change? For that matter, as a user how will
   this affect my 'zypper this', 'zypper that' (sounds awful, pardon
   me!) habits?
* As a packager, though admittedly not of any core packages, I know
   how to write basic rpm specfiles, am familiar with the OBS branch,
   fix, and submit methods, as well as other related stuff that I have
   learnt over the years (thanks for many gurus in the oS community, of
   course) that allow me to submit packages to Factory/Leap
   occasionally. Never built a flatpak in my life, always felt they
   were some upstream devs' way of getting around downstream distro
   packagers and shipping to users directly. What will I need to learn
   and do so that I can keep contributing packages — in whatever guise
   — when openSUSE ALP starts to take shape? What tooling is there
   currently or will be in the future to help my transition from an rpm
   packager to a flatpak (or related) one? Or, is the idea that every
   oS ALP distro shall come with some upstream Flathub repository
   subscribed to, making distro packaging, at least for non-core
   packages (e.g. some science packages like octave) unnecessary?

Apologies if this may have been made clear somewhere in this list
already previously, but if so please be so kind as to point me towards
it.

Thanks again and best wishes,

--
Atri (@badshah400) Sent from openSUSE Tumbleweed 20230417 on my laptop.