Notices by Neal Gompa (ニール・ゴンパ) :fedora: (conan_kudo@fosstodon.org), page 3

@js @hanalei (In case anyone forgot, I'm one of the upstream developers for Lugaru over at https://gitlab.com/osslugaru/lugaru)

@js @hanalei Well... Lugaru's native scripts are CMake scripts. I'm not really going to accept having plain makefiles for a port of Lugaru, assuming there's a goal to upstream it.

@vwbusguy @adamw @maxamillion You kept forgetting to give me one. But you did scare me with your spec file!

@ariadne @ocdtrekkie @scott @msw And also, put bluntly, neither Fedora nor Debian will accept anything SSPL because they don't comply with OSD, FSF-Free, nor DFSG. Both distribution organizations more or less require a license to fit among at least one of these and provide their own lists with justifications when they make their own decisions.

e.g. Fedora: https://docs.fedoraproject.org/en-US/legal/allowed-licenses/

@pid_eins @dalias @ariadne @leftpaddotpy @dysfun Technically you could have simple program emit udev events back to systemd and not have udev, but ehh, why? Even embedded systems I worked on several years ago were complex enough to need some of udev's capabilities anyway.

@ariadne @lanodan @pid_eins @luis_in_brief Most of the alternatives are half-and-half (with a bit of eventing thrown in for fun), which is arguably worse. In the past, Upstart did this everywhere, and it made it really confusing to understand what was going on and how to reason the interaction model.

@alice @cassidy We should acknowledge that money does in fact steer the direction. Ignoring that is foolish. Money affects priorities and drives the roadmap in all large projects.

For example, KDE's Wayland efforts have been supercharged over the past three years by a combination of a distro actually using it by default and people being funded to enhance it to the point that it is (IMO) the most advanced Wayland environment today.

A first for me: a perfectly sliced and peeled avocado! 😄

@volpeon @aks It's not illegal, but it's supposed to not be possible to trademark it.

@doctormo @andy @Di4na @pnathan The correct answer is that as soon as you know you have *one* system that it matters on, you should be funding it. For each extra system, you can incrementally add to it. The problem with all the existing solutions is that they are all designed to figure out how much you can ignore, not how much you should support. The attitude is just wrong for SLSA, SBOM, etc. Everyone just does risk assessments because nobody wants to actually fix the problem.

@whot I vaguely remember it used to just be called `/usr/bin/X` or is that just me being crazy and making stuff up?

@whot Yeah, I wouldn't want to go back further either. At that point, I think you start getting into weird history artifacts from the conversion from CVS...

@lanodan There's also an equal amount of avocado, I used half an avocado for this!

One of the more interesting sandwiches of mine 😋

@funkylab @lanodan @marcan I don't know if that's something separate from the folios work that is going on for all the filesystems, but if it isn't, then yes it's being adopted slowly everywhere.

@wjt The Windows 95 era warning always confused me, because it made the HTTP->HTTPS transition sound like a bad thing...

@funkylab @lanodan @marcan No. It's a terrible design choice, but we're stuck with it until everything moves to folios.

@lanodan @marcan This is a Linux thing. A lot of filesystems have had this problem, some still do, and some are in even worse position than Btrfs. For example, F2FS does this, doesn't support subpage at all, and it used to crash when you tried to use it on non-4K kernels (that was recently fixed).

Roast beef melt sandwich 😋

@BrodieOnLinux @marcan Most Linux subsystems do not have a bug tracker. It is extremely difficult to track down and identify whether a bug has been reported to upstream Linux. I'm pretty sure @adamw is magic, because he seems to always know when I ask him.