should be good to pull and test now https://github.com/ublue-os/nvidia/actions/runs/4983580030/jobs
should be good to pull and test now https://github.com/ublue-os/nvidia/actions/runs/4983580030/jobs/8920793465
PPerhaps I'm not quite the target for yafti at least the way it works right now since I think I want something that's a little more opinionated about making sure everything gets setup (and have some ideas about automating/guiding e.g. setting up github ssh keys etc). Probably something that keeps track of which items have been completed vs which haven't (e.g. like what the nix determinate installer does when it creates a plan/receipt)
Jthen the priority is basically top to bottom, left to right, so things in the Todo column should be in reasonable order based on who is interested and actively working on that
BWhile it can flatpak of vscode isnt all that greatly maintianed
Jyeah it would be nice if we could do all these things but it's just getting started
Jlike ideally we could whack a list of flatpaks and the installer magically does all the stuff correctly like how the silverblue installer does it, as part of the install
Jlike if it looked exactly like the default installer but flathub and your flatpaks instead it'd be what everyone wants I think
BAlso, lets scope this discussion right now... if we keep to config/main/nvidia(/akmods) that keeps yafti/startingpoint out of scope and helps things be focused on the core functions
PYeah I was wondering (esp with the move to the cockpit stuff) about maybe if it'd be possible to just add some kind of extension to that process
Jgood point, let's make this board about images and infra
J(we can make as many boards as we want)
BFlatpaks in fedora silberblue are installed during installation portion in anaconda aperently from what i saw
Jyeah
Jit grabs the runtimes and everything, the progress meter works correctly, etc.
AI'd suggest opening a ticket in yafti's repo about a
yafti.yml flag that is stricter about "don't treat this as a finished run until the user has done every step".
AAlright. We can delete that outdated thing:
https://github.com/orgs/ublue-os/projects/1/views/1?pane=issue&itemId=22693597
There's a ticket now (IDE integration):
https://github.com/ublue-os/main/milestone/2
https://github.com/orgs/ublue-os/projects/1/views/1?pane=issue&itemId=22693597
There's a ticket now (IDE integration):
https://github.com/ublue-os/main/milestone/2
Bhow do we get this into the project board? it's in progress with David and I working on it
https://github.com/ublue-os/main/issues/46
https://github.com/ublue-os/main/issues/46
JI'm checking now, but I also think we want that asap right?
Joh I guess technically we're on F39 work-wise
Byeah, pretty much everything i've done in ublue (not ucore) has been with this in mind 
Joh, ok, new info
JI thought you'd be able to board stuff but it has a whole seperate access section, sec
Byeah, i saw i could add milestone, but then couldn't do project board 
Jrefresh
BBOOM SHAKALAKA
Jthere should be a + at the bottom of each column
Jnice.
BJthe diagram for the images is done I just need to sit down with @marcoceppi and sort out the website build which I busted, so that one will be done
CUpdating
Jwe should probably split the "flatpak installer" one into more actionable items
Bi think i'll make 71 (split akmods/nvidia) a requirement for 46 (xbox controllers)
MI’ll have time in 20 mins @j0rge
Jok I might have a 3pm job interview so either way Jorge wins.
JI'll inline some things we can do so ya'll can practice milestoning and stuff
J"Turn on F39 builds" will need to be there, along with a link to the place we need to monitor to know when they branch it, if they haven't already
Jthat flatpak update one can be an easy one to get help wanted on, right now it's just a dumb timer, it needs some nuance there
Jlike, I suspect clear linux's flatpak update timers are smarter than ours, those timers are like the very first thing I did a long time ago and they're due
RDo you mind if I ask, are you organising your project boards at the organisation level in GitHub? I do admin on GitHub almost on the daily if I can be of any help
BGood luck
Jit'd also be good to get more hands on the website if we can find them, specifically the images page/python needs love still and could be fleshed out better
Bthere's a ticket for improving flatpak timers in
configand we need to chart out the metrics on the site too, but @jeefy's been capturing the data so that should be a matter of someone generating a chart and then putting it on the markdown page
Jlinked, bummer the sidebar link thing only does pull requests
RTo link to tickets across repos I am fairly sure the project boards have to be at the organisation level, and you can select which repository have access to use each project board.
Then you can add an issue to a project board at the same time as you label it
Then you can add an issue to a project board at the same time as you label it
C@j0rge @bsherman works 
BRMight help to have a 'easy first ticket' type thing, or even a 'help wanted' tab in a project board
Rso easy place for new contributors can help with documentation PRs?
ASomething that runs a flatpak update at every login + an interval would be excellent there.
AThat sounds excellent. Yes we have an overarching organization level board, and per-repo milestones. It's disconnected from each other atm.
So if we're able to configure it so that the repos can access the organization board, that'd be perfect.
So if we're able to configure it so that the repos can access the organization board, that'd be perfect.
