Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Guidelines for LLM generated contributions
byHi Quentin
I agree with everything you mention here. Let's not fall for the narrative of OpenAI.
Your personal take would be more suitable to be discussed in this thread: https://odoo-community.org/groups/contributors-15/contributors-2145247
I suggest to separate further discussions for a technical solution and community ideals on this topic.
Regards, Janik
Hello,
I agree with having changes in Guidelines to disclose LLM usage as in Ghostty project, thanks for the proposal
Raphaël telling "it is not going to stop any time soon..." are pure supposition and I think it's also part of the narrative of OpenAI etc. to let us think that this is inevitable.
No one can predicte futur so we can say if it's going to happen or not.That's why we can start adding this guidelines and adjust in future times.
I think that's the bare minimum.
Personally, I would be in favor of adding a line to mention the disastrous consequences of these technologies, such as:
Most LLM technologies are based on the exploitation of infinite resources, while we are already dying from not having enough drinking water for everyone, modern slavery, and the takeover of our private lives by capitalist giants. With great responsibility comes great power: let's code less, code better, document more, and cooperate more.
___
This email thread contains other subjects so I will provide my point of view
This technologies and all technologies are based on mega structure deeply linked with capitalismDo we want to depend on technologies that are so costly in terms of water and energy in a world where resources are inevitably becoming increasingly scarce?
Do we want to depend on technologies based on data theft, forced labor, and modern slavery?
It seems to me more ethical and even more pragmatic to work on tools that are resilient/robust in the face of current crises. (Like oca-port indeed!)
Also, are we going to fall for it again, thinking that it's wonderfully free?
For example, even Fabien Pickaers says so in the latest Micode video interview: currently, Odoo covers the cost of calls to ChatGPT, but tomorrow, it will probably be a paid service.Depending on such a non-free (non-open source) tool also means proletarianizing ourselves, making us more enslaved to technology, even though the goal of open source is to emancipate ourselves as much as possible with tools that we have learned to modify and hack.But I feel like I'm digressing from the main topic :D
Have a great day
Quentin
PS : some articles about AI bubblehttps://www.latimes.com/business/story/2025-08-20/say-farewell-to-the-ai-bubble-and-get-ready-for-the-crash
https://www.telegraph.co.uk/business/2025/08/21/zuckerberg-freezes-ai-hiring-amid-bubble-fears/
Le 23/09/2025 à 21:52, Pierre Verkest a écrit :
I agree with Daniel.
Blog posts (the second is linked in the first) inspiring me recently on this topic: https://www.bitecode.dev/p/the-kids-are-alright
Regards,Pierre
Le mar. 23 sept. 2025 à 10:41, Stuart J Mackintosh <notifications@odoo-community.org> a écrit :
+1
On 23/09/2025 10:28, Daniel Reis wrote:
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
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>> 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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Stuart J Mackintosh
Business & digital technology consultant
Open Digital Consulting Co
UK: +44 20 36 27 90 40
FR: +33 1 89 48 00 40
Email: sjm@opendigital.cc
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Quentin DUPONT Informaticien. En repos le mercredi après-midi.
Pôle informatique 09 73 79 64 40 - Bureau Grap 09 72 32 33 17
GRAP - Groupement Régional Alimentaire de Proximité
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Suggest a meeting: https://apmt.day/janikvonrotz/999120f2/ We are hiring: https://www.mint-system.ch/jobs CTO Mint System GmbH Tel: +41 44 244 7222
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
-