Pawb.Social Reports @transparency

0 posts0 participants0 posts today

Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.nz/@phlogiston" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>phlogiston</span></a></span> yeah.</p><p>Fortunately <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> hardlined on that, basically saying: <em>"Network Access is a Passive Connection Point."</em> and also enshrining <a href="https://infosec.space/tags/DeviceFreedom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DeviceFreedom</span></a> and banning <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISP</span></a>|s from forcibly bundling <a href="https://infosec.space/tags/CPE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPE</span></a>|s (with rent) towards consumers.</p>

SΛNDRΛ :verified_coffee:<p>UPDATE: Das <a href="https://norden.social/tags/pihole" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pihole</span></a> war es. <br>Danke an alle für Boost und Ideen!</p><p>Internet ist aus 🙄. Support ist auch aus. 😟. Jemand eine Idee? <br>(Ja, hab schon mal aus und wieder an gemacht).</p><p><a href="https://norden.social/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Internet</span></a> <a href="https://norden.social/tags/kaputt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kaputt</span></a> <a href="https://norden.social/tags/CPE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPE</span></a> <a href="https://norden.social/tags/Glasfaser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Glasfaser</span></a> <a href="https://norden.social/tags/offline" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>offline</span></a></p>

The New Oil<p>Hackers exploit critical unpatched flaw in <a href="https://mastodon.thenewoil.org/tags/Zyxel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Zyxel</span></a> <a href="https://mastodon.thenewoil.org/tags/CPE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPE</span></a> devices</p><p><a href="https://www.bleepingcomputer.com/news/security/hackers-exploit-critical-unpatched-flaw-in-zyxel-cpe-devices/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bleepingcomputer.com/news/secu</span><span class="invisible">rity/hackers-exploit-critical-unpatched-flaw-in-zyxel-cpe-devices/</span></a></p><p><a href="https://mastodon.thenewoil.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a></p>

Veza85UE<p><span class="h-card" translate="no"><a href="https://bird.makeup/users/grand_continent" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>grand_continent</span></a></span> También es verdad que lo que sí que hacen bien, lo hacen mejor que nadie. </p><p><a href="https://legrandcontinent.eu/es/2024/07/18/cumbre-de-la-comunidad-politica-europea-en-blenheim-en-que-paises-esta-la-poblacion-mas-a-favor-de-la-adhesion-a-la-union/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">legrandcontinent.eu/es/2024/07</span><span class="invisible">/18/cumbre-de-la-comunidad-politica-europea-en-blenheim-en-que-paises-esta-la-poblacion-mas-a-favor-de-la-adhesion-a-la-union/</span></a></p><p><a href="https://eupolicy.social/tags/CPE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPE</span></a> <a href="https://eupolicy.social/tags/Comunidadpol%C3%ADticaeuropea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Comunidadpolíticaeuropea</span></a> <a href="https://eupolicy.social/tags/Europa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Europa</span></a> <a href="https://eupolicy.social/tags/europol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>europol</span></a> <a href="https://eupolicy.social/tags/EUpol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EUpol</span></a></p>

amoloney<h2>Vol. I – Fedora Council 2024 Hackfest</h2><p>During the Council’s <a href="https://fedoraproject.org/wiki/Council/2024_Hackfest" rel="nofollow noopener noreferrer" target="_blank">February 2024 hackfest</a>, we discussed the future of Fedora’s git forge – that is, the platform Fedora uses for version control and tracking for packages, source code, documentation, and more. This topic has been around for quite some time. If you are just coming into this conversation, or would like a refresher, <a href="https://discussion.fedoraproject.org/tags/c/project/7/git-forge-future" rel="nofollow noopener noreferrer" target="_blank">#git-forge-future</a> is a good place to start.</p><p>Instead of one huge post, the <a href="https://communityblog.fedoraproject.org/category/council/" rel="nofollow noopener noreferrer" target="_blank">Fedora Council</a> divided the follow-ups from our hack-fest into a mini-series of posts throughout April that will cover all the topics we discussed and made decisions on. In each post, we will walk through one core topic, and share our discussion and thought process on how we reached our outcomes. The first in this series, because why not start strong 🙂 , is an update on our git forge evaluation. Read on for important information.</p><p></p><p>The Council arrived at two main decisions during this discussion. </p><h2>Pagure</h2><p><strong>First, the Council does not see Pagure as a viable git forge solution for Fedora’s future</strong>. Instead, we will investigate other git forge options which meet our core community values: <em>Freedom, Features, Friends, First</em>. When a suitable solution is found, the work needed to migrate to the new git forge will be shared. </p><p>At a later date, the Council will announce a sunsetting date for Pagure, with ample time for projects to migrate to the replacement.</p><h2>Options for an alternate git forge</h2><p><strong>Second, the Council examined a long list of possibilities, and eliminated those that do not fit</strong>. We narrowed down the list to these options we think might meet the needs and spirit of Fedora: </p><ol><li>GitLab Community Edition</li><li>Forgejo (a fork of Gitea)</li></ol><p>In both cases, the Council determined that <strong>the project will need to run the software in Fedora Infrastructure</strong>. <a href="https://communityblog.fedoraproject.org/category/infrastructure/" rel="nofollow noopener noreferrer" target="_blank">Fedora Infrastructure</a> previously investigated hosting possibilities from GitLab at length, and could not find something workable without compromising on our community values for software freedom.</p><p>The Council is grateful to everything the Pagure developers have done for us, and acknowledge Pagure’s immense positive impact on Fedora. In the end, these other two options were what the Council felt we could honestly ask our community to use. </p><p>The <a href="https://docs.fedoraproject.org/en-US/cpe/" rel="nofollow noopener noreferrer" target="_blank">Community Platform Engineering (CPE)</a> Team is a Red Hat-sponsored team that supports Fedora Infrastructure and Release Engineering with staffing, efforts, and resources. The Council will ask the Red Hat CPE to lead the maintenance efforts alongside the community. Therefore, the Council encourages the community to collaborate and support the Red Hat CPE in an in-depth technical evaluation for both options.</p><p>When these investigations are complete, the project will have at least two weeks of community discussion on the reports. Then, the Council will select an option and will launch a Community Initiative implementing the migration plan.</p><h2>Share your feedback on git forge future</h2><p>To keep track of feedback and conversations in one place, direct all feedback and comments to the <a href="https://discussion.fedoraproject.org/tags/c/project/7/git-forge-future" rel="nofollow noopener noreferrer" target="_blank">#git-forge-future</a> tag on Fedora Discussion. You can reply to an existing topic or start a new one.</p><p>This will be a long journey for us to take together as a community. Thank you for your patience and feedback as we go down this road together. Please remember to keep your feedback courteous, respectful, and aligned with the <a href="https://docs.fedoraproject.org/en-US/project/code-of-conduct/" rel="nofollow noopener noreferrer" target="_blank">Fedora Code of Conduct</a>.</p><p><a href="https://communityblog.fedoraproject.org/2024-git-forge-evaluation/" rel="nofollow noopener noreferrer" target="_blank">https://communityblog.fedoraproject.org/2024-git-forge-evaluation/</a></p><p><a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/community-platform-engineering/" target="_blank">#CommunityPlatformEngineering</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/council-hackfest-2024/" target="_blank">#CouncilHackfest2024</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/cpe/" target="_blank">#CPE</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/dist-git/" target="_blank">#distGit</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/git-forge/" target="_blank">#gitForge</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/gitlab/" target="_blank">#GitLab</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/hackfests/" target="_blank">#hackfests</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/pagure/" target="_blank">#Pagure</a></p>

zlopez<p>This is a summary of the work done on <a href="https://docs.fedoraproject.org/en-US/cpe/initiatives/" rel="nofollow noopener noreferrer" target="_blank">initiatives</a> by the <a href="https://docs.fedoraproject.org/en-US/cpe/" rel="nofollow noopener noreferrer" target="_blank">Community Platform Engineering (CPE)</a> Team. Every quarter, the CPE team works together with CentOS Project and Fedora Project community leaders and representatives to choose projects that will be being worked upon in that quarter. The CPE team is then split into multiple smaller sub-teams that will work on the chosen initiatives and day-to-day work that needs to be done. Some of the sub-teams are dedicated to the continuous efforts in the team whilst some are created only for the initiative purposes.</p><p>This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.</p><p></p><a class="" href="https://communityblog.fedoraproject.org/wp-content/uploads/2024/01/CPE_2023-scaled.jpg" rel="nofollow noopener noreferrer" target="_blank">[🖼 infographic]</a> <p></p> <p></p> [🖼 infographic] [🖼 infographic] <p></p> <h2>About</h2><p>The Community Platform Engineering Team is a Red Hat team that is working exclusively on community projects. Its members are part of Fedora Infrastructure, Fedora Release Engineering and CentOS Infrastructure teams. This team works on initiatives, which are projects with larger scope related to community work that needs to be done. It also investigates possible initiatives  with the ARC (The <a href="https://pagure.io/fedora-infra/arc" rel="nofollow noopener noreferrer" target="_blank">Advance Reconnaissance Crew</a>), which is formed from a subset of the Infrastructure & Release Engineering sub-team members based on the initiative that is being investigated.</p><p><strong>Issue trackers</strong></p><ul><li><a href="https://pagure.io/cpe/initiatives-proposal/issues" rel="nofollow noopener noreferrer" target="_blank">CPE initiative tracker</a></li></ul><h2>Initiatives</h2><h3>PDC Retirement</h3><p>PDC is the Product Definition Center, running at: <a href="https://pdc.fedoraproject.org/" rel="nofollow noopener noreferrer" target="_blank">https://pdc.fedoraproject.org/</a>.</p><p>However, this application which was developed internally, is no longer maintained. This codebase has been “orphaned” for a few years now and we need to find a solution for it.</p><p>We are reviewing and having a critical look on what we store in there, see what is really needed and then find a solution for its replacement.</p><p><strong>Status:</strong> In Progress</p><p><strong>Issue trackers</strong></p><ul><li><a href="https://pagure.io/releng/issue/11723" rel="nofollow noopener noreferrer" target="_blank">Tracker link</a></li></ul><p><strong>Documentation</strong></p><ul><li><a href="https://pagure.io/cpe/initiatives-proposal/issue/5" rel="nofollow noopener noreferrer" target="_blank">Initiative proposal</a></li><li><a href="https://fedora-arc.readthedocs.io/en/latest/pdc/index.html" rel="nofollow noopener noreferrer" target="_blank">ARC investigation</a></li></ul><p><strong>Application URLs</strong></p><ul><li><a href="https://pdc.fedoraproject.org/" rel="nofollow noopener noreferrer" target="_blank">https://pdc.fedoraproject.org/</a></li></ul><h3>Matrix Native Zodbot</h3><p>With ongoing stability issues with the Matrix <-> IRC bridge and many contributors switching over to Matrix, Zodbot has become increasingly unreliable. The bridge is currently <a href="https://matrix.org/blog/2023/08/libera-bridge-disabled/" rel="nofollow noopener noreferrer" target="_blank">shut off completely</a>. This initiative aims to provide a future-proof solution and allow us to conduct meetings without wasting time troubleshooting the Matrix <-> IRC bridge and Zodbot.</p><p><strong>Status:</strong> In Progress</p><p><strong>Issue trackers</strong></p><ul><li><a href="https://github.com/fedora-infra/maubot-fedora" rel="nofollow noopener noreferrer" target="_blank">Tracker link</a></li></ul><p><strong>Documentation</strong></p><ul><li><a href="https://pagure.io/cpe/initiatives-proposal/issue/29" rel="nofollow noopener noreferrer" target="_blank">Initiative proposal</a></li></ul><h3>FMN Replacement</h3><p>FMN is a project that allows people in our community to get notified when messages that interest them fire on the message-bus, making the message-bus more useful to people that are not directly developing or troubleshooting applications running in our infra.</p><p>The previous solution had plenty of tech debt which caused lag times between an event happening and the subscriber to be notified, so this initiative rewrote the service from scratch and is now live! Users are recommended to migrate their rules to the new service and notifications can also now be configured to email, IRC and Matrix.</p><p><strong>Status:</strong> Done</p><p><strong>Issue trackers</strong></p><ul><li><a href="https://github.com/orgs/fedora-infra/projects/13" rel="nofollow noopener noreferrer" target="_blank">Github project</a></li></ul><p><strong>Documentation</strong></p><ul><li><a href="https://pagure.io/cpe/initiatives-proposal/issue/10" rel="nofollow noopener noreferrer" target="_blank">Initiative proposal</a></li><li><a href="https://fedora-arc.readthedocs.io/en/latest/fmn/index.html" rel="nofollow noopener noreferrer" target="_blank">ARC investigation</a></li><li><a href="https://fmn.readthedocs.io/en/latest/" rel="nofollow noopener noreferrer" target="_blank">Documentation link</a></li></ul><p><strong>Application URLs</strong></p><ul><li><a href="https://apps.fedoraproject.org/notifications/" rel="nofollow noopener noreferrer" target="_blank">FMN Service</a></li></ul><h3>DNF-Countme Update</h3><p>DNF Mirrors Countme scripts are used to gain statistics data about the downloads of Fedora. Purpose of this initiative is to optimize the current solution by adding more comprehensive testing, removing unnecessary code and reducing storage consumption of the data. </p><p><strong>Status:</strong> Done</p><p><strong>Issue trackers</strong></p><ul><li><a href="https://github.com/orgs/fedora-infra/projects/16/views/1" rel="nofollow noopener noreferrer" target="_blank">Github tracker</a></li></ul><p><strong>Documentation</strong></p><ul><li><a href="https://pagure.io/cpe/initiatives-proposal/issue/17" rel="nofollow noopener noreferrer" target="_blank">Initiative proposal</a></li><li><a href="https://fedora-arc.readthedocs.io/en/latest/dnf-countme/index.html" rel="nofollow noopener noreferrer" target="_blank">ARC investigation</a></li><li><a href="https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/dnf-counting/" rel="nofollow noopener noreferrer" target="_blank">Documentation link</a></li></ul><h2>ARC Investigations</h2><h3>Investigate moving registry.fp.o to quay.io</h3><p>Traditionally, <a href="https://registry.fedoraproject.org/" rel="nofollow noopener noreferrer" target="_blank">registry.fedoraproject.org</a> was needed as quay.io did not support multiarch which it now does. The purpose of this ticket is to carry out some investigation work to confirm all the above is true as well as finding any other potential blockers to the move.</p><p><strong>Status:</strong> Done</p><p><strong>Documentation</strong></p><ul><li><a href="https://pagure.io/fedora-infrastructure/issue/10386" rel="nofollow noopener noreferrer" target="_blank">Initiative proposal</a></li><li><a href="https://fedora-arc.readthedocs.io/en/latest/registry_to_quay/index.html" rel="nofollow noopener noreferrer" target="_blank">ARC investigation</a></li></ul><h3>Spam fighting</h3><p>We had plenty of spam on <a href="http://pagure.io" rel="nofollow noopener noreferrer" target="_blank">pagure.io</a> this year. To fight it more effectively, the ARC team tried a few different approaches to recognize and delete spam. It’s now much easier to delete the spam user with all the spam it created.</p><p><strong>Status:</strong> Done</p><h3>ARC investigation/planning for FCAS</h3><p>In order to have a quantitative understanding of how the contributor activity has changed over the years and to provide the foundational support to the Fedora Project strategy 2028’s guiding star about doubling the number of active contributors every week, it is important to have a service that tracks their statistics. This measurement would help make the strategy goal meaningful as well as assist the Fedora Council and the related bodies understand how far they have progressed into making this happen and identify the underlying particular problems that act as a barrier in realizing this objective.</p><p><strong>Status:</strong> Done</p><p><strong>Documentation</strong></p><ul><li><a href="https://pagure.io/cpe/initiatives-proposal/issue/27" rel="nofollow noopener noreferrer" target="_blank">Initiative proposal</a></li><li><a href="https://fedora-arc.readthedocs.io/en/latest/fcas/index.html" rel="nofollow noopener noreferrer" target="_blank">ARC investigation</a></li></ul><h3>Badges backend for new Service</h3><p>Fedora Badges is a service that grants virtual accolades for milestones and completing tasks within the Fedora Project community. For example, a community member may collect badges for testing package updates on Bodhi when they test 1, 5, 10, 20, 40, 80, 125, 250, 500 and 1000 updates.</p><p><strong>Status:</strong> Done</p><p><strong>Documentation</strong></p><ul><li><a href="https://fedora-arc.readthedocs.io/en/latest/badges/index.html" rel="nofollow noopener noreferrer" target="_blank">ARC investigation</a></li></ul><h3>Pagure to GitLab importer</h3><p>With Fedora and CentOS now having an official namespace on GitLab, multiple projects want to migrate their repositories from Pagure to GitLab. This initiative is aimed to provide an easy way to migrate those projects.</p><p><strong>Status:</strong> Done</p><p><strong>Documentation</strong></p><ul><li><a href="https://pagure.io/cpe/initiatives-proposal/issue/25" rel="nofollow noopener noreferrer" target="_blank">Initiative proposal</a></li><li><a href="https://fedora-arc.readthedocs.io/en/latest/pagure2gitlab/index.html" rel="nofollow noopener noreferrer" target="_blank">ARC investigation</a></li></ul><h3>DNF-countme</h3><p>The purpose of this work was about investigating the current solution and it’s bottlenecks to identify what needs to be done to solve the following problems:</p><ul><li>Storage bottleneck when creating the intermediate database file</li><li>Operations efficiency for the infrastructure team</li></ul><p><strong>Status:</strong> Done</p><p><strong>Documentation</strong></p><ul><li><a href="https://pagure.io/cpe/initiatives-proposal/issue/25" rel="nofollow noopener noreferrer" target="_blank">Initiative proposal</a></li><li><a href="https://fedora-arc.readthedocs.io/en/latest/pagure2gitlab/index.html" rel="nofollow noopener noreferrer" target="_blank">ARC investigation</a></li></ul><h3>Dist-Git decoupling & ecosystem mapping</h3><p>The objective of the potential initiative is to move repository contents (including but not limited to source codes, Packit configurations, RPM specfiles) from Pagure Dist-Git to another platform and confirm that the associated tooling and services (including but not limited to FMN, Datanommer, COPR, Toddlers, FMN, CI, Monitor-Gating, Packit, Bodhi, Fedpkg) work well with the newer platform. The investigation aims to be as agnostic as it can be regarding the destination platform to help ideate a general solution for the compatibility of the associated tooling and services.</p><p><strong>Status:</strong> Done</p><p><strong>Documentation</strong></p><ul><li><a href="https://pagure.io/cpe/initiatives-proposal/issue/26" rel="nofollow noopener noreferrer" target="_blank">Initiative proposal</a></li><li><a href="https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html" rel="nofollow noopener noreferrer" target="_blank">ARC investigation</a></li></ul><h2>Epilogue</h2><p>If you get here, thank you for reading this. If you want to contact us, feel free to do it on <a href="https://matrix.to/#/#redhat-cpe:matrix.org" rel="nofollow noopener noreferrer" target="_blank">matrix</a>.</p><p>As CPE members are part of Fedora Infrastructure, Fedora Release Engineering and CentOS Infrastructure, see also the <a href="https://communityblog.fedoraproject.org/?p=13084" rel="nofollow noopener noreferrer" target="_blank">Fedora Infra & Releng update</a> and <a href="https://blog.centos.org/2024/01/centos-infrastructure-summary-2023/" rel="nofollow noopener noreferrer" target="_blank">CentOS Infrastructure update</a>.</p><p><a href="https://communityblog.fedoraproject.org/2023-year-in-review-cpe/" rel="nofollow noopener noreferrer" target="_blank">https://communityblog.fedoraproject.org/2023-year-in-review-cpe/</a></p><p><a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/cpe/" target="_blank">#CPE</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/dist-git/" target="_blank">#distGit</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/dnf/" target="_blank">#DNF</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/fedora-infrastructure/" target="_blank">#FedoraInfrastructure</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/fedora-messaging-notification-fmn/" target="_blank">#FedoraMessagingNotificationFMN_</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/infra/" target="_blank">#Infra</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/meetbot/" target="_blank">#Meetbot</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/year-in-review/" target="_blank">#YearInReview</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/year-in-review-2023/" target="_blank">#YearInReview2023</a></p>

c4rt0<p>This is a weekly report from the I&R (<a href="https://docs.fedoraproject.org/en-US/infra/" rel="nofollow noopener noreferrer" target="_blank">Infrastructure & Release Engineering</a>) Team. It also contains updates for CPE (Community Platform Engineering) Team as the CPE initiatives are mostly tied to I&R work.</p><p>We provide you with both an infographic and a text version of the weekly report. If you want to quickly look at what we did, just look at the infographic. If you are interested in more in-depth details look at the infographic.</p><p>Week: 19 February – 23 February 2024</p><p><a class="" href="https://communityblog.fedoraproject.org/infra-releng-update-week-8-2024/" rel="nofollow noopener noreferrer" target="_blank">Read more<span class="">: Infra & RelEng Update – Week 8 2024</span></a></p><a class="" href="https://communityblog.fedoraproject.org/wp-content/uploads/2024/02/Weekly-Report_week8.jpg" rel="nofollow noopener noreferrer" target="_blank">[🖼 I&R infographic]</a> <p></p> <p></p> [🖼 I&R infographic] [🖼 I&R infographic] <p></p> <h2>Infrastructure & Release Engineering</h2><p>The purpose of this team is to take care of day-to-day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.<br>It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).<br><a href="https://issues.redhat.com/issues/?filter=12428298" rel="nofollow noopener noreferrer" target="_blank">List of planned/in-progress issues</a></p><h3>Fedora Infra</h3><ul><li><a href="https://pagure.io/fedora-infrastructure/issue/11657" rel="nofollow noopener noreferrer" target="_blank">Fixed: Bodhi pod restarting</a></li><li><a href="https://pagure.io/fedora-infrastructure/issue/11651" rel="nofollow noopener noreferrer" target="_blank">Request for central database for OpenScanHub</a></li><li><a href="https://pagure.io/fedora-infrastructure/issue/11777" rel="nofollow noopener noreferrer" target="_blank">Fixed: Cannot comment on gnome-control-center, cannot merge merge requests “Forbidden You have been blocked from this project”</a></li><li><a href="https://pagure.io/fedora-infrastructure/issue/11577" rel="nofollow noopener noreferrer" target="_blank">Completed first system being monitored by Zabbix: releng_compose cronjobs</a> thanks to Kevin, darknao and smooge for troubleshooting help <3</li></ul><h3>CentOS Infra including CentOS CI</h3><ul><li><a href="https://pagure.io/centos-infra/issue/1364" rel="nofollow noopener noreferrer" target="_blank">New Build Targets and Tags for the Kmods SIG</a></li><li><a href="https://issues.redhat.com/browse/CS-1982" rel="nofollow noopener noreferrer" target="_blank">[CS10][RHEL10] Remove internal mirror of ELN buildroot</a></li></ul><h3>Release Engineering</h3><ul><li><a href="https://pagure.io/fedora-infra/toddlers/pull-request/188" rel="nofollow noopener noreferrer" target="_blank">Fixes for unretire packages plugin</a></li><li><a href="https://pagure.io/releng/issue/11932" rel="nofollow noopener noreferrer" target="_blank">Fixed: dozens of f39 builds mis-tagged, getting ejected from f39-stable bodhi pushes</a></li><li><a href="https://pagure.io/releng/issue/11950" rel="nofollow noopener noreferrer" target="_blank">Fixed: Wrong f40 / f41 release info in Bodhi</a></li><li><a href="https://pagure.io/releng/issue/11951" rel="nofollow noopener noreferrer" target="_blank">Update IoT Signing Keys for stable</a></li><li><a href="https://pagure.io/releng/issue/11956" rel="nofollow noopener noreferrer" target="_blank">Activate python3-rpm at epel8-next in PDC and unblock in Koji</a></li></ul><h2>CPE Initiatives</h2><h3>EPEL</h3><p><a href="https://docs.fedoraproject.org/en-US/epel/" rel="nofollow noopener noreferrer" target="_blank">Extra Packages for Enterprise Linux</a> (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).</p><h2>Updates</h2><ul><li><a href="https://pagure.io/fedpkg/pull-request/538" rel="nofollow noopener noreferrer" target="_blank">Resolved fedpkg test suite errors on Python 3.12 in preparation for EPEL 10 changes</a></li><li><a href="https://bugzilla.redhat.com/2264138" rel="nofollow noopener noreferrer" target="_blank">Added libplacebo5 to EPEL 9 to resolve mpv error</a></li></ul><h3>Matrix Native Zodbot</h3><p>With ongoing stability issues with the Matrix <-> IRC bridge and many contributors switching over to Matrix, zodbot has become increasingly unreliable. The bridge is currently shut off completely. This <a href="https://pagure.io/cpe/initiatives-proposal/issue/29" rel="nofollow noopener noreferrer" target="_blank">initiative</a> will provide a future proof solution and allow us to conduct meetings without wasting time troubleshooting the bridge and zodbot.</p><h2>Updates</h2><ul><li>This initiative is now finished as the Zodbot is already running in Matrix for a few months and most of the initial issues were resolved</li></ul><p>If you have any questions or feedback, please respond to this report or contact us on <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/redhat/" target="_blank">#redhat</a>-cpe channel on <a href="https://matrix.to/#/#redhat-cpe:matrix.org" rel="nofollow noopener noreferrer" target="_blank">Matrix</a>.</p><p></p><p><a href="https://communityblog.fedoraproject.org/infra-releng-update-week-8-2024/" rel="nofollow noopener noreferrer" target="_blank">https://communityblog.fedoraproject.org/infra-releng-update-week-8-2024/</a></p><p><a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/cpe/" target="_blank">#CPE</a></p>

lenkaseg<p>This is the last weekly report of the year 2023 from the I&R (<a href="https://docs.fedoraproject.org/en-US/infra/" rel="nofollow noopener noreferrer" target="_blank">Infrastructure & Release Engineering</a>) Team. It also contains updates for CPE (<a href="https://docs.fedoraproject.org/en-US/cpe/" rel="nofollow noopener noreferrer" target="_blank">Community Platform Engineering</a>) Team, as the CPE initiatives are in most cases tied to I&R work. Happy holidays, thanks for your interest and see you in 2024!</p><p>We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details, look below the infographic.</p><p>Week: 11 December – 15 December 2023</p><p></p><a class="" href="https://communityblog.fedoraproject.org/wp-content/uploads/2023/12/Weekly-Report-Template17-1024x1007.jpg" rel="nofollow noopener noreferrer" target="_blank">[🖼 CPE infographic]</a><h2>Infrastructure & Release Engineering</h2><p>The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.<br>It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).<br><a href="https://zlopez.fedorapeople.org/I&R-2023-12-13.pdf" rel="nofollow noopener noreferrer" target="_blank">Planning board</a></p><h3>Fedora Infra</h3><ul><li><a href="https://pagure.io/fedora-infrastructure/issue/11674" rel="nofollow noopener noreferrer" target="_blank">Bump debuginfod.stg RAM</a></li><li><a href="https://pagure.io/fedora-infrastructure/issue/11669" rel="nofollow noopener noreferrer" target="_blank">Request for a “kernel-maintainer” FAS group</a></li><li><a href="https://pagure.io/fedora-infrastructure/issue/11668" rel="nofollow noopener noreferrer" target="_blank">Koschei is down</a></li><li><a href="https://pagure.io/fedora-infra/ansible/pull-request/1694" rel="nofollow noopener noreferrer" target="_blank">[ResultsDB] Use the correct API version for deployment config</a></li><li><a href="https://pypi.org/project/pagure-exporter/0.1.2/" rel="nofollow noopener noreferrer" target="_blank">Pagure Exporter v0.1.2 is OUT NOW!</a></li></ul><h3>CentOS Infra including CentOS CI</h3><ul><li><a href="https://issues.redhat.com/browse/CS-1839" rel="nofollow noopener noreferrer" target="_blank">ELN reposync storage consumption</a></li><li><a href="https://pagure.io/centos-infra/issue/1327" rel="nofollow noopener noreferrer" target="_blank">Duffy fails to provision C9S nodes</a></li></ul><h3>Release Engineering</h3><ul><li><a href="https://pagure.io/releng/issue/11825" rel="nofollow noopener noreferrer" target="_blank">koji newRepo tasks frequently failing with “GenericError: Repo directory missing”</a></li><li><a href="https://pagure.io/releng/issue/11801" rel="nofollow noopener noreferrer" target="_blank">Retarget f39-toolchain to rawhide/f40</a></li><li><a href="https://pagure.io/releng/issue/11827" rel="nofollow noopener noreferrer" target="_blank">No new Fedora Atomic desktops composes since 2023-12-05</a></li></ul><h2>CPE Initiatives</h2><h3>EPEL</h3><p><a href="https://docs.fedoraproject.org/en-US/epel/" rel="nofollow noopener noreferrer" target="_blank">Extra Packages for Enterprise Linux</a> (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).</p><h2>Updates</h2><ul><li>Updated <a href="https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2023-f687651475" rel="nofollow noopener noreferrer" target="_blank">python-boto3 and python-s3transfer in EPEL 9 Next</a> to work with updated python-botocore in CentOS Stream 9</li><li>Started <a href="https://discussion.fedoraproject.org/t/allow-epel-packagers-sig-members-to-request-epel-next-branches-on-any-epel-package/98480" rel="nofollow noopener noreferrer" target="_blank">discussion for a policy change</a> to improve EPEL Next branching</li></ul><h3>Community Design</h3><p>CPE has few members that are working as part of <a href="https://fedoraproject.org/wiki/Design" rel="nofollow noopener noreferrer" target="_blank">Community Design Team</a>. This team is working on anything related to design in Fedora Community.</p><h2>Updates</h2><ul><li>Creative Freedom Summit schedule / accepted talks will be released soon 🙂 </li><li>Looking for feedback <a href="https://discussion.fedoraproject.org/t/fedora-40-wallpaper/98951" rel="nofollow noopener noreferrer" target="_blank">https://discussion.fedoraproject.org/t/fedora-40-wallpaper/98951</a></li></ul><h3>ARC Investigations</h3><p>The <a href="https://pagure.io/fedora-infra/arc" rel="nofollow noopener noreferrer" target="_blank">ARC</a> (which is a subset of the CPE team) investigates possible initiatives that CPE might take on.</p><h2>Updates</h2><ul><li>Dist-Git decoupling & ecosystem mapping<ul><li>Fedora Packit interactions with dist-git <a href="https://fedora-arc.readthedocs.io/en/latest/dist-git-move/packit.html" rel="nofollow noopener noreferrer" target="_blank">added</a></li></ul></li></ul><h2>List of new releases of apps maintained by CPE</h2><ul><li><a href="https://github.com/fedora-infra/bodhi/releases/tag/8.0.0" rel="nofollow noopener noreferrer" target="_blank">Major update of Bodhi from 7.2.2 to 8.0.0 on 2023-12-10</a></li><li><a href="https://github.com/fedora-infra/maubot-fedora/releases/tag/v0.4.0" rel="nofollow noopener noreferrer" target="_blank">Minor update of Fedora Maubot from 0.3.0 to 0.4.0 on 2023-12-09</a></li><li><a href="https://github.com/fedora-infra/the-new-hotness/releases/tag/1.3.0" rel="nofollow noopener noreferrer" target="_blank">Minor update of The New Hotness from 1.2.4 to 1.3.0 on 2023-12-08</a></li></ul><p>If you have any questions or feedback, please respond to this report or contact us on <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/redhat/" target="_blank">#redhat</a>-cpe channel on <a href="https://matrix.to/#/#redhat-cpe:matrix.org" rel="nofollow noopener noreferrer" target="_blank">matrix</a>.</p><p><a href="https://communityblog.fedoraproject.org/infra-releng-update-week-50-2023%f0%9f%8e%84/" rel="nofollow noopener noreferrer" target="_blank">https://communityblog.fedoraproject.org/infra-releng-update-week-50-2023%f0%9f%8e%84/</a></p><p><a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://communityblog.fedoraproject.org/tag/cpe/" target="_blank">#CPE</a></p>

Recent searches

Search options

Administered by:

Server stats:

#cpe