OpenJDK’s new interim policy bans any contribution generated by large language models, citing intellectual‑property risks, reviewer burden, and the critical safety role of the JDK, while Oracle simultaneously embraces AI internally, highlighting a stark double standard across the open‑source ecosystem.
The article examines OpenJDK’s new interim policy that outright bans any AI‑generated contributions, explains the underlying concerns about reviewer workload, safety, and intellectual‑property risks, contrasts Oracle’s internal AI adoption with its open‑source stance, and surveys how other major projects handle AI‑assisted code.
The article examines why Debian, despite its massive package base and developer community, remains indecisive on AI‑generated code policies, while smaller projects like Gentoo and NetBSD have imposed outright bans, analyzing false‑positive detection rates, legal uncertainties, trust‑based governance limits, and the broader implications for open‑source infrastructure.
