Yep, I think we should do this. I tried to check if there are any private issues, but I don't see a way to filter by that. If not, I think we should just do the migration and post links to the new tickets in all the open issues and make this read-only.

I don't think that there's much automation. Mostly just links and manual processes, and we'll have to adjust those.

There are two tickets that are private. One looked incorrectly private and I fixed it, the other is a bit weird (there's no obvious reason for it to be private, with no private details). We can probably just make it public, but I'd like to talk to @kevin about it first.

We shouldn't have anymore private tickets now.

See https://forge.fedoraproject.org/infra/tickets/issues/13277. This needs to be coordinated with @frostyx so the necessary changes can be made in https://github.com/FrostyX/fedora-review-service.

Thanks @gotmax23 . I've subscribed to the forge ticket for updates.

For later: we do have a script here to mass comment on tickets on pagure after the migration to the forge:

https://forge.fedoraproject.org/join/Fedora-Join/src/branch/main/scripts/CommentPagureForgejo/script.py

See https://forge.fedoraproject.org/infra/tickets/issues/13277. This needs to be coordinated with @frostyx so the necessary changes can be made in https://github.com/FrostyX/fedora-review-service.

Btw https://github.com/FrostyX/fedora-review-service/pull/74

This needs to be coordinated with @frostyx

As @lecris said, the Fedora Review Service PR is ready.
Also, I recently discovered https://github.com/FrostyX/fedora-review-service/issues/76

So as far as I am concerned, the sooner the migration happens, the better. And probably no need to let me know in advance, just ping me once I should deploy the new Fedora Review Service version, and I can do it fairly quickly.

For later: we do have a script here to mass comment on tickets on pagure after the migration to the forge:

If we can limit this to only apply to currently open tickets, that's fine, but otherwise, let's avoid it to so we don't spam everyone subscribed by bumping all the closed tickets.

Re. the request to create a new Forgejo team in the packaging org for packager group sponsors, it seems that didn't materialize, and Infra is busy on other changes to the accounts system, so I think we can just manage access by adding direct collaborators using the Forgejo API for now. I already have a script.

The other issue is how to handle notifications. Pagure has functionality to automatically send all issues to a mailing list (packager-sponsors AT fedoraproject.org, in this case). I suppose we can just send a email to all sponsors that they have to manually log in and push the Watch button in the Forge repo. Meh.

I suppose we can just send a email to all sponsors that they have to manually log in and push the Watch button in the Forge repo. Meh.

Oof, that doesn’t sound particularly reliable or sustainable.

I suppose we can just send a email to all sponsors that they have to manually log in and push the Watch button in the Forge repo. Meh.

Oof, that doesn’t sound particularly reliable or sustainable.

Honestly, notifications that integrate into the forge notifications system sounds preferable to a mailing list that I cannot unsubscribe from :)

Oof, that doesn’t sound particularly reliable or sustainable.

+1

If nobody thinks of something better, and this indeed turns out to be the problem, the worst case scenario we can have some script that compares the list of sponsors and watchers of the repo, run it from time to time and ask people nicely to subscribe.

But yeah, it would be much better if we could just automatically subscribe new sponsors to the repo or listen to Forge messages on Fedora Messaging and relay the relevant ones to mailing list or wherever.

I looked at the group thing and setup a test in staging. If it works for @gotmax23 I think I can setup production tomorrow...

The repository has been migrated: https://forge.fedoraproject.org/packaging/sponsors

All sponsors of the packager group were given permissions on the new repository. I updated the README and description in the Pagure repo to point to the new one, and I'll make the old issue tracker read only now. I'll send out an announcement later. Thanks everyone!