I'm still confused as to why this is seperate from the website?
I'm still confused as to why this is seperate from the website?
Xahh wel that's another fix, the min width on the images appears to not be based on page with
Xi did type a long message about that a long while ago with like five points and you didn't answer
X
Jthose seem like your personal reasons for doing this I mean why do we want to move to this over what we have now as a group?
Xbecause it exists and is a better image list than what we currently have?
JI don't agree
Jthat's why I'm asking
Xhow can i make it better then?
Xyou were at least originally asking why didn't I just do this atop of MkDocs, and I think I provided clear reasons for that
Xand of course, as I was the only person interested in the development of the site, I decided what to use
Jwell, you answered your own question then. 
RI can kinda see both points here. The current https://ublue.it site seems very docs-y (since it's built on a tool meant for documentation). It would be cool to have a nice homepage with that clearly explains what the project is. I'm not too sure on this homepage implementation, but it could be improved over time.
So the homepage site could link to https://docs.ublue.it.
So the homepage site could link to https://docs.ublue.it.
Xwell, the implementation is up for improvement, obviously i'm not just suggesting throwing the site at it's current mobile-useless state out there
RI also get that it's another site to maintain, which isn't the best. Double the hosting costs, difficult to get consistent theming between the sites etc
Xwant more content on the homepage? sure. hate how it looks? can be improved.
Xthe hosting costs are 100% free
Xnetlify can easily serve our purpose for free, and the docs are hosted on github pages i believe
Xconsistent theming, of course, but i don't know if anybody expects that from an off-the-shelf docs website
Xmy website is also SSG-based (not really a traditional ssg, but still), and the content is all in yml and md files, which shouldnt't be hard to maintain
K@j0rge any thoughts on that selinux package I linked you?
JI don't really have an opinion, all the rpm stuff is mostly foreign to me
JI think adding in a fix to everything in the world in there will lead to tears though
Kmostly the concept, do we want to ship an selinux rule to fix TF2 OOTB or skip it?
KIt's technically a security hole
J@hermmm sorry I'm just concentrating on the basics right now and fixing the core issues
Xyeah, np
J@.jstone you'll need these fixes in nvidia too, I can confirm the metadata is all correct and ingesting properly now
J
JI need two reviews pls
Jok one more!
CLooks like a good list of changes. I don't know exactly how to review. I'm particularly interested since I was about to test out gnome-tweaks from a distrobox
CCan I, would I be able to, and/or should I without digging into each linked entry?
JJin this case I think it's unreasonable to expect anyone to actually rebase all those times
Jfor READMEs and stuff you're mostly just reading to make sure it makes sense.
Jwant to do my next one? I'm about to add a small change
CWill read how, then sure 
Jyou click the Files changed tab, and then follow the instructions
CApproved
Did exactly that last time but was too focused on the actual file content and missed the review button up top
Did exactly that last time but was too focused on the actual file content and missed the review button up top
Jcongrats!
CHow long till a (routine?) update gets gnome-tweaks into my image?
C(silverblue-nvidia, 520 channel)
CAnd are the steam-devices rules already in?
Jyeah those come from the config image, you should already have them (the udev rules)
Jthe freshest one is an hour ago so if you do an update you'll be all caught up
CNice
Cleaning up my layered packages right now so good to know
Cleaning up my layered packages right now so good to know
CCan distrobox provide things like fzf or lm_sensors? I think I might have to keep solaar layered for stuff like pointer speed even though the rules should be there
