Category: Infrastructure (page 15 of 20)

All articles in this category are related to the Infrastructure team in the Fedora Project. https://fedoraproject.org/wiki/Infrastructure

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

Changes to Bugzilla queries

On 13 September 2021, Red Hat’s Bugzilla team released updates to Bugzilla that included new functionality for pagination. There is also a change to the default number of results with the bug search API to support this feature. The default is now 20 but can be adjusted to 1000 by using the limit/offset parameters. 

Continue reading

CPE to staff EPEL work

We are pleased to announce that Red Hat is establishing a small team directly responsible for participating in EPEL activities. Their job isn’t to displace the EPEL community, but rather to support it full-time. We expect many beneficial effects, among those better EPEL readiness for a RHEL major release. The EPEL team will be part of the wider Community Platform Engineering group, or CPE for short.

As a reminder, CPE is the Red Hat team combining IT and release engineering from Fedora and CentOS.
Right now we are staffing up the team and expect to see us begin this work from October 2021. Keep an eye on the EPEL mailing list and the associated tracker as we begin this exciting journey with the EPEL community.

Stories from the amazing world of release-monitoring.org #11

The sun is shining on the land as I walk through the streets of one of the cities on Anitya. My staff is doing clinking sounds on the stone road under my feet. Everything looks peacefully and seems to be in order. This is how I like it.

Not many citizens have noticed my humble presence. The life here is too busy and I’m a frequent guest in these parts. My steps are going towards the local tavern. I know who will wait for me there and this makes my heart happy. Traveler is always coming back to visit me and his visits are always good way to spent my time.

The tavern is a little dark like most of the taverns in these parts of the land. I looked around searching the faces sitting here, looking for the one that seems familiar to me. I found it! Traveler was sitting in corner sipping his pint of beer and looking at the fire crackling in the heart of the tavern. I came closer to his table: “Hello traveler, it’s nice to meet you again. It was few months till we saw each other last time. The times were busy, but I have plenty of good news for you. I know you want to know what is happening around. So let’s begin.” I sat on the stool beside his table and started talking.

Continue reading

Community Platform Engineering is hiring

The Community Platform Engineering (CPE) group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. See our docs for more information.

We are hiring new talent to come work full time on Fedora and CentOS. The following positions are now open:

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
Olderposts Newerposts

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 ↑