Fast moving, fresh apps and deprecation dilemma

Okay, I wasn’t sure if I want to respond here, the Deprecation thread, or the Bazaar thread. I don’t think it’s fair to Bazaar’s dev to express what is actually the culmination of my doubts towards Universal Blue there, and this thread’s original post is more forward facing than the Deprecation thread, so I’ll respond here.

I’d like to preface that this… Kinda got more emotional than what I originally planned. But as I think about what I wanted to convey, confusion and skepticism started to dig at “old and recent wounds” as it were. I am very sorry about this, but I’d like to honestly express my doubts here. Regardless, here goes what I originally wrote for the other threads, combined:

I won’t lie, I was and currently still having a knee-jerk, “Oh, great, it’s yet another GTK app that’s going to be forced on me, and watch as Discover gets hidden, and I have to fix that on my builder when I’d rather just use the DE defaults,” reaction towards Bazaar. I would be more excited if it’s something that looks at home on both GNOME and KDE, which would really set it apart from elementary/PopOS’ app store, which is another option as well. Alternatively, if there’s a firm commitment to trying to make it be adopted by Flathub itself- that would be cool and genuinely help enough new users and many Linux users that I can tolerate it.

Mind, it’s not like I can’t see the point made when Bazaar was brought up in that hour-long video. Yes, it uses the “modern design” that a lot of people expect these days (even if a lot of others aren’t big fan of it). Being able to blacklist certain apps would be powerful, if wielded wisely and not in a way that angers people (let’s not forget people still do not like “immutable” OS for “blocking” them from installing packages “the normal way”). Better DE integration (assuming that works on KDE as well) would be great. And of course donation is very important. Speed too, last but not least.

But I’m confused as to why this couldn’t just be done through something that already exists. If the problem is with DE defaults not being satisfactory, I’d be more interested in coordinating a bounty for either good DE defaults or Default Flathub GUI across distro, instead of coming out in favour of yet another shiny but not-yet-mature project. I’m not going to knock on the original dev, for making something cool that is then adopted by a larger project. I’m just questioning how does this make sense for Universal Blue, and its products outside of Bluefin, as well as how this actually fits with what was said in the Deprecation thread:

This outright feels like the opposite of the Project Non-Goals section of the Mission statement. When I read the missions, I felt, “You know what? That’s fair.” I can tolerate the decoupling, deprecation, and reworking of various stuff like Fleek, later Nix as a whole, yafti, and the various existing base images. And I can see how ublue focus on working with upstream, what with bootc and stuff. Ptyxis… Ehh, I can tolerate it, I have a builder anyways, I can restore it back to proper good old Konsole.

But between this, the weird “Ooh shiny”-like behaviour with choosing a Distrobox GUI between BoxBuddy Distroshelf and Kontainer, making an entire new installer- I feel like it’s just a bunch of distractions.

Something that could mitigate it is a real roadmap. I was tolerant of all the recent changes, and even still advocate for people to use Universal Blue as a whole, because I believed in that Mission statement. But lately there’s just so many things taken away, meanwhile random new stuff like Distroshelf and Bazaar are just brought up that is just yet more GTK-ism for KDE user like me, and all the while I just find myself really skeptical as to how this is making this better for everyone- not just Bluefin user, not just Bazzite and Aurora user, and not just Linux users.

Please just give me something rally on. Something that make me feels, “Okay, these are a lot of changes, these are a lot of new things that is pushed to the ecosystem as a whole, that will benefit me and the rest of the ecosystem, and is a major selling point that I can proudly say to other users looking into what Linux ‘distro’ to use.” A blogpost, about all planned changes and why it’ll be much better, or something. Instead of this, “new stuff here, deprecate stuff there, vague statements of intents now and then, oops, deal with it.”

As an example of something that can demonstrate Universal Blue’s capabilities in working with upstream to solve problems for 96% of Linux users (instead of new stuff that’ll benefit the few thousands users of Universal Blue) that I really would like to see is something like being able to solve the WebExtension gridlock, which is a thing that is still causing issue towards people welcoming Flatpak as the new ecosystem.

Unless we’re just going to use Bazaar’s blocking capability to block browser installation too now. Which is an unkind thought from me but it is a thing I thought as I remembered the whole Native Host Messenger saga in the context of Bazaar’s blocking capabilities. At the same time, if Bazaar could redirect and automate setting the “right way, with good user experience, everything working in a way understandable by new users,” a la Zorin’s Windows App Support (which is something that I wish more distro embrace, as it solves a real issue for 96% of new Linux users) then I’m on board with it.

Once again, I apologise for “crashing out” or whatever it is called these days. But I want to pack it all in one reply, so that I can get back to helping new users and promoting ublue as a solution to others, with a clear head and information.

4 Likes

There’s not much I can say on the GNOME apps on KDE thing, I’m the Bluefin guy. But maybe one of them can chime in. Lots of this stuff doesn’t apply to me since I use Bluefin, so I can’t address any of that cross DE/distro stuff.

Yes, I plan to approach GNOME and Flathub with this in order to work on the problem together. I’ve already brought it up to the new GNOME Executive Director, but there’s only so much time in the day. I don’t think you’re going to get firm commitment from any of those orgs, it’s volunteer driven. You can’t ask for commitment from an org we have to earn it, and to earn it we need numbers. So our mission tends to be “get people using flatpaks”.

We’ve made it clear that it’s to avoid footguns, none of us is interested in dealing with moderation. Also we don’t touch the CLI, we don’t take it away.

Those people aren’t our target audience though. We offer a path, the user must choose to learn it.

I consider fixing donations in the app store to be the single most important thing we can help fix right now. We’re trying to fix the economic problem. We’re tightening scope to help fix this.

fleek, nix, and yafti have been gone for so long that I don’t understand why this is even an issue. End users don’t care about base images and there’s plenty of choices for people who want a nix experience - that’s not our thing.

Distroshelf is a better app, does this seriously bother you? We’re the most focused we’ve ever been lol. Look at the contribution metrics I’ve been posting, the team is firing on all cylinders.

It seems to me that your biggest issues are that you don’t like the mixing of GNOME/KDE apps. The person choosing to make the decisions and Aurora and Bazzite make them in the context of Bazzite - when we remove base images we don’t take any of that into account. It’s entirely different people in some cases.

I can’t really answer this other than we’re doing the best we can. Most of the things you mention are nice improvements to me. I love distroshelf, it makes me happy. There’s nothing stopping you from doing any of these things either. There’s not going to be a roadmap for any of this stuff. Here’s our mission statement.

Accelerate operating system development by integrating with the cloud native ecosystem, in order to provide an on-ramp for new open source contributors.

When I go to an open source conference and I meet up with a bunch of surfer kids who want to take a stab at a new installer – that does sound crazy. But then you look at what we had at the time, which I will point out was non-functional. Then you start to spend time with them and as a 20 year veteran of open source, I feel their vibe, I feel their energy. This is a people business - So we take that bet.

When I see some random self taught kid whip up a store that can do a better job than an app that has been around for years, I have no choice but to investigate. Over here in Bluefin land this has probably been one of the top complaints I deal with. This gets me closer to the goal in a really large jump. So yeah, nobrainer bet too.

Everyone’s nitpicking over the design but that’s fine, it’s a css thing we can make it look however we want. We need it so app developers and new contributors can be compensated for their work so that they can build all the stuff you think we should be building. :smiley:

Also if someone wanted an Aurora KDE pure mode just make a custom image - if there is a demand someone will make one.

5 Likes

I’ll just add some comments from Aurora side here.

First, and this is my personal opinion, I don’t really understand the mentality that KDE “can’t have GTK/libadwaita apps”. It seems this seem to, for some specific reason, irk people off. I just think there are great GTK/Gnome apps, and sometimes there is no QT/KDE alternative - so in these cases I don’t see the real issue.

Then the situation where there is both, here we try to prefer the QT versions but sometimes it just isn’t enough. Lets take Boxbuddy/distroshelf vs Kontainer example. Boxbuddy seems to be pretty slow maintenance at the moment, where as Distroshelf is actively maintained and its pretty much 1:1 with BB.

Kontainer is really new, and its missing some stuff and last i checked its going on a refactoring phase at somepoint which should remove some of the issues (there was lot of hardcoded stuff etc). But I am not a software developer so can’t really speak too much into it. Once Kontainer matures, I am totally fine replacing DistroShelf with it.

On the Bazaar front, we haven’t decided anything yet. We will propably ship it alongside Discover for sometime to get some feedback. If people hate it, then its going to go away but this also depends on how Discover develops, currently it has few of the same issues that GnomeSoftware has. It tends to be slow, the UI is (atleast to me) pretty mediocre. Atleast Plasma 6.4 removes some of the issues we have reported upstream.

Don’t really see the issue with the installer. Currently we are still using the Anaconda installer, we just made it as LiveCD, which has been requested (not just from us, but also from upstream - to have a live environment, not just a straight to installer boot ISO). With F43 we hope that the new webui comes to the atomic editions. Currently for Aurora the issue is the keyboard layout selection that doesn’t work with KDE (as its hard coded to Gnome-settings) but there is already newer versions that have that removed, so we are hopefull that we will get a working version for KDE even before F43.

1 Like

Maybe it’s just a presentation mismatch, but I’ve always seen you more as the Universal Blue guy. Especially if it’s in General space, instead of Bluefin banner or the title clearly talking about Bluefin specifically.

Where you say we go, the ublue ship will sail to.

I meant commitment from you and ublue. Maybe it’s just miscommunication, but I’m still not 100% sure if Bazaar is being looked at by you as a candidate for “this, this can be the Flathub GUI app, we are locking commitment into getting this to be the one that Flathub will officially offer - should they eventually be willing to offer an official GUI.”

I can get behind the dream that eventually SteamOS and Ubuntu (and their derivatives) can open Flathub, click install, and eventually getting Bazaar - if it doesn’t just come by default. That’s a great dream, one that I can see fitting for ublue to push forward, and willing to compromise my sensibilities for because I’m not about to get so selfish as prevent the newcomers from experiencing a proper unified Linux app store.

I know that, but what I meant to say there is that the design and communication with the blocking has to be properly thought through.

There are proper reasons as to why Ubuntu links their apt install firefox and snap install firefox together - it is also very badly communicated from an end-consumer user-experience perspective that all anyone can see is “Ubuntu blocks classic Firefox apt install in favor of their proprietary store.” A single poorly thought UX when an app is “blocked” and an entire conspiracy theory sprung.

You may think I’m grasping straws, but you know what Linux user is like. Regardless, that’s why I combined that thought in a single paragraph of how I think Bazaar might work well if it is done properly.

I think that’s great! It’s just that it wasn’t quite upfront as to why does Bazaar have to be the answer, instead of either the elementary/PopOS app, or outright working with DE to implement it on their own GUI app installer. Yes, the ability to go to GNOME Overview, search app name, and clicking on it quickly takes you to the app to install it is cool. But it could also be done natively with GNOME Software with some improvements.

(And kind of just irrelevant to how a lot of the “96%” non-Linux users get their apps, which is by opening Chrome and typing “install x app”, so while it is a neat ability, I don’t see what’s so cool about it as it feels more like solving a “0.4%” users’ issue)

In any case, if the problem is “Donation needs to be fixed” and the answer is “Donation/purchasing in Bazaar will Just Work and we will strive to get it adopted by Flathub as the one true official GUI app so that it will fix it for almost every Linux OS,” then sure, I can get behind that. It’s just wasn’t clear to me that that’s what is happening here.

It is more of an example as to things that’s been adopted into Universal Blue, and then deprecated (Nix is more of a recent thing though, with the composefs issue being the one that made it clear to users). I still miss them, but at the same time, I accepted it because the Mission says “we front load saying no,” along with the rest of the things Project Non-goals section says. Imagine me, accepting but still missing them, as well as still being wary from Bluefin LTS, ucore, and several base-image deprecation… only for things to turn around and adopt some very new untested not-even-two-months-old project that looks like GNOME Software, and with the way this is also in General (and how Bazzite went and pushed Ptyxis on me anyways), feels like “I found this cool new project and I’m going to push it on everyone even if I don’t know if it’s still going to be alive next year.”

I guess what I’m saying is that it is poorly communicated that I don’t know what the intent is, I don’t know if I can trust it, and at the same time it reminds me of old and recent wounds.

I am bothered by changes. I’m not expecting for things to not evolve or things to not become deprecated. But I do want some stability and certainty. I came to Universal Blue because of two main things that happened to my two systems:

  1. I used Garuda on my PC circa 2022, which tracks closely to Arch. The glibc issue was annoying, but the grub one was fatal. I don’t want to do manual intervention, I want things to be up to date enough, with as little attention as I could. Part of why I made and maintain an image builder repo (aside for, as you say on Brodie’s podcast, the idea of building your own Linux OS on Microsoft’s dime to be funny) is so that I can procrastinate fixing random update errors and also so that in the case of things being broken I can just restore everything immediately on reinstall.
  2. I used Manjaro on my other system. Manjaro, surprisingly enough, managed to minimize the glibc broken period and evade the grub breakage for most of their users, thanks to their staggered and managed Arch updates - it shows me having someone managing updates is pretty good actually. But I don’t trust their team, they do a lot of weird stuff, with the last straw being the mesa h264 issue when they remove unremoved then remove it from their mesa build - all without clear communication if I need to do something on my side.

Basically, much like me going from Windows to Linux, it is a trauma response. I am just afraid that there’s yet more things, that I may actually use, that gets deprecated. I don’t want to manage everything, just the thing that matters to me.

I am wary with all the “old thing, deprecated not our mission, new thing we making… But now deprecated… Also new thing taking our attention.”

It is a pet peeve. Something like, “why are we mixing DE? Why not use the DE defaults?” Doesn’t help that I don’t really trust GNOME as a whole - they care only about their ecosystem, if it’s not to their vision, then they’re willing to block an entire Wayland protocol everyone wanted until people had to work to behind the GNOME person’s back. I don’t think that’s the way FOSS should be done, so I’m always wary about anything GNOME - again, call it trauma response, as someone who did start on GNOME and tried many time to make it work.

For me, I see enough times where Bazzite and ublue as a whole is dismissed by someone who’ve used Debian or Mint for more than a decade. I’ve also seen projects comes and goes despite only using Linux for 6 years.

My Universal Blue experience had been phenomenal. I had to leave Linux land for close to a year due to IRL job, but I was impressed by how well my image builder still works when I plug it into my newly purchased ROG Ally. That is insane, it reminds of those Debian and Mint users who just keep on trucking with the same old 10+ years install.

I like Universal Blue as a whole. I trust you, because you seem very experienced. If it was your project, then I could trust it. But it’s not, and instead it feels like many Nice Things To Have was deprecated in favor of some random new thing that isn’t even a year old, that might get deprecated anyways.

It comes down to too much change, all at once, not enough explanation as to what I can expect to use and not use in the next two years. I guess I’m not too used to that, given how KDE usually operates.

As closing, I’d like to hope that there’s no hard feelings here? I don’t know if I got too heated, still a bit sleep deprived here after working to 4AM. But I am just rather wary and scared as to what does all these changes means for me.

2 Likes

I don’t trust GNOME as a whole, and GTK is frankly the GNOME Toolkit nowadays. I liked Global Menu, but they removed that. I liked having my themes, they made it harder. I don’t like CSD, they lack the same control KDE SSD has. I have set up my KDE to work like Unity, and everything they do seems to want to dismantle that. Issues like the cursor size aren’t prioritized too.

They may be GNOME, but I don’t like that they get to dictate my experience outside of their DE. So I consider Gtk and Libadwaita to be GNOME apps, and I’d rather not have them. Let them live in GNOME space, and I live in non-GNOME space as much as I can (which is limited, given how pervasive GNOME is as the de facto GUI of Linux). I’d rather I have my peace and they theirs, I want to stop complaining about them too so I want to just avoid it.

This is something that I’ve gotten heated over, for years. Agree to disagree and let me choose what I want to use and avoid is the best compromise I could make, after how heated those arguments got.

It’s fine if it eventually make it to “stable”. I just don’t want to redo all my image builder setup, get a nice ISO I could install that restores all of my setups, only to have things be deprecated and I need to redo things later, again.

This is a worry that I had, ever since we don’t just choose what image Anaconda will install by inputting the uri on grub menu anymore. Baseless, alarmist, and petty? Maybe. But I don’t know man, I don’t know what I’m supposed to trust in with so many deprecation around. I don’t have any power - I’m not a contributor, and if there’s one thing that GNOME taught me, if you don’t contribute in some way that matters, you don’t get to say what things get added or removed. And I get that, I accept that, it is what it is, but my powerlessness scares me here.

1 Like

I would agree that some simple ‘roadmap’ or ‘what’s in the works’ page would be nice for users to see on the main image pages to see what’s cookin’ (Bluefin, Bazzite, Aurora), for new users/visitors especially if they have not visited github or the discourse forums.

Separate from that, what I think the project needs to keep sailing along is some degree of a freemium model. A yearly donation of 10-20 dollars in exchange for some extended features and add-ons desired by the community to be supported/added over time.

Also a half/half model with open source and popular proprietary apps on an appstore. I’m sure there are many companies that would take the opportunity to cooperate and allocate resources so their products/services are available and visible to users who will spend money to use them (Photoshop, Davinci Resolve, etc. as requested by the community maybe even microsoft office…it is available on macOS after all). Users likewise want some proprietary apps available with easier access…no messing with wine, terminal or third party apps.

Here would be some other things on my short wishlist:

Firewalld- added functionality to easily create domain blocklists (and perhaps country block lists) along with prompting from firewalld when new connections are made by an app (choice to accept/reject with option to alter these later)

DNS over TLS as the default configuration for network management. Why not?

CVE Scanner- let users know about vulnerable packages so they can make they own choices.

Downloads and Website Scanner- We all know users can mistakenly wander onto an unsafe website here or there or perhaps accidentally click a link that downloads a malicious package…there needs to be something there to detect this and block those instances. (Yes, you can use browser toolbar extensions but not all of them play nice with linux and this is third party stuff…the OS needs to have something of its own.

Dedicated Background Services App across DEs- let users know what is running and whether these may be safely closed and not restarted next time, so users may save computer resources (third party apps and even current DE implementations do not give a complete list) Closing things in system monitor apps can be risky and most things pop back up after restarting computer.

Time sync- option to securely sync date/time only once daily (instead of fedora default chronyd pings once every couple minutes)

Recovery Toolkit or Refresh of Image function- easily restore/refresh corrupted packages or system files through ‘chunks’ or the whole OS (kind of like how DISM in command prompt works in windows) this avoids the need for rebasing later from older versions, or waiting for new versions with updated chunks to fix problems after a hard crash.

An Isolated AI help app for understanding the terminal, all available commands and the DE…this makes it easier for new users to learn what commands actually do rather than sifting through forums or documentation to find that one specific use-case answer to their questions. Also what each option in the DE actually does…(looking at network manager in KDE…lots of options, but not all things are documented in help section)

Simple step by step and visual how-to pdfs- included for various installed apps to get users started on the right foot

Needless to say…this is a wishlist…but please do consider over time :grin:

Go ahead.

Using Jorge as a model, assemble teams of people to build your ideal systems and applications. Be forewarned, it will take a lot of work, unwavering enthusiasm, and diplomacy; and will often be thankless.

2 Likes

@j0rge is my Linux concierge. He’s led these projects that are just what I need to do my work, and some play. Things do change, and I’m okay with that, most changes don’t affect me. If I wanted everything exactly as I want, never to change, I’d use LFS, Arch, NixOS, … I’m cool with Jorge finding the new, cool stuff people are creating. I’m happy he’s making it easier to support people, and I try to support the people I can.

When ZFS was added to Bluefin, that was the green light I needed to make the switch. I forget the exact wording, but it was added tentatively, or on a trial basis. That’s fine. If, for some reason, it is removed in the future, then I can mope back to EndeavourOS, which is quite good, but it would still be with a heavy heart.

With Linux (and Windows and macOS, et al.) there are no guarantees, but there are choices. If EndeavourOS also ceased to be, there is always Hannah Montana Linux RebeccaBlackOS, or thousands of others.
Sure, there will be switching costs, but those pale in comparison to the work to bring projects like Bluefin, Aurora, and Bazzite to life.

TL;DR, I’m on board.

3 Likes

Being well aware of how hard it is is part of the reason why I feel powerless. I’m just a dumb guy who can only do simple thing, and my passion is reading and writing, messing around with tech is more of a fun hobby. I understand how hard it is after talking to a lot of people… So I’m left not even being able to get angry. So all that’s left is just feeling almost as powerless as back when I used Windows - either I put up with it and try to make it work, or I just have to go somewhere else.

I am the same. Well, I do have some doubts. There’s just a LOT of changes recently. Changes that affect me, or I worry may affect me. I accepted most of them because, I get it, this is still a community project and it has to be sustainable to the time of day that the devs have. And things just happened, you can’t guarantee anything in life.

At the same time, it is kinda what made the Bazaar adoption surprise me. I mean, okay, Bluefin LTS didn’t pan out. But now we have another new project, not even controlled by ublue, shoved and put into the system? It’s kinda like talking about a new investment scheme a week after the last one failed.

I don’t know. I feel bad about mentioning Bazaar so much, when the core of it is just me having some doubts and unreasonable annoyance, I guess.

None of the existing app stores will work because we are moving to a work where the app store is flatpak only and doesn’t come with any of the baggage of the past.

Sounds good to me!

I will clarify (once again) that we deprecated nix a long time ago and we do not support nix. It doesn’t matter to me that composefs broke nix, we don’t use or support nix.

I’m not making considerations like that (why would I? I’m working on Bluefin, it is a GNOME experience). If you don’t trust GNOME then you’re certainly not going to trust me, heh.

Sounds like we’re doing it right!

We put dinosaurs and telescope people in Linux, I don’t think any of us are taking any of this too seriously hahah.

2 Likes

Lots of this is out of scope for us but someone could do this if they wanted. For things like the ntp adjustments someone should file an issue and we can do that.

1 Like

I am still confused about that. Sure, GNOME Software and PopShop/Appcenter can manage traditional packages as well. But it could just be gutted so that it’s only Flatpak.

I read and hear what you’re saying, but I don’t get what is about the legacy stuff that is so bad, and is so unsolvable, that there needs to be something new instead of just fixing what exists.

And there’s a LOT of custom app installer GUI. All I feel so far is the classic, “there are now 50 competing standards” situation. I hear you being excited about how it is just a month old, and I see it as unproven toy being brought up as savior to decade-old issue.

The thing is that there is a kind of double hats situation as well. It might be something is focused for Bluefin. But at the same time, you do also have control of various background ublue stuff, what’s with being the one to announce the deprecation of images not used by Bluefin, Aurora, and Bazzite. I don’t know if and when you’re speaking about Bluefin, or if you’re speaking about everything under ublue’s umbrella.

So when I’m hearing about Bazaar, and looking at the Ptyxis situation, what I also hear is, “Bazaar is the future, it will be part of ublue-os, meaning that much like with ptyxis hiding and overriding konsole, Bazaar will go over Discover.”

Am I reading too much into this? Maybe, but it’s kinda not clear what is the scope we are talking here since the Gardiner video uses Bazzite, and THAT would affect me. So before anything I was already preemptively annoyed, expecting to do chores to fix the unwanted changes to get back to my good old preferred solution.

Note that the context is less about adopting new things, but more like not having the years and proven track record that it can be relied and recommended to others the same way Linux Mint is.

And a part of me feels, “Okay, if Mint is still the default, what is ublue doing that is actually going to impact the larger Linux community and new non-Linux users?” I feel like, as a first step, ublue should be able to eventually convince the Mint-forevers to at least agree that there is something here, something that can be trusted as much as Mint is trusted. Or else any waves being made will be limited being just a small fish in a small pond.

1 Like

You’d have to find someone who is willing to do that. We’re opportunistic, we didn’t sit down and say “let’s look at every app and see which one we should use.” We saw someone doing it that vibed with us and we took it.

Old appstores is a thing that isn’t coming with us. We’re not fixing what exists because in lots of places it’s “let’s just get rid of it”, that’s why we describe this as a generational shift.

Our answer to the XKCD paradox is … we choose one standard, Flathub. The existing app stores have to cater to the needs of existing Linux distros. That’s what got us here in the first place. If people want that world, they can stick with Linux Mint.

We’re concensus driven I don’t tell people what to do. What Bazzite and Aurora do here is up to them. My title across the project is “Approver”, same as the others, I’m just the one stuck posting the updates. :smiley:

I hope it ends up just like ptyxis. Where we had a burning need for a solution, and someone else, independently came to that same conclusion - terminals need to be more container aware in general. We shipped ptyxis first (and early) and worked with Christian to file bugs and get it done.

We got rid of our janky homegrown solution and now have a world class terminal we can be proud of. It’s one of our best features and we get compliments all the time - and the collaboration story is in every one of my talks.

I would say this is Android, ChromeOS, and Ubuntu, in that order.

eventually convince the Mint-forevers

We don’t target existing users, we target people who don’t use Linux. Or in the case of Bluefin-dx we target advanced linux users. If someone is happy using Mint why would I bother them?

I would say generally speaking Jorge does straddle the line of Bluefin and Universal Blue. But for the most part Bluefin is his thing, with Universal Blue being the larger umbrella to hang all of our projects under.

For who speaks for what:

j0rge is Bluefin.
Kyle is Bazzite.
Niklaus is Aurora.
Bsherman is uCore/Server.

You will occasionally see j0rge, Kyle, and bsherman make announcements that affect many people as well. Pretty much any of our approvers have made such announcements in the past. Generally we work on lazy consensus.

Overall, we have been de-emphasizing Universal Blue base images for awhile now. You may have seen me in the past deprecate the hwe images and other images that we built. At one point we were building an absurd amount of images. Basically every DE imaginable each with Nvidia, Asus, and surface and a mixture of them. We’ve stopped doing that.

The removal of more base images is a continuation of this. We no longer want to be in the business of building images that we do not test let alone use. The big thing we’ve done is trying to reduce scope of our images.

And since people are more around during releases. We usually plan around releases being the timing for things.

9 Likes

Ok I think I figured out a way to explain this because I had to figure out a way for nontechnical people to understand this pattern so more people can follow along and participate. I guess let me explain why this feels so user-hostile … ok, I hope I don’t come off too preachy, and also this will be long, so let me get it all out there at once.

Let me take a stab at a State of Universal Blue

Off the top of my head:

So when I was getting into Linux in my early days, this kind of thing has existed for a while. Everything would get better if KDE and GNOME got together it would be so much better or how we have thousands of distros and they all suck, if only these people got together … and so on.

Now it’s like 25 years later and I understand how open source works more. The truth is, it’s a human thing, the software just happens to be what we produce. OSS tends to just spider out in different directions. People do what vibes for them. Just because we’re frustrated at the state of our woefully underfunded part of Linux doesn’t mean we’re immune to things. It’s slim pickings in this ecosystem.

Shit sounds easy until you have to go do it. That’s why we’re usually short, because in my mind … we need to act like an endangered species. Because we are. The dinosaurs are pretty cute right? But there’s a reason only the birds made it. It’s supposed to be a call to action.

Here’s an example, my take on the XKCD standards thing AND monetization of the linux desktop in one shot. If I was doing this at my job:

People often paint it as snap vs. flatpaks. And then this is the usual thing that people complain about. But Canonical understands the value of monetizing the work they do. And to be frank, they deserve to capitalize on their business model. Dude I’ve done that job, and I busted my ass on it too just like I am on this one. We’re growing a ton lately and I want to make sure we communicate this because most of the things I say will be a shock to desktop-only people. Part of what made Kubernetes explode was the fierce dedication to this way of thinking. I always like to say, we are not unique, this is a style of using Linux for servers, and this means using our desktops in a certain way.

Projects put these things on their pages like badges of honor, then half the time half the grid is red. Like who is happy when they see the page, this is so “why we’re losing” in one nice chart. So people stick with what they know, hence our current dismal situation.

Ok now let’s see this would play out in a cloud native community, this is what I think we should do:

The standard is the freedesktop portal. There is commercial interest from both Canonical and Red Hat to use this for commercial products. Snaps have their own store, proprietary. Red Hat commercializes Flatpak and then you can only access it as a RHEL subscriber, but flatpak is community driven, though Red Hat driven.

However everyone needs the portals, let’s just call this “The API” for simplicities sake. It’s in everyone’s best interest to keep that funded. This happens all the time, in fact, it’s what led to Kubernetes’ success! Big tech wanted to make the money, and yet, there is a place for everyone here, little companies, huge giant ones dominate, but as an opportunistic little guy, you can survive. (Damn I am spoiling the dinosaur story aren’t I) … This is a huge industry, but it’s relatively easy to see who is participating, because, the rules are laid out, and the data is out there. This is why LF opensourcing LFX is awesome, we can measure everything.

There for sure are companies taking advantage of open source developers. We are surrounded by predators, lots of awesome people losing jobs, etc. It’s a jungle out there haha. But what I’ve learned is you can staple yourself to something that is very interesting to you. I think of it as, some banks are going to pay a lot of money for this, and I want that world to pay for my Linux desktop. They won’t be interested at first, but our charts are climbing as you’d think. That’s why we measure and we show it off, it shows what working with us is “worth”. As a Bazzite user, you want to be counted.

RHEL10 ships image mode just while Bazzite explodes. Enterprise Linux is a multibillion dollar market! Gamers, they for sure heard you. :sailboat:

If anything, Universal Blue is an example of what can happen when you learn to work together with the commercial entity. I mean, we do good shit, but let’s be real, we have gotten millions of dollars of engineering, we know how the game is played. Red Hat has SO many ex-Ubuntu people in their ranks. Many of us were paid to work on desktop linux, and that’s so rare now. Once everyone collectively figured out that we could use this to make desktops awesome …

And also we all grew up together in this anyway. Everyone was in the same room when something cool happened.

But I also want to see Canonical succeed because right now more than ever, their support of this ecosystem is vital. I like to think of us as the Slayer (the metal band) of Flathub, like … you know what you are going to get. As a flatpak advocate, when people shit on snaps, you are NOT helping me out, trust me!

We’re being flooded with new users, instead of arguing about distros and packages, we should talk about the importance of having this. This is another cloud native property, there’s always going to be a spectrum, a fully commercial vendor, to a community run thing, and different business models. The API makes them play fair. Many of the things that people complain about with “so many linux app stores why are you making it worse” is not a thing in actual practice. You WANT to have multiple attempts at something, and eventually the ecosystem will find balance. The ecosystem will decide what lives and what dies, but the API rules are the same for everyone. But ours is just for Flatpaks, it sends a statement more than anything else.

It means that that everything to do with old world packaging isn’t coming with us. The API we’ve chosen is Flatpak. That means our GUIs for it can optimize for it. This push for standardization helps Canonical, Red Hat, and us. Ok, so … those two have money. Universal Blue does not. We want to be everyone’s friend. And now that ya’ll have been supportive of Bazzite, we have their attention. My proposal is, let’s standardize this user space for the sake of everyone. We’re picking this one, we don’t carry anything for the other stuff, we’re all in.

Ultimately it doesn’t matter, so much of this stuff just fades away in automation anyway, someone go look at how chainguard makes their wolfi OS. It’s like all bots. We’re doing a great job, look at the charts on Bazzite’s website, that renovate bot is doing so much work! Both flatpak and snaps are so automated that at some point we’re arguing about what the machines are doing. :smiley:

If you want your dream Aurora untouched by my GNOMEness … the only way I can help you get that is to solve the economic part, and the best way we can do that right now is to help pick “The API” with the best chance of winning, so we’re all in on that. Putting Bluefin LTS on hold for a bit to fix this first is fine, and yeah, bummer, but we have limited resources, so gotta prioritize this right now.

I think a test of a healthy community shouldn’t be to complain about not getting your perfect exact desktop – instead I would look at it as an opportunity to fire up some folks. Let’s see some KDE people cooook. The inconvenience is part of adjusting to changes in the ecosystem.

And now the circle of life is complete: A need must be met, our mission is to onboard new contributors. Someone out there is going to look at this feature set, and find enough people who are interested to work out. Then boom, Plasma pushes the boundaries and with the amount of checkboxes you all put into stuff, you will indeed have brought Kubernetes to the desktop lol.

But we also do what we want. Shipping Docker with Bluefin makes that statement upfront. :slight_smile: And we need to show that Bluefin knows where it sits in the open source world, which is currently, right where we are today. At this moment in time our mission appears to help make this world a reality. We don’t really have a roadmap because we just find the next thing to do. Bazaar was a side quest that ended up being an important part of the main story.

7 Likes

I have full faith that this model will bring the linux desktop to the mainstream.The biggest key factor in reaching that is slaying the package dragon once and for all. Firstly with pushing flatpak only, and second having a suitable and efficient store front that’s designed with a flatpak first mindset from the get go. (Including getting developers paid)

Thank you for taking the time to write out this post. It was very easy to comprehend and did a great job getting across the purpose and mission of Universal Blue.

If you are willing to, you should definitely consider making this its own announcement post. And maybe even adapt parts of it for a youtube video. As like an “State of Universal Blue Address” sort of dealing. I think it would help emphasize what Universal Blue has turned into and the concept it represents, rather than as others have said a collection of untested automated base images.

3 Likes

I agree with @Chandeleer says:

Fundamentally, my issue is more about clarity and trust. The GNOME part is a tangent that gets out of hand, but I do tolerate some GNOME apps like Bottles since they make playing my “alternatively acquired” games so much easier.

My issue is, you say, “this is just one month old,” and think “impressive, it’s already this far” while I think, “high chance of not lasting long,” because that’s usually how it goes. Now, I can have faith, but at the same time a bunch of things got deprecated at the same time, with little communication as to what will remain supported, and for how long.

It’s kind like asking someone to stay on the same plane for another 12 hours flight after the previous one had had to do sudden landing.

2 Likes

didnt find the time to read the entire thread, but a few thoughts

Bazaar

havent seen the bazaar vid yet but a small demo. Looks nice but kinda just GNOME software? What about GNOME or KDE Extensions, firmware updates or native packages?

KDE Discover has all of that, though no native packages via plasma-discover-rpm-ostree anymore. That would need a different approach more like the traditional “make a list, enter password once” GUI packag managers like dnfdragora/synaptic.

If uBlue would need something different, then one that unites all of their packaging methods! I think on Ubuntu it is most absurd, as you have a firmware updater (I think), a GUI updater, GNOME software, Extensionmanager and maybe the Snap store too.

KDE has a single one, unless you use Distrobox and/or homebrew, so you would need something to bring that into a single app!

Payments are important, why shouldnt they be added to GNOME Software or KDE Discover? I agree with @j0rge tho that people just do what they like and time spent on a fancy new appstore is not wasted or anything. still, flatpak only? i dont see the point.

GTK

I use a ton of GTK apps and they look fine everywhere, meanwhile KDE apps look awful on GNOME (and COSMIC and others too!). Yes, the whole GNOME not using a full FDO icon theme thing, but they still look bad after they include their icons. So absolutely a Qt/KDE issue.

Though, that was the reason why I didnt use Ptyxis either. apart from the… name.

Usability

Especially with bootc I have no idea if on-device changes are even planned for the future. I never got brew installed and rely on a couple of things that really (currently) need to be on the system.

I switched to NixOS, mainly because the frequent crashes caused by the non-longterm Kernel. NixOS is waay nicer if you want a custom system with sudo-rs, uutils, debloated Qt6-Wayland-only packages etc. But the usability is pretty hard.

I think uBlue is a great project and wish you the best! And yes, the abbreviation will likely stay forever :wink:

1 Like

@moderators a few comments seem to need pushing back to the original thread

The point, if I am reading it right, is to create something so good, work so well, and solves the donation/purchase/monetization issues that it could plausibly be adapted to be THE default. Become THE Flathub GUI used by everyone, solving the “how do I get my apps?” issue and having something on par with the other app store apps on other OS.

At the same time, what’s also going on is that we don’t want to push it THAT hard yet. Incubate it in Bluefin, but we don’t want any rhetorics that could jeopardize the relationship necessary to make such a thing possible.

I personally liked the idea of NixOS, but it is just too annoying troubleshooting everything. I like the system of building your image on GitHub, with a yaml-style (or Containerfile-style, if that’s your thing) file.

First, it’s just more understandable - even with the Containerfile format, it is a universal format used by the industry, so it has more resources (whereas in my experience, even NixOS diehards admits there are issues with documentation and learning the format). Next, if there’s any error, you’re not stuck with a broken config file on your machine - everything is natively on git/github so it is easier to track everything, isolate experiments to branches, and separate your images to different tracks. Last, collaboration and benefitting from upstream is easier - you can take an image you agreed the most with, and just maintain your own changes, as well as in tracing where any issues occurred since you can rollback to previous 90 days on your builds and your upstreams.

That last one is why the base images deprecation alarms me so much. I don’t want to maintain my own - I agree with most of ublue’s decision and would rather alter a few things than setup the whole image myself. I may not be immediately affected, but the direction and speed of things make me worried that a major motivation for my use of uBlue is threatened.

It was fine, at least back then when I used GNOME. I just needed to use Kvantum and then things look and work fine.

My issue with the GNOME stack (as much as I don’t like talking about it too much, but I want it to be clear) is mainly with the functionality of it. CSD is a major annoyance - I have 768p laptop and ROG Ally, screen real estate is a premium, which is why I have my Unity-like setup. I want Menubar and Global Menu because it works - it can be on my top panel, but barring that, navigating with both keyboard and mouse is simple. On everything that isn’t GTK4, we have SSD, meaning expected behaviour like being able to Shade window, hide the titlebar automatically or manually (and, remember, Menu functions can be shifted to Global Menu), setting order of window buttons, and controlling the window from titlebar (moving Virtual Desktop by scrolling and customized left/right/middle clicks) all just works. Also, issues like cursor size suddenly being bigger on GTK app for some reason, is still not fixed.

I have, at this point, reached the point where I would rather have electron apps than GTK. And it all goes back to CSD because of course it does. I wouldn’t have that much problems if GTK/libadwaita isn’t so prevalent that it is the de facto default toolkit for Linux apps, and GNOME controlling it while not caring about designs that don’t fit their vision of how the desktop should be.

I won’t deny that there are issues with Qt as well, I have far more hope of it being fixed than Gtk.