I will probably move it out of Fedora infrastructure.

I'm not sure I agree that's a good idea. It's a critical part of how Fedora live images function. Why would we not want it to be in Fedora's infrastructure?

So? That's not a good reason for it to be there, we depend on plenty of things that aren't hosted in Fedora infrastructure.

The Fedora Forge's restrictions make it unappealing (it doesn't belong in releng, and since the deliverables organization that was originally requested was blocked, there isn't a place that makes sense there), and I've wanted to add useful CI to this project for a while, but can't because with Zuul CI going away, there's no pathway to native VM-based CI. I don't want to go back to crappy duffy-style hacks like we did for Pagure CI, either.

If you really think it should be in Fedora Forge, it needs a place that actually makes sense. Release Engineering isn't it, though.

Well, for VM-based CI there's https://github.com/packit/packit-service/issues/2999#issuecomment-3935950993 . Basically, use testing-farm . I haven't tried this, but you could ask @lecris for some details.

I don't really care about the question of what organization stuff goes into as much as you seem to, but I'm fine with any solution to it that makes you happy.

Yes, testing-farm is already available on forge, and we figured out many kinks over with atomic-desktops:
- https://forge.fedoraproject.org/ci/testing-farm
- https://forge.fedoraproject.org/atomic-desktops/config/pulls/767
- https://forge.fedoraproject.org/ci/_fedora-kiwi-descriptions/src/branch/testing-farm

It'd be great if we could document it somewhere, I guess...