Zen

Source string Source string

6/10000 · 6

The string is read only.

English Actions
Fedora Minimization Objective
Second Phase Proposal
Objective lead: Adam Samalik (asamalik)
The problem
While Fedora is well suited for traditional physical/virtual workstations and servers, it is often overlooked for use cases beyond traditional installs.
Some modern types of deployments — such as IoT and containers — are quite sensitive to size. For IoT that's usually slow data connections (for updates/management) and for cloud and containers it's the massive scale.
A specific example is Systemd — while being very useful (everybody loves Systemd) and is always present on physical systems, it is rarely needed in containers. So it wasn't a problem for packages to require Systemd just for __systemd-sysusers__ to create users. However, in containers, that means a significant size increase.
Besides that, basically all types of deployments benefit from a reduced size, as there is a direct relationship between the installation footprint and attacks surface & relevant CVEs.
Vision
Thousands of individual and corporate contributors collaborate in the Fedora community to explore new problems and to build a fast-moving modern OS with a rich ecosystem allowing them to experiment on modernising their infrastructure.
Mission
Helping open source developers, sysadmins, and Linux distribution maintainers to focus on what's relevant for them.
Outcomes
Fedora is a popular platform because its ecosystem is both cutting-edge and well optimized for modern deployments such as IoT and containers. That makes many people use Fedora rather than to build and assemble their own artifacts directly from upstream projects. And that relieves the pressure on open source developers caused by users who would otherwise ask for their specific security and other issues to be fixed quickly.
So:
Open source developers can focus on feature development
Sysadmins can easily consume pre-built bits that also get regular updates
Fedora contributors (vendors and individuals) can collaborate within the Fedora community on exploring and developing open source solutions to problems of the future
Outputs
Specific use cases are defined in Fedora. The community then focuses on those use cases with development and maintenance, optimisation (like minimisation), and testing (like CI and gating). These use cases can be transparently prioritized for infrastructure resources based on community interests.
Feedback Pipeline actively monitors each use case and records the size and the dependencies required for it to run. Data history is kept and shown to see changes over time. And to keep things small over time, Feedback Pipeline also automatically detects size increases and potentially automatically opens Bugzilla bugs to track/fix/justify such increases transparently.
An active focus on minimization means that our maintainers produce size-optimised content with the same or lower amount of effort. Tooling, services, and data help them to make the right decision about dependencies easily, and to keep things smaller over time.
Actions
**Identify relevant use cases** and allow the community (meaning not just the Minimization Team) to define their own. We think of a use case as a set of packages installed in a specific context, having a specific purpouse — such as __Apache HTTP Server Container__. Define use cases at least for:

Loading…

User avatar None

Source string added
Vision
4 years ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Inconsistent: Indonesian, Finnish, Chinese (Simplified) (zh_CN), Portuguese (Portugal), Portuguese (Brazil), Dutch, Turkish, French, French, Swedish, Swedish

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: Title ===
Flags
no-wrap, read-only
Source string location
./pages/objectives/minimization-phase-2.adoc:17
String age
4 years ago
Last updated
a year ago
Source string age
4 years ago
Translation file
pot/master/pages/objectives/minimization-phase-2.pot, string 9