This page is to track requirements and progress on Fedora Git Forge change decision

Requirements

What	Why
Associates must be able to use SSO to sign in	So that RH as a business is protected against harmful activity from its employees
Example	Example

I want to be able to create branches via an API
- So that git branch management can be automated

I want to know 6 months in advance if CPE move git forge
- So that my team has time to adopt our dependant services to the new offering in a timely manner

I want a modern git workflow
- So that I can use upstream practices in RHEL development for quicker delivery of features & fixes

What	Why
I want to sign in using the SSO of my account system	So that I can access the git forge repos and contribute to RHEL
I want an API to interact programmatically with the forge	So that I can integrate any/my application with the gitforge
I need to be able to port patches between projects S	o that I can easily collaborate between projects
I need CentOS & Fedora to be integrated in gitforge	So I can push requests from one OS to the other
I need to be able to see SIG groups	So that I know what group to reach out to to ask for help
I will see inline images against comments	So that it is easier for me to see communications and status’s of issues
The gitforge supports a message bus	So that I can continue to create formatted messages and provide alerts and metrics
I want to be able to create a bot/service account	That integrates with the gitforge in the same way as a human does
I want to be able to make suggestions to fedora docs	Without having to set up an entire infrastructure for making low-friction contributions