Skip to content
This repository has been archived by the owner on Apr 29, 2024. It is now read-only.

Deprecate this repo #73

Open
castrojo opened this issue Feb 26, 2024 · 9 comments
Open

Deprecate this repo #73

castrojo opened this issue Feb 26, 2024 · 9 comments

Comments

@castrojo
Copy link
Member

castrojo commented Feb 26, 2024

Both Bazzite and Bluefin would like to commit to just having direct support in their images so that we can remove this set.

For AMD users the new tuned setup is the way to go for us anyway and it's working great since we switched Bazzite/Bluefin to tuned a while back.

And on my intel framework 13 the tuned setup is a much better experience and the battery life is much better, I don't see why we'd use TLP instead. Kyle also mentions that tuned can import a TLP config so if we wanted to keep that as an option we can, though IMO it's not worth saving that. 😄

And then on the website picker we'll still show Framework so the users know, it'll just also recommend the same image as stock. Then sometime in the future a better landing page for them, etc.

Thoughts from @ublue-os/approver @ublue-os/member

@noelmiller
Copy link
Member

I support having direct support in Bluefin and Bazzite rather than a separate image.

Just want to make sure to alias any framework tags to the proper versions for folks going forward.

@bsherman
Copy link
Contributor

This make sense. We want to solve problems generically where possible. Having distinct repos per laptop manufacturer, etc, is quite unwieldy.

@noelmiller
Copy link
Member

Do we know if Tuned is on the roadmap for F40 and we are just shipping it early?

@bsherman
Copy link
Contributor

Do we know if Tuned is on the roadmap for F40 and we are just shipping it early?

I'm not sure, but I have two comments about that.

  1. if it is, Bazzite and Bluefin are great places to get early Fedora testing for it :-)

  2. if not, Bazzite and Bluefin are great places to prove the idea and help push for getting it on the Fedora roadmap

@castrojo
Copy link
Member Author

F40 should have tuned, it was just punted for time. I've gone ahead and updated the README.

@prometoys
Copy link

This is sad. I love to have a opinated Silverblue with Framework optimizations. How hard is it to keep this repository alive and how can I help? If it makes no sense, because Fedora 40 don't need Framework (13 Intel) optimization, I have no complains :D

@HikariKnight
Copy link
Member

The way i see it, explicit "laptop/manufacturer" images should only be used when absolutely needed (like in the case of the rog ally early on and it requiring some stuff we would not want in the base image)
Other than that supporting things directly in the image is easier.

@marcoceppi
Copy link

@prometoys there wouldn't be anything stopping someone from taking this repo further outside of the ublue-os org if there needed to persist a specific vendor flavor of ublue either. That would need one or more people with that vendor hardware interested in maintaining the repo vs placing the expectation on the ublue-os org directly

@castrojo
Copy link
Member Author

castrojo commented Mar 4, 2024

Other than the kargs, everything we needed is in upstream Fedora now so even the vanilla images will run better than the TLP images.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants