Tag: git forge

CPE Update Q2 2024

This is a summary of the work done on initiatives by the CPE Team. Every quarter, the CPE team works together with CentOS Project and Fedora Project community leaders and representatives to choose projects that will be being worked upon in that quarter. The CPE team is then split into multiple smaller sub-teams that will work on the chosen initiatives + day-to-day work that needs to be done. Some of the sub-teams  are dedicated to the continuous efforts in the team whilst some are created only for the initiative purposes.

This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.

Continue reading

2024 Git Forge Evaluation

Vol. I – Fedora Council 2024 Hackfest

During the Council’s February 2024 hackfest, we discussed the future of Fedora’s git forge – that is, the platform Fedora uses for version control and tracking for packages, source code, documentation, and more. This topic has been around for quite some time. If you are just coming into this conversation, or would like a refresher, #git-forge-future is a good place to start.

Instead of one huge post, the Fedora Council divided the follow-ups from our hack-fest into a mini-series of posts throughout April that will cover all the topics we discussed and made decisions on. In each post, we will walk through one core topic, and share our discussion and thought process on how we reached our outcomes. The first in this series, because why not start strong 🙂 , is an update on our git forge evaluation. Read on for important information.

Continue reading

GitLab available for Fedora

I’m excited to tell you we will have hosted GitLab available for the Fedora community. GitLab is providing this to Fedora as part of their GitLab for Open Source program. With this, our community has an additional option for code and project management.

The GitLab instance will available for any Fedora-related activities. After we complete connecting the authentication system, you will log in with your Fedora account and create projects as you need them. If your team wants a group within our namespace, we can create that for you. We will follow up with guidance on how to make those requests, but in the short term, you can open a ticket in the infrastructure tracker in Pagure.

Continue reading

Git repo branch name changes

The Fedora Project envisions a world where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities.

The Fedora Project Vision

In line with the Fedora vision, we just completed some changes to the git branch names used on src.fedoraproject.org and elsewhere. We removed the “master” branch for those repositories. For rpms and containers, the default branch is now named “rawhide”, with a symref (alias) of “main”. For flatpaks, “stable” is the default/only branch. The fedpkg tool is updated on all supported released to accommodate this change.

For now module repos are unchanged. We are awaiting improvements in the branch/repo requesting tool to allow module owners to request only those specific named branch streams, since “main” and “rawhide” don’t make sense in that context.

For a list of other impacted repositories, see the change proposal. Of course, other repos have been migrated by their owners independently.

If you have a repo checked out with the master branch still, you can run: git fetch && git switch main

This work is part of a larger effort across the technology industry to be more inclusive in the language we use. See Rich Bowen’s Nest With Fedora keynote, for example. If you encounter any trouble, please file a ticket in the infrastructure issue tracker.

GitLab AMA follow-up

Last month, we invited folks from GitLab to a public Ask Me Anything (AMA) session. We collected questions from the community in advance about the upcoming Fedora migration to GitLab. 

The Community Platform Engineering (CPE) team has been working with GitLab for the past few months on understanding and troubleshooting the technical challenges associated with the migration. This AMA was a natural next step to enable the community to participate and give the Fedora community a chance to get to know some of the GitLab team members who are supporting the migration process.

Continue reading

Fedora Council and the git forge

I love the passion the Fedora Project inspires in our community. That passion has been on display in the past week as the community has discussed the decision to move forward with GitLab as our git forge. I want to be very clear: we, the Fedora Council, dropped the ball on communication here. No one intended to be secretive or hide from the community, but we should have done better.

Continue reading

Making a git forge decision

After evaluating over 300 user stories from multiple stakeholders, the Community Platform Engineering (CPE) team have aligned on a decision for the git forge that CPE will operate for the coming years. We are opting for GitLab for our dist git and project hosting and will continue to run pagure.io with community assistance.

Continue reading

Git Forge requirements

This document lays out a problem statement, requirements, and constraints according to the Open Decision Framework. The aim is to arrive at a transparent decision about the future of a git forge for the communities that represent the platforms that the Community Platform Engineering (CPE) team manages. Those communities are the CentOS and Fedora platforms and also include the Red Hat Enterprise Linux (RHEL) platform from a tooling and integration perspective. This document is the first in a series of documents capturing the conversation about the problems we face and driving the conversation to implement the decisions captured.

Continue reading

Copyright © 2024 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑