Welcome to the first of a monthly set of updates on key areas within Fedora. This update includes Fedora Council representatives, Fedora Editions, and Fedora Objectives. The content here is based on the weekly updates submitted to the Fedora Council, published to the project dashboard.
The Minimization objective was approved by the Council earlier this summer. It has published a short-term action plan and is recruiting members. In the past month, it has started using rpm-showme to analyze the dependencies of packages. The team is working with the Fedora IoT team to get feedback and testing on the feedback pipeline.
The Fedora CoreOS team published a preview release on July 24. This was followed by 30.20190801.0, which successfully demonstrated a gradual rollout. The previous release runs on AWS’s us-east-1 region, bare metal, QEMU, and VMware. The team gave a talk at Flock and two talks at DevConf.us. Work is underway to fix issues like manual artifact signing and implement release streams and automatic updates.
The Fedora Server team removed over one gigabyte from the DVD by removing unnecessary packages that had built up over time. However, Stephen Gallagher writes
Fedora Server is on life-support. It continues to build and be released, however there is no clear vision for its future. At the “State of Fedora Server” session at Flock 2019, it was generally agreed that the project needs to be restarted, with an eye on finding goals that encourage more participation.
The Fedora 31 schedule remains on track, with the preferred beta release targeted for 17 September. Ursa Prime is code complete, but testing is deferred to Fedora 32. Other updates can be found in the weekly FPgM reports.
Diversity and Inclusion
During Flock, the Diversity and Inclusion team brainstormed ideas to maximize the impact of the team given limited contributions. They conducted interview sessions with community members in order to collect feedback. The team is working on events for other underindexed groups using Fedora Women’s Day as a template.
They also worked with the localization (l10n) team to identify and translate important content.