Soliciting volunteers to test Git forge scenarios

Share it

Call for Volunteers to Experiment with Git Repository Scenarios

Are you interested in exploring and testing Git forge scenarios? After insightful talks by @t0xic0der and @humaton at the Fedora Linux Release Party 40 and Flock To Fedora 2024, we are excited to extend our investigation to all contributors in the Fedora Project. Visit the ARC initiative page to access or define the use case requirements for the replacement of the Git forge. As part of this endeavor, we have established community deployments for Forgejo and GitLab.

If you wish to access the GitLab instance, note that it requires manual account approval. Here’s how you can request an account:

Sign up on the GitLab instance.
Create a ticket on the Fedora Infrastructure issue tracker with “Approve my user on GitLab test instance” as the summary.
Choose the ‘gitlab_testing_request’ template under Types.
Complete the template and wait for account approval.

It’s important to highlight that our test GitLab instance only supports HTTPS pushes, not SSH pushes.

On the other hand, setting up an account on the Forgejo test instance, connected to our staging Fedora Account System, is simpler. Here’s what you need to do:

Create an account on the staging Fedora Account System (skip this if you already have one).
Use the “Sign In with Fedora Accounts” button to log in to the Forgejo test instance with your staging Fedora account.

Similar to the GitLab instance, our Forgejo test environment does not allow SSH pushes; only HTTPS is supported. For security, you’ll need to generate a token in “Settings->Application->Access Tokens” for password entry during HTTPS pushes.

Once you’ve tested both platforms, share your feedback on the suitability of GitLab or Forgejo for the scenarios you explored in the discussion thread provided.

For any queries or assistance, feel free to engage with us in this discussion thread or join our Matrix ARC investigation room.