Hi, please note that this reply is not directly related to the earlier posts but I didn't want to create another thread and I lost track and a few mails in my mailbox to find a better thread. I was silently reading most of the mails but I'm still a bit confused and might not fully get it yet. One thing of the discussion is not that important for me: If we use binary builds or source copies of packages imported from SLE. Yes, there are some challenges to do it right and keep it trustable and look into deeper details of build configurations so they are compatible. But this is just technology and I'm sure a bunch of people will work on that and cover it. My main concern is though and it's not totally new: Is Leap still an openSUSE project afterwards? Or is it SUSE controlled to an extent which does not qualify for the name openSUSE anymore? We (or at least I) always understood that a hybrid distro like Leap will be some sort of compromise. In the 42.x series I was totally happy with the balance between openSUSE <-> SLE. With Leap 15 that was much stricter already. It became much more pain to request a fork or updates if the SLE version was not matching my expecations (as user and community maintainer of some packages). With the last 15.1 cycle it already was a major pain to get things in if a package was inherited from SLE. And now the whole thing seems as if it would be like totally prohibitive in many situations. Yes, I also want a solid base and I also like that SUSE does most of the maintenance work. But there were situations in the past years where for example I as the community maintainer failed to push an upgrade or a fork (I would maintain anyhow) into Leap when the package was based on SLE in the first place. Similar concerns were raised by others in the previous posts and that's why I didn't write something up earlier but it seems the concerns were not taken serious enough. I would have one prominent example about "mercurial". I guess most developers love to have more or less up to date version of their dev tools. This update request was rejected for obscure reasons (no they were not obscure, the reason was "we did not receive any business reasoning for the request"). The upgrade request was moved into an internal product and is now closed to the openSUSE community so I cannot refer to it. And that for a package I maintained for several years. No, I don't have business reasons. I just want to have a (half-way) modern toolchain. If it goes on like this and will be handled even stricter then I have to consider Leap a SUSE-only where the community is just a burden. Good enough to contribute to Factory and Tumbleweed but let your hands off "SUSE products" including Leap or "Jump". Wolfgang -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org