Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • cleaning mailing list subscriptions of dead addresses 
    Hello everyone,

Do you know of a module which could help in cleaning up mailing list 
memberships?

I spent some time this morning going through the OCA's inbox, and 
checking for bounce messages saying 'this email address is no longer 
valid', and then finding the partners in our database and archiving 
them. However doing this manually feels a bit stupid, so I was wondering 
if the community had some pointers for the lazy sysadmin that I am, or 
some ideas about how to tackle this in a nice way.

Thanks for your feedback :)



-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
    by Alexandre Fayolle - 12:56 - 4 Oct 2021

    1 replies 1 replies

  • OCA Days Call for Speakers Reminder - get your proposals in
    Hello OCA Contributors

    I hope the week is ending well for you all.

    Just a reminder if you have a talk proposal for the OCA Days 2021 please get it sent in. We are in the process of pulling together the agenda with the talks we have had submitted already and really need to know what else is coming our way to get things organised.


    You'll see some of the confirmed talks already published with more to come...

    Also, Odoo Experience is happening next week and we still need a few more volunteers to help out at our Virtual Exhibition Booth - just to join the chat room and be around to answer any questions of visitors stopping by. Not quite the same as when we are at the physical event but still a bit of community spirit will go a long way. If you can spare an hour over the two days of Odoo Experience please pop your name on our rota. We definitely appreciate your efforts.

    Enjoy the rest of the day.
    RebeccaCall-for-speakers-Twitter-post-web.png

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 10:26 - 30 Sep 2021

    1 attachments 1 attachments

    Call-for-speakers-Twitter-post-web.png
  • Request for access to Iranian repository
    Hi
    I need Iranian repository access to develop Iranian localization modules
    https://github.com/OCA/l10n-iran

    I am a member of the translation team
    And I sent a pull request for this repository
    But no action has been taken

    Currently, the only technical team in Iran is fadoo that is working on this project
    by Saeed Raeisi - 07:01 - 25 Sep 2021

    6 replies 6 replies

  • Product set configurator

    Dear contributors,

     

    I am looking for a product configuration module to assemble a coherent set of compatible products. The typical example of use is the configuration of a computer (motherboard, processor, memory...). Each step of the assembly must allow to choose a component compatible with the previous choices according to rules to be defined (example: the processor chosen at step 2 must be compatible with the motherboard chosen at step 1).

    I looked at the Product configurator module but it does not correspond exactly to what I am looking for because it uses the attributes of a single product but, in my case, the result will be a set of products added to the sale order (or to the cart on a e-commerce website).

    Example of typical use on dell.com for a server configuration:

    https://www.dell.com/en-us/work/shop/servers-storage-and-networking/poweredge-t340-tower-server/spd/poweredge-t340/pe_t340_13159_vi_vp?view=configurations

    Does this functionality exist in an OCA module (front end and back end) ?

     

    Thank you for your help

    Best regards

     

    Yves Le Doeuff

     

    y.ledoeuff@alliasys.fr

    Description : alliasys_SLOGAN-3

    Intégrateur ERP Odoo

    Assistance, Hébergement, Formation

     

    www.alliasys.fr

    Tél. 02 23 20 03 25

    2, rue de la Senestrais – 35520 La Chapelle des Fougeretz

    P Pensez ENVIRONNEMENT : n'imprimer que si nécessaire.

     

    by Yves Le Doeuff - 05:21 - 24 Sep 2021

    1 attachments 1 attachments

    image003.jpg

    6 replies 6 replies

  • VOIP Customers Contact List.

    Hi,

     

    Hope you are doing Well.

     

    I would like to know if you are interested in acquiring VOIP Customers Contact List.

     

    Information fields: Names, Title, Email, Phone, Company Name, Company URL, Company physical address, SIC Code, Industry and Specialty (Revenue and Employee).

     

    Please let me know your target geography so that I will get back to you with the counts, Pricing and more information.

     

    Best Regards,

    Virginia Adams

    Demand Generation

     

    by "Virginia Adams" <virginia.adams@optincontacts.tech> - 04:16 - 22 Sep 2021
  • Odoo Experience - volunteers for the OCA Virtual Booth
    Hello OCA Contributors,

    As you know Odoo Experience is online again this year and we need your help at our virtual exhibitor booth.

    The opening hours of the virtual booth will be right after the keynotes: 
    • Wednesday Oct 6th - 15:30 - 22:00 (CEST) 
    • Thursday Oct 7th - 14:30 - 22:00 (CEST) 
    I've set the schedule/rota up in hourly blocks, any time you can give will be greatly appreciated. We'd love at least 3 or more people each hour to help out.

    Schedule:  https://docs.google.com/spreadsheets/d/1Jp3MLgtpWx3odR134gO50rW5JY62s5nmNTlbuuMP8Xk/edit?usp=sharing

    Please add in your name, company and email address on the schedule with the times you can help out, this way I can get in touch directly etc.

    The online set-up will be slightly different to the one used in 2020. Once I have the meeting details and how to log in etc I will share with our awesome volunteers.

    Looking forward to seeing some familiar faces online over the Odoo Experience.

    Warm regards,
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 04:51 - 21 Sep 2021

    1 replies 1 replies

    • Re: Odoo Experience - volunteers for the OCA Virtual Booth
      HI everyone,

      Just a friendly reminder if you have an hour to spare next week over the Odoo Experience the OCA could do with a bit more help to "man the stand" at our virtual exhibitor booth. 


      It is really just a matter of logging into the chat on the site and being around to answer any questions. If you don't know the answer to any queries it isn't a worry as you can just get back in touch with me and I'll be able to get someone in touch with the person quickly enough.

      Really appreciate your help in advance.

      Warm regards,
      Rebecca

      On Tue, 21 Sept 2021 at 14:48, Rebecca Gellatly <rebecca@o4sb.com> wrote:
      Hello OCA Contributors,

      As you know Odoo Experience is online again this year and we need your help at our virtual exhibitor booth.

      The opening hours of the virtual booth will be right after the keynotes: 
      • Wednesday Oct 6th - 15:30 - 22:00 (CEST) 
      • Thursday Oct 7th - 14:30 - 22:00 (CEST) 
      I've set the schedule/rota up in hourly blocks, any time you can give will be greatly appreciated. We'd love at least 3 or more people each hour to help out.

      Schedule:  https://docs.google.com/spreadsheets/d/1Jp3MLgtpWx3odR134gO50rW5JY62s5nmNTlbuuMP8Xk/edit?usp=sharing

      Please add in your name, company and email address on the schedule with the times you can help out, this way I can get in touch directly etc.

      The online set-up will be slightly different to the one used in 2020. Once I have the meeting details and how to log in etc I will share with our awesome volunteers.

      Looking forward to seeing some familiar faces online over the Odoo Experience.

      Warm regards,
      Rebecca

      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association


      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association
      by Rebecca Gellatly - 05:51 - 29 Sep 2021
  • OCA / OCB
    Dear community,

    I am curious about OCA/OCB. Nowadays, is it still recommended to use OCB over Odoo?

    We has made some bug fix and propose to odoo/odoo, but it is not merged easily. Should we propose PR to OCB instead? But then, it will never land to Odoo, right?

    What is the practice around OCB today?

    Thanks!
    Kitti U.
    by Kitti Upariphutthiphong - 04:51 - 21 Sep 2021

    2 replies 2 replies

    • Re: OCA / OCB
      Same as Tom here

      De: "Tom" <tom@sunflowerweb.nl>
      Para: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
      Enviadas: Terça-feira, 21 de setembro de 2021 0:22:12
      Assunto: Re: OCA / OCB

      For me at least it is quite relevant because I am supporting older Odoo versions with bugs, and usually these bugs are fixed in newer versions, then I can backport these in OCB. At least there we have a chance to share, code review, discuss, and possibly merge, without the PR being closed by Odoo.

      Furthermore, when I use OCB, I can trust the above process will be followed even without me paying much attention. So I generally run instances on "latest OCB", saving me some bugs to have to think about.

      It can be argued if these are good reasons but these are my reasons. Curious to know others opinions.

      Sep 21, 2021 04:52:55 Kitti U. <kittiu@ecosoft.co.th>:

      Dear community,

      I am curious about OCA/OCB. Nowadays, is it still recommended to use OCB over Odoo?

      We has made some bug fix and propose to odoo/odoo, but it is not merged easily. Should we propose PR to OCB instead? But then, it will never land to Odoo, right?

      What is the practice around OCB today?

      Thanks!
      Kitti U.

      _______________________________________________
      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 Luis F Miléo - 02:46 - 21 Sep 2021
    • Re: OCA / OCB
      For me at least it is quite relevant because I am supporting older Odoo versions with bugs, and usually these bugs are fixed in newer versions, then I can backport these in OCB. At least there we have a chance to share, code review, discuss, and possibly merge, without the PR being closed by Odoo.

      Furthermore, when I use OCB, I can trust the above process will be followed even without me paying much attention. So I generally run instances on "latest OCB", saving me some bugs to have to think about.

      It can be argued if these are good reasons but these are my reasons. Curious to know others opinions.

      Sep 21, 2021 04:52:55 Kitti U. <kittiu@ecosoft.co.th>:

      Dear community,

      I am curious about OCA/OCB. Nowadays, is it still recommended to use OCB over Odoo?

      We has made some bug fix and propose to odoo/odoo, but it is not merged easily. Should we propose PR to OCB instead? But then, it will never land to Odoo, right?

      What is the practice around OCB today?

      Thanks!
      Kitti U.

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

      by Tom Blauwendraat - 05:21 - 21 Sep 2021
  • OCA Days 2021 - Online - talk proposals
    Hi everyone,

    I hope you have all had a great week.

    We've had some wonderful talks sent through already for the OCA Days 2021 but we NEED MORE.

    Key areas that we could do with extra talks are:
    • Trainings and tutorials 
    • Functional talks
    • Specific modules and their awesome features - share your hard work and knowledge
    Over the coming weeks you'll see more of these requests from me and we really want to hear from you. We have so many knowledgeable people in our community that put in so much effort on so many different topics. If you have something to share (not just limited to the bullet points above) we want to hear about it.


    Have a fabulous weekend everyone.
    Rebecca
    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 08:21 - 17 Sep 2021
  • Travis security issue 
    Hello everyone,

I recently became aware of this issue at Travis

https://travis-ci.community/t/security-bulletin/12081

more information available on

https://twitter.com/peter_szilagyi/status/1437646118700175360

I just updated the secrets we have on travis for our repositories. In 
case you notice something strange on Travis builds, please ping me, as 
it is the first time I use our configure-travis script (kudos to 
Stéphane Bidoul for this) and I could have make a mistake (such as 
uploading the wrong token...)


Best regards


-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
    by Alexandre Fayolle - 04:50 - 16 Sep 2021

    6 replies 6 replies

  • SIGNATURE WIDGET ODOO 13 
    Hello Community,

    I wanted to use signature widget in odoo 13, but i can't remove horizontal line, and there are no customizing to change string parameter 'Signature'. can you help me please.
    Best regards.

    by akalala - 01:55 - 16 Sep 2021
  • Reviews 
    Hi all,

For years, OCA has a big problem with unmerged PR's.

Also, even if there are 2 reviews then PSC's generally don't respond to 
merge requests.

The answer has always been "let's review more" or "Let's use 
gitaggregator and so we can use unmerged PR's".

But why don't we try something more radical:

- Let's write a script to assign "maintainer" role for all modules to 
the person who committed the oldest/original version of it

- If maintainer does not respond to a ping longer than 1 month he loses 
the maintainer role, which then changes to the default maintainer that 
is set for the full repo.

- Let's require only 1 positive review from now on. After that the 
maintainer can merge.

--> I don't think that having 2 reviewers is always necessary and it 
also does not prevent bugs from being merged - this happens anyway. I 
used to have high trust of merged OCA modules but after seeing some 
quite ugly bugs and incomplete work being merged I am starting to think 
that maybe the quality of the unmerged stuff is not that bad as compared 
to what is actually merged. The maintainer can prevent really bad 
changes from entering, by just closing the PR.

Tom
    by Tom Blauwendraat - 01:51 - 16 Sep 2021

    10 replies 10 replies

    • Re: Reviews
      Such fw-port tool exists somehow, but in local, thanks to Sébastien Alix:


      But theory is one thing, and the other is the reality: most of the fw-ports will fail due to pre-commit and black, different code due to version changes, refactorings... Automating the creation of the PR simply won't work, as if it's not satisfactory, or requires extra work, you won't be able to push to the fw-port created branch.

      Instead of having a lot of tools, which is not bad, IMO you should instead involve more and more of your people in PSCs and as maintainers inside your organization, or spread the adopt a module campaign for more casual contributors, trying to involve them in this.

      Regards.
      by Pedro M. Baeza - 12:16 - 17 Sep 2021
    • Re: Reviews
      El vie, 17 de sep de 2021 a las 07:41:54 AM, Tom <tom@sunflowerweb.nl> escribió:
      Regarding the "smarter bot" ideas: although it's typical for a bunch of programmers to come up with a solution to a problem by throwing more engineering into it, I feel there's something to it, it just needs more crystallization and then a hackathon to make it happen. 

      Let's take for example Firefox.

      Firefox has the desktop product, and it builds in different platforms: Linux, Windows, Mac... How to handle that? They have a build system that applies conditionals ("if", "case" and similar) to produce the platform-compatible artifact. Usually this is a Makefile, but there are other systems for the same. Result: single code base, multiple platforms.

      However it also has Android and iOS versions, which are almost completely different. They share some essential concepts, but code bases are split. This is more complex to handle, but they end up supporting these extra platforms too. Result: split code base, single platform.

      As you can imagine, the desktop product is more maintainable.

      Now, OCA. Our products are, mainly:
      1. Addons.
      2. OpenUpgrade.
      3. OCA tooling.
      We only follow the "single code base, multiple platforms" approach in OCA tooling.

      For OpenUpgrade, we use "split code base, single platform", and it would be impossible to change that.

      And for addons? The platforms they run on are different versions of Odoo. I always believed it's possible to have a single code base, but that's a dead discussion and simply won't happen, so the best we can do is improve what we have. And what we have is "split code bases, single platform". And IMHO the way to improve it is a fwbot, just like Odoo does.

      Maybe a good theme for a team at this year's online code sprint?

      Indeed.
      by Jairo Llopis - 12:01 - 17 Sep 2021
    • Re: Reviews

      Regarding the "smarter bot" ideas: although it's typical for a bunch of programmers to come up with a solution to a problem by throwing more engineering into it, I feel there's something to it, it just needs more crystallization and then a hackathon to make it happen. Maybe a good theme for a team at this year's online code sprint?


      As a reminder, OCA Days are coming up, and there will be the usual code sprint.
      It would be nice to have a group working on OCABot improvements.
      This can be to work both on code or process change proposals.


      A question that popped to my mind yesterday is one for the board - has it ever been considered for OCA to pay people to fulfill maintainer roles within the organisation? Money seems to be something thats available, and the spending of money on OpenUpgrade has been a great things throughout the last years also.

      It has been discussed.
      The feeling was that doing so it would work against the volunteer spirit of the community, and could break volunteers motivation.
      Investing on better tooling would be better.
      For the record, there has been an initiative for bounties, where people could publish a bounty, awarding a payment for a task, but it didn't get traction.


      Thanks
      Daniel



      by Daniel Reis - 10:25 - 17 Sep 2021
    • Re: Reviews
      Wow, i must say that everyone comes up with much better ideas than I had originally.

      Regarding the "smarter bot" ideas: although it's typical for a bunch of programmers to come up with a solution to a problem by throwing more engineering into it, I feel there's something to it, it just needs more crystallization and then a hackathon to make it happen. Maybe a good theme for a team at this year's online code sprint?

      I hope more people keep contributing to this thread since I do think it's a big issue. I'm also interested to know how other open source projects are handling this. And perhaps we can look at the "IT projects LLC" repos for inspiration - even though i dont understand their system, it looks pretty happy with all the icons. A "important bugfix" being represented by an ambulance.

      A question that popped to my mind yesterday is one for the board - has it ever been considered for OCA to pay people to fulfill maintainer roles within the organisation? Money seems to be something thats available, and the spending of money on OpenUpgrade has been a great things throughout the last years also.

      Thanks all

      Sep 17, 2021 09:02:07 Yann Papouin <ypa@decgroupe.com>:

      +1 for the bw/fwport bot

      - It would be nice to have a new convention to tag a PR with a label like "Review it in 30 seconds" [R30] when it is a basic/simple/quick fix add/fwd that does not require you to soak up the functioning.
      - It would be nice too that a bot automatically tag an issue/PR with a github label based on the issue/PR name or simply the target branch name : eg: [12.0] -> image.png


      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le ven. 17 sept. 2021 à 08:52, Jairo Llopis <jairo.llopis@tecnativa.com> a écrit :
      I should add that repos using the template (all AFAIK) can upgrade to the latest version and benefit from https://github.com/OCA/oca-addons-repo-template/pull/63. A bot will warn and close stale PRs/issues.


      El jue, 16 de sep de 2021 a las 12:51:48 PM, Sylvain LE GAL <sylvain.legal@grap.coop> escribió:
      That's true ! One of the origins is the fast release rate of Odoo, which requires continuous migration of modules that, for many, do not change.

      Unfortunately, that situation will not change. Odoo policy seems to be : "a year = a release".

      Yep. They do it because they can handle it. The question is: why we can't?

      There are many reasons, but the one that I find most important and easiest to fix is that we need a bw/fwport bot.

      That will make maintenance pleasing, so we'll have more maintainers.

      _______________________________________________
      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 Tom Blauwendraat - 09:40 - 17 Sep 2021
    • Re: Reviews
      +1 for the bw/fwport bot

      - It would be nice to have a new convention to tag a PR with a label like "Review it in 30 seconds" [R30] when it is a basic/simple/quick fix add/fwd that does not require you to soak up the functioning.
      - It would be nice too that a bot automatically tag an issue/PR with a github label based on the issue/PR name or simply the target branch name : eg: [12.0] -> image.png


      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le ven. 17 sept. 2021 à 08:52, Jairo Llopis <jairo.llopis@tecnativa.com> a écrit :
      I should add that repos using the template (all AFAIK) can upgrade to the latest version and benefit from https://github.com/OCA/oca-addons-repo-template/pull/63. A bot will warn and close stale PRs/issues.


      El jue, 16 de sep de 2021 a las 12:51:48 PM, Sylvain LE GAL <sylvain.legal@grap.coop> escribió:
      That's true ! One of the origins is the fast release rate of Odoo, which requires continuous migration of modules that, for many, do not change.

      Unfortunately, that situation will not change. Odoo policy seems to be : "a year = a release".

      Yep. They do it because they can handle it. The question is: why we can't?

      There are many reasons, but the one that I find most important and easiest to fix is that we need a bw/fwport bot.

      That will make maintenance pleasing, so we'll have more maintainers.

      _______________________________________________
      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 Papouin - 09:01 - 17 Sep 2021

      1 attachments 1 attachments

      image.png

  • Request for Reviews 
    Hello Contributors,

Greeting!

On behalf of Initos team member for OCA contributions I am writing this 
email. Currently we focus on migration of module to v14 as well as doing 
some reviews. I would like to request you that please let us know if 
there are any reviews we can do for you.

You can assign to @fshah-initos / dsolanki-initos / hkapatel-initos

Thank You!

Regards,

Dhara Solanki
    by Dhara Solanki - 02:21 - 15 Sep 2021
  • Odoo Developers Telegram Group
    Welcome to worlds largest Odoo Developers Group on Telegram 
    Join Odoo Developers Telegram Group https://t.me/odoo_developers
    Or 
    Search " Odoo Developers" in your Telegram.
    --




    Regards,
    Albin John
    by Albin John - 11:46 - 15 Sep 2021
  • Opportunity To Increase Your Sales with Odoo Users

     

    Hi,

     

    Hope you are doing well!

     

    I would like to know if you are interested in Acquiring Odoo users’ information for your business campaign.

     

    We can also provide you below mentioned technology users’ information.

     

    ·         NetSuite.

    ·         SAP ERP.

    ·         Acumatica.

    ·         SAP Business One.

    ·         Kinetic.

    ·         Microsoft Dynamics GP (And many more).

     

    Data can be customized based upon your requirement (e.g., Job title, Verticals, Geography, etc.)

     

    Please feel free to get back to me with your target criteria, and we will provide you the detailed information accordingly.

     

     Regards,

    Ashlee Robinson

    Demand Generation Head

     

    If you wish not to receive marketing emails please respond “Opt-Out”

     

     

     

    by "Ashlee Robinson" <Ashlee.Robinson@mynextmedia.com> - 08:00 - 14 Sep 2021
  • [Communication Strategy] Thank you for your time!
    Dear contributors,

    You contribute your time to create our great OCA Apps but you also contributed your time and energy to build our new communication strategy.

    I just wrote a Thank you blog post about it.
    You'll learn what we've done this summer and what's next.

    Have a nice day all over the world,
    --
    Virginie
    0477/64.17.20
    by Virginie Dewulf. - 02:51 - 8 Sep 2021
  • Translations and UI

    Dear all,

    We are struggling with dealing with translations for one of our customers using mainly advanced surveys (with Odoo 12.0).

    Basically, they design all their surveys in French + they use template surveys that they duplicate for new ones, changing titles and a few labels / questions inside.


    Then they need to translate these surveys in English and German, since some of them are sent to non-French speaking companies.


    Because Odoo considers that sources terms are en_US, we have everywhere names in source terms like "template (copy)", which is of course not the term they need to translate in English and German but the French terms are to be translated in these languages. Also names in survey tables are the original en_US ones (with (copy) inside) which means nothing to them...


    I am not sure how to address this ? I have seen a number of issues on GitHub which are marked as normal behaviour and won't fix, but of course this does not help.

    I have tried a few things, and my last idea is the following : force context to lang = en_US and do not translate in French (leave terms untranslated) so that it will use source terms for French. Then activate en_GB and de_DE for translating french source in these languages.

    I have tried using context="{'lang': 'en_US'}" on translated fields in views but this does not seem to be taken into account, only context in action is but this use all fields in English then (meaning labels, group strings, etc.), which is not the intended purpose.

    We will probably override write() actions to force lang in context.


    I suppose many of you have already faced issues with translations, any idea, remark, link is welcome !

    Best Regards,

    --

    Le Filament
    		 Rémi CAZENAVE
    ------
    SCOP LE FILAMENT
    by Rémi Cazenave - 10:21 - 7 Sep 2021

    6 replies 6 replies

    • Re: Translations and UI

      Thanks Moises,

      I have proposed PR here : https://github.com/OCA/server-backend/pull/132

      Best Regards,


      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT
      06.87.23.26.04
      remi@le-filament.com
      Le 08/09/2021 à 16:17, Moises Lopez a écrit :
      Hi Rémi,

      If you like contribute it in OCA umbrella you can do it in

      Ping me in order to review it, please
      @moylop260



      On Wed 8 Sep 2021 at 4:32 a.m. Rémi CAZENAVE - Le Filament <remi@le-filament.com> wrote:

      Thank you Yann, Joerg and Tom for your proposals.


      I have implemented a new module based on the proposal from Yann : https://sources.le-filament.com/lefilament/base_default_lang_translate

      I added a boolean on res_lang in order to select your default language. Any update performed with this language would then :

      • Update translation in this language (default behaviour)
      • Update source terms for all translations with the new value
      • Store new value in object table in database

      I also have added a function to modify state of existing translations in case a source term is modified (state changes to to_translate).


      Still need to work on scripts to bring database back to a proper state, cleaning all the mess coming from default Odoo behavior :)


      Of course if you believe this could be useful for OCA, I can create a PR to move it under OCA umbrella.


      Best Regards,

      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT
      06.87.23.26.04
      remi@le-filament.com
      Le 07/09/2021 à 13:31, Yann Papouin a écrit :
      This is an old PR from launchpad that I still use in production on odoo 12.0

      With this patch, the current language is considered the database one (written to tables) and always override 'en_US', but it could be easily modified to only override when the current env.context lang is 'fr*', that way the source (database language) becomes "french".

      It is better to have this patch running since the first launch but a simple script could be written to override "database" data with the french one.

      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le mar. 7 sept. 2021 à 10:22, Rémi CAZENAVE - Le Filament <remi@le-filament.com> a écrit :

      Dear all,

      We are struggling with dealing with translations for one of our customers using mainly advanced surveys (with Odoo 12.0).

      Basically, they design all their surveys in French + they use template surveys that they duplicate for new ones, changing titles and a few labels / questions inside.


      Then they need to translate these surveys in English and German, since some of them are sent to non-French speaking companies.


      Because Odoo considers that sources terms are en_US, we have everywhere names in source terms like "template (copy)", which is of course not the term they need to translate in English and German but the French terms are to be translated in these languages. Also names in survey tables are the original en_US ones (with (copy) inside) which means nothing to them...


      I am not sure how to address this ? I have seen a number of issues on GitHub which are marked as normal behaviour and won't fix, but of course this does not help.

      I have tried a few things, and my last idea is the following : force context to lang = en_US and do not translate in French (leave terms untranslated) so that it will use source terms for French. Then activate en_GB and de_DE for translating french source in these languages.

      I have tried using context="{'lang': 'en_US'}" on translated fields in views but this does not seem to be taken into account, only context in action is but this use all fields in English then (meaning labels, group strings, etc.), which is not the intended purpose.

      We will probably override write() actions to force lang in context.


      I suppose many of you have already faced issues with translations, any idea, remark, link is welcome !

      Best Regards,

      --

      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT

      _______________________________________________
      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

      --
      Moisés López Calderón
      Mobile: (+521) 477-752-22-30
      Twitter: @moylop260
      hangout: moylop260@vauxoo.com
      http://www.vauxoo.com - Odoo Gold Partner
      Twitter: @vauxoo

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

      by Rémi Cazenave - 01:56 - 13 Sep 2021
    • Re: Translations and UI
      Hi Rémi,

      If you like contribute it in OCA umbrella you can do it in

      Ping me in order to review it, please
      @moylop260



      On Wed 8 Sep 2021 at 4:32 a.m. Rémi CAZENAVE - Le Filament <remi@le-filament.com> wrote:

      Thank you Yann, Joerg and Tom for your proposals.


      I have implemented a new module based on the proposal from Yann : https://sources.le-filament.com/lefilament/base_default_lang_translate

      I added a boolean on res_lang in order to select your default language. Any update performed with this language would then :

      • Update translation in this language (default behaviour)
      • Update source terms for all translations with the new value
      • Store new value in object table in database

      I also have added a function to modify state of existing translations in case a source term is modified (state changes to to_translate).


      Still need to work on scripts to bring database back to a proper state, cleaning all the mess coming from default Odoo behavior :)


      Of course if you believe this could be useful for OCA, I can create a PR to move it under OCA umbrella.


      Best Regards,

      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT
      06.87.23.26.04
      remi@le-filament.com
      Le 07/09/2021 à 13:31, Yann Papouin a écrit :
      This is an old PR from launchpad that I still use in production on odoo 12.0

      With this patch, the current language is considered the database one (written to tables) and always override 'en_US', but it could be easily modified to only override when the current env.context lang is 'fr*', that way the source (database language) becomes "french".

      It is better to have this patch running since the first launch but a simple script could be written to override "database" data with the french one.

      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le mar. 7 sept. 2021 à 10:22, Rémi CAZENAVE - Le Filament <remi@le-filament.com> a écrit :

      Dear all,

      We are struggling with dealing with translations for one of our customers using mainly advanced surveys (with Odoo 12.0).

      Basically, they design all their surveys in French + they use template surveys that they duplicate for new ones, changing titles and a few labels / questions inside.


      Then they need to translate these surveys in English and German, since some of them are sent to non-French speaking companies.


      Because Odoo considers that sources terms are en_US, we have everywhere names in source terms like "template (copy)", which is of course not the term they need to translate in English and German but the French terms are to be translated in these languages. Also names in survey tables are the original en_US ones (with (copy) inside) which means nothing to them...


      I am not sure how to address this ? I have seen a number of issues on GitHub which are marked as normal behaviour and won't fix, but of course this does not help.

      I have tried a few things, and my last idea is the following : force context to lang = en_US and do not translate in French (leave terms untranslated) so that it will use source terms for French. Then activate en_GB and de_DE for translating french source in these languages.

      I have tried using context="{'lang': 'en_US'}" on translated fields in views but this does not seem to be taken into account, only context in action is but this use all fields in English then (meaning labels, group strings, etc.), which is not the intended purpose.

      We will probably override write() actions to force lang in context.


      I suppose many of you have already faced issues with translations, any idea, remark, link is welcome !

      Best Regards,

      --

      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT

      _______________________________________________
      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

      --
      Moisés López Calderón
      Mobile: (+521) 477-752-22-30
      Twitter: @moylop260
      hangout: moylop260@vauxoo.com
      http://www.vauxoo.com - Odoo Gold Partner
      Twitter: @vauxoo
      by Moisés López Calderón - 04:15 - 8 Sep 2021
    • Re: Translations and UI

      Thank you Yann, Joerg and Tom for your proposals.


      I have implemented a new module based on the proposal from Yann : https://sources.le-filament.com/lefilament/base_default_lang_translate

      I added a boolean on res_lang in order to select your default language. Any update performed with this language would then :

      • Update translation in this language (default behaviour)
      • Update source terms for all translations with the new value
      • Store new value in object table in database

      I also have added a function to modify state of existing translations in case a source term is modified (state changes to to_translate).


      Still need to work on scripts to bring database back to a proper state, cleaning all the mess coming from default Odoo behavior :)


      Of course if you believe this could be useful for OCA, I can create a PR to move it under OCA umbrella.


      Best Regards,

      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT
      06.87.23.26.04
      remi@le-filament.com
      Le 07/09/2021 à 13:31, Yann Papouin a écrit :
      This is an old PR from launchpad that I still use in production on odoo 12.0

      With this patch, the current language is considered the database one (written to tables) and always override 'en_US', but it could be easily modified to only override when the current env.context lang is 'fr*', that way the source (database language) becomes "french".

      It is better to have this patch running since the first launch but a simple script could be written to override "database" data with the french one.

      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le mar. 7 sept. 2021 à 10:22, Rémi CAZENAVE - Le Filament <remi@le-filament.com> a écrit :

      Dear all,

      We are struggling with dealing with translations for one of our customers using mainly advanced surveys (with Odoo 12.0).

      Basically, they design all their surveys in French + they use template surveys that they duplicate for new ones, changing titles and a few labels / questions inside.


      Then they need to translate these surveys in English and German, since some of them are sent to non-French speaking companies.


      Because Odoo considers that sources terms are en_US, we have everywhere names in source terms like "template (copy)", which is of course not the term they need to translate in English and German but the French terms are to be translated in these languages. Also names in survey tables are the original en_US ones (with (copy) inside) which means nothing to them...


      I am not sure how to address this ? I have seen a number of issues on GitHub which are marked as normal behaviour and won't fix, but of course this does not help.

      I have tried a few things, and my last idea is the following : force context to lang = en_US and do not translate in French (leave terms untranslated) so that it will use source terms for French. Then activate en_GB and de_DE for translating french source in these languages.

      I have tried using context="{'lang': 'en_US'}" on translated fields in views but this does not seem to be taken into account, only context in action is but this use all fields in English then (meaning labels, group strings, etc.), which is not the intended purpose.

      We will probably override write() actions to force lang in context.


      I suppose many of you have already faced issues with translations, any idea, remark, link is welcome !

      Best Regards,

      --

      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT

      _______________________________________________
      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 Rémi Cazenave - 11:31 - 8 Sep 2021
    • Re: Translations and UI
      This is an old PR from launchpad that I still use in production on odoo 12.0

      With this patch, the current language is considered the database one (written to tables) and always override 'en_US', but it could be easily modified to only override when the current env.context lang is 'fr*', that way the source (database language) becomes "french".

      It is better to have this patch running since the first launch but a simple script could be written to override "database" data with the french one.

      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le mar. 7 sept. 2021 à 10:22, Rémi CAZENAVE - Le Filament <remi@le-filament.com> a écrit :

      Dear all,

      We are struggling with dealing with translations for one of our customers using mainly advanced surveys (with Odoo 12.0).

      Basically, they design all their surveys in French + they use template surveys that they duplicate for new ones, changing titles and a few labels / questions inside.


      Then they need to translate these surveys in English and German, since some of them are sent to non-French speaking companies.


      Because Odoo considers that sources terms are en_US, we have everywhere names in source terms like "template (copy)", which is of course not the term they need to translate in English and German but the French terms are to be translated in these languages. Also names in survey tables are the original en_US ones (with (copy) inside) which means nothing to them...


      I am not sure how to address this ? I have seen a number of issues on GitHub which are marked as normal behaviour and won't fix, but of course this does not help.

      I have tried a few things, and my last idea is the following : force context to lang = en_US and do not translate in French (leave terms untranslated) so that it will use source terms for French. Then activate en_GB and de_DE for translating french source in these languages.

      I have tried using context="{'lang': 'en_US'}" on translated fields in views but this does not seem to be taken into account, only context in action is but this use all fields in English then (meaning labels, group strings, etc.), which is not the intended purpose.

      We will probably override write() actions to force lang in context.


      I suppose many of you have already faced issues with translations, any idea, remark, link is welcome !

      Best Regards,

      --

      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT

      _______________________________________________
      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 Papouin - 01:30 - 7 Sep 2021
    • Re: Translations and UI

      My idea:

      1. Write a one-time script that will replace all current source values for translated fields for records that are noupdate=1 or dont come from the database at all, with the French translation (gets rid of all the "copy names" and replace by something meaningful)

      2. Add "en_GB" for English and dont use "en_US"

      3. For any translated fields in future dont allow direct edit but force the user to use OCA "web_translate_dialog", which shows the source and all the translations in view so people will have to fill something meaningful always. We have made a module for this 'web_widget_enforce_translate', can opensource it when useful (wanted to, but didnt get the time to polish it)

      On 9/7/21 10:22 AM, Rémi CAZENAVE - Le Filament wrote:

      Dear all,

      We are struggling with dealing with translations for one of our customers using mainly advanced surveys (with Odoo 12.0).

      Basically, they design all their surveys in French + they use template surveys that they duplicate for new ones, changing titles and a few labels / questions inside.


      Then they need to translate these surveys in English and German, since some of them are sent to non-French speaking companies.


      Because Odoo considers that sources terms are en_US, we have everywhere names in source terms like "template (copy)", which is of course not the term they need to translate in English and German but the French terms are to be translated in these languages. Also names in survey tables are the original en_US ones (with (copy) inside) which means nothing to them...


      I am not sure how to address this ? I have seen a number of issues on GitHub which are marked as normal behaviour and won't fix, but of course this does not help.

      I have tried a few things, and my last idea is the following : force context to lang = en_US and do not translate in French (leave terms untranslated) so that it will use source terms for French. Then activate en_GB and de_DE for translating french source in these languages.

      I have tried using context="{'lang': 'en_US'}" on translated fields in views but this does not seem to be taken into account, only context in action is but this use all fields in English then (meaning labels, group strings, etc.), which is not the intended purpose.

      We will probably override write() actions to force lang in context.


      I suppose many of you have already faced issues with translations, any idea, remark, link is welcome !

      Best Regards,

      --

      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT

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

      by Tom Blauwendraat - 12:51 - 7 Sep 2021

  • A methodology / best practice / Odoo / Python question

    Hello,

     

    I am struggling with this for a while so I have decided to ask here. I am building a module that would be showing active filters/ordering as tags on e-commerce by parsing query part of the URL. Besides the standard ones (search, order) we are also using brands filter and also custom_info. Both of these can have multiple options checked. User has the option to remove them individually instead of searching for appropriate checkobxes on the page. Now my approach is basically iterate through key/value pairs and for each generate what looks like a tag visually with URL that has that key/value pair removed (so it in fact removes that part of filter). For that I have devised a code like this:

     

    from odoo.http import request

     

    from werkzeug import OrderedMultiDict

    from werkzeug.urls import url_parse, url_encode

     

    def _get_filtered_url(param, value):

    filtered_args = OrderedMultiDict(filter(lambda arg: arg[0]!=param or arg[1]!=value, request.httprequest.args.items(multi=True)))

    url = url_parse(request.httprequest.url)

    return url.replace(query=url_encode(filtered_args)).to_url()

     

    Now this code is obviously not a object/class method - it should be (in my opinion) a static method. Now the question is: static method of what? Because I need to be able to call it from XML template that renders part of WebsiteSale. I guess I could create a dummy (transient?) class and call it like request.env['my_transient_class']._get_filtered_url(param, value) but that somehow does not seem right to me. Or is it the right way? I am trying to write a clean concise code that is not hacky.

     

    Any advice is welcome here. Thank you very much.

     

    Best regards

     

    Radovan Skolnik

     

    by Radovan Skolnik - 10:25 - 6 Sep 2021

    2 replies 2 replies

    • Re: A methodology / best practice / Odoo / Python question 
      Simone!

Thanx a lot! That's exactly what I was looking for. Seems so straightforward 
now.

Best regards

	Radovan

On utorok 7. septembra 2021 10:32:07 CEST Simone Rubino wrote:

> Hi, you can also use functions to render QWeb templates, so you can declare

> the function in any Python file and add it to the values used to render the

> pages that will need your function. For instance, see how `format_date` is

> used in 

> https://github.com/odoo/odoo/blob/070bec2f3a7a50c6fc8f104cf92a9416ebc001b8/

> addons/mail/models/mail_render_mixin.py#L244 [1]  for rendering e-mails. To

> add your function to the values of any website page you can override

> `_prepare_qcontext` (

> https://github.com/odoo/odoo/blob/3f96cff0aa5097a386c289cf9fd2aeb3048376ab/

> odoo/addons/base/models/ir_ui_view.py#L1720 [2] ) or you can add it

> individually to the values of the page that need your function. On Mon, 6

> Sept 2021 at 10:26, Radovan Skolnik < radovan@skolnik.info [3] > wrote:

> Hello,

> 

> I am struggling with this for a while so I have decided to ask here. I am

> building a module that would be showing active filters/ordering as tags on

> e-commerce by parsing query part of the URL. Besides the standard ones

> (search, order) we are also using brands filter and also custom_info. Both

> of these can have multiple options checked. User has the option to remove

> them individually instead of searching for appropriate checkobxes on the

> page. Now my approach is basically iterate through key/value pairs and for

> each generate what looks like a tag visually with URL that has that

> key/value pair removed (so it in fact removes that part of filter). For

> that I have devised a code like this:

> 

> from odoo.http import request

> 

> from werkzeug import OrderedMultiDict

> from werkzeug.urls import url_parse, url_encode

> 

> def _get_filtered_url(param, value):

> filtered_args = OrderedMultiDict(filter(lambda arg: arg[0]!=param or

> arg[1]!=value, request.httprequest.args.items(multi=True))) url =

> url_parse(request.httprequest.url)

> return url.replace(query=url_encode(filtered_args)).to_url()

> 

> Now this code is obviously not a object/class method - it should be (in my

> opinion) a static method. Now the question is: static method of what?

> Because I need to be able to call it from XML template that renders part of

> WebsiteSale. I guess I could create a dummy (transient?) class and call it

> like request.env['my_transient_class']._get_filtered_url(param, value) but

> that somehow does not seem right to me. Or is it the right way? I am trying

> to write a clean concise code that is not hacky.

> 

> Any advice is welcome here. Thank you very much.

> 

> Best regards

> 

> Radovan Skolnik

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [4]

> Post to: mailto: contributors@odoo-community.org [5]

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [6]

> 

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [7]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [8]

> 

> 

> 

> [1]

> https://github.com/odoo/odoo/blob/070bec2f3a7a50c6fc8f104cf92a9416ebc001b8/

> addons/mail/models/mail_render_mixin.py#L244 [2]

> https://github.com/odoo/odoo/blob/3f96cff0aa5097a386c289cf9fd2aeb3048376ab/

> odoo/addons/base/models/ir_ui_view.py#L1720 [3] mailto:radovan@skolnik.info

> [4] https://odoo-community.org/groups/contributors-15

> [5] mailto:contributors@odoo-community.org

> [6] https://odoo-community.org/groups?unsubscribe

> [7] https://odoo-community.org/groups/contributors-15

> [8] https://odoo-community.org/groups?unsubscribe
      by Radovan Skolnik - 01:40 - 7 Sep 2021
    • Re: A methodology / best practice / Odoo / Python question
      Hi,
      you can also use functions to render QWeb templates, so you can declare the function in any Python file and add it to the values used to render the pages that will need your function.

      To add your function to the values of any website page you can override `_prepare_qcontext` (https://github.com/odoo/odoo/blob/3f96cff0aa5097a386c289cf9fd2aeb3048376ab/odoo/addons/base/models/ir_ui_view.py#L1720) or you can add it individually to the values of the page that need your function.


      On Mon, 6 Sept 2021 at 10:26, Radovan Skolnik <radovan@skolnik.info> wrote:

      Hello,

       

      I am struggling with this for a while so I have decided to ask here. I am building a module that would be showing active filters/ordering as tags on e-commerce by parsing query part of the URL. Besides the standard ones (search, order) we are also using brands filter and also custom_info. Both of these can have multiple options checked. User has the option to remove them individually instead of searching for appropriate checkobxes on the page. Now my approach is basically iterate through key/value pairs and for each generate what looks like a tag visually with URL that has that key/value pair removed (so it in fact removes that part of filter). For that I have devised a code like this:

       

      from odoo.http import request

       

      from werkzeug import OrderedMultiDict

      from werkzeug.urls import url_parse, url_encode

       

      def _get_filtered_url(param, value):

      filtered_args = OrderedMultiDict(filter(lambda arg: arg[0]!=param or arg[1]!=value, request.httprequest.args.items(multi=True)))

      url = url_parse(request.httprequest.url)

      return url.replace(query=url_encode(filtered_args)).to_url()

       

      Now this code is obviously not a object/class method - it should be (in my opinion) a static method. Now the question is: static method of what? Because I need to be able to call it from XML template that renders part of WebsiteSale. I guess I could create a dummy (transient?) class and call it like request.env['my_transient_class']._get_filtered_url(param, value) but that somehow does not seem right to me. Or is it the right way? I am trying to write a clean concise code that is not hacky.

       

      Any advice is welcome here. Thank you very much.

       

      Best regards

       

      Radovan Skolnik

       

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

      by Simone Rubino - 10:31 - 7 Sep 2021
  • What do you want to learn about at OCA Days 2021?
    HI everyone,

    I hope you are all well.
    We are in full planning mode for the OCA Days (28th-29th Oct) and would love to hear from you.

    Are there talk topics, tutorials etc you would like to see presented at the OCA Days?
    Please give us an idea about what you want to know about.

    Thanks so much,
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 10:45 - 2 Sep 2021

    5 replies 5 replies

    • Re: What do you want to learn about at OCA Days 2021?

      Hello Stéphane and thank you! Looking forward to hear it.

      Kind Regards,

      Kiril

      On 30.9.21 11:52, Stéphane Bidoul wrote:
      Hello Kiril and all,

      On Thu, Sep 2, 2021 at 12:32 PM Kiril Vangelovski <kiril@lambda-is.com> wrote:
      It would be nice to hear more about the OCA python packaging infrastructure:

      I'm considering preparing a talk about this. Beyond the topics proposed by Kiril below, are there any other related questions you would like me to address?

      - how and when are addons published on PyPI

      - how to package you own addons

      - example development workflows & deployment strategies using pip instead of a git based approach.

      Best regards,

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

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

      -- 
Lambda IS DOOEL - free/open-source information systems implementation & development

Kiril Vangelovski - consultant/developer

web: https://www.lambda-is.com
tel: +38971753823
      by Kiril Vangelovski - 12:16 - 30 Sep 2021
    • Re: What do you want to learn about at OCA Days 2021?
      Hello Kiril and all,

      On Thu, Sep 2, 2021 at 12:32 PM Kiril Vangelovski <kiril@lambda-is.com> wrote:
      It would be nice to hear more about the OCA python packaging infrastructure:

      I'm considering preparing a talk about this. Beyond the topics proposed by Kiril below, are there any other related questions you would like me to address?

      - how and when are addons published on PyPI

      - how to package you own addons

      - example development workflows & deployment strategies using pip instead of a git based approach.

      Best regards,

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120
      by Stéphane Bidoul - 11:50 - 30 Sep 2021
    • Re: What do you want to learn about at OCA Days 2021?
      Open Upgrade best practice for contributors in more detail would interest me.

      On Fri, Sep 3, 2021, 16:51 Pierre Verkest <pierreverkest84@gmail.com> wrote:
      Hi there,

      What could be interesting from my point of view, would be:
      - sharing on integration workflow, how do we manage module update (not migrating major version) to unfreeze version, test and deploy to production to avoid side effect according different instance diversities
      - get into short tracks that would present OCA modules from the functional point of view to get more informations on existing module (in any domain DDMRP, sales...)

      regards

      Le jeu. 2 sept. 2021 à 10:47, Rebecca Gellatly <rebecca@o4sb.com> a écrit :
      HI everyone,

      I hope you are all well.
      We are in full planning mode for the OCA Days (28th-29th Oct) and would love to hear from you.

      Are there talk topics, tutorials etc you would like to see presented at the OCA Days?
      Please give us an idea about what you want to know about.

      Thanks so much,
      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



      --
      Pierre

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

      by Kitti Upariphutthiphong - 09:31 - 6 Sep 2021
    • Re: What do you want to learn about at OCA Days 2021?
      Hi there,

      What could be interesting from my point of view, would be:
      - sharing on integration workflow, how do we manage module update (not migrating major version) to unfreeze version, test and deploy to production to avoid side effect according different instance diversities
      - get into short tracks that would present OCA modules from the functional point of view to get more informations on existing module (in any domain DDMRP, sales...)

      regards

      Le jeu. 2 sept. 2021 à 10:47, Rebecca Gellatly <rebecca@o4sb.com> a écrit :
      HI everyone,

      I hope you are all well.
      We are in full planning mode for the OCA Days (28th-29th Oct) and would love to hear from you.

      Are there talk topics, tutorials etc you would like to see presented at the OCA Days?
      Please give us an idea about what you want to know about.

      Thanks so much,
      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



      --
      Pierre
      by Pierre Verkest - 11:50 - 3 Sep 2021
    • Re: What do you want to learn about at OCA Days 2021?

      Hello,


      It would be nice to hear more about the OCA python packaging infrastructure:

      - how and when are addons published on PyPI

      - how to package you own addons

      - example development workflows & deployment strategies using pip instead of a git based approach.


      I don't think it has been covered in much details previously.


      Thank you for the effort!


      Kind Regards,

      Kiril


      On 2.9.21 10:46, Rebecca Gellatly wrote:
      HI everyone,

      I hope you are all well.
      We are in full planning mode for the OCA Days (28th-29th Oct) and would love to hear from you.

      Are there talk topics, tutorials etc you would like to see presented at the OCA Days?
      Please give us an idea about what you want to know about.

      Thanks so much,
      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

      -- 
Lambda IS DOOEL - free/open-source information systems implementation & development

Kiril Vangelovski - consultant/developer

web: https://www.lambda-is.com
tel: +38971753823
      by Kiril Vangelovski - 12:31 - 2 Sep 2021
  • [28984] Scaling and healing issues with Odoo.SH, any experiences / further documentation available 
    Dear community of Odooers,

Odoo.SH plattform, based on a not precisely known method pauses cron
jobs. 

Our analysis shows that the pause of a period T happens, if a job A
produces a certain amount of errors Y within a certain period Z of
time. 

Furthermore if the load exceeds some magic threshold entire systems
seem to be shut down by the higher level VM environment causing the
Odoo Server to restart. 

Especially for larger installations in productive usage this is
inacceptable. So we are wondering if this or similar behaviour is
specified and documented somewhere or others did make the same or
similar experiences with Odoo.SH. 

This knowledge would be very valuable in either decide when to pull the
plug on SH or at least how to monitor and prevent those situations from
happening. 

Best Frederik

P.S.: It is clear that for a cloud environment to operate properly such
measures shall be taken but at least they must clearly be documented

P.P.S: What i found was this 
https://www.odoo.com/documentation/master/administration/odoo_sh/advanced/frequent_technical_questions.html

basically saying that and why they are doing it but not on the basis of
which measures

and that 
https://www.odoo.com/de_DE/forum/hilfe-1/odoo-sh-performance-sizing-142865


-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
    by Frederik Kramer - 03:36 - 1 Sep 2021
  • Migration 12.0 -> 14.0
    Hello everyone,

    Is it allowed to create a PR for a module migration that bypasses 13.0 ?
    Yann PAPOUIN
    Ingénieur R&D | DEC

    A ZAC du Monné 3 r Champ du Verger 72700 ALLONNES
    T 02 43 21 65 50 ext 51  ­ F 02 43 39 30 78  ­ E ypa@decgroupe.com ­ W www.decgroupe.com ­
    by Yann Papouin - 10:26 - 31 Aug 2021

    5 replies 5 replies

    • Re: Migration 12.0 -> 14.0
      With https://github.com/OCA/oca-github-bot/pull/97, we try to achieve such thing.

      Regards.
      by Pedro M. Baeza - 10:51 - 2 Sep 2021
    • Re: Migration 12.0 -> 14.0
      Oh, I don't pretend to make a such request 😅
      I thought that Github was able to give enough fine control to create a "Moderator" group across all OCA's modules projects to include users that would be able to edit issues or tag PRs with labels.

      I don't have any knowledge on Github bots, but would it be possible to have specific commands that would add/update the task list for Issues named like "Migration to version xxx" ?

      Analyse the current task list and update the check status based on the linked PR
      /ocabot migration-issue

      Add a module to the task list:
      /ocabot migration-issue module_name

      Add/edit a module to/from the task list and link it with a PR:
      /ocabot migration-issue module_name #123

      Add/edit a module to/from the task list and add/edit a comment:
      /ocabot migration-issue module_name "Merged with another_module"
      /ocabot migration-issue module_name "Move to OCA/another_repo"

      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le mar. 31 août 2021 à 15:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
      Well, for having such permission you need to be PSC of the area of the repository. You can propose yourself in this list if you think you have enough contributions for such place. More information at https://odoo-community.org/page/oca-project-steering-committee-guide

      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 Yann Papouin - 02:40 - 1 Sep 2021
    • Re: Migration 12.0 -> 14.0
      Well, for having such permission you need to be PSC of the area of the repository. You can propose yourself in this list if you think you have enough contributions for such place. More information at https://odoo-community.org/page/oca-project-steering-committee-guide

      Regards.
      by Pedro M. Baeza - 03:35 - 31 Aug 2021
    • Re: Migration 12.0 -> 14.0
      Thank you, that's good news.

      I've started an audit on our database to know current OCA module migration status before starting on it.
      This is really complicated (long task in fact) as for each module, you need to know the github repo and find the "Migration to version 1x.0" issue, and this one is not always updated with the latest comments.
      To help the community, is there a way to give me write access to the main topic to edit/update the task list ?

      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le mar. 31 août 2021 à 10:31, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
      Yes, that's possible while respecting commit history. If the 13.0 version ever needed, it can be backported from 14.0, or migrated from 12.0 again.

      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 Yann Papouin - 02:21 - 31 Aug 2021
    • Re: Migration 12.0 -> 14.0
      Yes, that's possible while respecting commit history. If the 13.0 version ever needed, it can be backported from 14.0, or migrated from 12.0 again.

      Regards.
      by Pedro M. Baeza - 10:30 - 31 Aug 2021