I kinda like it just being a png though, because it's easily shareable,,, and I can make it in Figma
I kinda like it just being a png though, because it's easily shareable,,, and I can make it in Figma.
XThose logos are customized to fit the colors inside the same main Figma frame, but it would have to be done separately if it wasn't a image.
APNG is definitely the easiest solution. Anything else would require the ability to use CSS styles to create something like https://www.fedoraproject.org/workstation/ and that's just so much work. 
BI've got some PRs needing approval:
- 2.5Gbit USB udev rules https://github.com/ublue-os/config/pull/36
- standardize path and justfile refactoring https://github.com/ublue-os/config/pull/42
- nvidia justfile removal after config PR 42 https://github.com/ublue-os/nvidia/pull/101
AI checked the last two PRs, they both look ready to me. 
Bthank you, I definitely appreciate the feedback you've been giving to get this stuff done, but now I need PR approval from someone with commit in those repos
AYep! While we wait... I am working on improving the way people fork
A:
While we wait... I am working on improving the way people fork startingpoint and I'm not sure which path is cleaner, so let's hear opinions:A:
- Mark the GitHub workflow as "only build the
mainbranch". - Users fork the
startingpointrepo. - They turn it away from "template" mode into regular repo mode.
- They create a branch called
upstream-mainand link it toupstream/main. - They perform their own edits in
main. - They periodically sync
upstream-mainand then rebase their ownmainontoupstream-mainto get the latest template improvements.
- Mark the GitHub workflow as "only build the
buildbranch". - Users fork the
startingpointrepo. - They turn it away from "template" mode into regular repo mode.
- They link
maintoupstreamfor easy syncing. Although they can do that effortlessly via the GitHub web UI with one click since that's doable by default. - They create a
buildbranch and perform their own edits there. - They periodically sync
mainand then rebase their ownbuildontomainto get the latest template improvements.
build idea (B) because the naming is more deliberate and clear. Syncing via web UI also becomes possible. I kinda wish startingpoint's main branch was named template instead of main.
S@j0rge is busy gaming if the discord status is right lol.
Sbut took a look at them and they make sense to me, the changes make it much cleaner imo and more traceable if any problems did arise.
ASeeing it point by point like that made it easier to decide... I think a dedicated
build branch makes the most sense. It also allows us to move away from main to rename the main branch to template in the future.SI think the naming comes down to the actual build process, we did change the name of the Kinoite builds at one point and it went a little wonky... not sure the issue is something that can fixed this side. It's like they have a "required" way of doing things (just my take on it though).
AYeah those "required names" are specified inside the
.github/ directory's workflow files. This is about making it easier to work with the ublue-os/startingpoint repo, for people who decide to clone it and make their own uBlue images. SAhh right, not looked into it myself, just going from past experience as it were lol
AYeah it's all very interlinked in the main and nvidia repos.
Jgot em!
Joh I went in the wrong order though so I'll rekick off main/nvidia
BI think we were discussing "merge" vs "squash merge" the other day... i think it defaults to either last thing you did or last thing done on the repo, one of two...
because I noticed a main/nvidia PR merge was squashed but the recent config merges are not quashed
because I noticed a main/nvidia PR merge was squashed but the recent config merges are not quashed
FIs it possible to fix 3.5mm front panel not working from Realtek sound card inside the ISO?
This is the fix:
https://discussion.fedoraproject.org/t/front-panel-headphone-jack-is-not-being-detected/78370/2
It doesn't work on installed system due to r/o path it needs to modify, /usr/ something, forgot which
This is the fix:
https://discussion.fedoraproject.org/t/front-panel-headphone-jack-is-not-being-detected/78370/2
It doesn't work on installed system due to r/o path it needs to modify, /usr/ something, forgot which
Fedora Discussion
Ok. I was able to fix this. 1 - install alsa-tools: $ sudo dnf install alsa-tools; 2 - open HDA Jack Retask: $ hdajackretask; 3 - at the top, verify if the right codec is selected in “Select a codec”. On my case, the right one is “Realtek ALC897”; 4 - on “options”, at the right, click on “Set model=auto” and “advanced override”; 5 - on “pin...
Jyeah I didn't bother with MQ on config
JBUT IF YOU WANT TO DO IT I AM DOWN!
Bi just wanted you to squash my ugly commits LOL so i look more pro 
JPR in the MQ fixes and I can turn it on
Jlooks like we can't without it
Bwhy?
Jthere's no optin in there afaict
Bi mean, i'm fine with merge queue, just curious what that meant
Bhuh wild
Jyeah we can't select a custom merge method without the MQ
Jbut I've turned it on in the settings so we just need to PR the snippet in the build,yml
J
JI truly do not understand this option
Bmaybe you want to merge stuff that's expected to fail builds?
Jyeah but there's always the bypass protections checkbox, just seems like an odd option
AYes indeed I remember it defaulting to the last thing that was done, which is why I often remind people gently to check the setting lol. GitHub is annoying like that.
BI'm waiting for your PR to approve it
AThis is the last
https://github.com/ublue-os/startingpoint/pull/76
startingpoint PR. It improves the workflow for people who fork the repo, since it's currently hard to work with downstream forks.https://github.com/ublue-os/startingpoint/pull/76
AIt's a small change. Mostly interested in any other ideas or feedback.
Jyou might need to link up to docs or explain how to lifecycle manage having a build branch
AYeah, next week I plan to update the
making-your-own webpage with instructions for that management.AI placed a visible description in the readme of startingpoint itself too, the "warning" in the Getting started section, so that nobody can miss it:
https://github.com/ublue-os/startingpoint/blob/f13e486ad80ced06e58b86232e4101ed1d0165b0/README.md#getting-started
https://github.com/ublue-os/startingpoint/blob/f13e486ad80ced06e58b86232e4101ed1d0165b0/README.md#getting-started
BI'm pretty excited, with all these changes to config/nvidia... we're in even better shape to add more akmods
AYeah and I am hyped for the universal signing key so we can easily add akmods that all work with the same secureboot key. drools
JGitHub
An OCI base image of Fedora with batteries included - Pull requests · ublue-os/main
Jok 2 incoming
Bon it
J@bsherman don't approve yet, let's have arcitec take a look
Jeven tho the perms aren't there this is a good way to learn
Jthen you do the final, sound good?
Bwaiting on alsa-tools
Balready did the new form field for issues template