Tag: Pagure

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

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.

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

Two shell functions to simplify Pagure pull request reviews

A project maintainer of an active open source project will learn new git magic tricks. Every maintainer also has their own procedure of reviewing and testing pull requests. To do this, a maintainer may have an incantation of git commands to set things up exactly the way they want.

But there is no easy, one-click way of doing this. Some commands must be run a specific order to pull a fresh local copy of a pull request. While reviewing several pull requests in a week, I realized a set of commands I was using frequently and converted them into these shell functions:

Continue reading

Contribution opportunity! Quick docs!

Quick docs are meant to be short articles on the official Fedora documentation site that cover commonly used workflows/tools.

Unlike wiki pages which are generally unreviewed, information on quick-docs follows the PR (peer-review + pull request) process. So the new information that is added there is more trustworthy and should be too, given that quick docs is listed on the official Fedora documentation website.

Continue reading

Introducing Contributor Stories

The Fedora Project community is a strong, caring community sharing the same Four Foundations: Freedom, Friends, Features, and First. Becoming friends is a natural consequence of our work as contributors, working together to advance free software. All of us have a good memory about someone or maybe a funny or inspirational moment with another contributor.

Contributor Stories are just that: the record of our best moments with our Fedora friends. The story can be about our work in Fedora or something personal or unique which you would like to share with the community. Contributor Stories are a part of Fedora Appreciation Week, starting in November 2018.

Why have Contributor Stories?

The purpose of Contributor Stories is to recognize a contributor who has impacted you at any time in Fedora. Let them know what you are thankful for and share a common memory or experience you remember. Taking the time to single out someone to give thanks is one of the best ways to make a personal impact.

Continue reading

Migration from Trac / FedoraHosted

Earlier in Kevin’s announcement,  it was announced that Fedora Infrastructure will retire fedorahosted.org. They urge all its active projects to move to pagure.io (or any other place they feel best meets their needs). The tentatively scheduled retirement date is February 28th, 2017.

After this announcement, there are many discussions and movement in different sub-projects.  Some teams have already completed the migration successfully.

Continue reading

FedoraHosted sunset: 2017-02-28

Fedora Infrastructure currently maintains two different sites for general open source code hosting: fedorahosted.org and pagure.io.

Fedorahosted.org was established in late 2007 using Trac for issues and wiki pages, Fedora Account System groups for access control and source uploads, and offering a variety of Source Control Management tools (git, svn, hg, bzr). With the rise of new workflows and source repositories, fedorahosted.org has ceased to grow, adding just one new project this year and a handful the year before.

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 ↑