On the rules, citing hperrin:

It sounds like their policy is basically the same as Human Contribution Policy 2-TR. That’s awesome.

Yeah it really fucks with your psyche.

That, at first glance, you cannot distinguish any digital work from being real work, or the result of telling an AI to do it. And the result isn't anybody's work. Except of those the AI stole from.

But I have seen meltdowns like this long before any sort of LLM-based fakery.

As I wrote before: "Linux drama"

Then again, I’m giving a much closer look at Haiku & BSD again since a slop generator was used in the Linux kernel.

As far as I understand, the Linux kernel uses LLMs in practice for code review, not for code generation. And they do not replace human review with it, but use it in addition.

I’m so tired of “Ai big number” headlines. 100+ packages - but how many good ones? (Genuinely, I don’t know, as I don’t the recognize those listed.)

There might be a bit confusion. A package maintainer does not (necessarily) author the packages (the source code of the projects they contain), but typically maintains build scripts and security patches for upstream packages maintained by their authors. This is necessary because build systems and scripts are complex and packages from one distro would usually not fit into another one.

In other words, most code he/she produces are build scripts, and testing and adapting updates. And yes, this is still a lot of work.

A lot of those packages are pretty core to deployments, the docker ones in particular are probably on every developer/homelabber using void (so everyone probably?)

The docker runtimes handle a lot of the container sandboxing and security configuration, and are a huge source of container escape vulnerability.

It is a small and comperatively frugal distro. Which pretty much makes sense for an AI-free distro.

The now orphaned packages include Adapta, Autodia, SFML, abootimg, alacritty, arpwatch, asus-kbd-backlight, backblaze-b2, bash-preexec, beep, binfmt-support, bitlbee-facebook, bitlbee-steam, cdm, clementine, crane, csound, daemonize, darkhttpd, dep, diff-pdf, docker-cli, docker-gc, docker-gen, dtc, embree, entr, etcd, fcron, flannel, flint, font-fontin, forego, freeplane, fscrypt, gede, gettext-stub, git-cola, gkill, glock, go-bindata, go-jira, hans, hivex, hopper, hostaliases, hugo, iio-sensor-proxy, indicator-doom-cpu, interbench, ispc, jbigkit, kaitai-struct-compiler, kubernetes, kvirc, libguestfs, libnfc, libpodofo0.9.7, logstalgia, massren, mbox, mfoc, mkinitcpio-nfs-utils, mksh, moby, motion, openresolv, packer, pd, perl-Template-Toolkit, pinktrace, podofo, python3-Arrow, python3-b2sdk, python3-pdm-backend, python3-xattr, racket, rakarrack, rancher-compose, rmlint, rng-tools, rocker, runit-swap, sassc, scanmem, schroot, sift, splix, sublime-text3, subtle, supermin, sydbox, tag, tbb, terraform, terragrunt, texmaker, thermald, trollock, ttf-ubuntu-font-family, urbanterror-data, urbanterror, usbredir, vagrant, vba-m, virt-manager, virtme, webcat, websocketd, wpa_actiond, xboxdrv, xcompmgr, and yoshimi.

I am using a few of them, for example virt-manager and racket.