Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

  • Display product template ref in product variant views?
    Hello, I cannot find a module to show product template reference in common "product.product" (aka product variant) form-views. Something like this (screenshot)

    image.png

    Do we have a module for this task?
    Thanks
    ____________________
    Francesco Ballerini
    by Francesco Ballerini - 10:36 - 28 Sep 2023

    1 attachments 1 attachments

    image.png

    1 replies 1 replies

  • RFQ for OCA Open Upgrade Programme Manager
    Hello OCA Contributors,

    I hope this finds you all well.
    The deadline for this RFQ is 28th October, 2023.

    If you have any questions please get in touch.

    Warmest regards,
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 11:35 - 28 Sep 2023

    1 attachments 1 attachments

    2023 OCA RFQ for OpenUpgrade Programme Manager.pdf
  • Documents associated to Sale Order - V12
    Hello All
     
    Nice to meet you. My name is Cedric DEBARD, i'm working as IT Administrator in the south of France. I'm using the Odoo Community Edition V12 as the main backbone application in my enterprise. I will be at OCA Days 2023 and i will be happy to meet members and discuss about version migration, module development, beer, life and philosophy. 

    Waiting november, i'm currently working in my sale module, i would like to add the possibility to attach documents (working documents) to a sale order. Those documents does not have to be seen or sent at the final client. It should be very very very simple, for me it should be done via a drag and drop on the sale order form.

    Do you have any thoughts, code snippets, or existing modules ?

    Regards, Enjoy life
    by Cedric DEBARD - 09:41 - 28 Sep 2023

    1 replies 1 replies

  • Translate with odoo GUI in 2023 is fine ?
    I have some modules where I need to translate some terms. 

    Assuming that:
    - most of those modules are not public (or definitely not widely used)
    - for this task I don't really need a cloud platform to share project with other people

    I was wondering if I could just translate my terms from English to another language, then simply export .pot and .po file. 

    Is there any tools that I should be aware of ?

    Thank you very much
    _______________
    Francesco Ballerini

    by Francesco Ballerini - 09:39 - 27 Sep 2023

    1 replies 1 replies

    • Re: Translate with odoo GUI in 2023 is fine ?
      El mié, 27-09-2023 a las 19:39 +0000, Francesco Ballerini escribió:
      Is there any tools that I should be aware of ?

      It seems like poedit is the one you need.
      by Jairo Llopis - 09:51 - 28 Sep 2023
  • [Feature] Some products in e-commerce must not been paid at checkout
    Dear all

    A customer of ours needs that some products should not been paid at e-commerce checkout

    It could be done by :
    - assigning payment methods to products/product categs, then one payment method would be 'dummy' (difficult to manage a cart with products linked to different payment methods)
    - some products/product categ must go to wishlist and cannot go to cart
    - ...

    Do you have any thoughts or existing modules ?

    Thanks in advance
    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 - 08:01 - 27 Sep 2023

    1 replies 1 replies

  • Operating unit details for Qweb reports
    Hi 
    The module https://github.com/OCA/operating-unit/tree/15.0/report_qweb_operating_unit says to use custom operating unit headers for any report in Odoo.
    When I go to report_qweb_operating_unit-15.0.1.0.0\report_qweb_operating_unit\views\report_qweb_operating_unit.xml , I the code talking about logo, phone, email and web ... etc of the Operating Unit to be used instead of the company details
    But actually I can not see where to add these 'operating unit' custom details?
    If I go to Settings>operating units. to show any operating unit,  I can not find any extra fields except Name, Code , Partner and Company

    image.png
    It seems there is something I miss.
    I'm asking because I want to use a custom header for the invoice pdf for every operating unit
    I hope you give me advice.
    by "Ahmed@HAAT" <a.ragab@haat.com.sa> - 01:36 - 26 Sep 2023

    1 attachments 1 attachments

    image.png

    1 replies 1 replies

  • Development environement
    Hi, 

    My name is Sylvain.

    I would like to know about creating an Odoo local environment, because I want to be more efficient in the development of the modules, than on Odoo.sh.
    I can already launch my server with Odoo, Odoo enterprise and my custom_addons.

    However I have other problems like updating the code live, I have to constantly restart the server. I saw that there were default parameters for development like: --dev=reload using the "watchdog" lib, except that after 2 3 refresh the server shuts down.

    I have already used Odoo.sh and its editor, and Python recompiles well with each change, so this is doable

    Same for Owl components, I find it crazy that in 2023 there is no auto refresh, so I am looking for the most optimized solution for Odoo module development.

    Do you have an installation guide for local development?
    The development by Docker is perhaps simpler?

    Some additional information:

    I am on windows
    VScode, and I'm using vscode launch.js configs for Odoo server

    Thanks in advance

    Sans virus.www.avast.com
    by Sylvain - 08:35 - 23 Sep 2023

    2 replies 2 replies

    • Re: Development environement
      Hello

      It looks like you posted the same one on august 16th and you had a lot of replies already

      But maybe this is a message that has been sent twice by odoo-community.org
      We already had a weird thing like that a few days ago

      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 sam. 23 sept. 2023, 08:36, Sylvain Caron <notifications@odoo-community.org> a écrit :
      Hi, 

      My name is Sylvain.

      I would like to know about creating an Odoo local environment, because I want to be more efficient in the development of the modules, than on Odoo.sh.
      I can already launch my server with Odoo, Odoo enterprise and my custom_addons.

      However I have other problems like updating the code live, I have to constantly restart the server. I saw that there were default parameters for development like: --dev=reload using the "watchdog" lib, except that after 2 3 refresh the server shuts down.

      I have already used Odoo.sh and its editor, and Python recompiles well with each change, so this is doable

      Same for Owl components, I find it crazy that in 2023 there is no auto refresh, so I am looking for the most optimized solution for Odoo module development.

      Do you have an installation guide for local development?
      The development by Docker is perhaps simpler?

      Some additional information:

      I am on windows
      VScode, and I'm using vscode launch.js configs for Odoo server

      Thanks in advance

      Sans virus.www.avast.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 Cyril VINH-TUNG - 12:05 - 24 Sep 2023
    • Re: Development environement
      Hola Sylvain..

      Before I was looking for the same topic, what I did was install the windows installer that Odoo has on its official website; I installed it on my windows 10. Configure and connect the vs Code to the folder; To develop the modules there was no problem, the details were to see the changes, what I did was try to restart the service in Windows; and I used the Odoo Google Chrome extension to update the module that made changes, and it worked perfectly; To debug code, what I did was filter the Odoo log and review it.
      Maybe there is other easy way. But it worked for me

      Atte:
      Daniel

      El sáb, 23 sept 2023 a las 13:37, Sylvain Caron (<notifications@odoo-community.org>) escribió:
      Hi, 

      My name is Sylvain.

      I would like to know about creating an Odoo local environment, because I want to be more efficient in the development of the modules, than on Odoo.sh.
      I can already launch my server with Odoo, Odoo enterprise and my custom_addons.

      However I have other problems like updating the code live, I have to constantly restart the server. I saw that there were default parameters for development like: --dev=reload using the "watchdog" lib, except that after 2 3 refresh the server shuts down.

      I have already used Odoo.sh and its editor, and Python recompiles well with each change, so this is doable

      Same for Owl components, I find it crazy that in 2023 there is no auto refresh, so I am looking for the most optimized solution for Odoo module development.

      Do you have an installation guide for local development?
      The development by Docker is perhaps simpler?

      Some additional information:

      I am on windows
      VScode, and I'm using vscode launch.js configs for Odoo server

      Thanks in advance

      Sans virus.www.avast.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 DANIEL CARRION - 11:40 - 23 Sep 2023
  • E-Mail Tracking V16
    Hello,
    are there any plans to upgrade this app: https://apps.odoo.com/apps/modules/15.0/mail_tracking/ to V16?
    --

    Herzliche Grüße / Kind regards
    Tim Vollmer
    Software Consultant






    by Tim Vollmer - 10:36 - 21 Sep 2023

    1 replies 1 replies

  • multi company issue
    Dear 
    i have that issue for multi company 
    image.png
    i solve this issue with add user group under record rule

    image.png
    when i add user group the user can issues the invoice but user now see all Customers for both companies 


    --
    Best Regards
    Samir Mahmoud
    00201062648111


    by Samir Mahmoud Hassan - 11:06 - 20 Sep 2023

    2 attachments 2 attachments

    image.png
    image.png

    5 replies 5 replies

  • Branches for v17.0
    Hello,

    I have a question, We are working for a customer who wants to be in v17 in October when Odoo 17 is done.

    Is it possible to create the OCA branches for v17 at this moment?  Or only when the Odoo branch for v17 is ready?

    Regards
    by Luis Ernesto Torres - 06:55 - 19 Sep 2023

    3 replies 3 replies

    • Re: Branches for v17.0 
      On 19/09/23 18:56, Luis Ernesto Torres [Vauxoo] wrote:

> I have a question, We are working for a customer who wants to be in v17 

> in October when Odoo 17 is done.

Hi Luis,

Don't forget that Odoo 17.0 is going to be released only in November, 
not October (the Odoo Experiences are a bit later this year).

Best,

Martin
      by Martin Trigaux - 01:30 - 20 Sep 2023
    • Re: Branches for v17.0 
      > Is it possible to create the OCA branches for v17 at this moment?  Or only

> when the Odoo branch for v17 is ready?

for what I assume you want to do (just now already develop stuff for v17), you 
don't need OCA v17 branches anyways. Just start doing your things in an empty 
branch using the usual migration steps (one branch per module), and you'll be 
able to easily cherry-pick this to the upcoming OCA branches and then PR them 
as your migration of whatever module(s) it's about.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 10:10 - 19 Sep 2023

      1 attachments 1 attachments

      signature.asc
    • Re: Branches for v17.0
      > Is it possible to create the OCA branches for v17 at this moment?

      No, that is not possible. CI wouldn't work without the 17.0 branches from Odoo.

      For reference here is the checklist we had to prepare our tooling for v16: https://github.com/OCA/maintainer-tools/issues/537

      Best regards,

      -Stéphane

      On Tue, Sep 19, 2023 at 6:56 PM Luis Ernesto Torres [Vauxoo] <notifications@odoo-community.org> wrote:
      Hello,

      I have a question, We are working for a customer who wants to be in v17 in October when Odoo 17 is done.

      Is it possible to create the OCA branches for v17 at this moment?  Or only when the Odoo branch for v17 is ready?

      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 Stéphane Bidoul - 09:59 - 19 Sep 2023
  • multi company issue
    Dear 
    i have that issue for multi company 
    image.png
    i solve this issue with add user group under record rule

    image.png
    when i add user group the user can issues the invoice but user now see all Customers for both companies 

    --
    Best Regards
    Samir Mahmoud
    00201062648111


    by Samir Mahmoud Hassan - 10:11 - 19 Sep 2023

    2 attachments 2 attachments

    image.png
    image.png
  • OCA Functional Group - Project Modules Documentation

    After the last OCA Days in 2022, a group of functional people from different countries and companies decided to work together to improve functional contributions in OCA. 


    Documentation of OCA modules has been identified as one of the main areas where functionals’ expertise can be useful. 


    Our primary goals with this project are:

    • to make it easier for everyone to understand what is the purpose of a module and how to use it ;

    • to provide guidelines on how to write good and complete documentation ;

    • to improve access to editing and contribution of module’s documentation for functional people (eg: adding screenshots).


    What are the changes?

    • Implementing Markdown in place of RST for Read Me

      • A great module documentation has screenshots so the reader can understand better how to use the module. The problem is that it is difficult for a functional person to add screenshots into an RST file.  You must upload the image in a folder (and you have to know which one ;) ), then you need to know how to put the link to the image, and if you make a mistake, the image doesn't show…

      • Markdown files are supported by GitHub and this format allows you to insert a screenshot easily by Drag & Drop.

      • Markdown provides a simple and unified layout (as RST do) so we don’t lose this advantage.

      • GitHub provides a Markdown editor tool so you don’t even have to learn the syntax (but, we tell you, it is very easy to learn ;) ) 

    • Providing guidelines for documentation

      • We are still working on the Guidelines but we will have a first version ready for the OCA days!

    • Enhancing Readme template

      • Adding some information into the description of the fragments so anybody (functional or developer) can understand the usage of each fragment.

      • Adding a new CONTEXT fragment. This new fragment can then be used to explain the why (context, use cases) of the module.


    What are the impacts of those changes?

    • The Read Me’s template files have been converted to Markdown.

    • We will be converting, in the next weeks, all Read Me files to Markdown for all repositories in branch “16.0”. 

    • Read Me in RST will still be accepted but we strongly recommend to use Markdown for all the reasons enumerated previously.

    • For the branch “17.0”,  only Markdown files will be accepted.


    How to proceed in case of migration of a module?

    • You can convert existing readme fragments from RST to Markdown for a whole repo using a command such as:

    $ oca-gen-addon-readme --convert-fragments-to-markdown --org-name OCA --repo-name rest-framework --branch 16.0 --addons-dir . --gen-html


    • You can also convert an individual addon with --addon-dir (instead of --addons-dir) with a command like this:

    $ oca-gen-addon-readme --convert-fragments-to-markdown --org-name OCA --repo-name purchase-workflow --branch 16.0 --addon-dir purchase_request --gen-html



    How to proceed in case of pushing a new module into OCA?

    • Using the templates (which are now in Markdown)

    • And we recommend you follow the Guidelines!

      • We will be communicating about these Guidelines when they are ready!


    We hope you enjoy these improvements!!!


    The OCA Functional Group, Documentation Team

    Julie LeBrun, Numigi Solutions

    Francesco Foresti, ooops

    Lara Freeke, Therp

    Benedito Monteiro


    by Julie LeBrun - 04:12 - 18 Sep 2023

    4 replies 4 replies

  • tool: Odoo Modules Migration 
    Hi!
I wrote a simple tool which helps me keeping an overview of module 
upgrades during ongoing upgrade projects, especially for a large amount 
of modules. I hope someone finds it useful.

https://github.com/Nitrokey/odoo-modules-migration

Best regards
Jan
    by Jan Suhr - 09:35 - 18 Sep 2023

    11 replies 11 replies

    • Re: tool: Odoo Modules Migration

      Hello Florian,

      Seems we are targeting the same goals with different solutions, but a common ground could be found.

      Like you the code is hosted under our github: https://github.com/camptocamp/odoo-repository
      (still a "POC", need to write tests). I added some screenshots in the README.

      How to use it:
      - define a list of repositories + where to find modules in it (addons paths), it's not tied to any development environment
      - grab all kind of data from these repositories
      - define your Odoo projects and import the installed modules to do the match with the scanned data from repositories (if there is no match, try to find the relevant PR URLs on GitHub - pending merges). We could imagine a "phone home" module installed on customer Odoo instances that will be in charge to push these data to this Odoo Repository node, for now it is a simple copy/paste of installed modules in a wizard.

      We have to talk about these tools at OCA Days, you are going a step further with the migration complexity it is really interesting.

      Kind regards,


      Le 05/10/2023 à 10:27, Florian Kantelberg a écrit :

      Hello,

      interesting mail Sebastian. Most of it sounds familiar because we aim for the same goals with [1] (pypi odoo-analyse). Generally speaking odoo-analyse goes deeper than a simple lines of code analyses because there are plenty of cases reading the manifest isn't enough (e.g. Odoo 16.0 website has a hidden dependency towards iap because of an import). In the last days we extended it also to allow to estimate the modules which would be installed in a system without a database which should influence the initial topic of this mailing list [see 3] (@Jan). It resolves auto_install and dependencies starting from an initial module list.

      The tool is the foundation of [2] one of our long term projects and this is the reason why the current code is under our github and not pushed towards the OCA in the past. There would be no problem for a joint operation and we could push it to the OCA if we can stay maintainer of it. We (initOS) are also on the OCA days and would welcome support/ideas/feedback.

      We also already added complexity measurements in preparation to estimate a module and system complexity and furthermore a migration complexity. In the future we plan to offer a service to estimate module complexities in conjunction with the files from odoo-analyse (via a trained model) or for experts to estimate the complexities of modules to train a model even further basically as part of [2].

      Btw it lacks the repository management because this one is better handled externally (e.g. git-aggregator is a great tool). There are various build environments for Odoo and we learned that without the repository management we can easier analyse in different environments. Often enough there is already a CI or a development environment and reading the odoo.cfg is easy enough.

      Best Regards,

      Florian

      [1] https://github.com/initOS/odoo-analyse

      [2] https://www.odoo-code-search.com

      [3] `cat modules.txt | odoo_analyse -p odoo --modules - --analyse analyse.json --estimate-state --state-filter installed`

      where odoo is the folder under which ALL modules can be found

      Am 04.10.23 um 17:57 schrieb Sebastien Alix:

      Hi,

      I am the author of 'oca-port' so I'll try to answer your questions.

      These two tools aim two different purposes, but have few common points:

      - oca-port: it doesn't really know what is Odoo, this tool only plays with commits of git repositories to help the user to:
          1) migrate the git history of the module ('git format-patch' dance) and run pre-commit before inviting the user to follow the OCA migration guide. It'll also request GitHub API to find a open PR to invite the user to review it instead of creating a new one.
          2) for modules already migrated, it'll list the commits and related PRs that could be ported to fill the gap (fixes or features)
          3) a parsable output is available so we at Camptocamp are using it to scan OCA repositories and generate reports to estimate the work to achieve for migration projects (which modules are 100% ported, missing some fixes/features, have to be migrated and which ones having a PR to review)

      - odoo-module-migrator: from what I know (I do not use this tool yet) its job is to help you to migrate Odoo code to the target version (e.g. if a XML tag has been deprecated, it'll warn or update to the new format).

      Both tools could be used together, my idea would be that 'oca-port' leverages 'odoo-module-migrator' to automatically update the code in a migration process. From now, the user can call 'oca-port' then call 'odoo-module-migrator' manually (not tested), no big deal.

      I think the common points right now is that 'odoo-module-migrator' also does the 'git format-patch' step, and run pre-commit.


      FYI I also started an Odoo project that scans all kind of git repositories (OCA, Odoo, private repos) to collect modules metadata and consolidate all these data in one place, and it leverages oca-port to collect the migration data presented above. This tool aims to help functional & technical people with these kind of features:

      - get number of lines of code (Python/JS/XML/CSS) by module/repo/branch/organization or any filter you want
      - for maintainers, get a quick overview of the state of their modules
      - what are the most used OCA addons among all your Odoo projects
      - in term of lines of code of a customer project, how are they distributed among  Odoo, OCA and specifics
      - generate reports to ease the estimation of migration projects for a given migration path (e.g. 14.0 -> 16.0)
      - know all Python dependencies used in OCA to avoid versions conflicts or to improve security updates

      A lot of use cases could be addressed I guess. I'll probably make a presentation of this at OCA Days (need to finish some stuff, do some cleanup, host the code in a OCA repository, and address some questions regarding the hosting).

      Kind regards,


      Le 04/10/2023 à 09:26, Rafael Blasco a écrit :

      This is a really nice topic to have a doc/talk about for new contributor. Maybe for OCA DAys

       

      • Which is the use of both tool?
      • Why 2 and not just a single 1? (they should be different with different authors)
      • A "How to" for newcontribs are really useful to increase OCA

       

      It is not trivial and easy for everyone. The moment we take things for granted we lose contributors along the way.

       

      https://github.com/OCA/oca-port

      https://github.com/OCA/odoo-module-migrator

       

      Thank you!

      Regards

      Rafael

       

       

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

      Enviado el: martes, 26 de septiembre de 2023 10:03

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

      Asunto: Re: tool: Odoo Modules Migration

       

      Hello, you should check oca-port too

       

      https://github.com/OCA/oca-port

       

      Best regards

      --

      Alexandre Fayolle

      Senior Software Engineer

      Tel : +33 4 58 48 20 30

       

       

       

      De: Fernando La Chica <notifications@odoo-community.org>

      Enviado el: lunes, 18 de septiembre de 2023 23:08

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

      Asunto: Re: tool: Odoo Modules Migration

       

      Take a look at this tool

       

      https://github.com/OCA/odoo-module-migrator

       

      At first I thought it was the same tool. I understand that it is out of the scope of your tool but I think it can be useful for your final objective which is to migrate a large number of modules.

       

      El lun, 18 sept 2023, 9:37, Jan Suhr | Nitrokey <notifications@odoo-community.org> escribió:

      Hi!

      I wrote a simple tool which helps me keeping an overview of module

      upgrades during ongoing upgrade projects, especially for a large amount

      of modules. I hope someone finds it useful.

       

      https://github.com/Nitrokey/odoo-modules-migration

       

      Best regards

      Jan

      __________________________________

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

      -- 
Sébastien Alix
Business Solutions Odoo Developer

Camptocamp France SA
https://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

      -- 
Mit freundlichen Grüßen

Florian Kantelberg
Softwareentwickler

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel.: +49 (0) 4181 1350344
Fax: +49 (0) 4181 1350310

Email: florian.kantelberg@initos.com
Internet: https://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: DE 815580155
Steuer-Nr: 15/200/53247

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

      -- 
Sébastien Alix
Business Solutions Odoo Developer

Camptocamp France SA
https://www.camptocamp.com/
      by Sébastien Alix - 11:21 - 11 Oct 2023
    • Re: tool: Odoo Modules Migration

      Hello,

      interesting mail Sebastian. Most of it sounds familiar because we aim for the same goals with [1] (pypi odoo-analyse). Generally speaking odoo-analyse goes deeper than a simple lines of code analyses because there are plenty of cases reading the manifest isn't enough (e.g. Odoo 16.0 website has a hidden dependency towards iap because of an import). In the last days we extended it also to allow to estimate the modules which would be installed in a system without a database which should influence the initial topic of this mailing list [see 3] (@Jan). It resolves auto_install and dependencies starting from an initial module list.

      The tool is the foundation of [2] one of our long term projects and this is the reason why the current code is under our github and not pushed towards the OCA in the past. There would be no problem for a joint operation and we could push it to the OCA if we can stay maintainer of it. We (initOS) are also on the OCA days and would welcome support/ideas/feedback.

      We also already added complexity measurements in preparation to estimate a module and system complexity and furthermore a migration complexity. In the future we plan to offer a service to estimate module complexities in conjunction with the files from odoo-analyse (via a trained model) or for experts to estimate the complexities of modules to train a model even further basically as part of [2].

      Btw it lacks the repository management because this one is better handled externally (e.g. git-aggregator is a great tool). There are various build environments for Odoo and we learned that without the repository management we can easier analyse in different environments. Often enough there is already a CI or a development environment and reading the odoo.cfg is easy enough.

      Best Regards,

      Florian

      [1] https://github.com/initOS/odoo-analyse

      [2] https://www.odoo-code-search.com

      [3] `cat modules.txt | odoo_analyse -p odoo --modules - --analyse analyse.json --estimate-state --state-filter installed`

      where odoo is the folder under which ALL modules can be found

      Am 04.10.23 um 17:57 schrieb Sebastien Alix:

      Hi,

      I am the author of 'oca-port' so I'll try to answer your questions.

      These two tools aim two different purposes, but have few common points:

      - oca-port: it doesn't really know what is Odoo, this tool only plays with commits of git repositories to help the user to:
          1) migrate the git history of the module ('git format-patch' dance) and run pre-commit before inviting the user to follow the OCA migration guide. It'll also request GitHub API to find a open PR to invite the user to review it instead of creating a new one.
          2) for modules already migrated, it'll list the commits and related PRs that could be ported to fill the gap (fixes or features)
          3) a parsable output is available so we at Camptocamp are using it to scan OCA repositories and generate reports to estimate the work to achieve for migration projects (which modules are 100% ported, missing some fixes/features, have to be migrated and which ones having a PR to review)

      - odoo-module-migrator: from what I know (I do not use this tool yet) its job is to help you to migrate Odoo code to the target version (e.g. if a XML tag has been deprecated, it'll warn or update to the new format).

      Both tools could be used together, my idea would be that 'oca-port' leverages 'odoo-module-migrator' to automatically update the code in a migration process. From now, the user can call 'oca-port' then call 'odoo-module-migrator' manually (not tested), no big deal.

      I think the common points right now is that 'odoo-module-migrator' also does the 'git format-patch' step, and run pre-commit.


      FYI I also started an Odoo project that scans all kind of git repositories (OCA, Odoo, private repos) to collect modules metadata and consolidate all these data in one place, and it leverages oca-port to collect the migration data presented above. This tool aims to help functional & technical people with these kind of features:

      - get number of lines of code (Python/JS/XML/CSS) by module/repo/branch/organization or any filter you want
      - for maintainers, get a quick overview of the state of their modules
      - what are the most used OCA addons among all your Odoo projects
      - in term of lines of code of a customer project, how are they distributed among  Odoo, OCA and specifics
      - generate reports to ease the estimation of migration projects for a given migration path (e.g. 14.0 -> 16.0)
      - know all Python dependencies used in OCA to avoid versions conflicts or to improve security updates

      A lot of use cases could be addressed I guess. I'll probably make a presentation of this at OCA Days (need to finish some stuff, do some cleanup, host the code in a OCA repository, and address some questions regarding the hosting).

      Kind regards,


      Le 04/10/2023 à 09:26, Rafael Blasco a écrit :

      This is a really nice topic to have a doc/talk about for new contributor. Maybe for OCA DAys

       

      • Which is the use of both tool?
      • Why 2 and not just a single 1? (they should be different with different authors)
      • A "How to" for newcontribs are really useful to increase OCA

       

      It is not trivial and easy for everyone. The moment we take things for granted we lose contributors along the way.

       

      https://github.com/OCA/oca-port

      https://github.com/OCA/odoo-module-migrator

       

      Thank you!

      Regards

      Rafael

       

       

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

      Enviado el: martes, 26 de septiembre de 2023 10:03

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

      Asunto: Re: tool: Odoo Modules Migration

       

      Hello, you should check oca-port too

       

      https://github.com/OCA/oca-port

       

      Best regards

      --

      Alexandre Fayolle

      Senior Software Engineer

      Tel : +33 4 58 48 20 30

       

       

       

      De: Fernando La Chica <notifications@odoo-community.org>

      Enviado el: lunes, 18 de septiembre de 2023 23:08

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

      Asunto: Re: tool: Odoo Modules Migration

       

      Take a look at this tool

       

      https://github.com/OCA/odoo-module-migrator

       

      At first I thought it was the same tool. I understand that it is out of the scope of your tool but I think it can be useful for your final objective which is to migrate a large number of modules.

       

      El lun, 18 sept 2023, 9:37, Jan Suhr | Nitrokey <notifications@odoo-community.org> escribió:

      Hi!

      I wrote a simple tool which helps me keeping an overview of module

      upgrades during ongoing upgrade projects, especially for a large amount

      of modules. I hope someone finds it useful.

       

      https://github.com/Nitrokey/odoo-modules-migration

       

      Best regards

      Jan

      __________________________________

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

      -- 
Sébastien Alix
Business Solutions Odoo Developer

Camptocamp France SA
https://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

      -- 
Mit freundlichen Grüßen

Florian Kantelberg
Softwareentwickler

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel.: +49 (0) 4181 1350344
Fax: +49 (0) 4181 1350310

Email: florian.kantelberg@initos.com
Internet: https://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: DE 815580155
Steuer-Nr: 15/200/53247
      by Florian Kantelberg - 10:31 - 5 Oct 2023
    • Re: tool: Odoo Modules Migration

      Hello,

      interesting mail Sebastian. Most of it sounds familiar because we aim for the same goals with [1] (pypi odoo-analyse). Generally speaking odoo-analyse goes deeper than a simple lines of code analyses because there are plenty of cases reading the manifest isn't enough (e.g. Odoo 16.0 website has a hidden dependency towards iap because of an import). In the last days we extended it also to allow to estimate the modules which would be installed in a system without a database which should influence the initial topic of this mailing list [see 3] (@Jan). It resolves auto_install and dependencies starting from an initial module list.

      The tool is the foundation of [2] one of our long term projects and this is the reason why the current code is under our github and not pushed towards the OCA in the past. There would be no problem for a joint operation and we could push it to the OCA if we can stay maintainer of it. We (initOS) are also on the OCA days and would welcome support/ideas/feedback.

      We also already added complexity measurements in preparation to estimate a module and system complexity and furthermore a migration complexity. In the future we plan to offer a service to estimate module complexities in conjunction with the files from odoo-analyse (via a trained model) or for experts to estimate the complexities of modules to train a model even further basically as part of [2].

      Btw it lacks the repository management because this one is better handled externally (e.g. git-aggregator is a great tool). There are various build environments for Odoo and we learned that without the repository management we can easier analyse in different environments. Often enough there is already a CI or a development environment and reading the odoo.cfg is easy enough.

      Best Regards,

      Florian

      [1] https://github.com/initOS/odoo-analyse

      [2] https://www.odoo-code-search.com

      [3] `cat modules.txt | odoo_analyse -p odoo --modules - --analyse analyse.json --estimate-state --state-filter installed`

      where odoo is the folder under which ALL modules can be found

      Am 04.10.23 um 17:57 schrieb Sebastien Alix:

      Hi,

      I am the author of 'oca-port' so I'll try to answer your questions.

      These two tools aim two different purposes, but have few common points:

      - oca-port: it doesn't really know what is Odoo, this tool only plays with commits of git repositories to help the user to:
          1) migrate the git history of the module ('git format-patch' dance) and run pre-commit before inviting the user to follow the OCA migration guide. It'll also request GitHub API to find a open PR to invite the user to review it instead of creating a new one.
          2) for modules already migrated, it'll list the commits and related PRs that could be ported to fill the gap (fixes or features)
          3) a parsable output is available so we at Camptocamp are using it to scan OCA repositories and generate reports to estimate the work to achieve for migration projects (which modules are 100% ported, missing some fixes/features, have to be migrated and which ones having a PR to review)

      - odoo-module-migrator: from what I know (I do not use this tool yet) its job is to help you to migrate Odoo code to the target version (e.g. if a XML tag has been deprecated, it'll warn or update to the new format).

      Both tools could be used together, my idea would be that 'oca-port' leverages 'odoo-module-migrator' to automatically update the code in a migration process. From now, the user can call 'oca-port' then call 'odoo-module-migrator' manually (not tested), no big deal.

      I think the common points right now is that 'odoo-module-migrator' also does the 'git format-patch' step, and run pre-commit.


      FYI I also started an Odoo project that scans all kind of git repositories (OCA, Odoo, private repos) to collect modules metadata and consolidate all these data in one place, and it leverages oca-port to collect the migration data presented above. This tool aims to help functional & technical people with these kind of features:

      - get number of lines of code (Python/JS/XML/CSS) by module/repo/branch/organization or any filter you want
      - for maintainers, get a quick overview of the state of their modules
      - what are the most used OCA addons among all your Odoo projects
      - in term of lines of code of a customer project, how are they distributed among  Odoo, OCA and specifics
      - generate reports to ease the estimation of migration projects for a given migration path (e.g. 14.0 -> 16.0)
      - know all Python dependencies used in OCA to avoid versions conflicts or to improve security updates

      A lot of use cases could be addressed I guess. I'll probably make a presentation of this at OCA Days (need to finish some stuff, do some cleanup, host the code in a OCA repository, and address some questions regarding the hosting).

      Kind regards,


      Le 04/10/2023 à 09:26, Rafael Blasco a écrit :

      This is a really nice topic to have a doc/talk about for new contributor. Maybe for OCA DAys

       

      • Which is the use of both tool?
      • Why 2 and not just a single 1? (they should be different with different authors)
      • A "How to" for newcontribs are really useful to increase OCA

       

      It is not trivial and easy for everyone. The moment we take things for granted we lose contributors along the way.

       

      https://github.com/OCA/oca-port

      https://github.com/OCA/odoo-module-migrator

       

      Thank you!

      Regards

      Rafael

       

       

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

      Enviado el: martes, 26 de septiembre de 2023 10:03

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

      Asunto: Re: tool: Odoo Modules Migration

       

      Hello, you should check oca-port too

       

      https://github.com/OCA/oca-port

       

      Best regards

      --

      Alexandre Fayolle

      Senior Software Engineer

      Tel : +33 4 58 48 20 30

       

       

       

      De: Fernando La Chica <notifications@odoo-community.org>

      Enviado el: lunes, 18 de septiembre de 2023 23:08

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

      Asunto: Re: tool: Odoo Modules Migration

       

      Take a look at this tool

       

      https://github.com/OCA/odoo-module-migrator

       

      At first I thought it was the same tool. I understand that it is out of the scope of your tool but I think it can be useful for your final objective which is to migrate a large number of modules.

       

      El lun, 18 sept 2023, 9:37, Jan Suhr | Nitrokey <notifications@odoo-community.org> escribió:

      Hi!

      I wrote a simple tool which helps me keeping an overview of module

      upgrades during ongoing upgrade projects, especially for a large amount

      of modules. I hope someone finds it useful.

       

      https://github.com/Nitrokey/odoo-modules-migration

       

      Best regards

      Jan

      __________________________________

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

      -- 
Sébastien Alix
Business Solutions Odoo Developer

Camptocamp France SA
https://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

      -- 
Mit freundlichen Grüßen

Florian Kantelberg
Softwareentwickler

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel.: +49 (0) 4181 1350344
Fax: +49 (0) 4181 1350310

Email: florian.kantelberg@initos.com
Internet: https://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: DE 815580155
Steuer-Nr: 15/200/53247
      by Florian Kantelberg - 10:26 - 5 Oct 2023
    • Re: tool: Odoo Modules Migration


      On Wed, Oct 4, 2023 at 5:57 PM Sebastien Alix <notifications@odoo-community.org> wrote:

      FYI I also started an Odoo project that scans all kind of git repositories (OCA, Odoo, private repos) to collect modules metadata and consolidate all these data in one place, and it leverages oca-port to collect the migration data presented above. This tool aims to help functional & technical people with these kind of features:

      - get number of lines of code (Python/JS/XML/CSS) by module/repo/branch/organization or any filter you want
      - for maintainers, get a quick overview of the state of their modules
      - what are the most used OCA addons among all your Odoo projects
      - in term of lines of code of a customer project, how are they distributed among  Odoo, OCA and specifics
      - generate reports to ease the estimation of migration projects for a given migration path (e.g. 14.0 -> 16.0)
      - know all Python dependencies used in OCA to avoid versions conflicts or to improve security updates

      A lot of use cases could be addressed I guess. I'll probably make a presentation of this at OCA Days (need to finish some stuff, do some cleanup, host the code in a OCA repository, and address some questions regarding the hosting).


      That's so cool! I can't wait to see it!
      Thanks a lot, Sebastien!

      --
      by Alex Comba. - 09:22 - 5 Oct 2023
    • Re: tool: Odoo Modules Migration
      Hi Sebastien,

      > I also started an Odoo project that scans all kind of git repositories (OCA, Odoo, private repos)

      I also did :) maybe we could share some efforts as it is hard to maintain ... https://oca-cm-15.komit.link/

      You can send me an email if you want jc@komit-consulting.com and I could show you.

      Regards,

      Jean-Charles


      On Wed, Oct 4, 2023 at 10:57 PM Sebastien Alix <notifications@odoo-community.org> wrote:

      Hi,

      I am the author of 'oca-port' so I'll try to answer your questions.

      These two tools aim two different purposes, but have few common points:

      - oca-port: it doesn't really know what is Odoo, this tool only plays with commits of git repositories to help the user to:
          1) migrate the git history of the module ('git format-patch' dance) and run pre-commit before inviting the user to follow the OCA migration guide. It'll also request GitHub API to find a open PR to invite the user to review it instead of creating a new one.
          2) for modules already migrated, it'll list the commits and related PRs that could be ported to fill the gap (fixes or features)
          3) a parsable output is available so we at Camptocamp are using it to scan OCA repositories and generate reports to estimate the work to achieve for migration projects (which modules are 100% ported, missing some fixes/features, have to be migrated and which ones having a PR to review)

      - odoo-module-migrator: from what I know (I do not use this tool yet) its job is to help you to migrate Odoo code to the target version (e.g. if a XML tag has been deprecated, it'll warn or update to the new format).

      Both tools could be used together, my idea would be that 'oca-port' leverages 'odoo-module-migrator' to automatically update the code in a migration process. From now, the user can call 'oca-port' then call 'odoo-module-migrator' manually (not tested), no big deal.

      I think the common points right now is that 'odoo-module-migrator' also does the 'git format-patch' step, and run pre-commit.


      FYI I also started an Odoo project that scans all kind of git repositories (OCA, Odoo, private repos) to collect modules metadata and consolidate all these data in one place, and it leverages oca-port to collect the migration data presented above. This tool aims to help functional & technical people with these kind of features:

      - get number of lines of code (Python/JS/XML/CSS) by module/repo/branch/organization or any filter you want
      - for maintainers, get a quick overview of the state of their modules
      - what are the most used OCA addons among all your Odoo projects
      - in term of lines of code of a customer project, how are they distributed among  Odoo, OCA and specifics
      - generate reports to ease the estimation of migration projects for a given migration path (e.g. 14.0 -> 16.0)
      - know all Python dependencies used in OCA to avoid versions conflicts or to improve security updates

      A lot of use cases could be addressed I guess. I'll probably make a presentation of this at OCA Days (need to finish some stuff, do some cleanup, host the code in a OCA repository, and address some questions regarding the hosting).

      Kind regards,


      Le 04/10/2023 à 09:26, Rafael Blasco a écrit :

      This is a really nice topic to have a doc/talk about for new contributor. Maybe for OCA DAys

       

      • Which is the use of both tool?
      • Why 2 and not just a single 1? (they should be different with different authors)
      • A "How to" for newcontribs are really useful to increase OCA

       

      It is not trivial and easy for everyone. The moment we take things for granted we lose contributors along the way.

       

      https://github.com/OCA/oca-port

      https://github.com/OCA/odoo-module-migrator

       

      Thank you!

      Regards

      Rafael

       

       

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

      Enviado el: martes, 26 de septiembre de 2023 10:03

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

      Asunto: Re: tool: Odoo Modules Migration

       

      Hello, you should check oca-port too

       

      https://github.com/OCA/oca-port

       

      Best regards

      --

      Alexandre Fayolle

      Senior Software Engineer

      Tel : +33 4 58 48 20 30

       

       

       

      De: Fernando La Chica <notifications@odoo-community.org>

      Enviado el: lunes, 18 de septiembre de 2023 23:08

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

      Asunto: Re: tool: Odoo Modules Migration

       

      Take a look at this tool

       

      https://github.com/OCA/odoo-module-migrator

       

      At first I thought it was the same tool. I understand that it is out of the scope of your tool but I think it can be useful for your final objective which is to migrate a large number of modules.

       

      El lun, 18 sept 2023, 9:37, Jan Suhr | Nitrokey <notifications@odoo-community.org> escribió:

      Hi!

      I wrote a simple tool which helps me keeping an overview of module

      upgrades during ongoing upgrade projects, especially for a large amount

      of modules. I hope someone finds it useful.

       

      https://github.com/Nitrokey/odoo-modules-migration

       

      Best regards

      Jan

      __________________________________

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

      -- 
Sébastien Alix
Business Solutions Odoo Developer

Camptocamp France SA
https://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 Jean-Charles Drubay - 04:41 - 5 Oct 2023

  • Auto unsubscribe
    Hi,

    Is there something done on OCA side that has triggered an unsubscribe action to this mailing list as I've just received a 'Confirm unsubscription to Contributors' email?

    Thanks to the Board for the answer (as some colleagues received it too).

    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel. - 03:17 - 15 Sep 2023

    4 replies 4 replies

    • Re: Auto unsubscribe
      Probably some odoo flaw. Just ignore it.

      On Sat, 16 Sept 2023, 1:53 am Radovan Skolnik, <notifications@odoo-community.org> wrote:
      +1

On piatok 15. septembra 2023 15:17:16 CEST Roussel, Denis wrote:


> Hi,


> 


> 


> Is there something done on OCA side that has triggered an unsubscribe action


> to this mailing list as I've just received a 'Confirm unsubscription to


> Contributors' email?


> 


> 


> Thanks to the Board for the answer (as some colleagues received it too).


> 


> 


> 


> --


> 


> 


> Denis Roussel


> Software Engineer


> T    : +32 2 888 31 49


> M : +32 472 22 00 57


> 


> 


> 


> 


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


> 


> Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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

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

      by Graeme Gellatly - 06:51 - 16 Sep 2023
    • Re: Auto unsubscribe 
      +1

On piatok 15. septembra 2023 15:17:16 CEST Roussel, Denis wrote:

> Hi,

> 

> 

> Is there something done on OCA side that has triggered an unsubscribe action

> to this mailing list as I've just received a 'Confirm unsubscription to

> Contributors' email?

> 

> 

> Thanks to the Board for the answer (as some colleagues received it too).

> 

> 

> 

> --

> 

> 

> Denis Roussel

> Software Engineer

> T    : +32 2 888 31 49

> M : +32 472 22 00 57

> 

> 

> 

> 

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

> 

> Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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 Radovan Skolnik - 03:51 - 15 Sep 2023
    • Re: Auto unsubscribe
      Hi Roussel,
      Yes I confirm, I received it as well.
      Thanks,

      Le ven. 15 sept. 2023 à 15:17, Roussel, Denis <notifications@odoo-community.org> a écrit :
      Hi,

      Is there something done on OCA side that has triggered an unsubscribe action to this mailing list as I've just received a 'Confirm unsubscription to Contributors' email?

      Thanks to the Board for the answer (as some colleagues received it too).

      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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



      --
      ---
      [ Youness @ MAAFI ]

      Tel:       +49.176.368.378.62
      Email: youness.maafi@gmail.com
      by Youness Maafi - 03:26 - 15 Sep 2023
    • Re: Auto unsubscribe
      +1
      Hi,

      Is there something done on OCA side that has triggered an unsubscribe action to this mailing list as I've just received a 'Confirm unsubscription to Contributors' email?

      Thanks to the Board for the answer (as some colleagues received it too).

      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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


      -- 
Très cordialement

Maurice MORETTI

_________________________________________________________________________
TeMPO CONSULTING 20, avenue de la Paix 67000 Strasbourg FRANCE
			
Web   : http://www.tempo-consulting.fr
email : mm@tempo-consulting.fr	
			
Tel      : 33 (0)3 88 56 82 10				
Mobile   : 33 (0)6 08 61 85 02
      by Maurice MORETTI - 03:26 - 15 Sep 2023
  • Confirm unsubscription to Contributors
    Your Channel
    Contributors     		Odoo Community Association (OCA)
    Hello,

    You have requested to be unsubscribed to the mailing list Contributors.

    To confirm, please visit the following link: https://odoo-community.org/groups/unsubscribe/15/25929/62a4e531b032a4a5754ff590ea1b3b1e.

    If this was a mistake or you did not requested this action, please ignore this message.


    Odoo Community Association (OCA)
    info@odoo-community.org | http://odoo-community.org
    Powered by Odoo

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

    by info@odoo-community.org - 03:06 - 15 Sep 2023

    1 attachments 1 attachments

    attachment

    2 replies 2 replies

  • OCA Days Talk Proposals - submissions close Friday 15th September
    Hi everyone,

    As you know OCA Days 2023 is coming up on the 6 + 7 November.
    We are very much looking forward to seeing those who can make it in Liège.

    You can still register here. 

    I wanted to remind people that the last day for talk submissions is today - Friday 15th September. Share your ideas here.

    We will accept a broad range of proposals:

    • presentations on different modules/ module updates
    • community project
    • trainings/tutorials
    • case studies
    • implementations
    • great discussion topics
    As long as the presentation is interesting and potentially useful to the audience, it will be considered for inclusion in the programme.

    When submitting a talk please put at the end of the talk title if it is a functional or technical talk.

    New for 2023 - Functional track.

    This year, we'll also host a functional track as well as our standard track. We would like to promote some topics and encourage experts to propose their talks to help functional  participants feel more integrated into the OCA.

    In the functional room we would like to give the opportunity for good discussions too - one person proposes a topic, gives his understanding and then it's more of a practice and ideas exchange moment.

    When submitting your functional talk please as mentioned above, let us know it is functional and also whether it is to be a presentation, training or discussion.

    Here are some examples of topics that will certainly interest functional profiles:

    • How to contribute to the OCA as a functional?

    • How to navigate Github as a functional?

    • How to use Weblate and why it is useful?

    • How to use the runboat and test every OCA module easily?

    • Presentation of must-have OCA modules from a functional perspective

    • Any other topic that you think could help functional get more engaged into the OCA community

    If you feel up to it, whether you have a technical or functional profile, please help us make the OCA Days interesting for functional roles! We'll have 30min, 45 min and  60min slots available.

    We can't wait to see what our community has to share for 2023!

    Have a great weekend everyone.
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 06:40 - 15 Sep 2023
  • tool: Odoo Modules Migration 
    Hi!
I wrote a simple tool which helps me keeping an overview of module 
upgrades during ongoing upgrade projects, especially for a large amount 
of modules. I hope someone finds it useful.

https://github.com/Nitrokey/odoo-modules-migration

Best regards
Jan
    by Jan Suhr - 06:05 - 13 Sep 2023
  • A (hope not stupid) question about wire transfer payment transactions 
    Hello,

hope this will not be a stupid question - I searched through all the Odoo sources, all OCA modules but couldn't find any answer. The scenario is really simple: Wire Transfer (payment_custom in 16.0, payment_transfer in previous versions) is selected as payment provider in e-shop (website_sale). Payment transcation (payment.transaction) object is created in Pending state. The question is: is there anything anywhere that would change its state to Confirmed (done)? I would assume imported bank statements could but I cannot see that anywhere (was mainly looking for _set_done() method calls but tried other means of search as well). Would be greateful if somebody shed some light on this for me.

Thank you very much. Best regards

	Radovan Skolnik
    by Radovan Skolnik - 09:46 - 13 Sep 2023

    5 replies 5 replies

  • 100 % coverage not enough? 
    Hi all,


I submitted a PR with 100% code coverage to the account-invoicing repo.


However the branch is red because 100% is apparently not enough. 
Supposedly the PR would decrease the overall coverage percentage. How??


See here: https://github.com/OCA/account-invoicing/pull/1544


I think any PR that gets code coverage > 90% (and that does not decrease 
coverage of an existing module), should get a branch green, but 
certainly 100%.


Kind regards, Ronald
    by "Ronald Portier" <rportier@therp.nl> - 08:56 - 8 Sep 2023

    5 replies 5 replies

    • Re: 100 % coverage not enough?
      El lun, 11-09-2023 a las 08:41 +0000, Ronald Portier escribió:
      The decrease must be an artifact of comparing a branch based on an older version of the main branch, that had less coverage overall, with the current version of the main branch

      Maybe coverage can be compared to the latest parent commit of the oldest PR commit? That way, we could be sure if it's really increasing.
      by Jairo Llopis - 08:40 - 13 Sep 2023
    • Re: 100 % coverage not enough?

      Hi,


      Rebasing the branch, as suggegested by Jairo solved the problem. So let us keep that in mind with future occurences of this issue.


      Denis, I understand why you do not want to remove the check, but I do not see how a PR that only concerns one module, could influence other modules. The decrease must be an artifact of comparing a branch based on an older version of the main branch, that had less coverage overall, with the current version of the main branch. However merging such a PR will not undo the changes that have occurred in the main branch since creating the PR/feature branch. So the proper measure on whether a PR increases or decreases overall coverage would be to compare the coverage percentage in only the patch (the changed code) with the overall coverage of the project (the main branch).


      Kind regards, Ronald


      Op 11-09-2023 om 10:22 schreef Roussel, Denis:
      The answer is in the details link.

      @jairo I don't agree about removing that check.

      The 'patch' coverage report concerns exclusively the code you introduce with your PR.
      The 'project' coverage report concerns the already existing code outside your PR. So, a decrease there means that your PR influences other modules (not executing a super in an inherited method, ...)

      Even if coverage is not mandatory in OCA, it gives indicators on technical tests quality.

      My two cents

      On Mon, Sep 11, 2023 at 10:11 AM jairo <notifications@odoo-community.org> wrote:
      El vie, 08-09-2023 a las 18:57 +0000, Ronald Portier escribió:
      Supposedly the PR would decrease the overall coverage percentage. How??

      The 1st thing you need to know is that hose checks are not required.

      Now, this is how your PR looks:


      That ✅ is telling the reviewer that the PR has a 100% of coverage. That's the important part.

      The ❌ however is the weirdo. Sometimes it happens, so I systematically ignore that check. IMHO it could be removed. My guess is that the base branch evolved and got more coverage, and that if you rebased it would always increase. But maybe it's just a bug somewhere.

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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 "Ronald Portier" <rportier@therp.nl> - 10:40 - 11 Sep 2023
    • Re: 100 % coverage not enough?
      The answer is in the details link.

      @jairo I don't agree about removing that check.

      The 'patch' coverage report concerns exclusively the code you introduce with your PR.
      The 'project' coverage report concerns the already existing code outside your PR. So, a decrease there means that your PR influences other modules (not executing a super in an inherited method, ...)

      Even if coverage is not mandatory in OCA, it gives indicators on technical tests quality.

      My two cents

      On Mon, Sep 11, 2023 at 10:11 AM jairo <notifications@odoo-community.org> wrote:
      El vie, 08-09-2023 a las 18:57 +0000, Ronald Portier escribió:
      Supposedly the PR would decrease the overall coverage percentage. How??

      The 1st thing you need to know is that hose checks are not required.

      Now, this is how your PR looks:


      That ✅ is telling the reviewer that the PR has a 100% of coverage. That's the important part.

      The ❌ however is the weirdo. Sometimes it happens, so I systematically ignore that check. IMHO it could be removed. My guess is that the base branch evolved and got more coverage, and that if you rebased it would always increase. But maybe it's just a bug somewhere.

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg
      by Denis Roussel. - 10:21 - 11 Sep 2023
    • Re: 100 % coverage not enough?
      El vie, 08-09-2023 a las 18:57 +0000, Ronald Portier escribió:
      Supposedly the PR would decrease the overall coverage percentage. How??

      The 1st thing you need to know is that hose checks are not required.

      Now, this is how your PR looks:


      That ✅ is telling the reviewer that the PR has a 100% of coverage. That's the important part.

      The ❌ however is the weirdo. Sometimes it happens, so I systematically ignore that check. IMHO it could be removed. My guess is that the base branch evolved and got more coverage, and that if you rebased it would always increase. But maybe it's just a bug somewhere.
      by Jairo Llopis - 10:11 - 11 Sep 2023

      1 attachments 1 attachments

      Imagen-VDE3A2.png
    • Re: 100 % coverage not enough?
      Hi Ronald,

      I replied on the PR.

      Bests

      On Fri, Sep 8, 2023 at 8:57 PM Ronald Portier <notifications@odoo-community.org> wrote:
      Hi all,


I submitted a PR with 100% code coverage to the account-invoicing repo.


However the branch is red because 100% is apparently not enough. 
Supposedly the PR would decrease the overall coverage percentage. How??


See here: https://github.com/OCA/account-invoicing/pull/1544


I think any PR that gets code coverage > 90% (and that does not decrease 
coverage of an existing module), should get a branch green, but 
certainly 100%.


Kind regards, Ronald

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi. - 07:55 - 11 Sep 2023
  • Login Case Sensative
    Howdy y'all,

    I wanted this issue to get some more attention as it can effect many people using Odoo:


    Feel free to reply in the PR or directly here.

    Take care,
    Jason
    jason@companionedu.com
    by companiontechnology - 05:15 - 7 Sep 2023