@opensuse Been a user for over a decade now and have faith in your involvement and commitment to #opensource and #community.
Ironically, I used to have the same "faith" in #redhat and their model too 😑 Turned out that corporates are ultimately led by the wills of their shareholders and not the community's and ideologies.
While I do hope you folks stay true to your roots in the face of economic changes, I'd like to ask if you've got any mechanisms/processes that'd prevent a similar scenario?
Fun fact for the young: Yast until 2004 was not Open Source. See: https://social.linux.pizza/@knurd42/110637112365125443
Attached: 1 image Fun fact reg. the "#SUSE has an impressive legacy deeply rooted in the world of #opensource"[1] for those that don't remember: Suse's Yast only became Open Source in 2004; before that the license forbade to use it in other distros. https://www.heise.de/news/YaST-wird-freie-Software-95583.html (German) [1] quote from https://fosstodon.org/@opensuse/110633130799606251
Out of curiosity reg. the "SUSE has an impressive legacy deeply rooted in the world of #opensource":
When did SUSE actually start to publicly publish their SRPMs[1] for Suse Linux Enterprise (both releases and updates)? My leaky and unreliable brain says it was about ~2014, but my googlefoo failed to find a confirmation. They were available in 2015:
https://ohmag.net/opensuse-now-and-the-future-an-interview-with-richard-brown/
[1] or something equivalent that would enable cloners