OpenJDK Interim Policy on Generative AI
blenderob
69 points
80 comments
July 30, 2026
Related Discussions
Found 5 related stories in 297.1ms across 15,510 title embeddings via pgvector HNSW
- Policy on the AI Exponential yjp20 · 147 pts · June 10, 2026 · 62% similar
- GCC steering committee announces AI policy arto · 271 pts · July 30, 2026 · 59% similar
- Ripgrep AI Policy singiamtel · 64 pts · May 27, 2026 · 59% similar
- How employment changes when firms adopt generative AI nreece · 23 pts · July 01, 2026 · 56% similar
- Have a Coherent AI Policy ai_critic · 64 pts · May 14, 2026 · 56% similar
Discussion Highlights (8 comments)
SomeHacker44
Seems short sighted for an interim policy, to me. Why not just require clear and detailed disclosure of the use of said tools, to generate data for which to make a properly informed non interim decision?
pizlonator
How do you enforce this?
kdavis
While I understand the caution, the current policy seems too draconian. It states in part: > Until that policy is in place, the Governing Board has approved this interim policy: > Contributions in the OpenJDK Community must not include content generated, in part or in full, by large language models... Note, this would exclude most spell checkers, as they often are LLM based. That said, they do soften this with the addition: > Q: Is it okay to continue using the spell-checking, grammar-checking, auto-completion, and refactoring features in my editor or IDE? > A: Yes, so long as they are not based on large language models or similar deep-learning systems. This addition will likely not help as most spell checkers are OS/IDE services and their implementation details are opaque to users.
effnorwood
Oracle determining how to add more sypware while not violating their own TOS
abc42
My prophecy is that in 3 years we'll see a complete reversal of this. Using GenAI to code will be the default and we'll see policies that put limits on human/artisan development. Possibly even projects that outright ban non-LLM development.
Viliam1234
This makes sense. AI contribution is basically just "prompt + AI work". Even if you are okay with AI work per se, you should accept prompts (after reviewing them) and let your own AI generate the code (and then also review the code)... rather then accept an output of someone else's AI with an unknown prompt, that may or may not include an instruction to create a vulnerability. In the age of AI, the prompt is becoming the actual source code. Accepting AI-generated code would be like accepting binary code from unknown source.
mrkeen
Am I not even allowed to use https://www.oracle.com/artificial-intelligence/enterprise-ai... ?
piinbinary
> Most generative AI tools, however, are trained on copyrighted and licensed content, and their output can include content that infringes those copyrights and licenses To some extent, it feels like the genie is out of the bottle on this. There's so much LLM-generated code out there, and I'm sure plenty of it could be argued to infringe a copyright or license (though I think the legal bar for counting as infringement is set too low), that there's no way to go back and undo it. That said, OpenJDK might be afraid that someone will decide to make an example of them because they are a high-profile target.