Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Re: Weblate 5.10
    Thank you!

    On 01/03/2025 11:18, Stéphane Bidoul wrote:
    Hi everyone,

    translation.odoo-community.org has been upgraded to Weblate 5.10.

    Let me know of any issue.

    Best regards,

    -Stéphane

    --
    Stéphane Bidoul
    http://acsone.eu/

    _______________________________________________
    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

    [Logo OpenSourceIntegrators.com]

    by Daniel Reis - 01:36 - 1 Mar 2025
  • Re: Weblate 5.10
    Great, thanks. On a first glance, everything seems very similar and I don't find issues.

    Regards.
    by Pedro M. Baeza - 12:26 - 1 Mar 2025
  • Weblate 5.10
    Hi everyone,

    translation.odoo-community.org has been upgraded to Weblate 5.10.

    Let me know of any issue.

    Best regards,

    -Stéphane

    --
    Stéphane Bidoul
    http://acsone.eu/
    by Stéphane Bidoul - 12:16 - 1 Mar 2025
  • Add me in the telegram channel
    by "Shaheedullah khan" <shaheedullahkhan7@gmail.com> - 11:31 - 1 Mar 2025
  • Re: Tests failure when invoicing is involved after a change in Odoo upstream
    I have hit this issue in one of my projects where I run all tests post-install.

    Instead of changing all my tests, I chose to install l10n_generic_coa in CI, which was an easy solution in my specific situation.
    Maybe this can help others hitting the same problem.

    Best regards,

    -Stéphane


    On Wed, Feb 26, 2025 at 4:53 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
    Stefan and Denis, the reason for the Odoo patch may be legit, and it is. The problem is that it comes too late for the lifecycle of this version IMO, and more having in version 17 integrated the generic CoA into account for better practices. Anyway, this is just undisclosing a problem that has been hidden in the design of our OCA tests, them not being deterministic and really unit tests, as they are relying on previous state of data for being successful:

    - The company used is the one populated by default instead of using a full set of data including the company. This may be reasonable for execution times, and that's why the decision to just fix this condition installing an existing CoA instead of populating on each test a new company.
    - There's no guarantee a CoA is loaded at the time of performing the tests, but creating an invoice requires it. That's why the post-install thing (and it's also a requirement if inheriting AccountTestInvoicingCommon).


    Inheriting from AccountTestInvoicingCommon, as explained in the commit message I linked in my first message, it's not improving the thing (at least in 16, in 17 it's more ironized), because it still requires `l10n_generic_coa` installed (and installed before the execution of this test), and its setup is very heavy, creating 2 companies (even if you only require one), so this would increase the test execution times a lot in the best case, or skipped without you really noticing in the worst (when generic CoA is not available).

    The added code is NOT boilerplate. It's legit code for making deterministic tests, the same as you may remove currency rates for having a deterministic environment. And it's totally harmless if you don't need it, because starting with, it's in test code, not in business code, and if you keep the previous status quo, the if it's not executed, so it doesn't affect any previous condition. This can only uncover other hidden defects on the modules being executed in post-install, and this is being patched at the same time.

    Replying to other threads answers, I don't think this will reverted, as AFAIK Odoo.sh is auto-installing the modules that hides the problem, and not installing any localization module, but I'm not expert of that platform, so I may be wrong.

    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 - 07:36 - 28 Feb 2025
  • Translations

    Hey OCA,

    I have a kind of „basic“ question I guess, regarding the handling of mail templates and its translations.

     

    If I need to overwrite email templates that are used „hard-coded“ in Odoo core create/write methods, what is the best way to do so.

     

    - 1st: Set the email template noupdate flag to false using the write function, then overwrite the template with your own record and set the noupdate flag back to true.

     

    The new template is now correct using create method of Odoo core. But here I have the problem that I cannot process the translations for the template correctly as they are referred to the Odoo core module. 

     

    - 2nd: Create „my module“-specific mail templates and load the records on module installation in addition to the original Odoo mail templates. This makes things easier concerning the translation po files.

     

    The Problem: as the original core code is using the hard-coded mail templates, I need to rebuild the whole logic from Odoo core in create and writes method in my module and include my adaptions.

     

     

    So in general… what is the better approach… or maybe a totally different one?

     

    Is it possible to override the Core module translations properly when a template is “replaced” by custom module?

     

    All the best

    Nils

    by Nils Coenen - 08:50 - 28 Feb 2025
  • Re: Tests failure when invoicing is involved after a change in Odoo upstream
    Stefan and Denis, the reason for the Odoo patch may be legit, and it is. The problem is that it comes too late for the lifecycle of this version IMO, and more having in version 17 integrated the generic CoA into account for better practices. Anyway, this is just undisclosing a problem that has been hidden in the design of our OCA tests, them not being deterministic and really unit tests, as they are relying on previous state of data for being successful:

    - The company used is the one populated by default instead of using a full set of data including the company. This may be reasonable for execution times, and that's why the decision to just fix this condition installing an existing CoA instead of populating on each test a new company.
    - There's no guarantee a CoA is loaded at the time of performing the tests, but creating an invoice requires it. That's why the post-install thing (and it's also a requirement if inheriting AccountTestInvoicingCommon).


    Inheriting from AccountTestInvoicingCommon, as explained in the commit message I linked in my first message, it's not improving the thing (at least in 16, in 17 it's more ironized), because it still requires `l10n_generic_coa` installed (and installed before the execution of this test), and its setup is very heavy, creating 2 companies (even if you only require one), so this would increase the test execution times a lot in the best case, or skipped without you really noticing in the worst (when generic CoA is not available).

    The added code is NOT boilerplate. It's legit code for making deterministic tests, the same as you may remove currency rates for having a deterministic environment. And it's totally harmless if you don't need it, because starting with, it's in test code, not in business code, and if you keep the previous status quo, the if it's not executed, so it doesn't affect any previous condition. This can only uncover other hidden defects on the modules being executed in post-install, and this is being patched at the same time.

    Replying to other threads answers, I don't think this will reverted, as AFAIK Odoo.sh is auto-installing the modules that hides the problem, and not installing any localization module, but I'm not expert of that platform, so I may be wrong.

    Regards.
    by Pedro M. Baeza - 04:52 - 26 Feb 2025
  • Re: Tests failure when invoicing is involved after a change in Odoo upstream
    Thanks Pedro for pointing that out.

    But as Stefan said, the changes you propose should be applied in particular modules that do pull particular localisation, not every.

    As said also, a lead could be using AccountTestInvoicingCommon.

    Moreover, I think proposing a hook in Odoo's tests should be great to lower the code we need to introduce in our modules, or... What do you think?

    Thanks

    Le mer. 26 févr. 2025, 11:27, Stefan Rijnhart <notifications@odoo-community.org> a écrit :
    Yes, but the reason given by the Odoo devs for this change (https://github.com/odoo/odoo/pull/194799) is that CI can break on other CoAs than the generic one. That implies that it is considered bad practise to encourage it, and maybe we should not be doing this in (potentially, a lot of) OCA modules. Maybe using AccountTestInvoicingCommon is still the best solution?

    Like you say, OCA CI should mostly not be affected because l10n_generic_coa is still installed automatically if you don't depend on a localized chart. Do you really *need* to test these modules on databases with l10n_es? Maybe you can enforce the installation of it on the main company with an extra step in your CI.

    On 25-02-2025 15:42, Pedro M. Baeza wrote:
    I write to inform you that Odoo has performed a change in "stable" 16.0 in this commit:


    that is affecting CIs, specially on those integration ones that OCA implementers perform combining all the modules of a specific instance.

    This change avoids the auto-install of one CoA on the existing demo main company, as it doesn't comply with a country CoA unless you have l10n_us installed. Some tests inheriting from  AccountTestInvoicingCommon won't fail if l10n_generic_coa is installed, but it's also a requirement that can't always be fulfilled.

    The impact of this is huge across OCA, as basically every test creating an invoice is affected. OCA CI may not be red, but use it in other place and you may be doomed.


    Thus, from Tecnativa, we have started a massive pull request campaign fixing most of the common modules with this problem.

    The strategy has been to force a load of the generic CoA or the first existing one into the main company if starting the test, it doesn't have any. Check the minimum example at:


    If you are inheriting from AccountTestInvoicingCommon, the strategy should be different. By default, you won't have a red CI, but the tests are skipped, which is also undesirable. Thus, you have to do the work before calling super. Check an example here:


    v17 is not affected for now. Let's hope it continues this way...

    Regards.

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



    -- 
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

    by Denis Roussel - 04:21 - 26 Feb 2025
  • Re: Tests failure when invoicing is involved after a change in Odoo upstream
    Yes, but the reason given by the Odoo devs for this change (https://github.com/odoo/odoo/pull/194799) is that CI can break on other CoAs than the generic one. That implies that it is considered bad practise to encourage it, and maybe we should not be doing this in (potentially, a lot of) OCA modules. Maybe using AccountTestInvoicingCommon is still the best solution?

    Like you say, OCA CI should mostly not be affected because l10n_generic_coa is still installed automatically if you don't depend on a localized chart. Do you really *need* to test these modules on databases with l10n_es? Maybe you can enforce the installation of it on the main company with an extra step in your CI.

    On 25-02-2025 15:42, Pedro M. Baeza wrote:
    I write to inform you that Odoo has performed a change in "stable" 16.0 in this commit:


    that is affecting CIs, specially on those integration ones that OCA implementers perform combining all the modules of a specific instance.

    This change avoids the auto-install of one CoA on the existing demo main company, as it doesn't comply with a country CoA unless you have l10n_us installed. Some tests inheriting from  AccountTestInvoicingCommon won't fail if l10n_generic_coa is installed, but it's also a requirement that can't always be fulfilled.

    The impact of this is huge across OCA, as basically every test creating an invoice is affected. OCA CI may not be red, but use it in other place and you may be doomed.


    Thus, from Tecnativa, we have started a massive pull request campaign fixing most of the common modules with this problem.

    The strategy has been to force a load of the generic CoA or the first existing one into the main company if starting the test, it doesn't have any. Check the minimum example at:


    If you are inheriting from AccountTestInvoicingCommon, the strategy should be different. By default, you won't have a red CI, but the tests are skipped, which is also undesirable. Thus, you have to do the work before calling super. Check an example here:


    v17 is not affected for now. Let's hope it continues this way...

    Regards.

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



    -- 
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 - 11:26 - 26 Feb 2025
  • Re: Tests failure when invoicing is involved after a change in Odoo upstream
    OCA doesn't exist for Odoo :)
    Many thanks for the good work!
    Sergio Corato


    Il giorno mar 25 feb 2025 alle ore 15:42 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:
    I write to inform you that Odoo has performed a change in "stable" 16.0 in this commit:


    that is affecting CIs, specially on those integration ones that OCA implementers perform combining all the modules of a specific instance.

    This change avoids the auto-install of one CoA on the existing demo main company, as it doesn't comply with a country CoA unless you have l10n_us installed. Some tests inheriting from  AccountTestInvoicingCommon won't fail if l10n_generic_coa is installed, but it's also a requirement that can't always be fulfilled.

    The impact of this is huge across OCA, as basically every test creating an invoice is affected. OCA CI may not be red, but use it in other place and you may be doomed.


    Thus, from Tecnativa, we have started a massive pull request campaign fixing most of the common modules with this problem.

    The strategy has been to force a load of the generic CoA or the first existing one into the main company if starting the test, it doesn't have any. Check the minimum example at:


    If you are inheriting from AccountTestInvoicingCommon, the strategy should be different. By default, you won't have a red CI, but the tests are skipped, which is also undesirable. Thus, you have to do the work before calling super. Check an example here:


    v17 is not affected for now. Let's hope it continues this way...

    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 Sergio Corato - 05:16 - 25 Feb 2025
  • Issue with ir.actions.server in Coverage Report – Curious About Others' Experience

    Dear OCA Community,

    I am using https://github.com/oca/oca-ci to run automated test cases in my GitLab pipeline, and I encountered a strange issue today.

    In one of the modules in my current repository, I am creating a Server Action (ir.actions.server) and executing it via the run method. However, during test execution, coverage.py mistakenly treated ir.actions.server as a file (might be because it is using safe_eval) and attempted to include it in the .coverage report. This resulted in the following error while generating coverage report:

    No source for code: '/builds/GIT_REPO/ir.actions.server(576,)'.

    I was able to resolve this by adding a .coveragerc file with the following configuration:

    [run]
    omit =
        *ir.actions.server*

    While this fix works, I am curious to know if others have encountered a similar issue, how it has been handled in other setups, and whether my solution is the proper way to address it.

    Looking forward to insights!

    BizzAppDev
    Erudite of Business Solutions
    With Kind Regards,
    Ruchir Y Shukla
    Founder & CTO
    BizzAppDev Systems Pvt. Ltd.
    M:
    +91 98 980 78748
    W:
    E:
    ruchir@bizzappdev.com

    Book time to meet with me
    by Ruchir Shukla. - 04:56 - 25 Feb 2025

    2 attachments 2 attachments

    Outlook-dfrr03sc.png
    Outlook-tsvh2lgl.png
  • Tests failure when invoicing is involved after a change in Odoo upstream
    I write to inform you that Odoo has performed a change in "stable" 16.0 in this commit:


    that is affecting CIs, specially on those integration ones that OCA implementers perform combining all the modules of a specific instance.

    This change avoids the auto-install of one CoA on the existing demo main company, as it doesn't comply with a country CoA unless you have l10n_us installed. Some tests inheriting from  AccountTestInvoicingCommon won't fail if l10n_generic_coa is installed, but it's also a requirement that can't always be fulfilled.

    The impact of this is huge across OCA, as basically every test creating an invoice is affected. OCA CI may not be red, but use it in other place and you may be doomed.


    Thus, from Tecnativa, we have started a massive pull request campaign fixing most of the common modules with this problem.

    The strategy has been to force a load of the generic CoA or the first existing one into the main company if starting the test, it doesn't have any. Check the minimum example at:


    If you are inheriting from AccountTestInvoicingCommon, the strategy should be different. By default, you won't have a red CI, but the tests are skipped, which is also undesirable. Thus, you have to do the work before calling super. Check an example here:


    v17 is not affected for now. Let's hope it continues this way...

    Regards.
    by Pedro M. Baeza - 03:41 - 25 Feb 2025
  • Re: Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0
    Hello, 
            


    Am Mo., 24. Feb. 2025 um 17:22 Uhr schrieb Christian Zöllner <notifications@odoo-community.org>:
    Hi Thorsten,

    I don't think anything has changed in the search logic for the fiscal positions in regard of the found problem. But the fiscal position “Business partner EU (with VAT ID)” was only changed to “auto apply” about 1 year ago. This should not have affected running systems, as an update of the accounting app has no effect on the fiscal positions, as these are set to “no update”.

    I have investigated the change and i am OK with that change, however it should not affect the logic who a fiscal position is assigned to a german partner.
    As the sequence of the rule is higher as the    “Business partner EU (with VAT ID)” rule Odoo should assign in any case (VAT ID / No VatID in combination with country germany) to "Domestic partner" / "Geschäftspartner Inland".
    That's who it was done in the past.


     


    I would prefer to create another fiscal position “Domestic business partner (with VAT ID)” rather than changing the country group “European Union”, because the latter may be used in other processes in Odoo and Germany should therefore remain included.

    If you check the video you have seen that i duplicated the country group, however i would be fine with a duplication of “Business partner EU (with VAT ID)” leading to:
    “Business partner EU (with VAT ID)”
    “Business partner EU (without VAT ID)”

    both before 
    “Business partner EU (with VAT ID)”


     

    Thank you for sharing all those informations in this mailing list.



    Yesterday i have received answer from Odoo support.
    They will investigate it, so no final answer yet.

    Best regards
    Thorsten
     

    Best Regards
    Christian
    Intero Technologies GmbH

    Von: "Thorsten Vocks" <notifications@odoo-community.org>
    An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
    Gesendet: Freitag, 21. Februar 2025 17:38:15
    Betreff: Re: Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0

    Hallo Frederik,

    This revert

    https://github.com/odoo/odoo/commit/af3a24c010d3e7158c1324f36a1529c510d886a6

    and this original commit

    https://github.com/odoo/odoo/commit/bcaf8cb859dc2f7e975d180ba0fc49da20204557

    introduced and reverted the problematic code if i am not mistaken. I didn't review the code duely, but afais that the problematic code should only be in databases / data that have been created between

    24th of September 2024 and 25th of October 2024

    That means customers with versions of Odoo 16, 17 and 18 that either updated their code in that time frame or installed new databases should be affected. Others hopefully not!



    Unfortunately not.
    I could recapture that today on Odoo runbot v18.
    Last week on v16, v17 (current runbot versions).
    And all my other testing was also databases on odoo runbot.

    I guess the revert didn't fix the introduced problem.
    Honestly i am not 100% sure which exact commit introduced 
    the issue.

     
    Best regards
    Thorsten


    Best and thanks for circulating this

    Frederik

    Am 21.02.25 um 13:47 schrieb Thorsten Vocks:
    Hello,

    approx. 7 days ago we have detected a critical issue regarding the fiscal position assignation for setups with installed german localisation (l10n_de). Obviously all databases created / last updated approx. 20th October are affected.

    At first we thought version 18.0 is not affected but that was wrong.

    Here is the video with a manual fix of the fiscal positions:

    At Odoo SA we have a open bug report but no response so far:

    Issue Type: Critical Bug

    Module: Accounting / German Localization

    Odoo Versions: [16.0, 17.0]

    Also affected is [18.0]

    Impacted Environment:

    * Both
    * Not affected is 17.04., 18.0


    Summary:

    The fiscal position is being incorrectly assigned to partners in the German localization (German B2B partners with Vat-ID assigned). This leads to incorrect tax calculations and potential legal compliance issues for users relying on automated fiscal position determination.


    Steps to Reproduce:

    1. Configure the German localization module.
    2. Create a new partner with an address located in Germany.
    3. Assign a VAT ID to the partner.
    4. Create a sales order or invoice for the partner.
    5. Observe the fiscal position that gets assigned automatically (wrong).

    Expected Behavior:

    * The fiscal position should be assigned based on the VAT ID, address, and configured fiscal rules.
    * The correct tax rates and exemptions should be applied in accordance with German tax regulations.


    Observed Behavior:

    * The fiscal position is either not assigned correctly or does not reflect the expected tax rules.
    * Especially B2B partners receive an incorrect fiscal position, leading to incorrect tax calculations.
    * This can result in non-compliance with German tax regulations and incorrect tax reporting.


    Impact:

    * Financial discrepancies due to incorrect tax application.
    * Compliance risks with German tax authorities.
    * Increased manual corrections required by users.

    Suggested Fix:

    * Review and correct the fiscal position assignment logic in the German localization module.
    * Ensure that VAT IDs and partner addresses are properly considered when determining fiscal positions.
    * Implement additional validation checks to avoid incorrect fiscal position assignments.
    * I have proposed a quick fix solution in my video.

    Video:


    https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view


    Priority: 

    Critical

    Additional Notes:


    * This issue was observed in trainings for our customers.
    * All customers running on v16, v17, v18 in Odoo are effected (except they assign fixed fiscal positions to partners, which happens in some rare cases).
    * Affected users have reported increased manual workload due to incorrect assignments.
    * Maybe they have created wrong account moves. Due to audit_trail we cannot fix that easily.
    * We have to investigate this now on all customer databases (german companies).
    * We strongly recommend you to warn other german customers working on a v16, v17, v18 version.


    Thorsten Vocks

    openBIG.org
    Dipl. Kaufmann (FH)
    Porscheweg 4-6
    49661 Cloppenburg

    Phone: +49 4471 8409000
    Fax: +49 4471 84090009
    Mail: thorsten.vocks@openbig.org

                  

    _______________________________________________
    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

    _______________________________________________
    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 Thorsten Vocks - 01:07 - 25 Feb 2025
  • Rotor Live Visitor List

    Rotor Live 2025

    Greetings Exhibitor,

    Reaching out to confirm if you’re interested in the Rotor Live 2025 attendee list.

    The event will be held 08 - 09 Mar 2025 in Rennbahn Iffezheim, Iffezheim, Germany , and the list provides 4,576 registrant records with contact information, roles...


    Thanks & Regards
    Monda Byrd
    by monda.byrd@leadcritics.cloud - 08:41 - 25 Feb 2025
  • Re: Odoo Experience 2025 - OCA Zone
    Thanks for all the feedback everyone.

    I will go back to Odoo and see what the possibility is of moving stands around a bit and come back to you (though I am aware that those already booked will have chosen carefully their position).
    If you could please let me know by personal email (rebecca@odoo-community.org) which stands you have booked already that would be great).

    Hopefully we can make something work this year but if not we will have a better chance with things next year (Virginie had discussed this idea with Odoo some time back but unfortunately it was forgotten in their initial planning, so we are playing a bit of catch up. But, thanks to the continuing relationship that is happening I think we will be able to move things forward with better planning between us all over the years to come).

    I will come back to those that have commented once I have talked again with Pauline - thank you for the interest.

    Just a note though, there won't be discounts or specials unfortunately.

    I'll keep you posted.
    Rebecca

    On Sun, 23 Feb 2025 at 01:55, Ivan Sokolov via Cetmix OÜ <team@cetmix.com> wrote:
    Internal communication: Hey Rebecca, We would go with a Standard booth. As long as it is not too late. Actually would be great if we could re-arrange the ones like Luc [...] ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​

    Hey Rebecca,

    We would go with a Standard booth. As long as it is not too late. Actually would be great if we could re-arrange the ones like Luc and Jay who already  paid their ones and move them to the OCA zone.


    Best regards,

    photograph
    Ivan Sokolov
     Cetmix Odoo Solutions
    cetmix.com
    Facebook Twitter LinkedIn Instagram 
    This message is sent using Mail Messages Easy app


    ----- Original message -----
    Date: Feb 19, 2025, 10:27:31 AM
    From: Rebecca Gellatly
    Subject: Odoo Experience 2025 - OCA Zone

    Hello OCA Contributors,

    We are in discussions with Odoo about having an OCA Zone for booths at the Odoo Experience this year.

    I need to collate a bit of information to try and work this out with the Event Manager at Odoo.
    • If you are interested in having a booth in this area could you please contact me? (rebecca@odoo-community.org)
    • If you book a stand what size would you require (Standard, double or double premium)
    • You can see the stand costings here
    • Please respond by Friday this week (21st Feb)
    Once we have agreed on the selected area with Odoo, then OCA community members will be able to book booths by sending an email to the Odoo Event Manager.
    They will generate the quotation for you, and they'll unpublish the booths from the website to make sure only community members get them.

    If you are keen on joining the OCA zone with a booth at the Odoo Experience, please get in touch with me.

    I hope you are all having a great week.
    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

    Powered by Messages Easy Pro



    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly (OCA) - 08:16 - 25 Feb 2025
  • Re: What OCA modules to use for a French micro-enterprise


    Thank you!

    Op 24-02-2025 om 19:22 schreef services:

    Hello virginie, thanks for the link !

    @Jeroen, Here also you will find the module list from "le filament" : https://sources.le-filament.com/lefilament/odoo_docker

    Regards.

    Yann

    Le 24.02.2025 17:58, Virginie Dewulf a écrit :

    Hello Jeroen,
     
    The consultants working group has been working on a list of "must have modules" for different topics (base, purchase, sales, ... and there is even one tab for the french accounting, you are lucky!):
     
    This list is only in a spreadsheet for now, but we (mainly the consultants WG, not really me) are working to make them available on various runboat instances, to let people test a set of modules that work great together for certain industries. Basically, this spreadsheet will be updated with the list of modules as a first step.
     
    Hope this helps you!
     
    Virginie Dewulf
    Executive Director
    +32 477 64 17 20

    Le lun. 24 févr. 2025 à 17:32, Jeroen Baten <notifications@odoo-community.org> a écrit :
    Hi,

I don't know if this the right channel, but asking for help on odoo.com 
about OCA modules  just doesn't seem the correct place.

My question is what OCA modules to use for a French micro-enterprise 
running CE.

Looking forward to any and all replies.

Regards,

Jeroen Baten




-- 
Jeroen Baten              | EMAIL :  JBATEN@I2RS.NL
  ____  _  __              | web   :  www.i2rs.nl
   |  )|_)(_               | tel   :  +31 (0)648519096
  _|_/_| \__)              | Frisolaan 16, 4101 JK, Culemborg, the Netherlands

    _______________________________________________
    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

    -- 
Jeroen Baten              | EMAIL :  JBATEN@I2RS.NL
 ____  _  __              | web   :  www.i2rs.nl
  |  )|_)(_               | tel   :  +31 (0)648519096
 _|_/_| \__)              | Frisolaan 16, 4101 JK, Culemborg, the Netherlands
    by Jeroen Baten - 08:34 - 24 Feb 2025
  • Re: What OCA modules to use for a French micro-enterprise

    Hello virginie, thanks for the link !

    @Jeroen, Here also you will find the module list from "le filament" : https://sources.le-filament.com/lefilament/odoo_docker

    Regards.

    Yann

    Le 24.02.2025 17:58, Virginie Dewulf a écrit :

    Hello Jeroen,
     
    The consultants working group has been working on a list of "must have modules" for different topics (base, purchase, sales, ... and there is even one tab for the french accounting, you are lucky!):
     
    This list is only in a spreadsheet for now, but we (mainly the consultants WG, not really me) are working to make them available on various runboat instances, to let people test a set of modules that work great together for certain industries. Basically, this spreadsheet will be updated with the list of modules as a first step.
     
    Hope this helps you!
     
    Virginie Dewulf
    Executive Director
    +32 477 64 17 20

    Le lun. 24 févr. 2025 à 17:32, Jeroen Baten <notifications@odoo-community.org> a écrit :
    Hi,

I don't know if this the right channel, but asking for help on odoo.com 
about OCA modules  just doesn't seem the correct place.

My question is what OCA modules to use for a French micro-enterprise 
running CE.

Looking forward to any and all replies.

Regards,

Jeroen Baten




-- 
Jeroen Baten              | EMAIL :  JBATEN@I2RS.NL
  ____  _  __              | web   :  www.i2rs.nl
   |  )|_)(_               | tel   :  +31 (0)648519096
  _|_/_| \__)              | Frisolaan 16, 4101 JK, Culemborg, the Netherlands

    _______________________________________________
    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 Yann Le Doaré - 07:21 - 24 Feb 2025
  • Re: Application for PSC Membership – OCA Spanish Localization
    Since people are still asking about PSC membership in this mailing list, in the future I would suggest to refrain from replying about the application itself and instead just provide info about opening a PR in https://github.com/OCA/repo-maintainer-conf/pulls and then moving the discussion with the relevant maintainers there. 

    Cheers 

    Francesco

    Il giorno lun 24 feb 2025 alle ore 18:13 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:
    Certainly there are roles of every type here. I'm not usually the "nice guy", I'm the "do it" and direct one, but it also depends on the topic and context.

    Regards.

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



    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790
    by Francesco Foresti - 06:46 - 24 Feb 2025
  • Re: Application for PSC Membership – OCA Spanish Localization
    Certainly there are roles of every type here. I'm not usually the "nice guy", I'm the "do it" and direct one, but it also depends on the topic and context.

    Regards.
    by Pedro M. Baeza - 06:11 - 24 Feb 2025
  • Re: What OCA modules to use for a French micro-enterprise
    Hello Jeroen,

    The consultants working group has been working on a list of "must have modules" for different topics (base, purchase, sales, ... and there is even one tab for the french accounting, you are lucky!):

    This list is only in a spreadsheet for now, but we (mainly the consultants WG, not really me) are working to make them available on various runboat instances, to let people test a set of modules that work great together for certain industries. Basically, this spreadsheet will be updated with the list of modules as a first step.

    Hope this helps you!

    Virginie Dewulf
    Executive Director
    +32 477 64 17 20


    Le lun. 24 févr. 2025 à 17:32, Jeroen Baten <notifications@odoo-community.org> a écrit :
    Hi,

I don't know if this the right channel, but asking for help on odoo.com 
about OCA modules  just doesn't seem the correct place.

My question is what OCA modules to use for a French micro-enterprise 
running CE.

Looking forward to any and all replies.

Regards,

Jeroen Baten



-- 
Jeroen Baten              | EMAIL :  JBATEN@I2RS.NL
  ____  _  __              | web   :  www.i2rs.nl
   |  )|_)(_               | tel   :  +31 (0)648519096
  _|_/_| \__)              | Frisolaan 16, 4101 JK, Culemborg, the Netherlands

    _______________________________________________
    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 - 05:56 - 24 Feb 2025