From Fedora Project Wiki
m (→Team) |
m (Jflory7 moved page Objectives/Git Forge Initiative 2025 to Initiatives/Git Forge Initiative 2025: Moved into Initiatives namespace, Objectives namespace is deprecated) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 6: | Line 6: | ||
== Mission == | == Mission == | ||
To consolidate Fedora's source code management, issue tracking, and project hosting onto a single Forgejo platform deployed on the Fedora OpenShift Cluster, replacing Bugzilla and sun-setting Pagure (src.fedoraproject.org and pagure.io), while offering a migration path for Fedora Project repositories currently hosted on external platforms. | To consolidate Fedora's source code management, issue tracking, and project hosting onto a single Forgejo platform deployed on the Fedora OpenShift Cluster, replacing Bugzilla and sun-setting Pagure (src.fedoraproject.org and pagure.io), while offering a migration path for Fedora Project repositories currently hosted on external platforms. | ||
== Plan == | |||
1. Deployment of Forgejo: | |||
* Deploy a single instance of Forgejo on Fedora Infrastructure. | |||
* Configure this instance to host repositories and groups directly related to the Fedora Project's core development and infrastructure. | |||
* Include the package source repositories (currently on src.fedoraproject.org) within this Forgejo instance. | |||
2. Migration of Fedora Project Repositories: | |||
* Migrate all relevant Fedora Project repositories and groups from Pagure.io to the new Forgejo instance. | |||
* Establish organizations within Forgejo to mirror existing team structures. | |||
3. Migration of Package Sources: | |||
* Migrate all package sources from src.fedoraproject.org to a dedicated organization within the Forgejo instance. | |||
* Use Forgejo teams to manage permissions on the package sources | |||
4. Decommissioning Pagure.io and src.fedoraproject.org: | |||
* Provide a migration window for non-Fedora Project repositories on Pagure.io to transition to alternative hosting platforms (e.g., Codeberg, GitLab.com, GitHub.com). | |||
* Provide a migration window for Fedora Project repos to migrate to Forgejo | |||
* Disable Pagure.io and src.fedoraproject.org after the migration period. | |||
* Archive or delete the data from the decommissioned platforms. | |||
5. Backend Tooling Development: | |||
* Develop necessary backend tooling to ensure seamless integration between Forgejo and Fedora's existing infrastructure and workflows. | |||
= Team = | = Team = | ||
| Line 11: | Line 30: | ||
* Lead: [[User:ryanlerch|Ryan Lerch]] | * Lead: [[User:ryanlerch|Ryan Lerch]] | ||
* Product Owner: [[User:Humaton | Tomáš Hrčka]] | * Product Owner: [[User:Humaton | Tomáš Hrčka]] | ||
* Council Executive Sponsor: [[User:Amoloney | * Council Executive Sponsor: [[User:Amoloney | Aoife Moloney]] | ||
* Contributors: | * Contributors: | ||
** [[User:lenkaseg|Lenka Segura]] | ** [[User:lenkaseg|Lenka Segura]] | ||
** [[User:nphilipp|nphilipp]] | ** [[User:nphilipp|nphilipp]] | ||
** [[User:dkirwan|David Kirwan]] | ** [[User:dkirwan|David Kirwan]] | ||
** Yaash | ** [[User:Thisisyaash|Yaash]] | ||
** [[User:ryanlerch|Ryan Lerch]] | ** [[User:ryanlerch|Ryan Lerch]] | ||
** [[User:Humaton | Tomáš Hrčka]] | ** [[User:Humaton | Tomáš Hrčka]] | ||
= Milestones & Timeframe = | = Milestones & Timeframe = | ||
By Fedora Linux 42 Release... | |||
* Forgejo will be available for general project hosting | |||
By Fedora Linux 43 Release... | |||
* The dist-git workflow will be replicated in Forgejo and will mirror the release pattern | |||
By Fedora Linux 44 Release... | |||
* Forgejo dist-git will be used in the official release building | |||
= Links = | = Links = | ||
| Line 29: | Line 57: | ||
* Regular weekly meeting: https://calendar.fedoraproject.org/Fedora%20release/#m10970 | * Regular weekly meeting: https://calendar.fedoraproject.org/Fedora%20release/#m10970 | ||
* Matrix Channel for Team Chat (all welcome): https://matrix.to/#/#fedora-forgejo:fedora.im | * Matrix Channel for Team Chat (all welcome): https://matrix.to/#/#fedora-forgejo:fedora.im | ||
* Flock to Fedora, June 5 - 7: BoF, Several talks submitted, general discussion | |||
== ARC Investigations == | == ARC Investigations == | ||
* https://fedora-arc.readthedocs.io/en/latest/dist-git-comparison/index.html | * https://fedora-arc.readthedocs.io/en/latest/dist-git-comparison/index.html | ||
* https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html | * https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html | ||
Latest revision as of 15:25, 26 February 2025
Purpose
Vision
To empower Fedora developers and the Fedora community with a streamlined workflow through a consolidated Git source control and issue tracking solution, powered by Forgejo on Fedora Infrastructure.
Mission
To consolidate Fedora's source code management, issue tracking, and project hosting onto a single Forgejo platform deployed on the Fedora OpenShift Cluster, replacing Bugzilla and sun-setting Pagure (src.fedoraproject.org and pagure.io), while offering a migration path for Fedora Project repositories currently hosted on external platforms.
Plan
1. Deployment of Forgejo:
- Deploy a single instance of Forgejo on Fedora Infrastructure.
- Configure this instance to host repositories and groups directly related to the Fedora Project's core development and infrastructure.
- Include the package source repositories (currently on src.fedoraproject.org) within this Forgejo instance.
2. Migration of Fedora Project Repositories:
- Migrate all relevant Fedora Project repositories and groups from Pagure.io to the new Forgejo instance.
- Establish organizations within Forgejo to mirror existing team structures.
3. Migration of Package Sources:
- Migrate all package sources from src.fedoraproject.org to a dedicated organization within the Forgejo instance.
- Use Forgejo teams to manage permissions on the package sources
4. Decommissioning Pagure.io and src.fedoraproject.org:
- Provide a migration window for non-Fedora Project repositories on Pagure.io to transition to alternative hosting platforms (e.g., Codeberg, GitLab.com, GitHub.com).
- Provide a migration window for Fedora Project repos to migrate to Forgejo
- Disable Pagure.io and src.fedoraproject.org after the migration period.
- Archive or delete the data from the decommissioned platforms.
5. Backend Tooling Development:
- Develop necessary backend tooling to ensure seamless integration between Forgejo and Fedora's existing infrastructure and workflows.
Team
- Lead: Ryan Lerch
- Product Owner: Tomáš Hrčka
- Council Executive Sponsor: Aoife Moloney
- Contributors:
Milestones & Timeframe
By Fedora Linux 42 Release...
- Forgejo will be available for general project hosting
By Fedora Linux 43 Release...
- The dist-git workflow will be replicated in Forgejo and will mirror the release pattern
By Fedora Linux 44 Release...
- Forgejo dist-git will be used in the official release building
Links
Source & Trackers
- The Fedora org on codeberg contains a few in-progess repos for this initiative - https://codeberg.org/fedora/
- Pagure repo (contains some prelim tracking) - https://pagure.io/fedora-infra/forgejo-deployment
Communication
- Regular weekly meeting: https://calendar.fedoraproject.org/Fedora%20release/#m10970
- Matrix Channel for Team Chat (all welcome): https://matrix.to/#/#fedora-forgejo:fedora.im
- Flock to Fedora, June 5 - 7: BoF, Several talks submitted, general discussion
