44

Timestamps:

00:00 Intro

00:36 Sponsor: TuxCare

01:46 KDE's AI policy

06:42 Existing AI policies

10:06 Going further on AI

12:58 My stance on AI

17:05 FOSS projects: yes or no to AI?

28:02 Sponsor: Tuxedo Computer

you are viewing a single comment's thread
view the rest of the comments
[-] brucethemoose@lemmy.world 7 points 1 day ago* (last edited 1 day ago)

This was an issue in the computer science field well before LLMs, though (like in many areas) they did pour gas on the fire.

TBH I think it’s more of an issue for paid software. Manpower and burnout is the bottleneck for FOSS projects, and contributions are largely thankless, hence I think amongst the people who do contribute, there will be more of an interest in truly learning the codebase.

[-] naught101@lemmy.world 6 points 21 hours ago

Multiple FOSS projects have been complaining over the last year or so that they are getting swamped with LLM-generate PRs that are often low-quality, but still require a similar amount of time to review. LLMs are shifting extremely lited FOSS core maintainer capacity away from development and into time-wasting code reviews with a high rejection rate.

[-] brucethemoose@lemmy.world 3 points 14 hours ago* (last edited 14 hours ago)

Well, yes, and that’s exactly what the KDE policy is addressing. They’re saying “we are going to reject vibecoded PRs, unconditionally; so don’t bother submitting them.”

[-] ProdigalFrog@slrpnk.net 1 points 10 hours ago

The biggest contributor to the backlash of the proposed policy was the additional aspect explicitly not requiring AI used in a PR to be disclosed, regardless of its quality (and which is unrelated to the ability to quickly reject obvious slop PRs).

this post was submitted on 24 Sep 2026
44 points (81.4% liked)

Linux

15040 readers
506 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS