- cross-posted to:
- programming@programming.dev
- cross-posted to:
- programming@programming.dev
You must log in or # to comment.
AI policy dispute
What dispute? It’s pretty clear actually. Bad maintainer throws hissy fit when caught breaking the rules for contribution. The maintainer volunteered that. There’s no dispute.
As I wrote below, it is a matter of boundaries.
Bad maintainer throws hissy fit when caught breaking the rules for contribution.
Do people do that because of AI mania?
But yes, I think this will bring the Void Linux distribution a couple of supportive users, some new people curious to try it, and perhaps new maintainers which share their view.
People do that because they’re selfish. That’s not a dig, it’s a truth. Pure altruism does not exist. Even when you do something good nobody sees you do and knowing you’ll get no recognition for you’re doing it because it makes you feel good. To varying degrees you can come close to true altruism as that example does but it’s unattainable. In this case the maintainer lost that feel good feedback from recognition and decided rather than fixing the error it felt better to be more selfish.
tl;dr: people suck
AI or not, I refuse to believe anyone is capable of being the sole maintainer of 100+ anything while preserving any kind of quality. Most of these packages were probably functionally abandoned already, if not technically.
Well maintaining a KISS repo of 100+ packages is something I once did to myself, so it is possible.
AI or not, I refuse to believe anyone is capable of being the sole maintainer of 100+ anything while preserving any kind of quality. Most of these packages were probably functionally abandoned already, if not technically.
He/She was maintainer of the Void Linux packages, that is the package build scripts, updates, etc., not the projects which these packages are based on.
For example, Guix has now over 32000 packages, including an Emacs package. But of course, they did not re-create Emacs to make that package - they just made a build definition which uses the Emacs git repo, in order to build the Guix package. Or in the case of Ubuntu, it is based on the package definitions in Debian testing, so the Ubuntu maintainers do not have to write all the build scripts or package definitions - but they still have to do significant work in order to adapt them that everything fits together.
Or with Arch Linux, the packages are taken relatively vanilla from upstream, they package stuff more “as is” as compared to Debian. Which means less work, and often more clarity for experienced users.
Coming back to Void Linux, this means for these 100+ Void Linux packages which are currently orphaned, it is feasible that other people with good Linux experience adopt these, with a reasonable effort - some are important.
Distro package maintainers are different than software dev maintainers.
They mean no one can be reasonably be up to date on software security updates, and (ideally) ensuring all packages changes are not malicious (as well as the small stuff like properly integrating to the distro, but idk how void works enough to comment on that)
Cause like I can write a ton of guix configs that’ll probably run until the next ice age, but that does nothing about the dev who’s software I packaged, that now decided they’re personally god and need to spread christ as fast as possible.
(Also off topic but that’s the power and curse of nixos-like distros, its too easy to package so odds are the shit ain’t updated, and suddenly there’s 1000 Firefox packages in nixpkgs)
They mean no one can be reasonably be up to date on software security updates, and (ideally) ensuring all packages changes are not malicious (as well as the small stuff like properly integrating to the distro, but idk how void works enough to comment on that)
Some people do an astounding amount of work.
And then there are many, many, which help a little.
Also, if, say, somebody finds that in Debian testing is a malicious package, people which maintain Arch will learn that. Open information sharing between many thousands of people willing to coordinate is a superpower.
ah, and the challenges to scale once again hit the wall … they’ll have to use AI to police maintainers to keep them from using AI 😂
Do we need to live in a police state to keep people from stealing?
do we have to be burdened by western existential narratives vis a vis Orwellianism that don’t scale? seemingly, yes! society seemingly doesn’t scale gracefully … though China looks better-adapted to present reality
You are absolutely right about Sartre. Some bad nights I dream I am talking with confused bots, and can’t exit by switching off the box.
then it’s probably good for you that you’re not bothering to wake up.
happy to be your hell, good citizen ☺️ I wish you the best
i would rewrite the title as “Slopper tried to be a maintainer on void linux: abducted and orphaned 100 packages they maintained after being discovered and forced to comply”
To say that, you would need proof that this was in bad faith, wouldn’t you? I wrote this comment about polarization for a reason.
i need proof of the already proben impact of AI and AI datacenters over territories in the country i live in? x3
“oh no, i am a maintainer of +100 packages and somehow i did not check any of the proofs about AI impact in the world”
i need proof of the already proben impact of AI and AI datacenters over territories in the country i live in?
No, proof about the maintainers intentions. Because you make a statement about them.
I am extremely worried about the implications of “AI” as well, but you do not win this discussion by name-calling. Are you aware that the Linux community is also a target of trolling?
It’s because they changed the deal! The deal was I had to write code, and now the deal is that I have to write code and not not write code! That’s crazy!
- The maintainer, probably
FOSS isn’t entirely immune to AI mania (or rather, LLM mania).
I think LLMs can tentatively be used for some useful things, like checking for security bugs in new kernel code. But this does not answer the question whether it should be used, because there are many important points in contra. Apart from massive pollution of the biosphere, it causes also a kind of pollution of collective knowledge and understanding. Which is a very important aspect of FOSS.
For example, if a distribution’s package build code is done by LLMs, it is likely to become harder to understand over time. This is probably not the kind of technical debt which a distribution with limited resources wants to have. And you see, the decisions of individual affect other people to, which is why we have rules.
Just wanted to chime in an say I appreciate your more balanced and or nuanced take on this topic.
I see a lot of hate for AI and for good reason, but it does have its use cases.
Unfortunately, like NFTs when they became popular for scams or whatever the fuck people started doing with them, it quickly became used for making garbage, scamming, and being shoved into everything companies thought it could be.
And the scale at which AI is harming our planet is too great a cost for what it does right now or even if it was amazing at what it did. Theres a lot of issues with it.
Also, polarization is another danger, it can seriously hurt communities, and also can be used against us. (I saw that with some dance communities during COVID.) We need to navigate between Scylla and Charybdis here, or possibly even avoid the journey.
