epel

#355 Transition from Pagure to Forgejo instance
Opened by dherrera. Modified

Open
Close Issue

The Fedora EPEL issue tracker currently resides on the Pagure instance, but as we have talked on previous meetings, we have the opportunity to migrate to the new Forgejo instance early.

I'm hoping that we can get ESC (EPEL Steering Committee) to approve the process and start working on the migration.

Also any feedback on the process is appreciated ^^

TASKS:
- Request for migration.
- Update infrastructure that targets our docs repo / issue tracker.
- Update documentation and mail templates that point to docs repo / issue tracker.
- Migration Announcement.

Things that need to be resolved:
Since we already have an EPEL organization in place in the new forge, we have the possibility to change the structure of our repos.
- One proposal would be to separate ESC issues into an esc repo (https://forge.fedoraproject.org/epel/esc) and the documentation into a docs repo (https://forge.fedoraproject.org/epel/docs).
- The other option is to migrate everything into an epel repo in the epel org (https://forge.fedoraproject.org/epel/epel).

From today's ESC meeting:

!agreed Migrate the EPEL docs source repo to the new area, and leave the issues where they are for now - +1(6) -1(0) 0 (0)

So we can migrate the repo (really a copy) and just leave the issues check box unchecked. Then we can proceed with reconfiguring the docs generation from the new location. Once that is working we can replace the content in this repo with a simple README that points users to the new location.

Metadata Update from @carlwgeorge:
- Issue untagged with: meeting

We discussed this again at today's ESC meeting. Since the docs migration to forge.fpo/epel/docs went smoothly, everyone present was happy with proceeding with moving the issues next. However, since many members will be traveling to FOSDEM at the end of the month, we'll defer the issues migration until the first week of February. In the original description of this issue it's suggested to use forge.fpo/epel/esc, but I think at some point in the meetings we at least discussed using forge.fpo/epel/steering instead. I don't remember if we had consensus, so let's revisit that particular detail at next week's meeting.

Metadata Update from @carlwgeorge:
- Issue tagged with: meeting

https://pagure.io/fedora-qa/issue/836 may be helpful as well (a checklist from qe folks for moving things)

During today's meeting, we agreed unanimously to proceed with forge.fpo/epel/steering.

Metadata Update from @carlwgeorge:
- Issue untagged with: meeting

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/355

Please continue any further discussion there.
Metadata
None
None
None
None
None
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.