Linux’s Sole Wireless/WiFi Driver Maintainer Is Stepping Down

Maintainer bus factor & funding

• Commenters see a “bus factor 1” for WiFi as symptomatic of a broader maintainer scarcity in Linux and OSS.
• Several suggest the Linux Foundation should fund more full‑time kernel developers; others note kernel spending is tiny relative to its overall budget, and doubt this will change.
• Some think the EU or other governments might be more likely than US institutions to fund open hardware/driver work, but acknowledge this isn’t happening now.
• One view: as Linux has become de facto corporate infrastructure, it’s less attractive for new volunteer maintainers, who must navigate both OSS and corporate “inner circles.”

Contribution process, culture & gatekeeping

• Many criticize the email-based workflow and patch submission process as archaic and intimidating, especially compared to “drive‑by PRs” on modern forges.
• Defenders argue the process is intentionally selective: the kernel is not a place for casual, low‑quality contributions, and the pipeline demonstrably still works.
• Critics counter that this acts as gatekeeping, filtering out not just noise but “many, many” potential contributors; some report knowing capable people driven away by process and culture.
• Suggestions include using more accessible tooling (e.g., a web-based forge) and doing less to discourage newcomers, while recognizing maintainers are already overworked.

Hardware vendors, users & driver sustainability

• One thread argues the real solution is buying hardware from vendors that explicitly support Linux and expecting those vendors to provide drivers and documentation.
• Others note that all maintainers start as users; more Linux adoption, especially with good out‑of‑box support, can still feed the future maintainer pool.

Personal impact of WiFi support

• Multiple stories describe early Linux experiences where working WiFi (or even winmodems) was the enabling feature that allowed abandoning Windows, sometimes shaping careers.
• Several reminisce about Ubuntu CD-by-mail days, early struggles with ndiswrapper, and how dramatically hardware support and “just works” experiences have improved.

Side debates: OS preferences & motivations

• There’s a long tangent about whether Windows 7 was “objectively” the best Windows and how that notion of “objective best” is itself contested.
• Some defend leaving Windows (even 7) for Linux due to performance, control, and the excitement of the desktop Linux ecosystem at the time (Compiz, etc.).

AI in kernel development

• One commenter predicts an inevitable debate over AI contributing to the kernel.
• Responses stress that maintainership is mostly people-work (coordination, review, testing, vendor interaction), and that current AI isn’t close to replacing that; AI‑generated patches, if useful, can already be submitted under existing processes.

WiFi elsewhere & vendor ecosystems

• WiFi is described as “cursed” in OSS: FreeBSD often has zero or one WiFi maintainer; OpenBSD has strong individual contributors but the domain is vast and complex.
• Some blame specific vendors (e.g., Qualcomm, Broadcom) or note that even friendlier ones (including Intel) still rely on proprietary firmware blobs, complicating fully open support.

Broader lesson: invisible single points of failure

• The thread closes with recognition that many critical OSS components depend on one or a few under‑recognized individuals, echoing the well-known “XKCD dependency” comic.