On 2/4/23 07:08, Robert Schweikert wrote:
A naming discussion, how fun
On 2/3/23 14:25, Carlos E. R. wrote:
On 2023-02-03 19:17, Jacob Michalskie wrote:
On Fr, Feb 3 2023 at 09:22:16 -0600, Larry Finger Larry.Finger@lwfinger.net wrote:
I hate that we jump around in naming the stable releases, but if Leap has to go, then a the name of a small mountain chain such as Hartz is a lot better than Grassy Knoll for the reasons stated in other responses. Choosing a German name makes sense for openSUSE.
As far as I understand this is more or less seen as a leaplacement :D for Leap, so I would hope it would inherit Leap name as well, don't give up on it yet, that's what happened with previous projects like Step.
No, if it is based on Alp, it is not "Leap".
Why not? "Leap" was created when we started consuming more packages from the enterprise build of SUSE. That concept still applies with the work that was done here. Whether that enterprise build is called SLE, timbuktu, or ALP should not matter.
So While I agree with you and LCP, for me this somewhat depends. For example if we are unable to provide Gnome or KDE with this model I might feel uncomfortable calling it Leap. Technically so far I don't see a reason why we couldn't have Gnome and KDE. However what we are doing here is significantly enough different from what SUSE is doing that I have no idea what buy in and how much involvement we will get from SUSE (Beyond providing 4 engineers a hackweek to get a prototype up and running).
Unlike current Leap where we can basically take SLED and have complete Gnome support out of the box the model we worked on including our Gnome livecd is completely different from what SUSE is planning with its ALP desktop. This combined with the fact we currently have an approximate 2000 package set to work with rather then 10,000 i'm sure this will grow as language stacks turn up.
What all this means is with just a few volunteers we can probably support the smaller desktops and a few other usecases. My needs are pretty straight forward, from this work its pretty clear that I could make and maintain something that meets my needs and gives other people a base to work off. If we are going to reach close to feature parity with Leap it'll take alot of extra help from the community and maybe we won't know if that level of help and support is there until people get a chance to provide it which is why I haven't just started calling it Leap 16 which if we get the community support would probably be a sensible name but if not probably isn't and maybe retiring it or using it for the open version of SUSE:ALP's next desktop is a better idea.