Bluefin Move
@Aurora Maintainer @Bazzite Maintainer @Bluefin Maintainer I thought we had agreed on giving bluefin time to move our stuff before making drastic changes?
NHow much time are you thinking you will need?
JWe talked about end of the year, post kubecon
NI don't see how that would be a problem. I created the vote to get the process moving. We can always delay implementation a bit to allow a smoother transition.
NObviously others can weigh in.
Jwe need a plan for all the other stuff
Jhomebrew tap, etc?
NWhat is the scope you are looking at that will move with Bluefin? I understood it as just being the Bluefin repo.
Jthere are 2 repos left
Jbut what do we do with the homebrew tap and the artwork repo?
NDo we know if any of the main images or Bazzite rely on them? @Kyle Gospo
JNo, you don't use them
NI don't see a reason why they couldn't move then if that is desired.
RI don't think we use that at all in our images. Just people who stumbled upon the repo
Jright
Jand we're not shipping it on any image actually, so those could both move?
Jthe experimental tap is there too
NWe can put together a deprecation notice for folks that use them. Obviously that is something that should be agreed on by more than just me.
Jthey never went production there's nothing to deprecate
Tartwork is gonna be fine, afaik its only referenced in the tap, right?
and the tap isn't being shipped so I think that's okay
and the tap isn't being shipped so I think that's okay
Twe can add an update for every package in the tap saying "yo we moved"
NI see. If it never went GA, it should be fine to move in my mind.
Jright, ok we'll move them as soon as we can.
NSure, let us know how we can help.
KBazzite uses homebrew
KOr at least should be using that tap
KArt is free to go anywhere
NI know we use the package, I didn't realize we use the tap.
N(why I asked lol)
RFor what does bazzite use it?
JThey just haven't gotten around to using it yet
