Category: Infrastructure (page 1 of 5)

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

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

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

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

I woke up to the cold morning in my tower. The sun shone brightly on the sky, but the stone of the tower was cold as it takes some time to make it warm. Everything was already prepared for today’s journey. I sat at my table and started going through some reports from workers. I still had some time til the traveler arrived. So I started reading the reports …

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

Infrastructure support over the holidays

As you may be aware, Red Hat has a mandatory shutdown period beginning 24 December and ending 2 January. This allows most associates to celebrate the holiday season with friends and family and recharge their batteries after a busy year. Multiple Red Hat teams will be observing this period, including the Community Platform Engineering team, which supports Fedora & CentOS infrastructure. We want to raise awareness that availability will be minimal during this time.

Continue reading
Olderposts

Copyright © 2020 Fedora Community Blog

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

Theme by Anders NorenUp ↑