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

@b0rk @nelson The GNU project was also an early champion of portability. They *wanted* their software to work everywhere to show that their stuff was *good*. So they built it that way. That had an outsized impact on how people thought about software portability.

(Fun fact, glibc is the only C standard library implementation that worked on multiple operating systems. Nobody else ever did that before and I haven't seen such a thing since.)

@b0rk @zwol This is defining behavior from GNU. It doesn't exist in CP/M or DOS. It doesn't exist in Unix. This "GNU-ism" is so useful that people straight up stopped using POSIX `getopt(3)` over it.

@cassidy For some time now, I've felt like there's this weird tension of feeling like a community vs feeling like a commercial product. And it shows up all over the project in different ways: overly generic names for applications and the UX trends in GNOME vs GNOME Circle vs community engagement vs contributor engagement, etc.

Some of this is kind of normal given the makeup of GNOME contributors and what they do, but I feel like this was one of the outcomes of that tension.

@cassidy To be honest, I think that the existing trend is kind of disappointing. I have many thoughts about why it's happening, but it's too hard to organize right now at nearly 2am after a week of mental agony.

I think there needs to be a step back and rethink about the progression of depersonalization that has been going on and find a new way to express things that acknowledge the project's roots and sense of community.

@cassidy My issue with this is that by "professionalizing" it like this, you've essentially gutted any visibility of the community that the project actually *is*.

Admittedly, I'm not a real GNOME person even though I've contributed a little bit to GNOME, but I used to be a heavy GNOME user. In general, I think giving up the "personality" of projects and communities leads to strictly worse products and services.

@cassidy Yes, I did. I'm specifically responding that it's a bad idea to eliminate this from user-facing aspects of the project, product, and services.

(As an aside, I definitely do not appreciate the assumption that I did not read the blog post before commenting. You know me better than that.)

@cassidy The implication in your blog post is that it has to be different from the foot. What I'm saying is that we should explicitly not do that. A new iteration of the foot is fine, eliminating the foot is what I take issue with.

Fedora went through a similar process a few years ago. A lot of effort was made to ensure we retained all the important aspects of the Fedora infinity logo iconography in the new one.

A new GNOME logo mark should go along the same vein.

@Lyude @gfxstrand @karolherbst I blame the purge of fun in Linux desktops and distributions. 😦

@mcepl @BrodieOnLinux Strictly speaking, that's not completely true. All the major Linux distributions have their own "trees of truth":

- Red Hat with CKI: https://gitlab.com/cki-project/kernel-ark
- SUSE with their thing: https://github.com/SUSE/kernel/tree/stable
- Canonical with Ubuntu Sauce: https://kernel.ubuntu.com/forgejo/ubuntu-kernel-next/linux

In truth, they are derived from Linus' tree, but Linus isn't the direct upstream for these distributions.

@jarkko What do you plan to do differently that will allow v4l2-loopback to make it into the kernel this time?

@jarkko That sounds great. Yeah, you've addressed most of it. There's also a foundational issue that occurred way back when that the v4l people consider it a loophole for proprietary camera drivers. I suspect this might not be an issue anymore now that MIPI allows this anyway and people are *currently* abusing it for proprietary camera drivers *today*.

I did more #SDL3 stuff in @fedora this week!

- Rawhide/F42 now has sdl2-compat 2.30.50 replacing #SDL2.

- Reported a couple more issues and got fixes done.

- Updated SDL3 to v3.2.0 for F40+
- F41: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8c064ffe4f
- F40: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ae473dc268

If you want to develop an SDL3 application for Linux or Windows, Fedora is the place to do it!

If you like my work, consider sponsoring me: https://github.com/sponsors/Conan-Kudo

@thesamesam @kees @brauner @uecker @pinskia Okay, this might be me just being stupid here, but in "PR118575", does "PR" stand for "problem report" or something else?

@pid_eins @axboe @osandov It's a special kind of madness in the Phoronix comments section.

It's kind of funny that the one thing eBPF can't do in Linux is actually do packet filtering (firewall) stuff. Calling it BPF without having that ability is just weird.

@lanodan Earlier today, @icculus tagged an RC for SDL3 with v3.1.10. Everything's all nice and locked down now. And even during the preview cycle, SDL3 had been ABI stable. So in the end, it's all gravy anyway.

This week, I've done a bunch of #SDL3 stuff in @fedora.

- My change for Fedora Linux 42 to replace #SDL2 with sdl2-compat is done. SDL3 powers all SDL applications in F42!
- https://fedoraproject.org/wiki/Changes/SDL2onSDL3

- Reported and got fixed an issue in sdl2-compat that caused mupen64plus to fail to build, backported that fix to Rawhide

- Updated SDL3 to v3.1.10 for F40+
- F41: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8c064ffe4f
- F40: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ae473dc268

If you like my work, consider sponsoring me: https://github.com/sponsors/Conan-Kudo

TIL the Hindus got pretty close to the age of the Earth with "kalpa". 4.32 billion years isn't that far off from 4.54 billion years. Give or take a couple hundred million years. 🤪

@mjg59 @idlestate From what I could gather, the reason it is *still* this way is not technical or legal.

@mjg59 @idlestate Yes, but nobody cares anymore. Most of our ability to push for real change seems to have gone away sometime after 2011. People don't care anymore about FOSS and supporting communities, or even building them in the first place.