Jcc @KyleGospo @akdev
ADope
BThat was a simple process, have created a custom image with it! I'll go watch the video Jorge had put up a while ago to learn more about how to customize it now.
FLast video I watched, they make a custom image from bluefin. While it takes less work, I would rather use starting point If have a need to create a custom image (right now, silverblue-main & bazzite-silverblue are making me happy)
Xidk if jorge has really made a video about customizing startingpoint-based images, but at least not about the rewrite
Xi suggest you read the docs
GSo rpm-ostree bundles bootc now?
B@fiftydinar & @hermmm, sorry, I don't understand that, I'll check the documentation for now to understand what you mean.
KVery cool this is there, but very unfortunate that it breaks layered packages
KOr rather, doesn't support them
Bvery nice
WIs anyone familiar with making gnome extensions? Or working on them? One of my favorite extensions' repository is "archive mode" and so I'm really tempted to fork it and try and do the gnome45 port myself
WJust wanted to know if anyone is familiar with it if I run into any huge roadblocks to rubber ducky.
BI'm dont have experience, but they have a guide on porting to 45. maybe that helps a little https://gjs.guide/extensions/upgrading/gnome-shell-45.html
Wyea, I knew guides existed. I expect it to be relatively straight forward. And from the looks of it, its a really stupid simple extension so my hope is it will (mostly indefinitely) be good by just porting it
Wwas more just pre-emptively putting feelers out for a good rubber ducky
Bi see. you can do it! 
WWhands down the best weather extension
Wand its repo is in archive mode
Wso just gonna fork it and try and port it
Woh... it also supposedly has a memory leak
Wif I can handle the port, I may try and tackle that.
Wits like 3 files, how hard can it be right?
Bi see somebody picked it up at github https://github.com/gilvbp/gnome-shell-extension-openweather-next/tree/dev
Bdon't know how that will go, its few days old
WPart of me is relieved that I have options
Wother part of me is annoyed cause I was hoping to hijack a very popular OSS project for my own for the resume boost
Wheh, its so new that the readme still points to the gitlab
Wthanks for pointing that out, I'll keep an eye on it
WThe only thing the dude has done so far is claim it as his own. If he doesn't move on it before we get close to 45, I may just do the same and port + there is a PR on the old repo for someone saying they think they fixed the memory leak
Wso it seems like an easy-ish slam dunk
Bgo for it
ADon’t think that guy knows how copyright works
Ayou can’t just change copyright tags on code you forked lmao
NLMAO
Whow... do you handle that?
W(as someone likely about to do the same thing, fork that exact code base and move forward with it)
AYou leave all the copyright notices in place and add your own in addition to the original for code that you wrote
AYou only hold the copyright for portions you write not the whole codebase
AYou’re merely a licensee under GPL protections
AThe additional copyright notice is also not strictly required as the git log works to prove you own the copyright of modified lines
Wyea, that fork looked less than great
Was mentioned, it still points to the gitlab which is readonly
Wbut its also like days old
WMy bet is that a lot of folks are going to try and make their own
Wcause openweather was wildly popular from what I can tell
Wwith it going readonly there will be a fracturing
Bwe want waffleophagus-openweather-next
