Repository navigation
Trust & Triage in the AI Era #122
BenTheElder
started this conversation in
Maintainer Summit NA 2026
Replies: 2 comments 1 reply
|
I'm happy to help with this particular topic! |
1 reply
|
This session has been selected for 2:20 PM: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/features-add-ons/maintainer-summit/?id=1318475#schedule Thank you for leading this discussion! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Topic
Trust & Triage in the AI Era
What projects are involved?
Kubernetes; any and all CNCF maintainers thinking about these problems
Description
Sustaining trusted open source projects in this new environment raises several pressing questions, with two core challenges standing out:
I don't think 1) is solvable without some component of 2).
How do we build genuine trust when pull requests and review comments are increasingly automated? How do we safeguard against future supply-chain threats like the xz utils backdoor in this environment?
What does advancement on the contributor ladder mean when a maintainer spends hours reviewing code, only for the author to prompt an AI agent to address the feedback? Who actually performed the work, and who gained a deep understanding of the project's codebase and architecture?
How do we effectively filter incoming changes when individual developers can generate massive volumes of pull requests with minimal effort? What stops malicious actors from trivially gaming these workflows, and how do we ensure legitimate contributors remain visible through the noise?
While large-scale projects like Kubernetes have faced similar challenges before, the scale and velocity are escalating rapidly.
In my opinion these questions are far more critical than surface-level metrics like PR merge velocity or initial review response times. Throughput does not equate to value or quality.
We must maintain confidence among our community and downstream users that we are building a secure, high-quality infrastructure foundation.
We need strategies to cut through low-effort automated submissions, highlight high-value contributions, and adapt how we mentor and cultivate future maintainers.
The goal of this session is to brainstorm actionable solutions and guidance for CNCF project communities.
Potential policy changes are NOT out of scope, unlike #115
Session lead contact information
@BenTheElder: https://cloud-native.slack.com/team/U01FKJ04708
@soltysh: https://cloud-native.slack.com/team/U0194M9FC5A
All reactions