<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Maintenance on Arkadii Yakovets</title><link>https://arkid15r.dev/tags/maintenance/</link><description>Recent content in Maintenance on Arkadii Yakovets</description><language>en</language><copyright>© Arkadii Yakovets</copyright><lastBuildDate>Sat, 15 Aug 2026 13:00:00 -0700</lastBuildDate><atom:link href="https://arkid15r.dev/tags/maintenance/index.xml" rel="self" type="application/rss+xml"/><item><title>AI slop: contribution gates that keep maintainer queues human</title><link>https://arkid15r.dev/ai-slop-contribution-gates/</link><pubDate>Sat, 15 Aug 2026 13:00:00 -0700</pubDate><guid>https://arkid15r.dev/ai-slop-contribution-gates/</guid><description>Unsolicited, low-effort pull requests burn maintainer attention on open projects, and AI made that volume cheaper to produce. This post starts from OWASP Nest queue pressure around mentorship seasons and the project's issue-first, assignment-before-code workflow. It then contrasts the archived check-pr-issue-action -- an assignee gate with an issue-link prerequisite -- with check-contribution-action's multi-check maintainer DX. The newer action adds selectable gates, selective auto-close, optional DCO and commit signatures, and safer wiring guidance for pull_request_target. Context also spans OWASP Nettacker and the Open World Holidays Framework, without pretending the bots can detect AI.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://arkid15r.dev/ai-slop-contribution-gates/feature.jpg"/></item></channel></rss>