Solus Leads

Brucehankins

WetGeek I grabbed a Tumbleweed .iso also and chose the minimal option for install. I wanted to see what the experience was like installing the Budgie desktop and configuring that, I know Plasma is fully supported. I use Gnome Boxes and didn't have any of the issues you ran into, but I wasn't happy with the Budgie experience on SUSE. I'm also just not a fan of zypper or YaST to be honest. I got Budgie working with the documentation, but I can't get the themes I want recognized (that aren't in their repos) and I just can get the feel quite right. I'll still check out LXQt too see what it has to offer, but that's more to do with my own curiosity than making backup plans. I still have Solus Mate, Garuda LXQt, Fedora, KDE Neon, and Debian Testing VMs on my machine because I like to tinker.

I did try Endeavor in Boxes also, and while I can appreciate it, the compile times on my hardware were very long and it would in no way work for my family without me being full time IT, which is the great thing about Solus, it just works and everyone can use it.

The family loves Budgie on Solus and I love either Budgie or Plasma on Solus. Like many have said before in other posts, it's home. No plans to leave Solus until it's long dead and there's a critical CVE that forces my hand.

h3o

WetGeek @Brucehankins I actually installed Tumbleweed a few weeks ago just cuz it's been on my distro bucket list and I've heard so many good things about it. Solus is wayyyy simpler to use, but I've been impressed with Tumbleweed speed and responsiveness, battery life, bootup time, and ease of customizing your system. I'm on hardware, dual-booting w/ Solus.

@Brucehankins I tried gnome (wayland + x), Cinnamon, XFCE, i3, Budgie, Sway, and Plasma.. all worked great, but nothing felt better than Budgie. Just install the Budgie pattern from Yast and should work fine?

@WetGeek to get Vivaldi you just need to add the Vivaldi repository then install it. Not as easy as Solus. And for micro, you just need to 'opi micro' from the command line to install it from their OBS or Packman. Again, not as easy as Solus.

Tumbleweed def feels more 'hacked' together with their various services and repos, but it seems to eventually get out of the way once you set up some initial stuff. I'm gonna continue with it for now as it's no slouch in the performance department, gives me longer batter life (laptop user), and I do enjoy the greater customization (ie. if I want to use Nemo instead of Nautilus, no problem), but I'm sure it's only a matter of time before I nuke it and boot back into Solus again lol

WetGeek

h3o Again, not as easy as Solus.

I guess what it boils down to is this: I don't see any advantages to Tumbleweed that would make up for the additional pain to install the software that I love and use all day. Although they're not defaults that install along with Solus, it's trivial to get what I want with eopkg.

elfprince

I do not see any announcements re Josh on this issue on this forum. Can anyone point the way please?

brent

elfprince https://www.phoronix.com/scan.php?page=news_item&px=Joshua-Solus-Steps-Down
(was not announced on forum--it was announced on twitter i believe)

jppelt

My biggest concern is Budgie. Josh suggests he is going to fork and team up with some like minded developers. Solus Budgie is a perfect combo. Will Solus relegate development to a 'Budgie' team or will it remain in-house? I guess we shall see...I really appreciated his leadership and voice.

Robotmike2

jppelt Josh suggests he is going to fork and team up with some like minded developers

So I wonder why it's necessary to fork it anyway. He could've been continuing his work on it, so there seem to be different opinions about something related to that.
Maintaining an additional Budgie version makes no sense for Solus.

I would really like to understand what's behind, from a technical point of view. Unaccomplished dependencies etc. or whatever, I'm not pro enough to know this as an obvious matters of course, but also too interested and nosy for just standing on the sidelines. And not even knowing what developers are talking about I'll have no chance to find some serious information, irrespective of the language barrier...

elfprince

brent Thanks a lot! This should have been in the forum too. Sad.

Brucehankins

Robotmike2 if I had to guess, it's because the Budgie DE was initially developed with/for Solus, and the main Solus repos house the Budgie DE code. Thus, he would fork it to a different repo to continue being the main developer and allow for others to contribute easier. I don't think you'd see a "different" Budgie for Solus, but something similar to the current Ubuntu Budgie. That is, if the dev team for Solus decides to do so, how to move forward is up to them.
Have faith that the new structure will make the best decision for themselves and the community, and understand it may take some time for them to announce those decisions.

brent

EbonJaeger As far as Solus using it goes, nothing should really change there, for as long as having Budgie available is still desired (and it's been stated on Twitter that it very much is). The only thing that's really changed is the repo where it lives.

It is a strange dealio when the Budgie lead and the Solus co-lead are the same person! Thanks for clearing that up. (edit: forgot to include Brucehankins in my response--I was replying to both)

EbonJaeger

From my understanding. Budgie was always meant to be distro-agnostic; while it was always primarily designed for Solus, it was the idea that it would work well for any distro that has the needed dependencies.

Splitting it out into its own org and everything makes this goal much easier, and it makes collaboration with downstreams easier and centralized. This couldn't be done with the old Budgie repo because no one has access to that organization, so it's just kind of stuck there.

With the primary developer of Budgie leaving Solus, it makes a bit more sense for Budgie to be under its own org instead of Solus's.

As far as Solus using it goes, nothing should really change there, for as long as having Budgie available is still desired (and it's been stated on Twitter that it very much is). The only thing that's really changed is the repo where it lives.

tomscharbach

EbonJaeger From my understanding. Budgie was always meant to be distro-agnostic; while it was always primarily designed for Solus, it was the idea that it would work well for any distro that has the needed dependencies. ... With the primary developer of Budgie leaving Solus, it makes a bit more sense for Budgie to be under its own org instead of Solus's.

Mating the Budgie DE (minimal, intuitive and uncluttered) with Solus OS (desktop-focused, curated, stable, no cruft or misdirection) is what makes Solus Budgie a "near perfect desktop environment" for me. I think that mating occurred, in part, because Solus and Budgie grew up together, so to speak, Budgie developing out of the same vision from which Solus developed.

I've looked at other Budgie implementations, and all, to be blunt, seem to be about 10% cockeyed, not quite fitting or working right, a bit clumsy and missing the elegance of Solus OS Budgie.

What is, though, is, and perhaps Josh's departure will help Budgie develop in ways that make it work as well with other distros as it does with Solus OS. Josh clearly intends to make that a reality, as he discusses in a post on the Ubuntu Budgie forum. It is interesting reading.

Robotmike2

Well...

we are encouraging everyone else to build what they like in a way that respects all Linux desktop environments. Folks from EndeavourOS, Fedora, GeckoLinux & OpenSUSE, and of course Ubuntu Budgie should feel encouraged to get involved. Eventually Serpent OS (my new home) when it is ready and usable.

Solus isn't invited there? Okay....

synth-ruiner

Robotmike2 maybe it goes without saying. let's be charitable...

EbonJaeger

Robotmike2 There are already a couple Solus people there (at least myself and @Staudey, that I know of). I don't think Solus is meant to be not included in any way. Previously, it was almost exclusively Solus people involved in Budgie, so I would guess that the wording is meant to encourage all the other people and distros that use Budgie to start to get involved.

Staudey

@Robotmike2 Yeah, as @EbonJaeger said that most likely isn't meant as an exclusionary message, but an invitation to all the other distros that haven't already been heavily involved in Budgie (as Solus was/is)

brent

It's sad that once Solus had a dependable cash flow (recent community funding) that the implementation of ideas deteriorated (in Josh's retelling). I was naively expecting the opposite since with cash always comes wiggle room.
2021=George Costanza's Opposite Day.

serebit

While Budgie was always primarily developed with Solus in mind, splitting it out to a separate org allows for it to flourish on its own and account for the needs of different downstreams. The new Budgie org on GitHub includes current and former Solus developers like myself, along with current Ubuntu Budgie developers and EndeavourOS developers. Solus is not excluded from the future of Budgie.

Robotmike2

OK, appeases me, I was waiting for a statement like that. Nice to see it clarified by internal people. Thank you!

serebit

Just to clarify, in case this is referenced elsewhere.

Budgie, prior to the changes of the last few days, was the flagship desktop environment for Solus. Because of this focus on the Solus experience, Budgie lagged behind on other distributions significantly. For example, the Budgie defaults on Solus are custom—the defaults in the upstream repository were years old due to having never been updated to fit with the more modern look of Solus's Budgie configuration. I installed EndeavourOS with Budgie and was immediately greeted by a Budgie configuration that I hadn't seen since around 2017 (anyone else remember the top panel?). This led many to the conclusion that Solus had the best configuration for Budgie and that other distributions were lagging behind, which shouldn't have been the case.

The goal of the new organization around Budgie is to pull together downstream consumers in order to improve it for everyone. We want the Budgie experience to be excellent on all operating systems that leverage it, not just Solus. We now have EndeavourOS contributors, Ubuntu Budgie contributors, and Solus contributors like @EbonJaeger helping out, and we hope for this list to expand in the future. If Josh's statement implied that we will be excluding Solus in some way, that is not at all what he meant. We want to meet the needs of Solus just like we want to meet the needs of all other Budgie-shipping distributions, and we encourage those who want to get involved to do so! Even if Josh and I are no longer contributing to Solus, that doesn't mean we harbor any animosity towards the distribution, its developers, its contributors, or its users.

If you feel inclined to get involved, you can find us on our new GitHub.

Solarmass

serebit I installed EndeavourOS with Budgie and was immediately greeted by a Budgie configuration that I hadn't seen since around 2017 (anyone else remember the top panel?)

tomscharbach

serebit I installed EndeavourOS with Budgie and was immediately greeted by a Budgie configuration that I hadn't seen since around 2017 (anyone else remember the top panel?). This led many to the conclusion that Solus had the best configuration for Budgie and that other distributions were lagging behind, which shouldn't have been the case.

I checked a number of Budgie implementations (Ubuntu Budgie, Gecko, openSUSE and so on) in Gnome Boxes yesterday and this morning. All seem to be following this pattern.

serebit [T]he Budgie defaults on Solus are custom—the defaults in the upstream repository were years old due to having never been updated to fit with the more modern look of Solus's Budgie configuration.

Thanks for pointing that out. I had assumed that other implementations were flawed/inexpert/clumsy. I did not understand that the issue arose out of different repositories, upstream/downstream failures. I hope that splitting off the Budgie project as a standalone will eventually result in common implementation across distros.

« Previous Page Next Page »