New initiative: pagure-to-forgejo (?)

Please note that this is NOT a new project but rather an extension of an existing project pagure-exporter that I developed a couple of years back (Ref. https://communityblog.fedoraproject.org/pagure-exporter-now-available/, https://fedora-arc.readthedocs.io/en/latest/pagure2gitlab/index.html and https://github.com/fedora-infra/pagure-exporter).

What is this initiative about?

pagure-exporter already supports GitLab and now, we want to add support for migrating repository files, data assets, and issue tickets from projects on Pagure to Forgejo.

Why this initiative?

Fedora Project is now moving over to Forgejo as their preferred choice for Dist Git and as we have our assets on Pagure Dist Git, we want a tool to streamline the migration process.

Definition of success

The following points must be satisfied

• ~~Migration functionality of associated Bugzilla tickets of a package from RHBZ to Forgejo~~
• ~~Migration functionality of repository assets from Pagure Dist Git project to Forgejo~~
• ~~Migration functionality of associated metadata from Pagure Dist Git project to Forgejo~~
• Migration functionality of repository assets from Pagure (pagure.io) project to Forgejo
• Migration functionality of issue tickets from Pagure (pagure.io) project to Forgejo
• Explore the migration of private tickets from Pagure to Forgejo with custom namespaces
• Retention of the 100% test coverage of the functional codebase after code changes
• Exhaustive documentation on how the tool can be used both in self-service and automation
• Exploratory testing event within the community for running the tooling and reporting

What are your nice or really nice to have wishes?

• Automation workflow for batch migration of multiple repositories from Pagure to Forgejo
• Migration of static assets like images from the issue ticket body from Pagure to Forgejo

Area/community impacted

Will this initiative impact CentOS, Fedora? All users? All contributors? A group of contributors (which)?

• Fedora Project
  • Packagers
  • Infrastructure
  • Release Engineers
  • Quality assurance

Dependencies

Do this initiative have any dependencies?

• Eh, I don't know.

Skills needed?

• Python
• Git
• Testing
• Understanding of Forgejo API
• Understanding of GitLab API

Person who must or should be involved?

• Eh, I don't know.

Other work that should be completed prior to this initiative?

• Eh, I don't know.

Deadline

Is this initiative under a time constraint? Should it start or end before a certain date?

As soon as possible.