sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs
I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility
the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

May is #maintainermonth
https://maintainermonth.github.com/
A month for open source maintainers to gather, share, and be celebrated.
Are you a maintainer? You can submit your idea!
Nothing against #French people, but literally the only people that reach out to me in a foreign #language (besides English and German as it's obvious I'm located in Germany) are French.
If you open an #issue, you want sth from me, so make sure I understand it.
Do you think it's harsh to ignore these issues or ask for an English translation?
#OpenSourceEconomy allows a #maintainer of #opensource software to market their services to #companies which depend on #software or could benefit from #coaching.
I really liked this notice that the @biomejs maintainers put in one of their discussions on GitHub. Hopefully folks read it, sadly I suspect the abusers won't
Respecting #maintainer time should be in #security #policies
https://sethmlarson.dev/respecting-maintainer-time-should-be-in-security-policies
After a volunteer developer rejected its code, an autonomous AI agent independently researched his background and published a hit piece attacking his character. The incident at Matplotlib shows how theoretical AI safety risks are becoming real.