Fedora Moves towards Forgejo

I want to thank everyone involved in the requirements gathering and analysis process. Never in Fedora have I seen a project-wide decision be made with this level of research and discussion. It has been a lot of information, but I really like how we have done this in the open and really making sure everyone’s voice is heard.

When we started down the path of finding a replacement for Pagure, I personally felt the only viable option that existed was GitLab CE. I will be honest and say that I was not particularly excited about that being the only option. GitLab’s open core approach was disconcerting to me. Would we find ourselves stuck at some point unable to extend functionality because what we were trying to do already existed in the commercial product? Would GitLab entertain us extending the community edition far? Would that even work for us?

On the other hand, I had never heard of Forgejo until we were in these discussions. The more I learned about it, the more I felt it fit Fedora’s needs better than GitLab. The one thing that sticks in my mind is that it is younger than other forges and just doesn’t have the proven track record.

That said, I am excited for us to move to Forgejo and extend it for our needs. I hope we, as Fedora, can extend it to the point where even Red Hat could consider it for use over GitLab for RHEL and CentOS Stream (on their own hosted instances, of course).

Thank you again to everyone involved in the research and thank you to the community for providing all of the input to help make this decision. Now it’s time for the hard work as well as thinking about our next infrastructure challenges (like Bugzilla :slight_smile: ).

7 Likes