2025-09-24 14:00:40
Today I’m a very proud and happy open standards maintainer: OpenAPI 3.2 is now available! The release notes are a good place to find out what’s new (it’s a lot!) https://github.com/OAI/OpenAPI-Specification/releases
Huge thanks to our contributor community, you are amazing!!
Well, I am complaining about #AI slop introducing some random bugs in a minor userspace project, and in the meantime I learn that #Linux #kernel LTS developers are using AI to backport patches, and creating new vulnerabilities in the process.
Note: the whole thread is quite toxic, so I'd take it with a grain of salt, but still looks like the situation is quite serious.
"You too can crash today's 6.12.43 LTS kernel thanks to a stable maintainer's AI slop."
And apparently this isn't the first time either:
"When AI decided to select a random CPU mitigation patch for backport last month that turned a mitigation into a no-op, nothing was done, it sat unfixed with a report for a month (instead of just immediately reverting it), and they rejected a CVE request for it."
#security #LLM #NVIDIA #Gentoo
I will be be at #FrOSCon during the weekend, in a triple role: As a @… and @… maintainer at our respective booths, and as part of the embedded dev ro…
Ah yes, classic "important backstory" that turns out to be half-assed personal attacks against a OSS maintainer; meanwhile no syllable lost about a millionaire who is speedrunning racism.
Last year I raised the idea of Open Source Quality Institute: https://www.tbray.org/ongoing/When/202x/2024/04/01/OSQI
Today, I’m wondering if anyone has tried to launch an Open-Source-Maintainer guild or union or whatever? It could set rates and draft contracts…
Interesting debian-user find:
The YouDao plugin of the stardict-plugin package on Debian by default captures the X selection buffer — which can be FROM OTHER APPS — and sends the entire text, unencrypted, to remote servers, without telling the user that it will do this.
The maintainer has marked this bug as "wishlist" because they consider the mention of this in the package description to be sufficient warning.
The package can be pulled in as a Recommends.
I just had to find out about a feature in one of my favourite open source software packages by finding it used in the test suite.
The worst part is, I'm the maintainer of the software package.
Frage an alle #GitLab Admins: gibt es eine Möglichkeit, einen User automatisch auf alle Projekte Instanz-weit in GitLab self hosted zuzulassen?
Für eine Überprüfung reicht ein Audit User nicht aus und ich möchte das so weit wir möglich automatisieren, auch für neue Projekte.
Growing Mathlib: maintenance of a large scale mathematical library
Anne Baanen, Matthew Robert Ballard, Johan Commelin, Bryan Gin-ge Chen, Michael Rothgang, Damiano Testa
https://arxiv.org/abs/2508.21593
When you see that a person with #Debian .org e-mail address is the maintainer of BLAS packages in #Gentoo: "what a nice collaboration…"
When you realize said person just took #GSoC money in 2019, and disappeared immediately afterwards: …
#FreeSoftware
1. Learn a bit about #BLAS / #LAPACK packaging for dayjob.
2. Learn that #MKL in #Gentoo is quite outdated. Take it over, bump it and improve the packaging.
3. Get curious about #FlexiBLAS. Start playing with it. Package it for #Gentoo.
4. Learn that runtime BLAS / LAPACK switching is quite broken. Come up with a FlexiBLAS transition plan and a proof-of-concept.
5. Notice inconsistency in ILP64 support flags. Propose unifying the behavior.
6. Learn that BLAS / LAPACK packages in Gentoo are pretty much unmaintained.
Well, looks like I'm the new maintainer of the whole stack, I'm working on consistent ILP64 support now, and then I'll have to rebase the FlexiBLAS transition bits.