N@Kyle Gospo @j0rge @Marco
@NerdsRun is interested in helping maintain Yafti and make improvements to it. Him and I talked quite a bit, and we are trying to determine what the scope of Yafti should be.
@NerdsRun is interested in helping maintain Yafti and make improvements to it. Him and I talked quite a bit, and we are trying to determine what the scope of Yafti should be.
NBased on my conversations with him, we have found a lot of the tests and code examples in the repo are surrounding flatpaks and installation of them. In Bazzite, there are a lot of ujust commands that are included as part of Yafti, which could make validating configurations done by yafti difficult unless there are stringent standards around what ujust will touch or do.
N@NerdsRun is OK with including ujust or arbitrary commands as part of the scope, but it just makes it difficult due to the varying commands being handled.
Jso one thing that is confusing to me is why we use just to execute complex commands where we could just have yafti do it directly so just isn't so unwieldly
Janyway no strong tech opinions other than I'm hugely grateful for a new contributor to step in and make things better. So much 
from me
from me
KI'm all for it calling just where it makes sense, I even have topgrade calling just now
NHere are my initial thoughts. I think anything in the scope of upstream (defined by someone ;p) should have builtin support.
Anything outside of this scope should be supported with the expectation that any additional components provide definitions for health checks / failures / idempotent installs.
Anything outside of this scope should be supported with the expectation that any additional components provide definitions for health checks / failures / idempotent installs.
Nexamples: flatpaks, rpm-ostree, distrobox(toolbox), and maybe homebrew?
While the one off just commands would require a little more effort for verification.
While the one off just commands would require a little more effort for verification.
JI think with F40 ~2 months away we can just concentrate on fixing the user-facing issues (like the checkboxes not reflecting the state at the top level), and since the flatpaks are going into the installer then that last part with the infinite-feeling progress bar probably won't feel as long as it does now.
JThis is one of the oldest things in the project, I think a fresh look at use cases and what we actually need is a good idea. Bazzite didn't exist when yafti was written so it's been over a year of growth
Jso like maybe have a branch that fixes the top annoyances but then a new branch where you can indulge yourselves, heh.
N
Nshould have a fix for review sometime next week fixing some of the issues with the progress bar and looking up flatpaks etc.
Jyeah and bluefin's needs are minimal - mostly "install a few flatpaks", so I would use bazzite's requirements as the basis
Jthough ... thinking aloud and future-proof ... wouldn't it be badass if one of the options was "turn on devmode" so you could DX and reboot right into it.
Jthough we had talked about the app being more like a control center than a next, next wizard
Jso maybe it should look like that, dunno, I'm sure others will have plenty of ideas
Nsome ofthis can be done with go and charm for a tui as well.
Jmy preferred choice is a TUI actually but normal people will want a wizard, heh.
Nagreed.
Nill get something submitted fixing the github issues and shoot over a small demo video or something first.
Jbubble tea and lipgloss all day long. 
Jthat would legit be the sweetest unix flex
Jyafti is front end swappable though iirc, a CLI and UI or a Qt UI for kde, etc is doable
Jthat would look sooooooo dope in Ptyxis
NTotally. Though i might suggest moving some of the core logic to go vs python and use yafti as just a user interface for the wizard.
NGitHub
A modern and customizable python UI-library based on Tkinter - TomSchimansky/CustomTkinter
Nseems pretty.
J@bketelsen is a go nerd too, and that might interest others as well
Gusing go for a backend project currently
Gi'd be willing to help with this when I have time
F"Yet Another First Time Installer" sounds off to me, "Just a dope OS Configurator" sound great to me.
judoc > yafti
judoc > yafti
Bdid a prototype go app using charm's new "huh" library
ESee what you're saying here. I guess the name has kind of shifted off basis since we began allowing run to be used as a module
EThough I'm not crazy about that acronym. I like yafti better
NYafti is a good name with history. Even if the scope has increased for it, we can just drop the fact it's an acronym
JAnd I don't care about the name, it's user invisible and I hope it stays that way.
NAlso true!
NBazzite Portal or Bluefin Portal(?) is what people know it by.
FYeah, I agree that yafti sounds better.
yafti gained legendary status anyway, so it should stay
yafti gained legendary status anyway, so it should stay
J@Kyle Gospo do you think calling the brew ujust thing from yafti will work? I'd still like to find a way to ship it by default since we can't do it from a service unit
KYeah that should be totally fine
MI also own yafti.com if that’s of interest
J@NerdsRun idea ...
JI wonder if we could embed a youtube video at the end of yafti. Like if we had a tour video.
Jlike don't autoplay it anything, but like, let the user just have a video tour as part of the first run
