# Open source maintainership in the age of AI

DevFeed: [Open source maintainership in the age of AI](<https://devfeed.tech/articles/open-source-maintainership-in-the-age-of-ai-17601.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/06/26/open-source-maintainership-in-the-age-of-ai/>)

Author: CLA enforcement

Published: 2026-06-26T18:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Code quality](<https://devfeed.tech/topics/code-quality.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted-coding](<https://devfeed.tech/tags/ai-assisted-coding.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [policy](<https://devfeed.tech/tags/policy.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [quality](<https://devfeed.tech/tags/quality.md>)

## AI overview

This article explains how the Kubernetes community is adapting its maintainership practices to AI-assisted coding. It describes an AI policy requiring contributors to disclose AI assistance, remain responsible for changes, avoid attributing commits to AI, satisfy contributor license agreement checks, and personally respond to review comments.

## Source excerpt

AI has really changed the game around software development. More people are leveraging AI than ever to contribute patches to projects they use. To me, this is a good thing as more folks will contribute patches rather than fork or not fix them. The main problem is that AI has made generating code fast but there has been very little improvement in maintaining code bases. In this post, we will highlight the ways the Kubernetes community is adapting to the world of AI assisted coding. The first step of this journey was to develop an AI policy. This seems mundane and bureaucratic but there were many PRs that derailed into discussions around AI usage. The AI policy helps steer the conversation around the project's stance on AI and provides a clear signal to contributors on how to use these tools responsibly. Kubernetes AI policy The Kubernetes project has established clear guidelines for AI-assisted contributions that balance innovation with accountability. These policies are designed to maintain code quality and ensure human oversight while acknowledging that AI tools can be valuable aids in the development process. Transparency first Contributors must disclose when AI tools have been used to assist with a pull request. A simple statement in the PR description such as "This PR was written in part with the assistance of generative AI" is sufficient. This transparency helps reviewers understand the context and apply appropriate scrutiny. Human accountability While AI tools can assist, the human contributor remains fully responsible for every change. The policy explicitly prohibits: Listing AI as a co-author on commits Using AI co-signing on commits Adding trailers like "assisted-by" or "co-developed" that attribute work to AI This isn't about diminishing AI's role as a tool--it's about maintaining clear accountability. If something breaks, there needs to be a human who understands why and can fix it. CLA enforcement for co-authors The CNCF provides a tool for verifying the