---
# System prepended metadata

title: GitForge ARC investigation

---

## GitForge ARC investigation

### Definition

Git forge is a git repository hosting service that provides extended funcionality to the basic git hosting like issue trackers, background job runners or artifact storage.

### Purpose:

Purpose of this investigation is to provide comprehensive comparisson of proposed solutions not a recomendation for one or another. 

### Resources

https://gitlab.com/rluna-gitlab/gitlab-ce
https://forgejo.org/
https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html

### Background

Fedora Council has announced intent to migrate from Pagure.io as a git repository hosting. 
They are suggesting 2 implementations of Git as a service that can be hosted on Fedora's Infrastructure, GitLab Communitty edition and Forgejo.


### Requirements
These set of abstract requirements was approved by council. This set does not represent feature set but high level overview. 

 1. Suitability for dist-git and src.fedoraproject.org replacement

 2. Suitability for replacement of bugzilla for packaging issues and review process

 3. Suitability for replacement of Pagure and bugzilla for release issues (change process, blocker bugs, etc)
     * https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
     * https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

 4. Suitability for replacement of Pagure for SIG and Team ticket tracking (e.g. FESCo tracker)

 5. Cost of hosting and maintenance (hardware + time and resources from CPE and wider infrastructure team)

 6. Ease of migration from current Pagure,github and gitlab.com

 7. Ease of extension and enhancement — can we improve things ourselves to add missing features / features that are really cool and useful like CI integration?



 9. New features like Asciidoc support, Online editor and others to make things easier for the Fedora teams and their workflows.

10. Estimate Future risk for Fedora project and Infrastructure team
    1. GitLab: open core squeeze and enshittification of services
    2. Forgejo: community health and sustainability as a younger project


11. Spam fighting

Consider previous ARC investigations regarding dist-git and pagure migration and answer the following questions for both proposed sollutions.

### Definition of Done

Have a document for each of proposed solutions that answers all requirements questions. 

#### milestones
1. flock have a comprehensive presentation/workshop
2. Fedora 41 release party talk
3. PoC For 42
4. Migration plan
5. Change proposal for fedora 43 

### Key Stakeholders
Representatives from various Fedora Teams:
* Infrastructure
* Rel-Eng
* QA
* Packaging
* Design
* Websites & Apps
* Docs
* Program Mgmt
* Marketing
* SIGs, Editions & Labs


## Venues for announcement
* devel-announce
* fpc email list
* discussions.fpo under infrastructure-projects tag

## How we will be gathering requirements
We would like folks to share their use cases with us on how they interact with git. We will be moderating repies on both the mailing lists and discussions.fpo. We will be collecting the requirements people share to create a more definitive list. The feedback period will be set until the end of April, in an effort to have a more defined set of requirements re-shared to the community by the early May on what the ARC team will investigate both Forgejo and GitLab

## How to get involved in the investigation


Notes for timeline
13 weeks to flock
