Hi Chris, On Tue, Nov 25, 2025 at 04:30:41PM +0000, Christopher Klooz wrote: > the AI that was used in the Change Wrangler process introduced > changes beyond formatting, and so I cannot say for sure if this > content is still identical to my proposal.
If you cannot say that of your own text that might suggest the proposal is too wordy and confusing in the first place. Several people have suggested you rewrite it to be shorter, more to the point and less adversarial. The proposal as written seems to just demand that Fesco tell the maintainers of the user space observability tools to drop their current policy/package and then report what breaks so that you can document that breakage. Which I feel is not serious. In general I don't find this proposal very constructive and hope you find something more useful to work on. You are presenting this as some kind of users vs developers "fight". Where there is only some binary choice of being pro-users or pro-developers. I don't think this is useful. I do think we should encourage everybody to think of themselves as hackers and to make it easy to explore all levels of the "full stack". That is also why I think your proposal is not great. You are essentially proposing to make exploring, observing, debugging, profiling, tracing your own processes impossible by default. Which makes it harder to become an admin or developer and more dangerous. I have tried to provide better explainations of the purpose of the Yama LSM and default-yama-scope dependency and less misleading descriptions of "default" choices. But you essentially just reverted/removed those. I also tried to explain how you could work on better security mitigations you seem to want, which you have ignored as alternatives to your proposal. I realize that is all more work than just documenting some user space packages are now broken by default. But it would be much more useful. Cheers, Mark -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
