On Thu, Dec 12, 2019 at 12:59:03PM +0100, Adam Samalik wrote:
The Minimization Objective[1] has been going on for a while. There
are two
high-level goals: making things smaller, and keeping things smaller. On the
keeping smaller side, the team prototyped a service called Feedback
Pipeline [2] that monitors use cases for their installation size and
dependencies, including a size history. This will help us see bigger
changes in size for things the community cares about [3].
I already got some feedback from a few individuals I asked while developing
it, but I feel it's in a good enough state for a more broad feedback. So I
have a few questions:
1/ We plan to send weekly size updates to the devel list. Would that be
useful? What should they include?
It would be great if they could include the size +/- of all the images.
Of course the most important ones would be boot.iso, workstation and
server, but labs and spins could be very helpfull as well.
2/ Regarding the use cases [4], especially the container ones, could people
please review and give feedback to those? Are all the packages there
actually required? I'm specifically looking at the "nss_wrapper" package
that drags in Perl and cmake which makes it huge.
Which use case is that? All of the container ones?
Sounds like a nice link to drop, but someone would need to find out the
details. Why is it included?
kevin