Contributors

• 1
• 2
• 3
• 4
• 5

• Please review security fix to the Python odoorpc package

  Hey,

  
  

  I've submitted a PR to fix an issue where odoorpc logs a password when running in debug mode. It has been hanging about for 2 weeks, any chance of a review and hopefully a merge?

  
  

  https://github.com/OCA/odoorpc/pull/103

  
  

  Cheers,

  Andrew

  -- 
  

  Andrew Ruthven

  Chief Information Security Officer, Manager Infrastructure and Security Team

  

  Aotearoa New Zealand's cloud provider

  e andrew.ruthven@catalystcloud.nz

  d +64 4 803 2231

  m +64 27 646 7658

  w catalystcloud.nz

  Follow us on LinkedIn

  Level 6, Catalyst House, 150 Willis St, Wellington 6011

  

  Confidentiality Notice: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

  ---

  by "Andrew Ruthven" <andrew.ruthven@catalystcloud.nz> - 11:41 - 12 Oct 2025

  5 attachments 5 attachments

  signature.asc

  attachment

  attachment

  attachment

  attachment

• New contributor

  Hello,
  My name is Jhon Romero, and I would like to contribute to OCA. My GitHub username is JhonRomero26.

  ---

  by romerogonzaga21 - 08:00 - 11 Oct 2025

  1 replies 1 replies

  • Re: New contributor

    Fantastic! Please read the contributor guidelines on odoo-community.org, and after that, open your first PR :)
    

    11 okt. 2025 20:02:14 Jhon Alexander Romero Gonzaga <notifications@odoo-community.org>:

    Hello,
    My name is Jhon Romero, and I would like to contribute to OCA. My GitHub username is JhonRomero26.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    ---

    by Tom Blauwendraat - 08:46 - 11 Oct 2025

• New module! Limiting number of records that a user can create in an Odoo model

  Hi,
  

  
  

  I migrated a module to limit the number of records to version 18 (original version is 15):
  

  https://github.com/it-projects-llc/access-addons/tree/15.0/access_limit_records_number

  
  

  For example, with the module it's possible to don't allow to create more than a maximum number of users
  

  
  

  This is the pull request:

  https://github.com/OCA/server-tools/pull/3394
  

  
  

  I added the names of the original authors in the manifest and the CONTRIBUTORS. I tried to contact them. Is it necessary  to sign the OCA CLA for them? The issue here is that I contacted the company and the author using 2 different emails but the email is always returned (not delivered). I can not contact to them.

  
  

  I am considering to close the pull request, to refactor and to create my own version.

  
  

  What is the best option?
  

  
  

  Cheers,

  Miguel.

  
  

  
  

  Sent with Proton Mail secure email.

  ---

  by python3developer - 03:06 - 10 Oct 2025

• [Odoo 19.0] Reverting the removal of Partner Title model

  Hello,

  I am currently working on the Odoo 19.0 migration of the Japan localization module (link), which relies on the partner title feature. I noticed that the res.partner.title model has been removed in Odoo 19.0 (https://github.com/odoo/odoo/pull/187357).

  For our localization needs, I would like to bring this model back. My proposal is:

  • If there is interest from others in using this model in Odoo 19.0, I will create a new module for it under the partner-contact repository.

  • Otherwise, I will simply add it within the Japan localization module itself.

  Please let me know if anyone else would like to make use of this model so I can decide the best approach.

  
  

  Best regards,

  Aung Ko Ko Lin

  ---

  by Aung Ko Ko Lin - 04:25 - 9 Oct 2025

  6 replies 6 replies

  • Re: [Odoo 19.0] Reverting the removal of Partner Title model

    +1. It will be needed for sure. "partner-contact" is the best repo IMO.

    
    

    Kind Regards, Ruchir Shukla

    Founder & CTO

    BizzAppDev Systems Pvt. Ltd.

    
    

    Book time to meet with me

    ---

    From: Peter Niederlag <notifications@odoo-community.org>
    Sent: 09 October 2025 3:22 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: [Odoo 19.0] Reverting the removal of Partner Title model

     

    Hi,
    
    +1 for partner-contact on OCA side.
    
    greets,
    Peter
    
    On 09.10.25 04:27, Aung Ko Ko Lin (QRTL) wrote:
    
    > Hello,
    
    > I am currently working on the Odoo 19.0 migration of the Japan localization module ( link [1] ), which relies on the /partner title/ feature. I noticed that the res.partner.title model has been removed in Odoo 19.0 ( https://github.com/odoo/odoo/pull/187357 [2] ).
    
    > For our localization needs, I would like to bring this model back. My proposal is:
    
    > 
    
    > If there is interest from others in using this model in Odoo 19.0, I will create a new module for it under the *partner-contact* repository.
    
    > 
    
    > Otherwise, I will simply add it within the Japan localization module itself.
    
    > 
    
    > Please let me know if anyone else would like to make use of this model so I can decide the best approach.
    
    > 
    
    > Best regards,
    
    > Aung Ko Ko Lin
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [3]
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [4]
    
    > 
    
    > 
    
    > 
    
    > [1] https://github.com/OCA/l10n-japan/tree/18.0/l10n_jp_partner_title_qweb
    
    > [2] https://github.com/odoo/odoo/pull/187357
    
    > [3] https://odoo-community.org/groups/contributors-15
    
    > [4] https://odoo-community.org/groups?unsubscribe
    
    > 
    
    mit freundlichen Grüßen,
    Peter Niederlag
    
    -- 
    Dipl. Ökonom Peter Niederlag
    Geschäftsführender Gesellschafter
    
    Lösungen für digitale Zeiten
    Agile DevOps, Cloud, TYPO3, Odoo und Linux
    
    Datenbetrieb Technologie UG(haftungsbeschränkt)
    Lipper Hellweg 146,  33605 Bielefeld
    Geschäftsführer: Peter Niederlag
    HRB 41826 Amtsgericht Bielefeld
    Fon 0521 / 446 958 60
    Fax 0521 / 446 958 69
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    ---

    by Ruchir Shukla. - 12:01 - 9 Oct 2025

    1 attachments 1 attachments

    Outlook-kk5huki5.png

  • Re: [Odoo 19.0] Reverting the removal of Partner Title model

    Hi,
    
    +1 for partner-contact on OCA side.
    
    greets,
    Peter
    
    On 09.10.25 04:27, Aung Ko Ko Lin (QRTL) wrote:
    
    > Hello,
    
    > I am currently working on the Odoo 19.0 migration of the Japan localization module ( link [1] ), which relies on the /partner title/ feature. I noticed that the res.partner.title model has been removed in Odoo 19.0 ( https://github.com/odoo/odoo/pull/187357 [2] ).
    
    > For our localization needs, I would like to bring this model back. My proposal is:
    
    > 
    
    > If there is interest from others in using this model in Odoo 19.0, I will create a new module for it under the *partner-contact* repository.
    
    > 
    
    > Otherwise, I will simply add it within the Japan localization module itself.
    
    > 
    
    > Please let me know if anyone else would like to make use of this model so I can decide the best approach.
    
    > 
    
    > Best regards,
    
    > Aung Ko Ko Lin
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [3]
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [4]
    
    > 
    
    > 
    
    > 
    
    > [1] https://github.com/OCA/l10n-japan/tree/18.0/l10n_jp_partner_title_qweb
    
    > [2] https://github.com/odoo/odoo/pull/187357
    
    > [3] https://odoo-community.org/groups/contributors-15
    
    > [4] https://odoo-community.org/groups?unsubscribe
    
    > 
    
    mit freundlichen Grüßen,
    Peter Niederlag
    
    -- 
    Dipl. Ökonom Peter Niederlag
    Geschäftsführender Gesellschafter
    
    Lösungen für digitale Zeiten
    Agile DevOps, Cloud, TYPO3, Odoo und Linux
    
    Datenbetrieb Technologie UG(haftungsbeschränkt)
    Lipper Hellweg 146,  33605 Bielefeld
    Geschäftsführer: Peter Niederlag
    HRB 41826 Amtsgericht Bielefeld
    Fon 0521 / 446 958 60
    Fax 0521 / 446 958 69
    
    

    ---

    by Peter Niederlag - 11:50 - 9 Oct 2025

  • Re: [Odoo 19.0] Reverting the removal of Partner Title model

    Hello

    
    

    We have 2 approaches concerning partner titles at OCA :

    https://github.com/OCA/partner-contact/pull/1930

    and 

    https://github.com/OCA/partner-contact/tree/17.0/partner_company_type

    
    

    Please input your pov

    
    

    Best regards

    --------------------------------
    Cyril VINH-TUNG
    INVITU
    Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99
    contact@invitu.com
    www.invitu.com
    

    
    

    Le mer. 8 oct. 2025, 16:27, Aung Ko Ko Lin (QRTL) <notifications@odoo-community.org> a écrit :
    

    Hello,

    I am currently working on the Odoo 19.0 migration of the Japan localization module (link), which relies on the partner title feature. I noticed that the res.partner.title model has been removed in Odoo 19.0 (https://github.com/odoo/odoo/pull/187357).

    For our localization needs, I would like to bring this model back. My proposal is:

    • If there is interest from others in using this model in Odoo 19.0, I will create a new module for it under the partner-contact repository.

    • Otherwise, I will simply add it within the Japan localization module itself.

    Please let me know if anyone else would like to make use of this model so I can decide the best approach.

    
    

    Best regards,

    Aung Ko Ko Lin

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    ---

    by Cyril VINH-TUNG - 09:40 - 9 Oct 2025

  • Re: [Odoo 19.0] Reverting the removal of Partner Title model

    partner-contact. It has more sense there. I am sure that other people will need that :D

    
    

    El jue, 9 oct 2025 a las 7:51, Daniel Reis (<notifications@odoo-community.org>) escribió:
    

    I think it should go in oca/partner-contact.

    
    

    --

    Daniel

    ---

    From: Aung Ko Ko Lin (QRTL) <notifications@odoo-community.org>
    Sent: Thursday, October 9, 2025 3:27:16 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: [Odoo 19.0] Reverting the removal of Partner Title model

     

    Hello,

    I am currently working on the Odoo 19.0 migration of the Japan localization module (link), which relies on the partner title feature. I noticed that the res.partner.title model has been removed in Odoo 19.0 (https://github.com/odoo/odoo/pull/187357).

    For our localization needs, I would like to bring this model back. My proposal is:

    • If there is interest from others in using this model in Odoo 19.0, I will create a new module for it under the partner-contact repository.

    • Otherwise, I will simply add it within the Japan localization module itself.

    Please let me know if anyone else would like to make use of this model so I can decide the best approach.

    
    

    Best regards,

    Aung Ko Ko Lin

    _______________________________________________
    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
    

    
    

    
    

    --
    

    Enric Tobella Alomar

    CEO & Founder
    

    
    

    www.dixmit.com

    ---

    by Enric Tobella Alomar - 08:11 - 9 Oct 2025

  • Re: [Odoo 19.0] Reverting the removal of Partner Title model

    I think so as well, especially because the change of Odoo doesn't seem to be explicitely justfied anywhere in the PR. 

    I am quite sure that this res.partner.title model is useful and after all used beyond the Japanase scope.

    Best Frederik
    

    Am 09.10.25 um 07:51 schrieb Daniel Reis:
    

    I think it should go in oca/partner-contact.

    
    

    --

    Daniel

    ---

    From: Aung Ko Ko Lin (QRTL) <notifications@odoo-community.org>
    Sent: Thursday, October 9, 2025 3:27:16 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: [Odoo 19.0] Reverting the removal of Partner Title model

     

    Hello,

    I am currently working on the Odoo 19.0 migration of the Japan localization module (link), which relies on the partner title feature. I noticed that the res.partner.title model has been removed in Odoo 19.0 (https://github.com/odoo/odoo/pull/187357).

    For our localization needs, I would like to bring this model back. My proposal is:

    • If there is interest from others in using this model in Odoo 19.0, I will create a new module for it under the partner-contact repository.

    • Otherwise, I will simply add it within the Japan localization module itself.

    Please let me know if anyone else would like to make use of this model so I can decide the best approach.

    
    

    Best regards,

    Aung Ko Ko Lin

    _______________________________________________
    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
    

    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
    
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
    
    Tel:   +49 (0) 4181 13503 12
    Fax:   +49 (0) 4181 13503 10
    Mobil: +49 (0) 179 3901819
    
    Email: frederik.kramer@initos.com
    Internet: www.initos.com
    
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    USt-IdNr.: DE815580155
    Steuer-Nr: 15/200/53247

    ---

    by Frederik Kramer - 08:11 - 9 Oct 2025

  1 more replies

• Row number

  Hi dear all,

  Odoo doesn’t use row number and row selection in forms like Sales,Purchases,Accounting and etc… i want to know why odoo doesn’t suppirt it? Is it have technical issues or reasons to handle it?

  Regards.

  ---

  by Amir Akbari - 04:46 - 7 Oct 2025

  1 replies 1 replies

  • Re: Row number

    Hi Amir,
    
    you should ask this to the company Odoo :-D this mailing list is just 
    for OCA contributors (github.com/OCA) not Odoo (github.com/odoo)
    
    That being said, OCA has developed some add-on modules that add 
    sequencing to certain form views.
    
    For example this one:
    
    https://github.com/OCA/sale-workflow/tree/16.0/sale_order_line_sequence
    
    You can see with Runboat: try me
    
    -Tom
    
    
    On 10/7/25 16:47, Amir Akbari wrote:
    
    >
    
    > Hi dear all,
    
    >
    
    > Odoo doesn’t use row number and row selection in forms like 
    
    > Sales,Purchases,Accounting and etc… i want to know why odoo doesn’t 
    
    > suppirt it? Is it have technical issues or reasons to handle it?
    
    > Regards.
    
    >
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    >
    

    ---

    by Tom Blauwendraat - 04:55 - 7 Oct 2025

• OCA OWL Training

  Dear contributors,
  Don't miss this opportunity to enhance your frontend skills with a hands-on OWL (Odoo Web Library) training!
  
  ⏰ Starts October 13
  13 hours spread over 2 weeks
  
  Register now: https://odoo-community.org/event/online-training-owl-2025-2025-10-13-2025-10-24-189/register
  Limited seats
  
  Have a good day!

  ---

  by Julie LeBrun (OCA) - 03:31 - 7 Oct 2025

• respecting the privacy of mass mailing recipients

  hello,

  i was quite surprised when i found out that it is not possible to disable open and click tracking in odoo mass mailing. i understand that people are interested in measuring the effectiveness of their marketing campaigns, but i think that this kind of individual tracking is very privacy-invasive as it is possible to know, for each recipient, whether or not they opened the message (and when) and on which links they clicked (and when).

  personally, i hate receiving messages like these where all urls are obfuscated (and thus you cannot inspect them before clicking them) and loading images will report this individual event to the sender. this is why i never load the images and never click on these links, and i’m probably not the only one. on the other hand, i also receive mass mailing messages from privacy-respecting organizations that don’t include any tracking mechanism and i’m grateful for these.

  i think it is important to allow to respect your recipient’s privacy. this is why i created the mass_mailing_disable_tracking module (oca/social#1681) (readme here). what do you think?

  kind regards,

  hugues
  

  ---

  by hugues - 04:21 - 5 Oct 2025

• Friendly reminder – Pending PR review in OCA/l10n-colombia

  Dear OCA Contributors,

  I hope this message finds you well.

  I would like to kindly inform you that on September 25th I submitted a Pull Request to the OCA/l10n-colombia repository (see link below):

  🔗 PR #22 – OCA/l10n-colombia

  It is still pending review, so I just wanted to bring it to your attention in case it has gone unnoticed. Please let me know if any additional changes or adjustments are required from my side.

  Thank you very much for your time and for all the great work you do for the community.

  Best regards,
  Yan Chirino

  ---

  by Yan Chirino - 10:16 - 2 Oct 2025

• OCA 2025 AGA Delegates Campaign - CLOSES Friday 3rd October

  Hello OCA Contributors

  
  

  Just a reminder that the opportunity to apply to become a Delegate this year closes this Friday 3rd October.

  
  

  So far we have had 9 applicants for the 10 spots available.

  
  

  The 2025 OCA Delegates Campaign is now open. Until October 3rd, you can apply to be an OCA Delegate if you are a current paid Member.
  If you are already a Delegate, you don't need to apply again. This is for 10 new Delegates.
  
  Why?
  The Delegate Assembly is the Association’s supreme authority. Each Delegate member is entitled to one vote at the Delegate Assembly. Decisions of the Delegate Assembly are taken by a majority vote of the Delegate members present and voting. For further details, please read the Bylaws.
  
  How?
  To apply as a candidate, you have to:
  

  • sign the CLA (if not already done)
  • have a valid membership. Make sure to purchase your membership or renew it (you should have received a quotation for your renewal earlier this year).
  • fill in this survey

  If you aren't sure if you have renewed/paid your membership for 2025 please contact me.
  
  The campaign will be closed on October 3rd, 2025.
  
  Then what?
  The vote will be open from October 6th - October 17th. Current OCA Delegates will have to vote for 10 new Delegates among the candidates.
  
  The results of the election will be announced on October 20th, 2025.
  
  The 10 new Delegates will then take part with the existing Delegates in :
  

  • the 2025 OCA Board Member Campaign from October 20th - October 31st, 2025
  • the 2025 OCA Financial Auditor Campaign from October 20th - October 31st, 2025
  • the 2025 General Assembly from November 3rd to November 14th 2025.
  • 2025 Board announced - week beginning November 17th, 2025 

  If you have any questions please get in touch.
  
  Warmest regards,
  Rebecca

  --
  

  Rebecca Gellatly

  General Secretary

  Odoo Community Association

  ---

  by Rebecca Gellatly (OCA) - 05:51 - 30 Sep 2025

• October OCA Events Schedule

  📣 Don't miss our upcoming events for OCA members in October!
  
  - October 1: Webinar - Manage your social media from Odoo with the new OCA modules V17
  - October 7: Support Group Session - OCA Consultant
  - October 13 to 24: Online Training - OWL
  - October 22: Webinar - Why OCA modules are like Magic Beans
  - October 28: Webinar - OCA from 2013 to now, the history!
  
  Register here : https://odoo-community.org/event
  **100% discount for OCA members**

  ---

  by Julie LeBrun (OCA) - 05:39 - 25 Sep 2025

  1 attachments 1 attachments

  Calendar October 2025.png

• Beyond LLM guidelines and generated contributions

  Hi everybody,

  First, thank you for the great time at the OCA Days and I hope you are enjoying the OXP.

  The ongoing discussion on LLM guidelines ~~had me triggered~~ got me thinking.

  I would like to give a different perspective on LLMs and what we as a community should care about.
  

  Let's talk about digital sovereignty and power-consumption. Most LLMs used by developers made by big tech companies [0]. These companies have built huge data centers that use an incredible amount of power to run LLMs. They have plans to build nuclear reactors to support the power demand. Anyone who is seriously concerned with digital sovereignty and cares about the environment knows that we need to become independent of big tech and use less energy.

  > Supporting AI tools by big tech is a step into the wrong direction.

  Moreover, the AI hype is igniting the next level of data collecting and user tracking. The data we generate when interacting with an AI chat and the like is incredibly valuable. As of now the tech bros still have no viable business model and burn money at an incredible amount [1].

  Every week a new model is released and we feel pressured to use AI.  Let us take a break and take it slow moving forward. We are not forced to do anything (at least for now).

  I ask the OCA members to do better than creating an OpenAI account, installing Claude desktop or click the Copilot icon. Use tools and create workflows that respect your privacy and the privacy of others. Make sure your stack uses less energy over time, works independent and is controllable.

  > Let us create guides on how to do better.

  Here is an example, not show off, but simply to share:
  The LLMs I am using are hosted by Infomaniak in Switzerland [2]. They are using "green" energy. I pay per token and I know where the data is stored. On the command line, I am using the LLM cli [3] by Simon Willison (LLM reseacher). Every LLM tool that supports the OpenAI API standard can be connected to an Infomaniak LLM. There are great scripts that help your write better code [4]. I don't have any kind of IDE integration [5]. I like to write code and not press tab tab tab ...

  Is somebody interested to create guides on how to work (better) with LLMs and create contributions that help the ecosystem?

  Kind regards,

  Janik

  [0]: https://en.wikipedia.org/wiki/Big_Tech
  [1]: https://www.wheresyoured.at/the-haters-gui/
  [2]: https://www.infomaniak.com/en/hosting/ai-tools
  [3]: https://llm.datasette.io/
  [4]: https://notes.billmill.org/blog/2025/07/An_AI_tool_I_find_useful.html
  [5]: https://janikvonrotz.ch/2025/01/27/work-with-llms-on-the-command-line/

  
  

  
  

  
  

  
  

  ---

  by Janik von Rotz - 11:05 - 19 Sep 2025

• Integration of knowledge or dms with onlyoffice ?

  Hello

  
  

  At oxp, I met https://www.onlyoffice.com/ who developped a connector with odoo's document app...

  https://github.com/ONLYOFFICE/onlyoffice_odoo

  
  

  AFAIK it's LGPL and they run infomaniak Kdrive

  
  

  I was wondering if we could have the same with knowledge and/or dms.

  
  

  WDYT ?

  
  

  Best regards

  
  

  
  

  --------------------------------
  Cyril VINH-TUNG
  INVITU
  Computer & Network Engineering
  BP 32 - 98713 Papeete - French Polynesia
  Tél: +689 40 46 11 99
  contact@invitu.com
  www.invitu.com
  

  ---

  by Cyril VINH-TUNG - 04:20 - 18 Sep 2025

  5 replies 5 replies

  • Re: Integration of knowledge or dms with onlyoffice ?

    Hello,
    
    Maybe another approach is to use external filesystem with this module https://github.com/OCA/storage/tree/18.0/fs_folder
    

    I proposed some improvements to the WebDAV connection.
    
    I tested it with Nextcloud and it works well. It should work with infomaniak Kdrive as it supports WebDAV in it's payed offer.

    It misses the feature to open the document in edition from Odoo. I'm not sure we can get the document's url with WebDAV natively.
    
    Best regards,
    
    Julien Guenat
    
    

    On 18.09.25 16:22, Cyril VINH-TUNG wrote:
    

    Hello

    
    

    At oxp, I met https://www.onlyoffice.com/ who developped a connector with odoo's document app...

    https://github.com/ONLYOFFICE/onlyoffice_odoo

    
    

    AFAIK it's LGPL and they run infomaniak Kdrive

    
    

    I was wondering if we could have the same with knowledge and/or dms.

    
    

    WDYT ?

    
    

    Best regards

    
    

    
    

    --------------------------------
    Cyril VINH-TUNG
    INVITU
    Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99
    contact@invitu.com
    www.invitu.com
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    ---

    by julien - 12:10 - 16 Oct 2025

  • Re: Integration of knowledge or dms with onlyoffice ?

    Hi Cyril, Hi Bruno,

     

    we have integrated onlyoffice since a long time in our dms - which is based on alfrsco and use it also in odoo. We are also aware of onlyoffics odoo ee integration.

     

    We can have a talk tomorow, if you like to on the OCA booth (Hall 11 / Stand 5) if youre intrested.

     

    Best 

    Chris

     

     

    ---

    Von: Cyril <notifications@odoo-community.org>
    An: Contributors <contributors@odoo-community.org>
    Datum: Donnerstag, 18. September 2025 17:27 CEST
    Betreff: Re: Integration of knowledge or dms with onlyoffice ?
    
    

    Hi Bruno

     

    What I saw on their demo is a direct integration of what you could find in a drive (spreadsheet, slides, docs...) in enterprise documents module. It looks like you can edit it in odoo UI.

    (I can go back tomorrow check it again)

     

    Then I had the idea of integrating the same functionality in OCA's document_page or dms...

     

     

    --------------------------------
    Cyril VINH-TUNG
    INVITU
    Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99
    contact@invitu.com
    www.invitu.com

    
    

    Le jeu. 18 sept. 2025, 16:32, Bruno Joliveau <notifications@odoo-community.org> a écrit :

    Hi Cyril,

     

    Could you elaborate "I was wondering if we could have the same with knowledge and/or dms." please ?

     

    DMS and Knowledge from Odoo Apps or others ?

     

    		Bruno Joliveau Architecte solutions - Président +1 514-317-7944

    Nouveau Votre avis est important pour nous ⭐

    Découvrir

    
    

    Le jeu. 18 sept. 2025 à 10:22, Cyril VINH-TUNG <notifications@odoo-community.org> a écrit :

    Hello

     

    At oxp, I met https://www.onlyoffice.com/ who developped a connector with odoo's document app...

    https://github.com/ONLYOFFICE/onlyoffice_odoo

     

    AFAIK it's LGPL and they run infomaniak Kdrive

     

    I was wondering if we could have the same with knowledge and/or dms.

     

    WDYT ?

     

    Best regards

     

     

    --------------------------------
    Cyril VINH-TUNG
    INVITU
    Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99
    contact@invitu.com
    www.invitu.com

    _______________________________________________
    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

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    ---

    by Chris Lorenz - 08:36 - 18 Sep 2025

  • Re: Integration of knowledge or dms with onlyoffice ?

    You need a running OnlyOffice Document Server to provide the online editor — not a big deal, but worth mentioning.
    The integration works quite well. One of my customers is using it on a daily basis. Unfortunately, there is no built-in document revisioning, as far as I know. I submitted a feature request for this a while ago.

    I might be wrong, but integration with a DMS shouldn’t be a problem, since OnlyOffice works on a temporary copy of the original file.

    I'll give it a try...

    ---

    Von: Cyril VINH-TUNG <notifications@odoo-community.org>
    Gesendet: Thursday, September 18, 2025 4:22:32 PM
    An: Contributors <contributors@odoo-community.org>
    Betreff: Integration of knowledge or dms with onlyoffice ?

     

    ACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.

    Hello

    
    

    At oxp, I met https://www.onlyoffice.com/ who developped a connector with odoo's document app...

    https://github.com/ONLYOFFICE/onlyoffice_odoo

    
    

    AFAIK it's LGPL and they run infomaniak Kdrive

    
    

    I was wondering if we could have the same with knowledge and/or dms.

    
    

    WDYT ?

    
    

    Best regards

    
    

    
    

    --------------------------------
    Cyril VINH-TUNG
    INVITU
    Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99
    contact@invitu.com
    www.invitu.com

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    ---

    by Nils Coenen - 06:46 - 18 Sep 2025

  • Re: Integration of knowledge or dms with onlyoffice ?

    Hi Bruno

    
    

    What I saw on their demo is a direct integration of what you could find in a drive (spreadsheet, slides, docs...) in enterprise documents module. It looks like you can edit it in odoo UI.

    (I can go back tomorrow check it again)

    
    

    Then I had the idea of integrating the same functionality in OCA's document_page or dms...

    
    

    
    

    --------------------------------
    Cyril VINH-TUNG
    INVITU
    Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99
    contact@invitu.com
    www.invitu.com
    

    
    

    Le jeu. 18 sept. 2025, 16:32, Bruno Joliveau <notifications@odoo-community.org> a écrit :
    

    Hi Cyril,

    
    

    Could you elaborate "I was wondering if we could have the same with knowledge and/or dms." please ?

    
    

    DMS and Knowledge from Odoo Apps or others ?

    
    

    		Bruno Joliveau Architecte solutions - Président +1 514-317-7944

    Nouveau Votre avis est important pour nous ⭐

    Découvrir

    
    

    
    

    Le jeu. 18 sept. 2025 à 10:22, Cyril VINH-TUNG <notifications@odoo-community.org> a écrit :
    

    Hello

    
    

    At oxp, I met https://www.onlyoffice.com/ who developped a connector with odoo's document app...

    https://github.com/ONLYOFFICE/onlyoffice_odoo

    
    

    AFAIK it's LGPL and they run infomaniak Kdrive

    
    

    I was wondering if we could have the same with knowledge and/or dms.

    
    

    WDYT ?

    
    

    Best regards

    
    

    
    

    --------------------------------
    Cyril VINH-TUNG
    INVITU
    Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99
    contact@invitu.com
    www.invitu.com
    

    _______________________________________________
    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
    

    ---

    by Cyril VINH-TUNG - 05:26 - 18 Sep 2025

  • Re: Integration of knowledge or dms with onlyoffice ?

    Hi Cyril,

    
    

    Could you elaborate "I was wondering if we could have the same with knowledge and/or dms." please ?

    
    

    DMS and Knowledge from Odoo Apps or others ?

    
    

    		Bruno Joliveau Architecte solutions - Président +1 514-317-7944

    Nouveau Votre avis est important pour nous ⭐

    Découvrir

    
    

    
    

    Le jeu. 18 sept. 2025 à 10:22, Cyril VINH-TUNG <notifications@odoo-community.org> a écrit :
    

    Hello

    
    

    At oxp, I met https://www.onlyoffice.com/ who developped a connector with odoo's document app...

    https://github.com/ONLYOFFICE/onlyoffice_odoo

    
    

    AFAIK it's LGPL and they run infomaniak Kdrive

    
    

    I was wondering if we could have the same with knowledge and/or dms.

    
    

    WDYT ?

    
    

    Best regards

    
    

    
    

    --------------------------------
    Cyril VINH-TUNG
    INVITU
    Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99
    contact@invitu.com
    www.invitu.com
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    ---

    by Bruno Joliveau - 04:30 - 18 Sep 2025

• Slides for OpenUpgrader module for Odoo at OCA Days 2025

  Hi all,

  as Alexandre did, I share the slides from the talk about an OpenUpgrade automatization tool I did: https://docs.google.com/presentation/d/1671gOwuPqaJD9mfsYzxcp0YgyEf8SUaRwrzSUhGdZvw/edit?usp=sharing

  
  

  Maybe there is a place to put them in the OCA Website to simplify finding them in the future?

  
  

  Sergio Corato
  

  ---

  by Sergio Corato - 09:51 - 18 Sep 2025

• Guidelines for LLM generated contributions

  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
  
  
  

  ---

  by Stefan Rijnhart - 09:40 - 18 Sep 2025

  32 replies 32 replies

  • RE: Guidelines for LLM generated contributions

    Thanks Stuart for the decent & constructive reply.

    Copyright is indeed an issue industry wise, as you mentioned, with many lawsuits in place but no clear direction. This is due to how LLM models are trained and how data converted into tokens, relations, and weights and stored into multi-dimensional vector space. Certain paths may represent a piece of copyrighted artifact.

    Yes, I do supervise my AI agents very strictly. Vibe coding, or whatever they call it, does not work in writing code for Odoo or any enterprise/ERP level codebase. In such complex codebase best is to treat AI agent as normal employees flow, keeping a human at last step is a must. It is crazy to see an LLM getting lazy like if it is the last hour before weekend, but it happened many times. Since those AI Agents are trained using humans data/traces, it includes good and bad behaviors and it requires some skills similar to managing normal team.

    I do respect and admire OCA brand very much and I know code quality is very high in general. It is not easy to get a module into OCA repository. OCA guidelines & policies are really rail guarding the quality and the brand.

    I think of LLM-OCA subject as two parts: 1) list of concerns and clarifications that would result into guidelines & policies, 2) AI tools and their usage. Even though there are many AI tools/agents but the ones that can really work in such codebase are very few.

     

    It is my pleasure to be part of it, it is always a joy to contribute.

     

    Sincerely,

    Hussain H.

     

    From: Stuart J Mackintosh <notifications@odoo-community.org>
    Sent: Thursday, October 9, 2025 7:18 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Guidelines for LLM generated contributions

     

     

    Thank you for your comments. Indeed we must not overlook the opportunities with automation however there are still issues unresolved (across industry) such as - if you use automated tools to create code, which was based on training code, and that was under AGPL, must you also apply AGPL terms? You certainly couldn't use AI as a filter to republish AGPL code as MIT for example.

    Ask your AI what rights you have to the code it creates for you - it is easy tl lead it to assuring you that the code is ok, but ask explicitly if it is safe to publish under MIT licence.

    In your case, it looks that you are supervising AI, but not everyone is as responsible, and abdication of responsibility is very different to delegating, and it takes quite some effort to keep up with moderating code at the speed and volume that it can be generated.

    Transparency is essential, and for any OCA code, guidance & policy are prerequisite so as to not dilute the brand.

    Hopefully we will get together sometime soon to consider the various points and outline the key criteria.

    Best wishes,

    Stuart.

     

     

    On 09/10/2025 10:22, Hussain Hammad wrote:

    Hi All,

     

    I’ve seen this subject “AI Usage” opened few times in mailing list but every time I see the same problem repeated. I think the main point is very missed in this area, starting from terminology and semantic to what is used and how. I’m not touching on people technical skills here, I’m touching on experience in AI arena. Who have first-hand experience in this area to clarify things and explain, in Odoo not other technology. Who can contribute in this knowledge level-up. Who can answer those concerns. I’m not talking about visionaries, I’m talking about first-hand users AI+Odoo.

     

    Proper decision comes from facts and understanding these facts.

     

    I believe we need to level up OCA (Management, Members, Contributors…etc) knowledge about the subject before thinking about policy and/or adaption, otherwise decisions might harm more than benefit.

     

    Why I’m raising this concern? We at OCA are late already in this subject. For someone like me, and many others, who breath code daily we cannot imagine not writing code for months. Believe it or not, in last 6 months I have not written a single line of code. It is more of architecting, code review, refactor, fine-tune, QC then production. AI tools are your team, managing it is on you. Bad players should not prevent us from adaption, same measures for bad player existed prior to AI time.

     

    I’m welling to do a session about it internally for OCA, or whatever OCA sees as good start to really open this subject. A list of questions and concerns can be answered as well, coordinated by OCA.

     

     

    Sincerely,

     

    Hussain Hammad  |  Solutions Unity Co. 6957 Abdullah Bin Harith Street, Shati District Tarout 32617, Saudi Arabia +966 56 963 4488   hussain@solutionsunity.com www.solutionsunity.com

     

     

    From: Joël Grand-Guillaume <notifications@odoo-community.org>
    Sent: Monday, September 29, 2025 10:27 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Guidelines for LLM generated contributions

     

     

     

    ...

    Whatever the case, transparency is essential, and omitting this will cause many problems such as compliance with the the new EU regulation which will activate in under 2 years.

    +1 - Transparency is key in this first steps - this will maintain trust.

     

    What's the action now - as Frederik proposed, a working group should pick this up, process the views of the community and define a policy based on consensus. This will continue to evolve so I don't think trying to nail it all down now is practical with this dynamic factored in.

    +1 to have the governance working group leading this topic
    
     

    Best wishes,

    Stuart.

     

    On 27/09/2025 15:07, Raphaël Valyi wrote:

    Hello,

     

    I think IA policies and risks/benefits may vary a lot depending on the use cases...

     

    The thread was initially started about migrations. This is really a use case where IA can bring a lot of benefits with very limited risks. Indeed, recent migrations are very easy for most modules. We could have a huge benefit if we could get 1000+ modules easily migrated (with possible AI automated ports), using standard OCA tools and letting the AI adjust the tests and pre-commit considering the framework and upstream modules changes in the context window. As Graeme explained, these simple migrations usually involves no creative work nor copyright issues.

     

    As for generating larger pieces of new modules/vibe coding, well of course there would be more things to care about, like copyrights, quality control etc...

     

    Some projects like Qemu recently banned IA completely because they fear large pieces of contributed IA code may infringe copyrights (the LLM would kind of replicated copyrighted code without enforcing licenses) and taint the whole project. This is definitely something we should pay attention to.

     

    For instance if the AI is trained on Odoo Enterprise code (or just even just in the context window) and new similar code is generated it could taint the OCA code. On the contrary it is also entirely possible AI could very soon replicate many EE module or ERP feature just from the UI/specs without infringing any copyright (Odoo tends to copy other apps from their UI, AI could soon do it too...)

     

    But more importantly, there is no need for AGI nor phD level AI for AI (probably an OpenAI/Anthropic bubble) to change completely the software industry. The current level of LLMs with lowering costs is far enough to raise many concerns how code is made and more importantly how open source communities like us are organized.

     

    As Daniel explained, AI may of course multiply toxic or spam behavior and we should hold AI users responsible for it.

     

    But I think it is also very important to consider this: as many open source communities, the whole OCA was organized as a meritocracy where ability to create proper code and ERP knowledge was earned after many years of seniority and acknowledged as such. Despite ocasional disputes, modules authors, repo PSCs and all our OCA decision process is kind if naturally structured atop of this "traditional" coding and ERP expertise. merged code was kind of our "proof of work" in our pre-IA world.

     

    But AI will soon bring us to a world were an LLM will be more knowledgeable than senior ERP consultants and only top coders will be able to add any value over AI generated code. Good coders with access to compute will also be able to generate or maintain orders of magnitude more code. Bad coders with bad intentions will also be able to flood the OCA with poor quality contributions and the average person will not be able/not have time to filter the good options. In this is world that is coming in just a few months, how will we be able to maintain trust and organization? IMHO this should be a top concern for the OCA.

     

    Finally, for more than a decade, the business model behind the OCA was kind of: in traditional ERPs 70% of the cost is from consulting/customization and 30% from licenses. So some alien skilled people able to do both the code and the consulting (or small companies able to do both) would charge the 70% and use that revenue produce the ERP code free of license charges. That was working because non specialists would typically not be able simply download open source code and do their ERP project alone. So companies would somehwat hire module authors, pay the 70% consulting/customization cost and with limited parasistism, the ecosystem could somehow sustain itself.

     

    But soon the expertise to use OCA modules will drop a lot. The AI will bring it to the user directly bypassing modules authors and contributors entirely...

     

    How will our open source economy work in this context? Well an option I see is use AI on our side: manage order of magnitude more code and more customers for a fraction of the cost... Now, I'm almost certain if we simply reject the IA entirety, then yes, it won't take long before we are made completely obsolete.

     

     

     

    On Sat, Sep 27, 2025, 4:47 AM Stuart J Mackintosh <notifications@odoo-community.org> wrote:

     

    Indeed - it would be of benefit for OCA to have a position.

    Best wishes,

    Stuart.

     

    On 27/09/2025 09:27, Frederik Kramer wrote:

    Hi Stuart, hi all,
    
    very valuable for decision making but I think within our community we have people thinking as strict as Gentoo, NetBSD on the matter and others that would rather adopt the stance of the Linux or Apache Foundation. So possibly the board / governance/community health WGs shall come up with a decision proposal along these lines and ask for a solid quorum in the next AGA.
    
    Best Frederik

     

    Am 26. September 2025 08:42:39 MESZ schrieb Stuart J Mackintosh <notifications@odoo-community.org>:

     

    Following up and to take a look at how others have dealt with these matters, I noticed Fedora released an AI policy yesterday so I have briefly summarised (perplexity) this compared with a bunch of other policies, full analysis here: https://codimd.mackintosh.me/s/ifsByh-G8#

    Brief overview of policies:

    - The main goal is to blend innovation with strong safeguards—using AI tools to help, but keeping people fully responsible for results.
    - Most projects see transparency as crucial for maintaining trust and enabling fair review and collaboration.
    - Quality control and copyright protection are prioritized: automation should not dilute standards nor introduce legal risk.
    - Some policies are stricter, fully banning AI output unless human-vetted and legally certified.
    - Clause implementation mostly revolves around commit messages, contributor guidelines, and reviewed workflow steps—simple, actionable, easy to follow.
    
    This format ensures contributors know where, when, and how AI use is welcomed—and where human effort and discretion are absolutely required.

    Best wishes,

    Stuart.

     

    On 24/09/2025 11:01, Stuart J Mackintosh wrote:

     

    I propose that you address these points through the mechanism proposed by Daniel - responsible use, and behavioural guidance alongside a code of conduct which can determine obligations such as disclosure of AI use; Ai is just one of a set of issues that must be addressed.

    Best wishes,

    Stuart.

     

    On 24/09/2025 10:47, Graeme Gellatly wrote:

    I disagree. If you are holding yourself out as a professional you should declare AI usage and the scope.   Declaring AI usage is mandated for my profession, if I prepare any advice or report in a professional capacity I must declare. It is just not an option to say, oh well it is just a tool, when it really isn't, it directly created output.

     

    It also gives valuable information to both the reviewer and ultimately the users. 

     

    It is also important from a copyright perspective. There is no copyright in a lot of AI generated work without later creative human input and even then only the human inputs are usually covered. To be fair there is also no copyright in a lot of human generated output (i.e. bug fixes and migrations) as there is no creative output, so for that kind of work AI is actually ideal. Ref https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf

     

     

    On Tue, Sep 23, 2025 at 8:27 PM Daniel Reis <notifications@odoo-community.org> 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

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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

    --
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
            
    Phone:  +49 4181 13503-12
    Fax:    +49 4181 13503-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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

    --

    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

    Web: https://opendigital.cc

    IM: xmpp: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

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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

    ---

    by Hussain Hammad - 04:26 - 11 Oct 2025

  • Re: Guidelines for LLM generated contributions

    
    

    Thank you for your comments. Indeed we must not overlook the opportunities with automation however there are still issues unresolved (across industry) such as - if you use automated tools to create code, which was based on training code, and that was under AGPL, must you also apply AGPL terms? You certainly couldn't use AI as a filter to republish AGPL code as MIT for example.

    Ask your AI what rights you have to the code it creates for you - it is easy tl lead it to assuring you that the code is ok, but ask explicitly if it is safe to publish under MIT licence.

    In your case, it looks that you are supervising AI, but not everyone is as responsible, and abdication of responsibility is very different to delegating, and it takes quite some effort to keep up with moderating code at the speed and volume that it can be generated.
    

    Transparency is essential, and for any OCA code, guidance & policy are prerequisite so as to not dilute the brand.

    Hopefully we will get together sometime soon to consider the various points and outline the key criteria.

    Best wishes,

    Stuart.
    

    
    

    
    

    On 09/10/2025 10:22, Hussain Hammad wrote:
    

    Hi All,

     

    I’ve seen this subject “AI Usage” opened few times in mailing list but every time I see the same problem repeated. I think the main point is very missed in this area, starting from terminology and semantic to what is used and how. I’m not touching on people technical skills here, I’m touching on experience in AI arena. Who have first-hand experience in this area to clarify things and explain, in Odoo not other technology. Who can contribute in this knowledge level-up. Who can answer those concerns. I’m not talking about visionaries, I’m talking about first-hand users AI+Odoo.

     

    Proper decision comes from facts and understanding these facts.

     

    I believe we need to level up OCA (Management, Members, Contributors…etc) knowledge about the subject before thinking about policy and/or adaption, otherwise decisions might harm more than benefit.

     

    Why I’m raising this concern? We at OCA are late already in this subject. For someone like me, and many others, who breath code daily we cannot imagine not writing code for months. Believe it or not, in last 6 months I have not written a single line of code. It is more of architecting, code review, refactor, fine-tune, QC then production. AI tools are your team, managing it is on you. Bad players should not prevent us from adaption, same measures for bad player existed prior to AI time.

     

    I’m welling to do a session about it internally for OCA, or whatever OCA sees as good start to really open this subject. A list of questions and concerns can be answered as well, coordinated by OCA.

     

     

    Sincerely,

     

    Hussain Hammad  |  Solutions Unity Co. 6957 Abdullah Bin Harith Street, Shati District Tarout 32617, Saudi Arabia +966 56 963 4488   hussain@solutionsunity.com www.solutionsunity.com

     

     

    From: Joël Grand-Guillaume <notifications@odoo-community.org>
    Sent: Monday, September 29, 2025 10:27 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Guidelines for LLM generated contributions

     

     

     

    ...

    Whatever the case, transparency is essential, and omitting this will cause many problems such as compliance with the the new EU regulation which will activate in under 2 years.

    +1 - Transparency is key in this first steps - this will maintain trust.

     

    What's the action now - as Frederik proposed, a working group should pick this up, process the views of the community and define a policy based on consensus. This will continue to evolve so I don't think trying to nail it all down now is practical with this dynamic factored in.

    +1 to have the governance working group leading this topic
    
     

    Best wishes,

    Stuart.

     

    On 27/09/2025 15:07, Raphaël Valyi wrote:

    Hello,

     

    I think IA policies and risks/benefits may vary a lot depending on the use cases...

     

    The thread was initially started about migrations. This is really a use case where IA can bring a lot of benefits with very limited risks. Indeed, recent migrations are very easy for most modules. We could have a huge benefit if we could get 1000+ modules easily migrated (with possible AI automated ports), using standard OCA tools and letting the AI adjust the tests and pre-commit considering the framework and upstream modules changes in the context window. As Graeme explained, these simple migrations usually involves no creative work nor copyright issues.

     

    As for generating larger pieces of new modules/vibe coding, well of course there would be more things to care about, like copyrights, quality control etc...

     

    Some projects like Qemu recently banned IA completely because they fear large pieces of contributed IA code may infringe copyrights (the LLM would kind of replicated copyrighted code without enforcing licenses) and taint the whole project. This is definitely something we should pay attention to.

     

    For instance if the AI is trained on Odoo Enterprise code (or just even just in the context window) and new similar code is generated it could taint the OCA code. On the contrary it is also entirely possible AI could very soon replicate many EE module or ERP feature just from the UI/specs without infringing any copyright (Odoo tends to copy other apps from their UI, AI could soon do it too...)

     

    But more importantly, there is no need for AGI nor phD level AI for AI (probably an OpenAI/Anthropic bubble) to change completely the software industry. The current level of LLMs with lowering costs is far enough to raise many concerns how code is made and more importantly how open source communities like us are organized.

     

    As Daniel explained, AI may of course multiply toxic or spam behavior and we should hold AI users responsible for it.

     

    But I think it is also very important to consider this: as many open source communities, the whole OCA was organized as a meritocracy where ability to create proper code and ERP knowledge was earned after many years of seniority and acknowledged as such. Despite ocasional disputes, modules authors, repo PSCs and all our OCA decision process is kind if naturally structured atop of this "traditional" coding and ERP expertise. merged code was kind of our "proof of work" in our pre-IA world.

     

    But AI will soon bring us to a world were an LLM will be more knowledgeable than senior ERP consultants and only top coders will be able to add any value over AI generated code. Good coders with access to compute will also be able to generate or maintain orders of magnitude more code. Bad coders with bad intentions will also be able to flood the OCA with poor quality contributions and the average person will not be able/not have time to filter the good options. In this is world that is coming in just a few months, how will we be able to maintain trust and organization? IMHO this should be a top concern for the OCA.

     

    Finally, for more than a decade, the business model behind the OCA was kind of: in traditional ERPs 70% of the cost is from consulting/customization and 30% from licenses. So some alien skilled people able to do both the code and the consulting (or small companies able to do both) would charge the 70% and use that revenue produce the ERP code free of license charges. That was working because non specialists would typically not be able simply download open source code and do their ERP project alone. So companies would somehwat hire module authors, pay the 70% consulting/customization cost and with limited parasistism, the ecosystem could somehow sustain itself.

     

    But soon the expertise to use OCA modules will drop a lot. The AI will bring it to the user directly bypassing modules authors and contributors entirely...

     

    How will our open source economy work in this context? Well an option I see is use AI on our side: manage order of magnitude more code and more customers for a fraction of the cost... Now, I'm almost certain if we simply reject the IA entirety, then yes, it won't take long before we are made completely obsolete.

     

     

     

    On Sat, Sep 27, 2025, 4:47 AM Stuart J Mackintosh <notifications@odoo-community.org> wrote:

     

    Indeed - it would be of benefit for OCA to have a position.

    Best wishes,

    Stuart.

     

    On 27/09/2025 09:27, Frederik Kramer wrote:

    Hi Stuart, hi all,
    
    very valuable for decision making but I think within our community we have people thinking as strict as Gentoo, NetBSD on the matter and others that would rather adopt the stance of the Linux or Apache Foundation. So possibly the board / governance/community health WGs shall come up with a decision proposal along these lines and ask for a solid quorum in the next AGA.
    
    Best Frederik

     

    Am 26. September 2025 08:42:39 MESZ schrieb Stuart J Mackintosh <notifications@odoo-community.org>:

     

    Following up and to take a look at how others have dealt with these matters, I noticed Fedora released an AI policy yesterday so I have briefly summarised (perplexity) this compared with a bunch of other policies, full analysis here: https://codimd.mackintosh.me/s/ifsByh-G8#

    Brief overview of policies:

    - The main goal is to blend innovation with strong safeguards—using AI tools to help, but keeping people fully responsible for results.
    - Most projects see transparency as crucial for maintaining trust and enabling fair review and collaboration.
    - Quality control and copyright protection are prioritized: automation should not dilute standards nor introduce legal risk.
    - Some policies are stricter, fully banning AI output unless human-vetted and legally certified.
    - Clause implementation mostly revolves around commit messages, contributor guidelines, and reviewed workflow steps—simple, actionable, easy to follow.
    
    This format ensures contributors know where, when, and how AI use is welcomed—and where human effort and discretion are absolutely required.

    Best wishes,

    Stuart.

     

    On 24/09/2025 11:01, Stuart J Mackintosh wrote:

     

    I propose that you address these points through the mechanism proposed by Daniel - responsible use, and behavioural guidance alongside a code of conduct which can determine obligations such as disclosure of AI use; Ai is just one of a set of issues that must be addressed.

    Best wishes,

    Stuart.

     

    On 24/09/2025 10:47, Graeme Gellatly wrote:

    I disagree. If you are holding yourself out as a professional you should declare AI usage and the scope.   Declaring AI usage is mandated for my profession, if I prepare any advice or report in a professional capacity I must declare. It is just not an option to say, oh well it is just a tool, when it really isn't, it directly created output.

     

    It also gives valuable information to both the reviewer and ultimately the users. 

     

    It is also important from a copyright perspective. There is no copyright in a lot of AI generated work without later creative human input and even then only the human inputs are usually covered. To be fair there is also no copyright in a lot of human generated output (i.e. bug fixes and migrations) as there is no creative output, so for that kind of work AI is actually ideal. Ref https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf

     

     

    On Tue, Sep 23, 2025 at 8:27 PM Daniel Reis <notifications@odoo-community.org> 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

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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

    --
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
            
    Phone:  +49 4181 13503-12
    Fax:    +49 4181 13503-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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

    --

    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

    Web: https://opendigital.cc

    IM: xmpp: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

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp:sjm@opendigital.cc

    ---

    by Stuart J Mackintosh - 06:16 - 9 Oct 2025

    1 attachments 1 attachments

    logo.png

  • RE: Guidelines for LLM generated contributions

    Hi All,

     

    I’ve seen this subject “AI Usage” opened few times in mailing list but every time I see the same problem repeated. I think the main point is very missed in this area, starting from terminology and semantic to what is used and how. I’m not touching on people technical skills here, I’m touching on experience in AI arena. Who have first-hand experience in this area to clarify things and explain, in Odoo not other technology. Who can contribute in this knowledge level-up. Who can answer those concerns. I’m not talking about visionaries, I’m talking about first-hand users AI+Odoo.

     

    Proper decision comes from facts and understanding these facts.

     

    I believe we need to level up OCA (Management, Members, Contributors…etc) knowledge about the subject before thinking about policy and/or adaption, otherwise decisions might harm more than benefit.

     

    Why I’m raising this concern? We at OCA are late already in this subject. For someone like me, and many others, who breath code daily we cannot imagine not writing code for months. Believe it or not, in last 6 months I have not written a single line of code. It is more of architecting, code review, refactor, fine-tune, QC then production. AI tools are your team, managing it is on you. Bad players should not prevent us from adaption, same measures for bad player existed prior to AI time.

     

    I’m welling to do a session about it internally for OCA, or whatever OCA sees as good start to really open this subject. A list of questions and concerns can be answered as well, coordinated by OCA.

     

     

    Sincerely,

     

    Hussain Hammad  |  Solutions Unity Co. 6957 Abdullah Bin Harith Street, Shati District Tarout 32617, Saudi Arabia +966 56 963 4488   hussain@solutionsunity.com www.solutionsunity.com

     

     

    From: Joël Grand-Guillaume <notifications@odoo-community.org>
    Sent: Monday, September 29, 2025 10:27 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Guidelines for LLM generated contributions

     

     

     

    ...

    Whatever the case, transparency is essential, and omitting this will cause many problems such as compliance with the the new EU regulation which will activate in under 2 years.

    +1 - Transparency is key in this first steps - this will maintain trust.

     

    What's the action now - as Frederik proposed, a working group should pick this up, process the views of the community and define a policy based on consensus. This will continue to evolve so I don't think trying to nail it all down now is practical with this dynamic factored in.

    +1 to have the governance working group leading this topic
    
     

    Best wishes,

    Stuart.

     

    On 27/09/2025 15:07, Raphaël Valyi wrote:

    Hello,

     

    I think IA policies and risks/benefits may vary a lot depending on the use cases...

     

    The thread was initially started about migrations. This is really a use case where IA can bring a lot of benefits with very limited risks. Indeed, recent migrations are very easy for most modules. We could have a huge benefit if we could get 1000+ modules easily migrated (with possible AI automated ports), using standard OCA tools and letting the AI adjust the tests and pre-commit considering the framework and upstream modules changes in the context window. As Graeme explained, these simple migrations usually involves no creative work nor copyright issues.

     

    As for generating larger pieces of new modules/vibe coding, well of course there would be more things to care about, like copyrights, quality control etc...

     

    Some projects like Qemu recently banned IA completely because they fear large pieces of contributed IA code may infringe copyrights (the LLM would kind of replicated copyrighted code without enforcing licenses) and taint the whole project. This is definitely something we should pay attention to.

     

    For instance if the AI is trained on Odoo Enterprise code (or just even just in the context window) and new similar code is generated it could taint the OCA code. On the contrary it is also entirely possible AI could very soon replicate many EE module or ERP feature just from the UI/specs without infringing any copyright (Odoo tends to copy other apps from their UI, AI could soon do it too...)

     

    But more importantly, there is no need for AGI nor phD level AI for AI (probably an OpenAI/Anthropic bubble) to change completely the software industry. The current level of LLMs with lowering costs is far enough to raise many concerns how code is made and more importantly how open source communities like us are organized.

     

    As Daniel explained, AI may of course multiply toxic or spam behavior and we should hold AI users responsible for it.

     

    But I think it is also very important to consider this: as many open source communities, the whole OCA was organized as a meritocracy where ability to create proper code and ERP knowledge was earned after many years of seniority and acknowledged as such. Despite ocasional disputes, modules authors, repo PSCs and all our OCA decision process is kind if naturally structured atop of this "traditional" coding and ERP expertise. merged code was kind of our "proof of work" in our pre-IA world.

     

    But AI will soon bring us to a world were an LLM will be more knowledgeable than senior ERP consultants and only top coders will be able to add any value over AI generated code. Good coders with access to compute will also be able to generate or maintain orders of magnitude more code. Bad coders with bad intentions will also be able to flood the OCA with poor quality contributions and the average person will not be able/not have time to filter the good options. In this is world that is coming in just a few months, how will we be able to maintain trust and organization? IMHO this should be a top concern for the OCA.

     

    Finally, for more than a decade, the business model behind the OCA was kind of: in traditional ERPs 70% of the cost is from consulting/customization and 30% from licenses. So some alien skilled people able to do both the code and the consulting (or small companies able to do both) would charge the 70% and use that revenue produce the ERP code free of license charges. That was working because non specialists would typically not be able simply download open source code and do their ERP project alone. So companies would somehwat hire module authors, pay the 70% consulting/customization cost and with limited parasistism, the ecosystem could somehow sustain itself.

     

    But soon the expertise to use OCA modules will drop a lot. The AI will bring it to the user directly bypassing modules authors and contributors entirely...

     

    How will our open source economy work in this context? Well an option I see is use AI on our side: manage order of magnitude more code and more customers for a fraction of the cost... Now, I'm almost certain if we simply reject the IA entirety, then yes, it won't take long before we are made completely obsolete.

     

     

     

    On Sat, Sep 27, 2025, 4:47 AM Stuart J Mackintosh <notifications@odoo-community.org> wrote:

     

    Indeed - it would be of benefit for OCA to have a position.

    Best wishes,

    Stuart.

     

    On 27/09/2025 09:27, Frederik Kramer wrote:

    Hi Stuart, hi all,
    
    very valuable for decision making but I think within our community we have people thinking as strict as Gentoo, NetBSD on the matter and others that would rather adopt the stance of the Linux or Apache Foundation. So possibly the board / governance/community health WGs shall come up with a decision proposal along these lines and ask for a solid quorum in the next AGA.
    
    Best Frederik

     

    Am 26. September 2025 08:42:39 MESZ schrieb Stuart J Mackintosh <notifications@odoo-community.org>:

     

    Following up and to take a look at how others have dealt with these matters, I noticed Fedora released an AI policy yesterday so I have briefly summarised (perplexity) this compared with a bunch of other policies, full analysis here: https://codimd.mackintosh.me/s/ifsByh-G8#

    Brief overview of policies:

    - The main goal is to blend innovation with strong safeguards—using AI tools to help, but keeping people fully responsible for results.
    - Most projects see transparency as crucial for maintaining trust and enabling fair review and collaboration.
    - Quality control and copyright protection are prioritized: automation should not dilute standards nor introduce legal risk.
    - Some policies are stricter, fully banning AI output unless human-vetted and legally certified.
    - Clause implementation mostly revolves around commit messages, contributor guidelines, and reviewed workflow steps—simple, actionable, easy to follow.
    
    This format ensures contributors know where, when, and how AI use is welcomed—and where human effort and discretion are absolutely required.

    Best wishes,

    Stuart.

     

    On 24/09/2025 11:01, Stuart J Mackintosh wrote:

     

    I propose that you address these points through the mechanism proposed by Daniel - responsible use, and behavioural guidance alongside a code of conduct which can determine obligations such as disclosure of AI use; Ai is just one of a set of issues that must be addressed.

    Best wishes,

    Stuart.

     

    On 24/09/2025 10:47, Graeme Gellatly wrote:

    I disagree. If you are holding yourself out as a professional you should declare AI usage and the scope.   Declaring AI usage is mandated for my profession, if I prepare any advice or report in a professional capacity I must declare. It is just not an option to say, oh well it is just a tool, when it really isn't, it directly created output.

     

    It also gives valuable information to both the reviewer and ultimately the users. 

     

    It is also important from a copyright perspective. There is no copyright in a lot of AI generated work without later creative human input and even then only the human inputs are usually covered. To be fair there is also no copyright in a lot of human generated output (i.e. bug fixes and migrations) as there is no creative output, so for that kind of work AI is actually ideal. Ref https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf

     

     

    On Tue, Sep 23, 2025 at 8:27 PM Daniel Reis <notifications@odoo-community.org> 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

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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

    --
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
            
    Phone:  +49 4181 13503-12
    Fax:    +49 4181 13503-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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

    --

    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

    Web: https://opendigital.cc

    IM: xmpp: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

    ---

    by Hussain Hammad - 10:21 - 9 Oct 2025

    1 attachments 1 attachments

    image001.png

  • Re: Guidelines for LLM generated contributions

    
    

    
    

    ...

    Whatever the case, transparency is essential, and omitting this will cause many problems such as compliance with the the new EU regulation which will activate in under 2 years.

    +1 - Transparency is key in this first steps - this will maintain trust.
    

     

    What's the action now - as Frederik proposed, a working group should pick this up, process the views of the community and define a policy based on consensus. This will continue to evolve so I don't think trying to nail it all down now is practical with this dynamic factored in.

    +1 to have the governance working group leading this topic
    
     

    Best wishes,

    Stuart.
    

    
    

    On 27/09/2025 15:07, Raphaël Valyi wrote:
    

    Hello,

    
    

    I think IA policies and risks/benefits may vary a lot depending on the use cases...

    
    

    The thread was initially started about migrations. This is really a use case where IA can bring a lot of benefits with very limited risks. Indeed, recent migrations are very easy for most modules. We could have a huge benefit if we could get 1000+ modules easily migrated (with possible AI automated ports), using standard OCA tools and letting the AI adjust the tests and pre-commit considering the framework and upstream modules changes in the context window. As Graeme explained, these simple migrations usually involves no creative work nor copyright issues.

    
    

    As for generating larger pieces of new modules/vibe coding, well of course there would be more things to care about, like copyrights, quality control etc...

    
    

    Some projects like Qemu recently banned IA completely because they fear large pieces of contributed IA code may infringe copyrights (the LLM would kind of replicated copyrighted code without enforcing licenses) and taint the whole project. This is definitely something we should pay attention to.

    
    

    For instance if the AI is trained on Odoo Enterprise code (or just even just in the context window) and new similar code is generated it could taint the OCA code. On the contrary it is also entirely possible AI could very soon replicate many EE module or ERP feature just from the UI/specs without infringing any copyright (Odoo tends to copy other apps from their UI, AI could soon do it too...)

    
    

    But more importantly, there is no need for AGI nor phD level AI for AI (probably an OpenAI/Anthropic bubble) to change completely the software industry. The current level of LLMs with lowering costs is far enough to raise many concerns how code is made and more importantly how open source communities like us are organized.

    
    

    As Daniel explained, AI may of course multiply toxic or spam behavior and we should hold AI users responsible for it.

    
    

    But I think it is also very important to consider this: as many open source communities, the whole OCA was organized as a meritocracy where ability to create proper code and ERP knowledge was earned after many years of seniority and acknowledged as such. Despite ocasional disputes, modules authors, repo PSCs and all our OCA decision process is kind if naturally structured atop of this "traditional" coding and ERP expertise. merged code was kind of our "proof of work" in our pre-IA world.

    
    

    But AI will soon bring us to a world were an LLM will be more knowledgeable than senior ERP consultants and only top coders will be able to add any value over AI generated code. Good coders with access to compute will also be able to generate or maintain orders of magnitude more code. Bad coders with bad intentions will also be able to flood the OCA with poor quality contributions and the average person will not be able/not have time to filter the good options. In this is world that is coming in just a few months, how will we be able to maintain trust and organization? IMHO this should be a top concern for the OCA.

    
    

    Finally, for more than a decade, the business model behind the OCA was kind of: in traditional ERPs 70% of the cost is from consulting/customization and 30% from licenses. So some alien skilled people able to do both the code and the consulting (or small companies able to do both) would charge the 70% and use that revenue produce the ERP code free of license charges. That was working because non specialists would typically not be able simply download open source code and do their ERP project alone. So companies would somehwat hire module authors, pay the 70% consulting/customization cost and with limited parasistism, the ecosystem could somehow sustain itself.

    
    

    But soon the expertise to use OCA modules will drop a lot. The AI will bring it to the user directly bypassing modules authors and contributors entirely...

    
    

    How will our open source economy work in this context? Well an option I see is use AI on our side: manage order of magnitude more code and more customers for a fraction of the cost... Now, I'm almost certain if we simply reject the IA entirety, then yes, it won't take long before we are made completely obsolete.

    
    

    
    

    
    

    On Sat, Sep 27, 2025, 4:47 AM Stuart J Mackintosh <notifications@odoo-community.org> wrote:
    

    
    

    Indeed - it would be of benefit for OCA to have a position.
    

    Best wishes,

    Stuart.
    

    
    

    On 27/09/2025 09:27, Frederik Kramer wrote:
    

    Hi Stuart, hi all,
    
    very valuable for decision making but I think within our community we have people thinking as strict as Gentoo, NetBSD on the matter and others that would rather adopt the stance of the Linux or Apache Foundation. So possibly the board / governance/community health WGs shall come up with a decision proposal along these lines and ask for a solid quorum in the next AGA.
    
    Best Frederik

    
    
    

    Am 26. September 2025 08:42:39 MESZ schrieb Stuart J Mackintosh <notifications@odoo-community.org>:

    
    

    Following up and to take a look at how others have dealt with these matters, I noticed Fedora released an AI policy yesterday so I have briefly summarised (perplexity) this compared with a bunch of other policies, full analysis here: https://codimd.mackintosh.me/s/ifsByh-G8#
    

    Brief overview of policies:
    

    - The main goal is to blend innovation with strong safeguards—using AI tools to help, but keeping people fully responsible for results.
    - Most projects see transparency as crucial for maintaining trust and enabling fair review and collaboration.
    - Quality control and copyright protection are prioritized: automation should not dilute standards nor introduce legal risk.
    - Some policies are stricter, fully banning AI output unless human-vetted and legally certified.
    - Clause implementation mostly revolves around commit messages, contributor guidelines, and reviewed workflow steps—simple, actionable, easy to follow.
    
    This format ensures contributors know where, when, and how AI use is welcomed—and where human effort and discretion are absolutely required.
    

    Best wishes,

    Stuart.
    

    
    

    On 24/09/2025 11:01, Stuart J Mackintosh wrote:
    

    
    

    I propose that you address these points through the mechanism proposed by Daniel - responsible use, and behavioural guidance alongside a code of conduct which can determine obligations such as disclosure of AI use; Ai is just one of a set of issues that must be addressed.
    

    Best wishes,

    Stuart.

    
    

    On 24/09/2025 10:47, Graeme Gellatly wrote:
    

    I disagree. If you are holding yourself out as a professional you should declare AI usage and the scope.   Declaring AI usage is mandated for my profession, if I prepare any advice or report in a professional capacity I must declare. It is just not an option to say, oh well it is just a tool, when it really isn't, it directly created output.

    
    

    It also gives valuable information to both the reviewer and ultimately the users. 

    
    

    It is also important from a copyright perspective. There is no copyright in a lot of AI generated work without later creative human input and even then only the human inputs are usually covered. To be fair there is also no copyright in a lot of human generated output (i.e. bug fixes and migrations) as there is no creative output, so for that kind of work AI is actually ideal. Ref https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf
    

    
    

    
    

    On Tue, Sep 23, 2025 at 8:27 PM Daniel Reis <notifications@odoo-community.org> 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
    

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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
    

    --
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
            
    Phone:  +49 4181 13503-12
    Fax:    +49 4181 13503-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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
    

    --
    

    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

    Web: https://opendigital.cc

    IM: xmpp: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
    

    ---

    by Joël Grand Guillaume - 09:26 - 29 Sep 2025

  • Re: Guidelines for LLM generated contributions

    
    

    How will our open source economy work in this context? Well an option I see is use AI on our side: manage order of magnitude more code and more customers for a fraction of the cost... Now, I'm almost certain if we simply reject the IA entirety, then yes, it won't take long before we are made completely obsolete.

    Good points and well made - yes, this future is coming and OCA and community must be at the front of it.

    I feel that a clear OCA position is important as without it, there is risk of collaborators working with different rules and assumptions which ultimately costs time and energy. So this is the opportunity for the community to work out what are the shared rules for this new world. If there is insufficient information owing to the rapidly changing landscape, then soft guidance may be the OCA position for now. 

    Whatever the case, transparency is essential, and omitting this will cause many problems such as compliance with the the new EU regulation which will activate in under 2 years.

    What's the action now - as Frederik proposed, a working group should pick this up, process the views of the community and define a policy based on consensus. This will continue to evolve so I don't think trying to nail it all down now is practical with this dynamic factored in.

    Best wishes,

    Stuart.
    

    
    

    On 27/09/2025 15:07, Raphaël Valyi wrote:
    

    Hello,

    
    

    I think IA policies and risks/benefits may vary a lot depending on the use cases...

    
    

    The thread was initially started about migrations. This is really a use case where IA can bring a lot of benefits with very limited risks. Indeed, recent migrations are very easy for most modules. We could have a huge benefit if we could get 1000+ modules easily migrated (with possible AI automated ports), using standard OCA tools and letting the AI adjust the tests and pre-commit considering the framework and upstream modules changes in the context window. As Graeme explained, these simple migrations usually involves no creative work nor copyright issues.

    
    

    As for generating larger pieces of new modules/vibe coding, well of course there would be more things to care about, like copyrights, quality control etc...

    
    

    Some projects like Qemu recently banned IA completely because they fear large pieces of contributed IA code may infringe copyrights (the LLM would kind of replicated copyrighted code without enforcing licenses) and taint the whole project. This is definitely something we should pay attention to.

    
    

    For instance if the AI is trained on Odoo Enterprise code (or just even just in the context window) and new similar code is generated it could taint the OCA code. On the contrary it is also entirely possible AI could very soon replicate many EE module or ERP feature just from the UI/specs without infringing any copyright (Odoo tends to copy other apps from their UI, AI could soon do it too...)

    
    

    But more importantly, there is no need for AGI nor phD level AI for AI (probably an OpenAI/Anthropic bubble) to change completely the software industry. The current level of LLMs with lowering costs is far enough to raise many concerns how code is made and more importantly how open source communities like us are organized.

    
    

    As Daniel explained, AI may of course multiply toxic or spam behavior and we should hold AI users responsible for it.

    
    

    But I think it is also very important to consider this: as many open source communities, the whole OCA was organized as a meritocracy where ability to create proper code and ERP knowledge was earned after many years of seniority and acknowledged as such. Despite ocasional disputes, modules authors, repo PSCs and all our OCA decision process is kind if naturally structured atop of this "traditional" coding and ERP expertise. merged code was kind of our "proof of work" in our pre-IA world.

    
    

    But AI will soon bring us to a world were an LLM will be more knowledgeable than senior ERP consultants and only top coders will be able to add any value over AI generated code. Good coders with access to compute will also be able to generate or maintain orders of magnitude more code. Bad coders with bad intentions will also be able to flood the OCA with poor quality contributions and the average person will not be able/not have time to filter the good options. In this is world that is coming in just a few months, how will we be able to maintain trust and organization? IMHO this should be a top concern for the OCA.

    
    

    Finally, for more than a decade, the business model behind the OCA was kind of: in traditional ERPs 70% of the cost is from consulting/customization and 30% from licenses. So some alien skilled people able to do both the code and the consulting (or small companies able to do both) would charge the 70% and use that revenue produce the ERP code free of license charges. That was working because non specialists would typically not be able simply download open source code and do their ERP project alone. So companies would somehwat hire module authors, pay the 70% consulting/customization cost and with limited parasistism, the ecosystem could somehow sustain itself.

    
    

    But soon the expertise to use OCA modules will drop a lot. The AI will bring it to the user directly bypassing modules authors and contributors entirely...

    
    

    How will our open source economy work in this context? Well an option I see is use AI on our side: manage order of magnitude more code and more customers for a fraction of the cost... Now, I'm almost certain if we simply reject the IA entirety, then yes, it won't take long before we are made completely obsolete.

    
    

    
    

    
    

    On Sat, Sep 27, 2025, 4:47 AM Stuart J Mackintosh <notifications@odoo-community.org> wrote:
    

    
    

    Indeed - it would be of benefit for OCA to have a position.
    

    Best wishes,

    Stuart.
    

    
    

    On 27/09/2025 09:27, Frederik Kramer wrote:
    

    Hi Stuart, hi all,
    
    very valuable for decision making but I think within our community we have people thinking as strict as Gentoo, NetBSD on the matter and others that would rather adopt the stance of the Linux or Apache Foundation. So possibly the board / governance/community health WGs shall come up with a decision proposal along these lines and ask for a solid quorum in the next AGA.
    
    Best Frederik

    
    
    

    Am 26. September 2025 08:42:39 MESZ schrieb Stuart J Mackintosh <notifications@odoo-community.org>:

    
    

    Following up and to take a look at how others have dealt with these matters, I noticed Fedora released an AI policy yesterday so I have briefly summarised (perplexity) this compared with a bunch of other policies, full analysis here: https://codimd.mackintosh.me/s/ifsByh-G8#
    

    Brief overview of policies:
    

    - The main goal is to blend innovation with strong safeguards—using AI tools to help, but keeping people fully responsible for results.
    - Most projects see transparency as crucial for maintaining trust and enabling fair review and collaboration.
    - Quality control and copyright protection are prioritized: automation should not dilute standards nor introduce legal risk.
    - Some policies are stricter, fully banning AI output unless human-vetted and legally certified.
    - Clause implementation mostly revolves around commit messages, contributor guidelines, and reviewed workflow steps—simple, actionable, easy to follow.
    
    This format ensures contributors know where, when, and how AI use is welcomed—and where human effort and discretion are absolutely required.
    

    Best wishes,

    Stuart.
    

    
    

    On 24/09/2025 11:01, Stuart J Mackintosh wrote:
    

    
    

    I propose that you address these points through the mechanism proposed by Daniel - responsible use, and behavioural guidance alongside a code of conduct which can determine obligations such as disclosure of AI use; Ai is just one of a set of issues that must be addressed.
    

    Best wishes,

    Stuart.

    
    

    On 24/09/2025 10:47, Graeme Gellatly wrote:
    

    I disagree. If you are holding yourself out as a professional you should declare AI usage and the scope.   Declaring AI usage is mandated for my profession, if I prepare any advice or report in a professional capacity I must declare. It is just not an option to say, oh well it is just a tool, when it really isn't, it directly created output.

    
    

    It also gives valuable information to both the reviewer and ultimately the users. 

    
    

    It is also important from a copyright perspective. There is no copyright in a lot of AI generated work without later creative human input and even then only the human inputs are usually covered. To be fair there is also no copyright in a lot of human generated output (i.e. bug fixes and migrations) as there is no creative output, so for that kind of work AI is actually ideal. Ref https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf
    

    
    

    
    

    On Tue, Sep 23, 2025 at 8:27 PM Daniel Reis <notifications@odoo-community.org> 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
    

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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
    

    --
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
            
    Phone:  +49 4181 13503-12
    Fax:    +49 4181 13503-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155

    _______________________________________________
    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

    Web: https://opendigital.cc

    IM: xmpp: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
    

    --
    

    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

    Web: https://opendigital.cc

    IM: xmpp:sjm@opendigital.cc

    ---

    by Stuart J Mackintosh - 05:31 - 28 Sep 2025

    1 attachments 1 attachments

    logo.png

  27 more replies

• Slides for Making Odoo Faster talk at OCA Days 2025

  Hello, 

  
  

  For those interested, the slides for the talk Making Odoo Faster
  Analyzing Odoo’s Speed that I gave yesterday are available here:

  
  

  https://docs.google.com/presentation/d/1HpEGgmxxSUvAhF5r1XWO-1OqiQWPPJF4jPZ-XRg-e4k/edit?slide=id.g29db379d51f_0_3#slide=id.g29db379d51f_0_3

  
  --
  

  Alexandre Fayolle
  Senior Software Engineer and Architect
  
  Camptocamp France SAS
  http://www.camptocamp.com
  
  

  ---

  by Alexandre Fayolle - 10:26 - 17 Sep 2025

  2 replies 2 replies

  • Re: Slides for Making Odoo Faster talk at OCA Days 2025

    Thanks Alexandre,
    
    very good and insightful talk from you. I enjoyed it very much. I will also directly share it with my team.
    
    Best Frederik

    
    
    

    Am 17. September 2025 10:26:46 MESZ schrieb Alexandre Fayolle <notifications@odoo-community.org>:

    Hello, 

    
    

    For those interested, the slides for the talk Making Odoo Faster
    Analyzing Odoo’s Speed that I gave yesterday are available here:

    
    

    https://docs.google.com/presentation/d/1HpEGgmxxSUvAhF5r1XWO-1OqiQWPPJF4jPZ-XRg-e4k/edit?slide=id.g29db379d51f_0_3#slide=id.g29db379d51f_0_3

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    --
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
            
    Phone:  +49 4181 13503-12
    Fax:    +49 4181 13503-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155

    ---

    by Frederik Kramer - 04:55 - 17 Sep 2025

  • Re: Slides for Making Odoo Faster talk at OCA Days 2025

    Thank you !!

    
    

     --

    Yves Goldberg
    

    --

    
    

    ----- Original message -----

    From: Alexandre Fayolle <notifications@odoo-community.org>

    To: Contributors <contributors@odoo-community.org>

    Subject: Slides for Making Odoo Faster talk at OCA Days 2025

    Date: Wednesday, September 17, 2025 11:26

    
    

    Hello, 

    
    

    For those interested, the slides for the talk Making Odoo Faster

    Analyzing Odoo’s Speed that I gave yesterday are available here:

    
    

    https://docs.google.com/presentation/d/1HpEGgmxxSUvAhF5r1XWO-1OqiQWPPJF4jPZ-XRg-e4k/edit?slide=id.g29db379d51f_0_3#slide=id.g29db379d51f_0_3

    
    

    --

    Alexandre Fayolle

    Senior Software Engineer and Architect

    
    

    Camptocamp France SAS

    http://www.camptocamp.com

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    
    

    ---

    by Yves Goldberg - 10:36 - 17 Sep 2025

• Oferta de empleo de Consultor/a Odoo

  Buenos días, 

  Me pongo en contacto con vosotros ya que actualmente disponemos de una oferta de empleo que podría resultar de interés para vuestros/as asociados/as. 

  Estamos buscando un perfil de Consultor Odoo para Valladolid en modalidad híbrida y me preguntaba si sería posible publicar la oferta en vuestra página web para que pudieran inscribirse las personas interesadas en la misma.

  En el siguiente enlace puedes ver todos los detalles de la oferta: https://www.jobfie.es/trabajo/13896540/Valladolid/consultora-erp-odoo-contrato-indefinido

  Cualquier duda quedo a vuestra disposición.

  Gracias de antemano, un saludo.

  --
  FIRMA SANDRA RODRIGUEZ

  	Sandra Rodríguez Jobfie | Portal de empleo Responsable de operaciones   sandra.rodriguez@jobfie.es Valladolid, España www.jobfie.es
  El contenido de este correo electrónico es confidencial y está destinado únicamente al destinatario especificado en el mensaje. Está estrictamente prohibido compartir cualquier parte de este mensaje con terceros, sin el consentimiento por escrito del remitente. Si recibió este mensaje por error, responda a este mensaje y continúe con su eliminación, para que podamos asegurarnos de que ese error no ocurra en el futuro.

  
  

  Libre de virus.www.avast.com

  ---

  by "Sandra Rodriguez" <sandra.rodriguez@jobfie.es> - 11:25 - 16 Sep 2025

• Application for PSC Role – RMA Repository

  Dear contributors,

  
  I would like to apply for the PSC role for the RMA repository.
  
  Over the last months, I have been actively contributing to the RMA repository, working on several improvements to the base module to provide a more flexible and configurable workflow depending on the operation. I have also introduced new modules that add important features, such as RMA reasons, lot/serial number tracking, and I am currently working on the integration between RMA and the repair module.
  
  I believe I can contribute to maintaining and evolving this stack by reviewing, testing, and supporting new contributors.
  
  You can find my PRs here: https://github.com/OCA/rma/pulls/sbejaoui
  
  Best regards,
  
  

  --
  

  Souheil Bejaoui

  Software engineer

  
  

  
  

  Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium

  Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

  Zone industrielle 22 | L-8287 Kehlen | Luxembourg

  ---

  by Souheil Bejaoui - 10:41 - 16 Sep 2025

  2 replies 2 replies

  • Re: Application for PSC Role – RMA Repository

    Hi Souheil,

    
    

    You can do a PR there: https://github.com/OCA/repo-maintainer-conf/pulls

    
    

    Le mar. 16 sept. 2025 à 10:42, Bejaoui, Souheil <notifications@odoo-community.org> a écrit :
    

    Dear contributors,

    
    I would like to apply for the PSC role for the RMA repository.
    
    Over the last months, I have been actively contributing to the RMA repository, working on several improvements to the base module to provide a more flexible and configurable workflow depending on the operation. I have also introduced new modules that add important features, such as RMA reasons, lot/serial number tracking, and I am currently working on the integration between RMA and the repair module.
    
    I believe I can contribute to maintaining and evolving this stack by reviewing, testing, and supporting new contributors.
    
    You can find my PRs here: https://github.com/OCA/rma/pulls/sbejaoui
    
    Best regards,
    
    

    --
    

    Souheil Bejaoui

    Software engineer

    
    

    
    

    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium

    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

    Zone industrielle 22 | L-8287 Kehlen | Luxembourg

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    ---

    by Denis Roussel - 10:51 - 16 Sep 2025

  • Re: Application for PSC Role – RMA Repository

    Souheil, put the PR directly in https://github.com/OCA/repo-maintainer-conf 

    
    

    Regards.

    ---

    by Pedro M. Baeza - 10:51 - 16 Sep 2025

• OCA Days 2025 Streaming

  
  

  Hi all,

  
  

  Here are the links to the OCA Days Streaming:
  
  odoocommunity1 => Mosane 5+6 

  odoocommunity2 => Mosane 2+3 
  

  odoocommunity3 => Mosane 7+8+9

  
  

  Here is the agenda: 

  https://odoo-community.org/event/oca-days-2025-liege-2025-09-15-2025-09-18-174/agenda

  
  

  Have a great day,

  Rebecca

  --
  

  Rebecca Gellatly

  General Secretary

  Odoo Community Association

  ---

  by Rebecca Gellatly (OCA) - 10:20 - 16 Sep 2025

  2 replies 2 replies

  • Re: OCA Days 2025 Streaming

    Hello,

    
    

    The OCA Days talks were uploaded to Twitch because Youtube would not let us livestream (we did the config too late it seems).

    
    

    The multiple accounts are linked to the 3 different rooms where there were talks in parallel.

    
    

    All the talks were recorded and will be shared on Youtube in a few days. (Not all, we might keep more "internal" talks outside of the public space)

    
    

    Virginie Dewulf

    Executive Director

    Odoo Community Association (OCA)

    +32 477 64 17 20

    
    

    
    

    Le sam. 20 sept. 2025 à 16:02, IB Teguh TM <notifications@odoo-community.org> a écrit :
    

    Hi Rebecca,

    
    

    Thank you for the information regarding the OCA Days Streaming. I have a few questions:

    1. Why is it being uploaded to Twitch? As far as I remember, it will be deleted within 1-2 months.
    2. Why are there multiple accounts like odoocommunity1, 2, and 3?
    3. Are there any plans to upload these to YouTube?

    
    

    On Tue, Sep 16, 2025 at 4:22 PM Rebecca Gellatly <rebecca@odoo-community.org> wrote:
    

    
    

    Hi all,

    
    

    Here are the links to the OCA Days Streaming:
    
    odoocommunity1 => Mosane 5+6 

    odoocommunity2 => Mosane 2+3 
    

    odoocommunity3 => Mosane 7+8+9

    
    

    Here is the agenda: 

    https://odoo-community.org/event/oca-days-2025-liege-2025-09-15-2025-09-18-174/agenda

    
    

    Have a great day,

    Rebecca

    --
    

    Rebecca Gellatly

    General Secretary

    Odoo Community Association

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    
    

    
    

    --
    

    Thank and Regards 
    

    IB Teguh TM

    about.me/teguhteja
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    ---

    by Virginie Dewulf - 06:21 - 29 Sep 2025

  • Re: OCA Days 2025 Streaming

    Hi Rebecca,

    
    

    Thank you for the information regarding the OCA Days Streaming. I have a few questions:

    1. Why is it being uploaded to Twitch? As far as I remember, it will be deleted within 1-2 months.
    2. Why are there multiple accounts like odoocommunity1, 2, and 3?
    3. Are there any plans to upload these to YouTube?

    
    

    On Tue, Sep 16, 2025 at 4:22 PM Rebecca Gellatly <rebecca@odoo-community.org> wrote:
    

    
    

    Hi all,

    
    

    Here are the links to the OCA Days Streaming:
    
    odoocommunity1 => Mosane 5+6 

    odoocommunity2 => Mosane 2+3 
    

    odoocommunity3 => Mosane 7+8+9

    
    

    Here is the agenda: 

    https://odoo-community.org/event/oca-days-2025-liege-2025-09-15-2025-09-18-174/agenda

    
    

    Have a great day,

    Rebecca

    --
    

    Rebecca Gellatly

    General Secretary

    Odoo Community Association

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe
    

    
    

    
    

    --
    

    Thank and Regards 
    

    IB Teguh TM

    about.me/teguhteja
    

    ---

    by IB Teguh TM - 04:00 - 20 Sep 2025

• OCA AGA Delelgates Campaign open now - till October 3rd

  Hello OCA Contributors

  
  

  I hope this finds you all well.

  It is that time of year again for the OCA Annual General Assembly
  
  

  The 2025 OCA Delegates Campaign is now open. Until October 3rd, you can apply to be an OCA Delegate if you are a current paid Member.
  If you are already a Delegate, you don't need to apply again. This is for 10 new Delegates.
  
  Why?
  The Delegate Assembly is the Association’s supreme authority. Each Delegate member is entitled to one vote at the Delegate Assembly. Decisions of the Delegate Assembly are taken by a majority vote of the Delegate members present and voting. For further details, please read the Bylaws.
  
  How?
  To apply as a candidate, you have to:
  

  • sign the CLA (if not already done)
  • have a valid membership. Make sure to purchase your membership or renew it (you should have received a quotation for your renewal earlier this year).
  • fill in this survey

  If you aren't sure if you have renewed/paid your membership for 2025 please contact me.
  
  The campaign will be closed on October 3rd, 2025.
  
  Then what?
  The vote will be open from October 6th - October 17th. Current OCA Delegates will have to vote for 10 new Delegates among the candidates.
  
  The results of the election will be announced on October 20th, 2025.
  
  The 10 new Delegates will then take part with the existing Delegates in :
  

  • the 2025 OCA Board Member Campaign from October 20th - October 31st, 2025
  • the 2025 OCA Financial Auditor Campaign from October 20th - October 31st, 2025
  • the 2025 General Assembly from November 3rd to November 14th 2025.
  • 2025 Board announced - week beginning November 17th, 2025 

  If you have any questions please get in touch.
  
  Warmest regards,
  Rebecca

  
  

  --
  

  Rebecca Gellatly

  General Secretary

  Odoo Community Association

  ---

  by Rebecca Gellatly (OCA) - 11:25 - 15 Sep 2025

• The Consultant Working Group is looking for you!

  Dear members,
  Did you know we have a working group for consultant / functional people?
  
  We are looking for new members in this group so if you are interested, please contact me (Julie) at julie@odoo-community.org.
  
  The “Raison d’être” of the group is to help and attract functional people (non-technical) to contribute to the OCA.
  
  Here are the requirements to be part of this group:
  - More than 3 years of experience with OCA tools (GitHub, Weblate…) and modules
  - More than 3 years of experience as a Consultant on Odoo
  - More than 3 years of experience with Odoo
  - Availability (1 wg meeting a month + 4h /month to contribute)
  - Approval from the majority of the actual members of the WG
  
  We will meet at the OCA Days on Monday morning so if you are interested, come and meet us (and contact me to let me know).
  
  P.S. In October, we will start a series of Support group meeting for functional / consultant so even if you don't meet the requirements to be part of the group, you can still attend these meetings.
  
  More info here : https://odoo-community.org/event/oca-consultants-support-group-session-2025-10-07-206/register

  ---

  by Julie LeBrun (OCA) - 10:21 - 13 Sep 2025

  2 replies 2 replies

  • Re: The Consultant Working Group is looking for you!

    Hello Michel,

    As discussed in person, the criterias are guides to ensure that people in the WG have enough experience in the OCA processes, tools and modules to help other people.  This experience needed is a functional one not a technical one. 

    
    

    I hope you understand better now.

    See you!

    
    

    Le lun. 15 sept. 2025 à 18:30, <mstroom@office-everywhere.com> a écrit :
    

    Dear Julie,

    I'm not sure why 3 years of experience is required for non-technical volunteer work in the 'Consultant / Functional Workgroup.' In my opinion, it's actually better for consultants not to have technical knowledge, and those with IT expertise can join other workgroups.
    
    What seems more important is finding people who are enthusiastic, willing to consistently contribute their free time, and committed to staying involved, even without compensation.
    
    Wishing you and the other Consultant / Functional Workgroup members the best in finding the right contributors. I also hope you’ll all consider dropping the 3-year Odoo experience requirement in favor of prioritizing commitment.

    Looking forward to seeing all OCA members at OCA Days 2025 in Liège.
    Let's have a drink next week, Julie. I’m also curious to hear why the workgroup is asking for 3 years of experience.

    
    Best, Michel.

    Office Everywhere
    Business Partner Odoo

    t: +31 6 53360677
    e: mstroom@office-everywhere.com
    w: Office-Everywhere.com

    
    

    On 2025-09-13 10:21, Julie LeBrun (OCA) wrote:

    Dear members,
    Did you know we have a working group for consultant / functional people?
    
    We are looking for new members in this group so if you are interested, please contact me (Julie) at julie@odoo-community.org.
    
    The "Raison d'être" of the group is to help and attract functional people (non-technical) to contribute to the OCA.
    
    Here are the requirements to be part of this group:
    - More than 3 years of experience with OCA tools (GitHub, Weblate...) and modules
    - More than 3 years of experience as a Consultant on Odoo
    - More than 3 years of experience with Odoo
    - Availability (1 wg meeting a month + 4h /month to contribute)
    - Approval from the majority of the actual members of the WG
    
    We will meet at the OCA Days on Monday morning so if you are interested, come and meet us (and contact me to let me know).
    
    P.S. In October, we will start a series of Support group meeting for functional / consultant so even if you don't meet the requirements to be part of the group, you can still attend these meetings.
    
    More info here : https://odoo-community.org/event/oca-consultants-support-group-session-2025-10-07-206/register

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    
    

    
    

    --
    

    Julie LeBrun

    Content Creator & Training Manager

    Odoo Community Association (OCA)

    GitHub : https://github.com/TumbaoJu 

    ---

    by Julie LeBrun (OCA) - 02:56 - 17 Sep 2025

  • Re: The Consultant Working Group is looking for you!

    Dear Julie,

    I'm not sure why 3 years of experience is required for non-technical volunteer work in the 'Consultant / Functional Workgroup.' In my opinion, it's actually better for consultants not to have technical knowledge, and those with IT expertise can join other workgroups.
    
    What seems more important is finding people who are enthusiastic, willing to consistently contribute their free time, and committed to staying involved, even without compensation.
    
    Wishing you and the other Consultant / Functional Workgroup members the best in finding the right contributors. I also hope you’ll all consider dropping the 3-year Odoo experience requirement in favor of prioritizing commitment.

    Looking forward to seeing all OCA members at OCA Days 2025 in Liège.
    Let's have a drink next week, Julie. I’m also curious to hear why the workgroup is asking for 3 years of experience.

    
    Best, Michel.

    Office Everywhere
    Business Partner Odoo

    t: +31 6 53360677
    e: mstroom@office-everywhere.com
    w: Office-Everywhere.com

    
    

    On 2025-09-13 10:21, Julie LeBrun (OCA) wrote:

    Dear members,
    Did you know we have a working group for consultant / functional people?
    
    We are looking for new members in this group so if you are interested, please contact me (Julie) at julie@odoo-community.org.
    
    The "Raison d'être" of the group is to help and attract functional people (non-technical) to contribute to the OCA.
    
    Here are the requirements to be part of this group:
    - More than 3 years of experience with OCA tools (GitHub, Weblate...) and modules
    - More than 3 years of experience as a Consultant on Odoo
    - More than 3 years of experience with Odoo
    - Availability (1 wg meeting a month + 4h /month to contribute)
    - Approval from the majority of the actual members of the WG
    
    We will meet at the OCA Days on Monday morning so if you are interested, come and meet us (and contact me to let me know).
    
    P.S. In October, we will start a series of Support group meeting for functional / consultant so even if you don't meet the requirements to be part of the group, you can still attend these meetings.
    
    More info here : https://odoo-community.org/event/oca-consultants-support-group-session-2025-10-07-206/register

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    ---

    by Michel Stroom - 06:30 - 15 Sep 2025

• 1
• 2
• 3
• 4
• 5