I didn't realize that general migrations were already started.

Is there a quality org on forgejo that this should be migrated to? I'm not seeing one at the moment

Well, I don't know if there's going to be a "This Is Your Cue To Start Migrating" signal exactly. I think simple projects can already be moved if you feel like it. server issue repo is moved already, for instance.

I wasn't planning to actually do any migrations yet, though, I just wanted to file the tickets so we can Agile them...

There isn't an org yet, no. @kparal , were we requesting one? I can't remember.

No, I don't think we requested the org yet. I was planning to look into it and figure out the required structure and naming and everything first.

OK, I thought that the issue was more of a "migrate this now" kind of thing but I misunderstood.

I guess the next question is whether this belongs in the new forge as a Fedora Quality project. I don't have any strong opinions on whether I move it to a personal account or to the new forge once that becomes an option.

yeah, sorry, I should have worded a bit more carefully.

Note: There's a migration checklist and a lot of useful advice in https://pagure.io/fedora-qa/issue/836 , in case we want to move it under the quality org

@adamwill It's probably your call whether you see us using this project in future or not (and therefore whether we should migrate it to Forge or not). My assumption is that we're unlikely to follow up on this at this moment, and so we can leave it here (or wherever Tim decides to move it to).

I'd say let's leave it to @tflink , since it's really still more of a personal project at this point - we didn't ultimately integrate it into any team workflow yet. Is that OK with you @tflink ?

Right now I'm going to put this onto the "don't migrate" pile in our ticket. We can talk about this at any time, as long as Pagure is around (which will likely still be a long time).

I've migrated the project to https://codeberg.org/tflink/openqa_classifier