Leigh Griffin, Author at Fedora Community Blog

Author: Leigh Griffin

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.

CPE to staff EPEL work

September 2, 2021 / Leigh Griffin / Comments Off

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.

Making a git forge decision

March 27, 2020 / Leigh Griffin / 4 Comments

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.

Git Forge requirements

January 20, 2020 / Leigh Griffin / Comments Off

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.

Application service categories and community handoff

July 16, 2019 / Leigh Griffin / 5 Comments

The Community Platform Engineering (CPE) team recently wrote about our face-to-face meeting where we developed a team mission statement and developed a framework for making our workload more manageable. Having more focus will allow us to progress higher priority work for multiple stakeholders and move the needle on more initiatives in a more efficient manner than how we are working right now.

During the F2F we walked through the process of how to gracefully remove ourselves from applications that are not fitting our mission statement. The next couple of months will be a transition phase as we want to ensure continuity and cause minimum disruption to the community. To assist in that strategy, we analysed our applications and came up with four classifications to which they could belong.

Author: Leigh Griffin

GitLab available for Fedora

CPE to staff EPEL work

Making a git forge decision

Git Forge requirements

Application service categories and community handoff

Code of Conduct

Recent Posts

Recent Comments