Category: Infrastructure (page 1 of 6)

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

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

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

It’s a nice view from top of my tower. The goblins are working tirelessly on their tasks. The sun is shining on the city. And most of the things working as they should. Even the plans for the future are coming nicely together. It’s shame that I didn’t have much time to take care of it and my skills were needed elsewhere.

I turned my back to the view and returned back to the table, where Traveler already sat. “So, you want to know what the future can reveal? Let’s look at it then.” I took my mage staff and created a vision on the table.

Continue reading

MBBox – Module Building in a Box

MBBox is a way to deploy everything you need to build modules in Fedora/CentOS ecosystems. It contains Koji (koji-hub, koji-builder, kojira) and MBS (mbs-frontend and mbs-backend). This should be enough to start building your own modules. It is now one of the initiatives being worked on by the CPE team.

Continue reading

CPE achievements during Q1 2020

2020 has seen a lot of changes for everyone—understatement of the year right? One of these changes has been how the Community Platform Engineering (CPE) Team has decided to adjust how they work. We are on an agile workflow journey. We began this year with quarterly planning, for the first time ever! We kicked off the start of the year working on some prioritised initiatives that we discussed as a review team during our first quarterly planning session. The review team included Brian ‘Bex’ Exelbierd, Paul Frields, Jim Perrin, Leigh Griffin, Pierre-Yves Chibon, Brian Stinson and Clément Verna.

The initiatives chosen to be worked on during Quarter One were:

  • FAS Replacement Login Phase 1 
  • Fedora Data Centre Move
  • CentOS Stream Phase 1 
  • CI/CD 
Continue reading

The future of Fedora Community apps

The Community Platform Engineering team (formerly Community Infrastructure) indicated in July of 2019 that they have a higher workload than the team can bear. To ease this, they evaluated the applications that fit their mission statement. The applications that didn’t fit the mission were proposed for hand off to the community. 

I am happy to say there is a lot being done to preserve the applications that our community values. I have been working with the Fedora Project Leader (FPL), Fedora Program Manager (FPgM), Community Platform Engineering team (CPE), and the Open Source Program Office (OSPO) at Red Hat to transition app hosting and maintenance from CPE to OSPO.

Continue reading

What’s coming up next in Fedora and CentOS infrastructure?

As you may know, the Community Platform Engineering (CPE) team that helps manage both infrastructure for both Fedora and CentOS is trying to improve how the different initiatives or requests for changes we receive are planned and prioritized. This effort to improve has led us to look at planning our work in three-month windows. By planning, limiting, and focusing our work every three months, we can dedicate a substantial team around each initiative, driving it to completion before working on the next. Overall this helps us finish and deliver work faster.

Continue reading
Olderposts

Copyright © 2021 Fedora Community Blog

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

Theme by Anders NorenUp ↑