fedora-qa

#839 Migrate fedora-qa to forgejo (without CI)
Opened by kparal. Modified

Open
Close Issue

This repository should be migrated to forgejo as part of migrating all Fedora Quality repositories.

This repository DOES NOT have CI, which makes the migration more straightforward. But it's our primary ticket tracker, so we want to preserve all tickets (including numbers) as part of the migration, and ideally have common pagure.io URLs redirect to the appropriate forge.fp.o URL.

There's a migration checklist and a lot of useful advice in https://pagure.io/fedora-qa/issue/836 , please read that first and follow the steps.

Metadata Update from @kparal:
- Custom field story_points adjusted to 5

What do we want to call the migrated repo? I saw tickets as the name for the main ticketing repo here:
https://forge.fedoraproject.org/server/tickets/issues
(I think I saw it multiple times, but can't find them now)

Other groups chose other names:
https://forge.fedoraproject.org/epel/releng
https://forge.fedoraproject.org/releng/tooling
https://forge.fedoraproject.org/forge/forge

Tickets sounds OK to me, but we can also call it quality (the same as the org), or something else, if anyone has a better idea.

Metadata Update from @kparal:
- Issue marked as blocking: #836

Guess I'm fine with 'tickets'.

This is currently blocked on https://forge.fedoraproject.org/forge/forge/issues/306

Guess I'm fine with 'tickets'.

A suggestion from Kashyap is planning, which they use themselves in risc-v/planning.
Edited by kparal

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/quality/tickets/issues/839

Please continue any further discussion there.
Metadata
None

meta task

None
None
Low
5
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.