All of lore.kernel.org
 help / color / mirror / Atom feed
From: Morten Linderud <foxboron@archlinux.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: distributions@lists.linux.dev
Subject: Re: Looking for advice on how to deal with potential slop packages
Date: Sat, 7 Mar 2026 13:36:18 +0100	[thread overview]
Message-ID: <aawYbre5_xvhfwKA@framework> (raw)
In-Reply-To: <a3f792e918674e208492a077679ae6ffc88ce0c9.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]

A lot of this is probably already a lost cause I think.

Linux accept LLM contributions (look for the `Assisted-by` tags), and there are
already multiple subsystems that are being developed in-part, or full, by LLM
agents.

See the LWN discussion: https://lwn.net/Articles/1026558/

`b4` has also incorperated llm agents for the review workflow.
https://b4.docs.kernel.org/en/latest/maintainer/review.html#configuration

b4 is also heavily developed by Claude these days.

I don't think we can reasonably argue that Linux is not free software, and I
don't think we can argue for forking Linux to remove llm generated code.

My take on this is mostly apathy. I don't think we can reasonably challenge the
use in the FOSS community. The productivity boost of experienced developers
using these is too appealing when we are looking at overburdened FOSS
maintainers.

We've aleady been repeadetly DDoSed by these companies. Spending hundreds of
volunteers hours keeping our services running while the companies extract the
labour to sell back to the FOSS community, using their standing in the Linux
Foundation to further cement their usage in our communities.

Then the FOSS communities use these models without any care of the ethical considerations.

Is this depressing? Yes.

-- 
Morten Linderud
PGP: 9C02FF419FECBE16

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2026-03-07 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 10:38 Looking for advice on how to deal with potential slop packages Michał Górny
2026-03-07 12:07 ` Noé Lopez
2026-03-07 12:36 ` Morten Linderud [this message]
2026-03-07 15:31   ` Simon Josefsson
2026-03-08  4:00     ` Guillem Jover
2026-03-22 23:53     ` Andreas K. Huettel
2026-03-23  8:14       ` Simon Josefsson
2026-03-11  2:48   ` Sam James
2026-03-11  2:50 ` Sam James
2026-03-27  8:01 ` Bernhard M. Wiedemann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aawYbre5_xvhfwKA@framework \
    --to=foxboron@archlinux.org \
    --cc=distributions@lists.linux.dev \
    --cc=mgorny@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.