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?
All "interim" AI contributions to OpenJDK can and will be sued to make big money off of Oracle if those court cases don't go a certain way. This is ironic given how Oracle has bet almost everything on AI succeeding.
OpenJDK Interim Policy on Generative AI
11–20 of 90 posts
Re: OpenJDK Interim Policy on Generative AI
#12It 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.
Re: OpenJDK Interim Policy on Generative AI
#13How do you enforce this?
In this case, this is coming from Oracle, which holds the OpenJDK purse strings, so being found in violation is also likely to have financial consequences for the violator.
Re: OpenJDK Interim Policy on Generative AI
#14How do you enforce this?
Re: OpenJDK Interim Policy on Generative AI
#15Seems 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?
I suspect one of the principle reasons for the blanket decline is specifically that AI generated PRs are already responsible for a substantial uptick in the amount of work required to be done by maintainers. Engaging in discussions about those PRs may be more fulfilling and useful for the developer but it also then increases that work yet again manifold, so that would likely be highly counter-productive. What I don't…
You can. The policy explicitly allows you to use AI for understanding the codebase, debugging, etc. It just says “no AI generated content”. So if you use Claude to increase your understanding but then write your own code, that’s fine.
Re: OpenJDK Interim Policy on Generative AI
#16While 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 ad…
Who is using an LLM as a spell checker?
Re: OpenJDK Interim Policy on Generative AI
#17How do you enforce this?
Re: OpenJDK Interim Policy on Generative AI
#18Re: OpenJDK Interim Policy on Generative AI
#19While 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 ad…
> this would exclude most spell checkers, as they often are LLM based Who is using an LLM as a spell checker?
Re: OpenJDK Interim Policy on Generative AI
#20While 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 ad…
But this also bans "simple" AI-powered auto-complete, like Zed's Zeta2 model. This is a very conservative model that rarely tries to propose more than a few obvious lines (at least in my use cases). If a developer accepts a three-line autocomplete that introduces a bug, that's kind of on them. Honestly, about the only thing that Zeta2 is good for is reducing the risk of RSI.
To be fair, it's also their project, and I completely support their right to set whatever policies they want.