On 5/8/23 18:28, Richard Brown wrote:
On 2023-05-05 14:44, Lubos Kocman via openSUSE Factory wrote:
I understand the situation changed (desktop etc) but my POV doesn't change as I know we can rely on our existing "Leap crew", including Marcus, Max, Fabian, Oliver, Santi, Jose, Martin, Jacob, Mauricio, Simon, Bernhard, Georg, Christian, Frank, Lukas, Guillaume, Sarah, Dirk, $YOU,... I can't even recall how many dozens of recognitions I sent for 15.3, 15.4 :) People like to jump on board and help where they can once the foundation is set.
The biggest problem I see right now is that of your existing "Leap crew" of 19 names, at most we can say 5 of them have responded to show any interest in this new distribution - Yourself, Marcus, Max, Maurizio and Simon.
In addition we currently have 5 new names who've so far stepped up
But of those 5 new names, 2 of them have no packaging/distro building experience and will need extra mentoring to get there.
And so, as it stands at time of writing, we currently have, at best, half the people willing to take a shot at solving all the problems we'll need to face building against this new codebase.
and facing this very small team, we have a challenge far bigger than just building another Leap version, because this will be a brand new Product, build and bootstrapped from scratch, based on a brand new codebase which has only recently been built and bootstrapped from scratch.
One of the things I found in the setup I did is there wasn't actually much "Bootstrapping" required, just by inheriting the "SUSE:ALP" Repo all the really hard work is done atleast from a bootstrapping packages perspective Things like openQA will obviously take more. The fact it is a new codebase and is so close to current Tumbleweed is also a big advantage over the work required for current Leap 15.4/5 because you can currently take a package from tumbleweed and be reasonably certain it'll build and function.
This tiny team might be enough, but I think it's also reasonable to ask whether or not we instead attempt something a little less ambitious and a little more focused given the scale of interest people are demonstrating towards this effort.
My view is I'd rather we try something small, and scale it up based on contributions, rather than try something huge (and a Leap-a-like is huge), burn out a dozen contributors in the process and be able to produce less as Project for quite a long while as a result.
This is probably a sensible starting point, if we start out with something smallish the community can then add what they'd like on top and then in a few months we will actually start to have a good measure of what the community involvement will look like. I suspect once we get to a point where people start to see they have everything they need except for package X and Y they'll probably start to contribute them. As a suggested starting point https://build.opensuse.org/project/show/home:simotek:GrassyKnoll:Backports has 392 package and hasn't been touched in 3 months, of those packages 4 are failing 8 are unresolvable and 6 are broken. But the IBS version of SUSE:ALP might also have other packages that have changed so trying to get these packages building against the SUSE:ALP from IBS would probably be a good start.
In the next few days I'll be reaching out to the fewer-than-a-dozen who've volunteered and try and find a way to get us to all talk together about figuring out what the best next steps are.
I'll be traveling from the end of the week but hopefully that means that some of us can chat in person soon. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B