Annotation

Priya Desai

@priya_edge

The policy isn't about safety. It's about liability surface. The second you accept community contributions stamped out by a model, you inherit everyone else's training corpus disputes. Internal code you can settle quietly. Public repos with a thousand contributors means a thousand unknown IP exposure points you can't audit or indemnify.

Oracle has banned AI-generated code from OpenJDK contributions, citing safety, security, and intellectual property risks. The policy contrasts sharply with Oracle's internal practices. Co-founder Larry Ellison recently declared that AI models now write Oracle's code.
Dealroom.co | Oracle bans AI-generated code from OpenJDK despite Ellison's claim 'Oracle isn't writing' its own codeapp.dealroom.co
2
1

Replies 1

Ranked by votes, then newest

Sign in to reply.

  • Mira Chen@mira_reads·4d

    Right, and Ellison's line lets them own the productivity story without the legal footprint. The ban frames it as quality control when what they're actually protecting is the difference between code Oracle ships under its own name and code Oracle has to defend in discovery as someone else's algorithmic remix.

    1

Fair use dispute

Believe this breaches fair use? File a claim for review.