Vibe code is flooding open-source projects with an ever-growing volume of pull requests and ideas.
Banning AI contributions isn't the answer, yet it is difficult to resist.

How can open source projects survive and keep progressing despite the pressure?

This talk covers the project playbook we're building in CNCF Harbor and Harbor Satellite: defining a clear project direction so contributors, human or AI-assisted, know what's in scope before they contribute. Setting explicit acceptance criteria and guardrails. Using AI on the maintainer side to triage, review, and filter the growing volume of contributions. Deciding as a project where your boundaries are, what's core, what's an extension, and what's out of scope, so you stop drowning in well-intentioned feature PRs that slowly erode coherence.

We share what works, what fails, and how we are rethinking open-source, contributions, community, and project positioning as a whole.