Purpose The bridge between matrix and IRC is no longer working and this is leading to deprecated service when running meetings in Matrix and a bad user experience Impact Goals Create and implement a Bot that matches Zodbot in functionality for Matrix https://fedoraproject.org/wiki/Zodbot Create a meetbot that has similar functionality and uses Mote Deadline As soon as possible, with a working Minimum Viable Product or Beta versions available for use by end of September 2023.

The landscape of message filtering has changed since FMN was first developed. There are multiple Goals Make the UI more useable for Decouple the filters from the destination Possible Technical Choices Rabbitmq plugin jeremy Cline investigated the use of rabbitmq for a replacement for FMN. This involved writing a module for rabbitmq where the filtering is done in rabbitmq and the quees are done behind the user name

Fedora Infrastructure & Release Engineering osbs build issue now fixed Scheduled Q3 Projects Datanomer/Datagrepper About These apps are currently used to retrieve historical information about messages on the fedmsg bus and add them to a postgresql database. Datanomer reads-in messages from the bus and stores them in the database and Datagrepper exposes the messages in the database via an API with different filtering capacities. We want to upgrade these applications to use fedora-messaging and increase the performance of the applications for users. Work Tracker: https://github.com/orgs/fedora-infra/projects/10 Delivered in August

Intro The Community Platform Engineering team is a group of people who work on infrastructure, release engineering, documentation, development and just about anything else you can think of that supports both the CentOS and Fedora projects. In an effort to try work even more effectively and improve on our work planning, we have been scheduling some of our work on a quarterly basis for the last 15-18 months. And its been working pretty well...once we got the hang of it :) This in a nutshell, just means that there is work the CPE team will commit to delivering every quarter that relates to both distros, while also still providing support to the projects infrastructure that come in as bugs, tickets, etc. Quarter two 2021, or April, May and June to give them their government names, has been a particularly good quarter for our team with a lot of work getting completed. Below is a breakdown of what our team delivered over the quarter per project. A note, that is a given but should never go without saying - is that the CPE team work in the Fedora and CentOS communities, and rely on community member feedback and discussion while working. Without your continued support and engagement with our team - be it when we are announcing something available and need input on how it works or an idea we have had and we want more discussion on a proposal before we start developing - the work we deliver at the end of each quarter would not be possible. So on behalf of the CPE team, thank you for your involvement in our quarterly work! This is as much your bragging rights as it is ours :) Fedora RPMautospec

CPE Weekly: 2021-03-31 Hi Everyone, Sorry for the two week gap since my last report, we had a busy time in the CPE team with the new fedora accounts deployment, our quarterly planning cycle started for Q2 and Ireland had a bank holiday mid week which seemed like a great idea at the time. Until no-one knew what day it was for about a week! So here I am, right at the end of Q1 with the CPE teams final weekly report for January, February and March... two days early :) If you would like to see this report and toggle to the section you are most interested in, I would suggest visiting this link https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view and use the header bar on your left to skip to where you want to go! Initiative FYI Links

Hi everyone, Thanks again for your involvement in the GitLab AMA session on IRC in September. This email discussion thread is on Namespace & Issue Tracking. I have pulled the relevant questions and answers from the original hackmd doc into one email and if you would like to discuss this topic specifically, here might be a good place to do so so your conversations don't go down a 'rabbit hole' :) Here are some links to resources as well: Questions and Answers hackmd link https://hackmd.io/RW8HahOeR7OJPON1dwuo3w Chat log from session https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-10/ama_session_with_gitlab.2020-09-10-13.31.log.html AMA Blog post https://communityblog.fedoraproject.org/gitlab-ama-follow-up/#more-9346 Here is this email in hackmd if you wish to view it there: https://hackmd.io/oZrDwbSeSWO-l_X65A1ndg?view

Hi everyone, I hope you enjoyed the F33 release party this weekend! Getting back to the GitLab topic mail threads, this weeks topic from the GitLab AMA session on September 10th is on Message Bus. As always, here are some links to the resources I have been pulling content from as well: Questions and Answers hackmd link https://hackmd.io/RW8HahOeR7OJPON1dwuo3w Chat log from session https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-10/ama_session_with_gitlab.2020-09-10-13.31.log.html AMA Blog post https://communityblog.fedoraproject.org/gitlab-ama-follow-up/#more-9346 Here is this email in hackmd if you wish to view it there: https://hackmd.io/tfOqCXNEQtqsGNLAEfZ2zg?view Topic: Message Bus

Hi everyone, Thanks again for your involvement in the GitLab AMA session on IRC in September. As promised, this is the first of a 5-part series breaking down main topics that came up during the session. I will send a topic every week for discussion to both Fedora and CentOS devel lists. I have pulled the relevant questions and answers from the original hackmd doc into one email. If you would like to discuss this topic specifically, here might be a good place to do so. I dont consider myself technical enough to weigh in on details, but I am happy to facilitate as best I can via email. And more importantly (for me), learn from the discussion. Here are some links to resources as well: Questions and Answers hackmd link https://hackmd.io/RW8HahOeR7OJPON1dwuo3w Chat log from session https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-10/ama_session_with_gitlab.2020-09-10-13.31.log.html AMA Blog post https://communityblog.fedoraproject.org/gitlab-ama-follow-up/#more-9346 Here is this email in hackmd if you wish to view it there: https://hackmd.io/1pjX1cVnTjekOLVowj5UiQ?view

To: devel-announce@lists.fedoraproject.org, centos-devel@centos.org Subject: CPE Team Engagement Hi Everyone, As we kick off our team's work for Quarter 3 of this year, we would like to take this opportunity to ask for your feedback on our engagement over the last few months. The CPE have been working on trying to improve our communication with our communities and increase visibility on how we decide on what to work on. We have taken many steps to improve our communication such as IRC Office hours, regular initiative updates on our taiga board, weekly mail and blog posts on what we achieved in each quarter and what we are planning to work on next. We have also had a few discussions before with some Fedora Council and CentOS Board members on how best to engage with the CPE Team when you wish to brief in an initiative or need to file a bug/issue/enhancement, and as time goes by we are refining our processes. We would like to share with you our current approaches that we are using for you to provide feedback on how you feel these are working.

Last updated: 2020-05-20 Data Centre Move Affected week of 2020-06-08 Services that are currently offline: Communishift (down on 2020-04-13 and back at the end of June, est.) Data Center Move Affected week of 2020-06-08 until est. 2020-07-28 Note that during this week we will be moving all services over to IAD2 (new datacenter). Each particular service/application may be up or down during this week as we move it or services it depends on. We will be updating this document as we plan and move things.

Hi Everyone, As you may or may not be aware, last year Red Hat took the decision to move datacenters in 2020. The lease on the current datacentre in Phoenix was due to expire in 2020 and Red Hat negotiated a better lease with a provider in Northern Virginia. This datacentre is home to Fedora servers. So, what does this mean for you as a Fedora user? Very little we hope! The Community Plaform Engineering team have been working closely with Red Hat IT to plan logisitics, and other 'fun stuff' to make sure this move is successful and as undisruptive to everyone as possible. During this planning phase, we identified a need to have a minimum viable fedora offering in place during some key dates to facilitate the move, and allow for the shipment of hardware that is integral to Fedora Infrastructure without halting development - or a whole infrastructure!

Hi Pagure Community, During a recent office hours on IRC, I was asked, actually reminded, that the analysis of Pagure had yet to be sent. My apologies for this and thank you Defolos for the reminder :) and for holding me accountable! The below text was lifted from an internal google document used by CPE management and above, when discussing what gitforge option to pursue and copied to this hackmd file for convenience for readers who are using terminals, etc to consume. I hope this email serves an information sharing purpose and even possibly aroadmap of sorts of improvements that I have no doubt are either being actively worked on or could be developed in Pagure, and I look forward to the good conversations this may generate. Recently, the Community Platform Engineering (CPE) team who look after both the Fedora and CentOS Communities ran an analysis on what their future Gitforge needs would look like. As part of that, we analysed Pagure and in our follow on discussions we promised to feed back into the Pagure community the gaps as we saw them which played a part in our decision making process. The text below can be ported to various issues, just let us know the most appropriate location and we are happy to offer our assistance in fleshing these out. Please note that this is a requirements driven view of the capabilities of Pagure and is not a slight at the work the community and indeed the CPE team have put into this project over the years. We deeply appreciate the efforts of all contributors and we hope that this mail is insightful and helps to build a strong Pagure. Technical Recommendations: A number of technical requirements that Pagure would need to consider to meet some of our requirements are as follows:

Background: The Community Platform Engineering 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. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here.

Acronyms Used in Document MVFE - Minimal Viable Fedora Environment PHX2 - Chandler Arizona datacentre RDU-CC - Morrisville NC datacentre community cage IAD2 - Ashburn Equinix datacentre AAA - Authentication, Authorization, Auditing IPA - Identity, Policy, Audit FAS - Fedora Account System (older AAA solution) FreeIPA - Newer account system

We would like to welcome you all to our first blog update on the CentOS Stream initiative. Over the course of this initiative, we will share regular updates on our plans, our progress and our deliverables. The CentOS Stream team is currently working within a Scrumban framework broken down into two week blocks. This allows the PO and team to plan and prioritise work for each block allowing stakeholders to gain updates on progress, plans and deliverables each fortnight. Each fortnight, stakeholders will review the block deliverables and provide feedback to be taken into consideration when planning the next block. Ensuring that CentOS Stream is delivered in line with changing requirements and expectations as the project build progresses. The CentOS Stream team has made significant progress throughout February where their focus was on the cornerstone foundational build phase. Block 1 and 2 (2020-02-03 to 2020-02-21) delivered: Nightly composes: Reports are being generated internally for now until a bug fix has been resolved CentOS QA can consume composes and the test suite can now run against both Stream and Linux This has also caught three issues that would have made it to downstream otherwise The module for Stream this week is PHP:7.2 This is ahead of 8.1 in RHEL

MVFE- Minimal Viable Fedora Environment PHX2 - Chandler Arizona datacentre RDU-CC Morrisville NC datacentre community cage IAD2 - Ashburn Equinix datacentre Week 00 (2020-03-02 -> 2020-03-08) Hardware shipping needs to be planned out Rack layouts for IAD2 and RDU-CC need to be finalized Work with RH IT on what they need in network diagrams

The month of February was a very busy month for the CPE AAA team and community contributors working on this initiative. Great progress was made in the development phase of the AAA: FAS replacement build. Sprint 2 and 3 resulted in the completion of multiple user stories which added user functionality to join groups, change email address and password, disable account, database access along with putting a mapping solution in place for users moving from the current FAS to the new FAS (potential name incoming!). We also came to the end of developing our wireframes and mapping our user experience flow. Unit tests were carried out regarding password controller and the current codebase. We received great support from the wider CPE team as well as Patrick Uiterwijk to allow us progress with user stories by gaining permissions and merging PR’s for the integration of CentOS CI. Christian Heimes assisted us greatly with sharing his knowledge regarding FREE IPA and answered numerous questions to allow us to move forward. Sprint 4 began on Thursday the 20th of February. This sprint will focus on development tasks which will include working on FAS Json, Free IPA, API, Fedora Messaging integration, continuous deployment to stage environment, developing a secure coding tool to ensure code adheres to best practice, as well as continuing working on user functionality user stories. Please see our github board here to view current activity. We also received some sad news since our last update, that we are losing a team member, Rick Elrod, as he moves on to pastures new with the Ansible team. Rick provided an excellent POC for AAA which is leaving us in good shape to continue on as planned. Thanks Rick and we will hopefully still see you around as a contributor going forward. We also welcomed a new team member Leonardo (Leo) Rossetti who joined at the start of Sprint 4 and has already hit the ground running. Leo is currently working on our FAS JSON user stories. Regarding delivery of AAA, we may look at a phased release , this current phase focus is on the development of AAA to be delivered by 3/31/20. It is looking likely that the deployment of AAA will happen in a later phase due to requiring System Admin assistance. We are likely to gain this on the completion of the Colo Move (which is our planned data center move), approximately in mid April. We are enquiring to see if deploying to staging is possible within this phase to allow for a long testing period. I will provide an update on this in our next blog. The integration of CentOS will be worked on within an additional phase following the completion of AAA centric stories for Fedora. On a final note, I would like to commend the CPE AAA team on their collaboration and productivity throughout this initiative even in the face of unknowns, team changes, cross team dependencies and other challenges, they continued to proactively work together and find solutions to keep this initiative moving forward.