On Di, Mär 22 2022 at 09:51:40 +0000, Lubos Kocman firstname.lastname@example.org wrote:
I think there are in general two problems. We don't have many volunteers for ruby runtime (not sure if it's the code-base or set of technologies).
And then we break systems with current repo enablement, we want to free the forum from half-upgraded Leap/Tumbleweed systems.
That's fairly easy to fix though, don't allow to install the things from default repos with ymp, show an appstream button for desktops and zypper command for everyone who doesn't have a store that handles those links.
I think whoever first announces "This is what I have and it works" and we can see if that would be viable direction wins. I'd love personally if that direction could help us decide what particular devel/home/project to choose. So some sort of stats / thumbs up would be very helpful.
I'd love to see OPI utilization as people generally seem to like it, or at least the people that I regularly speak to.
I don't really see in what way opi is useful within software-o-o. It replaces software-o-o functionality in cli, so it feels like an alternative rather than a thing to integrate within software-o-o.
On the other side, fixing current codebase would help as well as long as we can find active maintainers :-)
What is the guarantee the next stack chosen will be in a better position than the current one? There are plenty of rubists and rails developers in openSUSE, which didn't stop the codebase from becoming stale overtime.
LCP [Sasi] https://lcp.world/