English Burmese
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.
**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:
__Fedora IoT__
__Python 3__
Also, consider looking at container-native use cases, such as:
__GO for container apps__
__Rust for container apps__
Collect specific use cases by talking to people at tech events, internet forums, and any other viable venues.
**Extend monitoring services** (Feedback Pipeline) that:
Visualize dependencies and a total size for each use case
Monitor size changes over time
Auto-detect large size changes
Notifies maintainers about unexpected size increases