Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Guidelines for LLM generated contributions
by
ClosingAp Open Source Integrators Europe, LDA., Daniel Reis
Hello all,
It begs the question of what is "AI generated code".
AI can assist code writing from code completion suggestions, to full design and code writing.
Or just assist with code reviews or issue resolution, without writing code.
In the end AI is just a tool.
Irresponsible use can happen with AI or any other automation tool.
What really matters is the behavior of people using these tools.
I feel that we might need a guideline regarding responsible use of automated tools, including AI, rather than specifically for AI use.
This could be fitted into a code of conduct for the community.
Thanks
Daniel
It begs the question of what is "AI generated code".
AI can assist code writing from code completion suggestions, to full design and code writing.
Or just assist with code reviews or issue resolution, without writing code.
In the end AI is just a tool.
Irresponsible use can happen with AI or any other automation tool.
What really matters is the behavior of people using these tools.
I feel that we might need a guideline regarding responsible use of automated tools, including AI, rather than specifically for AI use.
This could be fitted into a code of conduct for the community.
Thanks
Daniel
On 18/09/2025 08:41, Stefan Rijnhart
wrote:
Dear all, at least one contributor is planning again to flood the OCA projects with PRs for module migrations: https://github.com/OCA/web/issues/3285. This volume is likely made possible through automation, with an LLM generating the actual migration code (on top of, hopefully, a more deterministic tool like OCA's odoo-module-migrator). Regardless of the volume and the submitter, if the submitter has reviewed, refined and tested the code generated by an LLM, this should not be a problem but as a reviewer I'd like to know what I can expect. Holger Brunn pointed out to me that in other projects, this may be covered by a demand in the guidelines to disclose LLM usage and its extend. For an example, see https://github.com/ghostty-org/ghostty/pull/8289/files. I would very much like to see such an addition to the OCA guidelines. Additionally, I would like to suggest that the basic premise (the generated code is indeed first self-reviewed, refined and tested) is also made explicit, and that it is unacceptable to pass on reviewer comments to the LLM only to copy back the LLM's response (which has happened to me on one or two occassions). Can I have a temperature check for your support for such an addition to the guidelines? Or do you have other ideas or perspectives on the matter? Cheers, Stefan -- Opener B.V. - Business solutions driven by open source collaboration Stefan Rijnhart - Consultant/developer mail:stefan@opener.amsterdam tel: +31 (0) 6 1447 8606 web:https://opener.amsterdam_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL
REIS
MANAGING PARTNER
MANAGING PARTNER
>> Schedule time on my calendar.
M:
+351 919 991 307
E:
dreis@OpenSourceIntegrators.com
A:
Avenida da República 3000, Estoril Office Center, 2649-517
Cascais
Reference
-
Guidelines for LLM generated contributions
byOpener B.V., Stefan Rijnhart-
Re: Guidelines for LLM generated contributions
byCamptocamp SA, Joël Grand Guillaume -
-
-
-
Re: Guidelines for LLM generated contributions
byInitOS GmbH, Frederik Kramer -
-
-
-
-
Re: Guidelines for LLM generated contributions
byMint System GmbH, Janik von Rotz
-