Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

  • Recall process
    Hello,

    I know we have RMA modules in Odoo 14 but I have a customer with a requirement prior to the RMA process.

    His recall process can start from a vendor call/email/document or an internal quality check that would trigger the recall process:

    * Create a recall with a product and serial/number
    * Provide the list of customers or stock locations of where the recalled serial/lot number is located (as a product or as an ingredient from a manufacturing order)
    * different actions based on the location:
      * scrap orders if it is still somewhere in the warehouse as a product
      * unbuild orders if it has been used in MOs
      * a customer RMA order if it has been shipped as a product or part of a finished good to a customer

    The recall would keep some basic information: created by, created on, assigned to, the state (New, In Progress, Done, Cancelled), the status of each subprocess (scrap orders, unbuild orders, RMA orders) and some actions like emailing customers.

    Do we have a module that would get me closer to those requirements?

    Thank you.

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    R & D DIRECTOR
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236
    by Maxime Chambreuil - 12:06 - 4 Aug 2021

    1 replies 1 replies

    • Re: Recall process
      Maybe helpdesk?

      El mié., 4 ago. 2021 0:07, Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
      Hello,

      I know we have RMA modules in Odoo 14 but I have a customer with a requirement prior to the RMA process.

      His recall process can start from a vendor call/email/document or an internal quality check that would trigger the recall process:

      * Create a recall with a product and serial/number
      * Provide the list of customers or stock locations of where the recalled serial/lot number is located (as a product or as an ingredient from a manufacturing order)
      * different actions based on the location:
        * scrap orders if it is still somewhere in the warehouse as a product
        * unbuild orders if it has been used in MOs
        * a customer RMA order if it has been shipped as a product or part of a finished good to a customer

      The recall would keep some basic information: created by, created on, assigned to, the state (New, In Progress, Done, Cancelled), the status of each subprocess (scrap orders, unbuild orders, RMA orders) and some actions like emailing customers.

      Do we have a module that would get me closer to those requirements?

      Thank you.

      MAXIME CHAMBREUIL
      MANAGING DIRECTOR LATAM
      R & D DIRECTOR
      O: 1.855.877.2377 EXT. 710
      M: 602.427.5632
      E: MChambreuil@OpenSourcelntegrators.com
      P.O. BOX 940, HIGLEY, AZ 85236

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

      by Pedro M. Baeza - 01:11 - 4 Aug 2021
  • Adopt an addon
    Hi,

    As you may have noticed, our faithful bot is now calling for addon maintainers.

    When a contributor submits a pull request on an addon that does not have declared maintainers it emits a friendly comment suggesting the author to become a maintainer.

    As a reminder, the maintainer role is described at https://odoo-community.org/page/maintainer-role.

    In a nutshell it is a way to claim that you care about a particular module. This gives you some responsibilities, but also benefits such as receiving notifications when PRs are made on the modules you maintain, and the possibility to merge pull requests without being a full PSC member.

    A huge thank you to Lorenzo Battistini who contributed this feature to the OCA GitHub bot.

    Enjoy,

    -sbi

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

    12 replies 12 replies

    • Re: Adopt an addon
      Hi Tom,

      On Tue, Aug 3, 2021 at 4:51 PM Tom <tom@sunflowerweb.nl> wrote:
      Thanks so much! Does it also mean that a maintainer can merge his own pull requests on a module, thereby do unreviewed development?
       
      On this topic, the maintainer role description says "Maintainers may proceed to some maintenance operation with relaxed code review rules (e.g. performing simple, low risk, forward and backports, maintaining documentation, applying cosmetic improvements to the code such as linting). Maintainers are expected to follow the highest quality standard when performing such operations."

      So yes, more freedom, but also more responsibilities :)

      -sbi

      by Stéphane Bidoul - 06:35 - 3 Aug 2021
    • Re: Adopt an addon
      > Thanks so much! Does it also mean that a maintainer can merge his own pull requests on a module, thereby do unreviewed development?

      He can, but he should not ! (as all people having write access on oca repositories : board member, PSC member, etc...)




      Sylvain LE GAL - Twitter
      GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
      Site Web | FramaSphere | Facebook
      3 Grande rue des Feuillants, 69001 Lyon
      Standard : (+33) 09.72.32.33.17
      Service Informatique : (+33) 09.73.79.64.40
      Astreinte Informatique : (+33) 06.81.85.61.43
      Member of the OCA (Odoo Community Association)


      Le mar. 3 août 2021 à 16:51, Tom <tom@sunflowerweb.nl> a écrit :
      Thanks so much! Does it also mean that a maintainer can merge his own pull requests on a module, thereby do unreviewed development?

      Aug 3, 2021 11:47:32 Francesco Apruzzese <cescoap@gmail.com>:

      Great! Thank you guys!

      Il giorno lun 2 ago 2021 alle ore 19:42 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:
      Hi,

      As you may have noticed, our faithful bot is now calling for addon maintainers.

      When a contributor submits a pull request on an addon that does not have declared maintainers it emits a friendly comment suggesting the author to become a maintainer.

      As a reminder, the maintainer role is described at https://odoo-community.org/page/maintainer-role.

      In a nutshell it is a way to claim that you care about a particular module. This gives you some responsibilities, but also benefits such as receiving notifications when PRs are made on the modules you maintain, and the possibility to merge pull requests without being a full PSC member.

      A huge thank you to Lorenzo Battistini who contributed this feature to the OCA GitHub bot.

      Enjoy,

      -sbi

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



      --

      Francesco Apruzzese

      Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

      Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
      This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

      Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.

      _______________________________________________
      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 Sylvain LE GAL - 05:21 - 3 Aug 2021
    • Re: Adopt an addon
      Thanks so much! Does it also mean that a maintainer can merge his own pull requests on a module, thereby do unreviewed development?

      Aug 3, 2021 11:47:32 Francesco Apruzzese <cescoap@gmail.com>:

      Great! Thank you guys!

      Il giorno lun 2 ago 2021 alle ore 19:42 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:
      Hi,

      As you may have noticed, our faithful bot is now calling for addon maintainers.

      When a contributor submits a pull request on an addon that does not have declared maintainers it emits a friendly comment suggesting the author to become a maintainer.

      As a reminder, the maintainer role is described at https://odoo-community.org/page/maintainer-role.

      In a nutshell it is a way to claim that you care about a particular module. This gives you some responsibilities, but also benefits such as receiving notifications when PRs are made on the modules you maintain, and the possibility to merge pull requests without being a full PSC member.

      A huge thank you to Lorenzo Battistini who contributed this feature to the OCA GitHub bot.

      Enjoy,

      -sbi

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



      --

      Francesco Apruzzese

      Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

      Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
      This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

      Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.

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

      by Tom Blauwendraat - 04:51 - 3 Aug 2021
    • Re: Adopt an addon
      Great! Thank you guys!

      Il giorno lun 2 ago 2021 alle ore 19:42 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:
      Hi,

      As you may have noticed, our faithful bot is now calling for addon maintainers.

      When a contributor submits a pull request on an addon that does not have declared maintainers it emits a friendly comment suggesting the author to become a maintainer.

      As a reminder, the maintainer role is described at https://odoo-community.org/page/maintainer-role.

      In a nutshell it is a way to claim that you care about a particular module. This gives you some responsibilities, but also benefits such as receiving notifications when PRs are made on the modules you maintain, and the possibility to merge pull requests without being a full PSC member.

      A huge thank you to Lorenzo Battistini who contributed this feature to the OCA GitHub bot.

      Enjoy,

      -sbi

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



      --

      Francesco Apruzzese

      Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

      Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
      This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

      Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
      by Francesco Apruzzese - 11:46 - 3 Aug 2021
    • Re: Adopt an addon
      Thanks!
      Sergio Corato


      Il giorno mar 3 ago 2021 alle ore 09:22 Alex Comba <alex.comba@agilebg.com> ha scritto:
      Great! Thanks, Lorenzo and Stéphane!

      On Mon, Aug 2, 2021 at 7:41 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Hi,

      As you may have noticed, our faithful bot is now calling for addon maintainers.

      When a contributor submits a pull request on an addon that does not have declared maintainers it emits a friendly comment suggesting the author to become a maintainer.

      As a reminder, the maintainer role is described at https://odoo-community.org/page/maintainer-role.

      In a nutshell it is a way to claim that you care about a particular module. This gives you some responsibilities, but also benefits such as receiving notifications when PRs are made on the modules you maintain, and the possibility to merge pull requests without being a full PSC member.

      A huge thank you to Lorenzo Battistini who contributed this feature to the OCA GitHub bot.

      Enjoy,

      -sbi

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



      --

      _______________________________________________
      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 - 10:31 - 3 Aug 2021

  • Tests failing - related non dependent modules and bridging module.

    Hello, all,

    I am facing an issue which I hope someone else in the OCA has encountered and solved.

    We have a module that depends on product and changes the behaviour of costing.
    We have another module, auto installed, which depends on that module and on sale_stock_margin



    So loosely, the tree is


    product
          |
          +------------------------------------------+
          |                                                    |
     sale_stock_margin                extension_module_basic
          |                                                    |
          +------------------------------------------+
           |
    extension_module_sale_stock


    In "production" everything works fine - as soon as both modules are installed, the extension module which makes them work together is installed and we are happy.

    But we are using runbot, and sale_stock_margin tests are failing.

    Essentially, I have finally worked out, that when it runs the tests for sale_stock_margin, it does not execute the code from extension_module_sale_stock.  BUT, it does run the code from extension_module_basic when it is setting the costs (unrelated to the sale_stock_margin tests, but related to their values)

    The tests work if both modules are "known" and executed, or neither.

    Obviously, we don't want to make extension_module_basic dependent on sale_stock_margin - it isn't and can be run independent.  And that is the purpose of the bridging module, to unify the behaviour of the two independent modules.

    There is no code problem being highlighted, but we would obviously like the tests to pass.

    Any help appreciated.

    Richard

    Richard deMeester

    Senior Development Analyst

    WilldooIT Pty Ltd

    E: richard.demeester@willdooit.com

    M: +61 403 76 76 76

    P: +61 3 9135 1900

    A: 10/435 Williamstown Road, Port Melbourne, Vic 3207

     

     

    Making growth through technology easy

     

     

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.

    by "Richard deMeester" <richard.demeester@willdooit.com> - 05:50 - 30 Jul 2021

    2 attachments 2 attachments

    Outlook-erb4avho.png
    Outlook-rgyi4dti.jpg
  • Looking for best approach of changing description_sale of product.template from fields.Text to fields.Html 
    Hello,

the users require that products description is at least somewhat "rich" - i.e. allow for some formatting that would be displayed in various places like: quotations, website, ... We already have more than 5000 products. Most of the descriptions were imported, some few hundreds have been manually edited to contain some plain text pseudo formatting. For simplicity we want to keep one description that goes out of company - i.e. quotations, website, ...

We are not able to edit all of them at the same time so we need to take iterative approach to this meaning for some (long) time there will be products with plain text descriptions and some already HTML formatted (I plan to ask users to edit them whenever they add them to quotation). 

However this brings forward another issue: what would be the best approach? Because few issues come to mind:
1) I can either force different widget in product (and other) form(s) or (I guess) it should be possible to re-define the field as HTML.
2) If I just force different widget on forms I need to modify all the web templates that use the field to use t-raw instead of t-field and there is lot of them. It's doable but if I want to keep the changes in one place (module) there would be many dependencies across many modules which I do not consider healthy.
3) I also need to take into consideration that in the process I need to treat descriptions that weren't updated yet - i.e. put <pre> around them to get at least some formatting. Should I detect that in templates or is it possible to write a getter method that would do that automatically?

So I would welcome any suggestions here. Which way would you recommend to go here?

Thank you very much. Best regards

	Radovan Skolnik
    by Radovan Skolnik - 02:41 - 30 Jul 2021

    2 replies 2 replies

    • Re: Looking for best approach of changing description_sale of product.template from fields.Text to fields.Html 
      add an init_hook that calls odoo.tools.(somewhere there in mail I think is a 
text2html function) on the column, and redefine it as html. Or if the module 
already exists increase the version number and do the same in a migration 
script.

Rémi's point stays valid, there are places where templates or code assume text 
and not html, that you'll have to change to t-raw etc.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 10:21 - 30 Jul 2021

      1 attachments 1 attachments

      signature.asc
    • Re: Looking for best approach of changing description_sale of product.template from fields.Text to fields.Html

      Dear Radovan,

      We changed the field to HTML for both sale ordre line and account invoice lines (on v9 then v10 then v12) for a customer. It works fine if you then use proper widget for views and templates.
      However it creates a number of side effects if yoy use the functions to create automatically tasks from sale order (since it takes the first line from sol as task name or related sol on task)...

      Best Regards,
      Rémi CAZENAVE
      SCOP Le Filament

      Le July 30, 2021 12:41:45 PM UTC, Radovan Skolnik <radovan@skolnik.info> a écrit :
      Hello,

the users require that products description is at least somewhat "rich" - i.e. allow for some formatting that would be displayed in various places like: quotations, website, ... We already have more than 5000 products. Most of the descriptions were imported, some few hundreds have been manually edited to contain some plain text pseudo formatting. For simplicity we want to keep one description that goes out of company - i.e. quotations, website, ...

We are not able to edit all of them at the same time so we need to take iterative approach to this meaning for some (long) time there will be products with plain text descriptions and some already HTML formatted (I plan to ask users to edit them whenever they add them to quotation). 

However this brings forward another issue: what would be the best approach? Because few issues come to mind:
1) I can either force different widget in product (and other) form(s) or (I guess) it should be possible to re-define the field as HTML.
2) If I just force different widget on forms I need to modify all the web templates that use the field to use t-raw instead of t-field and there is lot of them. It's doable but if I want to keep the changes in one place (module) there would be many dependencies across many modules which I do not consider healthy.
3) I also need to take into consideration that in the process I need to treat descriptions that weren't updated yet - i.e. put <pre> around them to get at least some formatting. Should I detect that in templates or is it possible to write a getter method that would do that automatically?

So I would welcome any suggestions here. Which way would you recommend to go 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 Rémi Cazenave - 06:41 - 30 Jul 2021
  • New module derived from Odoo CE licensing/credits question 
    Hello,

I have modified module website_sale_comparison from Odoo CE into website_sale_custom_info_comparison to work with website_sale_custom_info (based on PR from 9.0 by Jairo Llopis - will create PR for 13.0 soon) which uses product_custom_info. The modifications are really minimal: removed some unneeded code and templates (as these are already present in custom_info), rework of method _prepare_categories_for_display of product.product to work with custom info and slight changes to template displaying the comparison table. So basically it is 90% Odoo code, 10% of modifications.

Licensing-vise it should be OK as Odoo is LGPL v3. However my understanding is that original author should be kept there if this was to be included in OCA repository. Any comments on how to do this properly? I mean shoudl I just put Odoo as one of the authors or look up commits to these files in git? Would such module be acceptable for OCA?

Any comments are welcome. Best regards

	Radovan Skolnik
    by Radovan Skolnik - 01:21 - 30 Jul 2021

    7 replies 7 replies

    • Re: New module derived from Odoo CE licensing/credits question
      Hi,

      A couple things from what happens in practice.

      Firstly in this case it seems unnecessary. So it is better not to. It is always preferable not to.

      Secondly, the purpose of that clause in CLA is mostly 3 fold. 

      1 it allows us to change a license to another OSI approved license without having to gain approval of all copyright holders.
      2 it allows us to defend the copyrights in court (in many jurisdictions including the US you must have a 100% claim to be able to take a court case).
      3 it gives us protection over the history of the copyright and licence (e.g. that the code isn't "stolen" from a private code base, basically that it is licensed correctly)

      For Odoo SA derived code, of which we have quite a bit, not just OCB, we effectively have option 1 off the table. We just notate the README as such for those modules that we cannot change license without Odoo SA approval. In practice, this is a minor concern. If Odoo SA relicenses, and the module is still current, then we can relicense to the same to be compatible. Otherwise, we might need to ask their permission, which is in their interest. 

      For the second case, in any such action, Odoo SA is a) going to take action themselves, b) we'd have to join them in court action and it is likely to be in their interest, c) it isn't worth it.

      It is kind of 1 of the 2 exceptions for pragmatic purposes to the CLA. And in large part it is because in any enforcement we either don't care or our interests are aligned. The other exception is where 3rd party content is bundled, such as js libs. But again, we don't care, because we wouldn't want to defend or change license.

      The 3rd case doesn't matter, as Odoo SA has an upstream CLA and we can check the license.



      On Sat, Jul 31, 2021 at 9:37 PM Frederik Kramer <frederik.kramer@initos.com> wrote:
      Am Freitag, den 30.07.2021, 18:29 +0200 schrieb Radovan Skolnik:


> Frederik,

HI Radovan,



> 


> it will be interesting to hear on this licensing-vise. Regarding


> this:


> > but they also inheretly hand over rights (that they


> > don't own) to the OCA in the first place.


> From my understanding you can fork/modify all you want provided you


> keep the 


> original author and license as well and distribute such work further.

yes for the LGPL that is perfectly fine.



> For me 


> this seems like this scenario: someone (in this case S.A.) publishes


> module 


> under LGPLv3. Someone else (in this case me) takes it, modifies its 


> functionality retaining original copyright as well and submits it to


> be 


> included in some other project (OCA) with the same licensing. I fail


> to see 


> where a problem could be in this scenario. But I am not alawyer ;-)

The problem here is 

https://raw.githubusercontent.com/OCA/odoo-community.org/master/the-association/ICLA.pdf

Section 3.b:

"You own the Copyright and patent claims covering the Contribution
which are required to grant
the rights under Section 2."

As you "own" only your contribution but the code that you contribute
is, as you said 90% done elsewere and by somebody else not filling this
ICLA (i.e. S.A.), this paragraph is simply not applying. 

Anyway as i said this is the very same problem (as Holger pointed out)
with the OCB code, so i wonder how we as a community deal with that.
Thats why am loudly asking for others' opinion. 

Disclaimer: I am no lawyer mayself either but i have dealt with these 
matters in my scientific carreer quite a bit.

Best and have a nice weekend 

Frederik  




> 


> However what Holger suggested is probably much better approach. My


> module 


> will:


> 1) depend on the Odoo one


> 2) only modify stuff that is different


> 3) disable what is not needed from the original one


> 


> This will provide pretty simple/dense module.


> 


> Best regards


> 


> 	Radovan


> 


> On piatok 30. júla 2021 18:17:04 CEST Frederik Kramer wrote:


> > Hi Radovan,


> > i tend to agree to what Holger just said, but you hit a general


> > problem


> > that to me is somewhat unsolved. This is as follows:


> > OCA is requiring (and checking) if contributions are made by


> > contributors that have signed the ICLA / CLA. By signing these


> > documents one claims that the code he or she add to he baseline is


> > his


> > / her own in its entirety.


> > Now afaik S.A. itself (though publishing its core code in LGPLv3)


> > isn't


> > officially contributing to the OCA but other OCA contributors do.


> > This


> > means by pushing the OCB code these contributors already work in a


> > grey


> > zone because what they do is legally absolutely fine (i.e.


> > contributing


> > to LGPLed code) but they also inheretly hand over rights (that they


> > don't own) to the OCA in the first place.


> > I might be wrong but OCB is a special case and your contribution


> > would


> > be like OCB (as Holger just said) but it cannot be treated an


> > ordinary


> > contribution to an arbitrary OCA repo, at least if we as the


> > community


> > would retain the right to defend the IPR of the entire set of code


> > against uncompliant use (example Flectra).


> > With that having said, i kindly ask you to wait pushing the code


> > until


> > some other (prefierably long term contributors and members have


> > added


> > their interpretation of the legal case). Ususally our vice


> > president


> > Graeme has some nice and valuable thoughts on these matters.


> > Best and have a nice weekend


> > Frederik


> > 


> > Am Freitag, den 30.07.2021, 15:56 +0000 schrieb Radovan Skolnik:


> > > Holger,


> > > 


> > > thanx for an input. I initially thought to make it in a way so


> > > that


> > > both modules can work side-by-side. But that is probably pretty


> > > useless so your idea is actually pretty good and would make the


> > > module really small.


> > > 


> > > The code and templates I removed are for


> > > product.attribute.category


> > > for product.attribute to group them. I think I cannot (can I?)


> > > disable the code so the additional object/table/column will be


> > > there.


> > > However I would like to disable the templates relating to these


> > > so


> > > they do not confuse the user. According to a Google search it can


> > > be


> > > done in this way:


> > > 


> > > <record id="full_external_id_of_the_template" model="ir.ui.view">


> > > 


> > >     <field name="active" eval="False"/>


> > > 


> > > </record>


> > > 


> > > If I uninstall my module will the active statu return to its


> > > previous


> > > state? Should I use anything like that or just document in the


> > > readme


> > > that the product.attribute.category is useless while using


> > > custom.info?


> > > 


> > > Best regards


> > > 


> > > Radovan


> > > 


> > > On piatok 30. júla 2021 13:47:19 CEST Holger Brunn wrote:


> > > > > Would such module be acceptable for OCA? Any comments


> > > > > are welcome. Best regards


> > > > 


> > > > shouldn't be very different than backporting an Odoo SA module,


> > > 


> > > right?


> > > 


> > > https://github.com/OCA/odoo-community.org/blob/master/website/Contribution


> > > /


> > > 


> > > > CONTRIBUTING.rst#backporting-odoo-modules


> > > > But if there's so little changes, why can't you just depend on


> > > > the


> > > 


> > > module


> > > 


> > > > and change what's to be changed in your code?


> > > > _______________________________________________


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


> > > >  [1]


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


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


> > > > 


> > > > 


> > > > 


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


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


> > > 


> > > _______________________________________________


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


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


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


> > 


> > --


> > Dr.-Ing. Frederik Kramer


> > Geschäftsführer


> > initOS GmbH


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


> > 


> > _______________________________________________


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


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


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


> > 


> > 


> > 


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


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


> 


> 


> 


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

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

      by Graeme Gellatly - 09:11 - 31 Jul 2021
    • Re: New module derived from Odoo CE licensing/credits question 
      Am Freitag, den 30.07.2021, 18:29 +0200 schrieb Radovan Skolnik:

> Frederik,

HI Radovan,


> 

> it will be interesting to hear on this licensing-vise. Regarding

> this:

> > but they also inheretly hand over rights (that they

> > don't own) to the OCA in the first place.

> From my understanding you can fork/modify all you want provided you

> keep the 

> original author and license as well and distribute such work further.

yes for the LGPL that is perfectly fine.


> For me 

> this seems like this scenario: someone (in this case S.A.) publishes

> module 

> under LGPLv3. Someone else (in this case me) takes it, modifies its 

> functionality retaining original copyright as well and submits it to

> be 

> included in some other project (OCA) with the same licensing. I fail

> to see 

> where a problem could be in this scenario. But I am not alawyer ;-)

The problem here is 

https://raw.githubusercontent.com/OCA/odoo-community.org/master/the-association/ICLA.pdf

Section 3.b:

"You own the Copyright and patent claims covering the Contribution
which are required to grant
the rights under Section 2."

As you "own" only your contribution but the code that you contribute
is, as you said 90% done elsewere and by somebody else not filling this
ICLA (i.e. S.A.), this paragraph is simply not applying. 

Anyway as i said this is the very same problem (as Holger pointed out)
with the OCB code, so i wonder how we as a community deal with that.
Thats why am loudly asking for others' opinion. 

Disclaimer: I am no lawyer mayself either but i have dealt with these 
matters in my scientific carreer quite a bit.

Best and have a nice weekend 

Frederik  



> 

> However what Holger suggested is probably much better approach. My

> module 

> will:

> 1) depend on the Odoo one

> 2) only modify stuff that is different

> 3) disable what is not needed from the original one

> 

> This will provide pretty simple/dense module.

> 

> Best regards

> 

> 	Radovan

> 

> On piatok 30. júla 2021 18:17:04 CEST Frederik Kramer wrote:

> > Hi Radovan,

> > i tend to agree to what Holger just said, but you hit a general

> > problem

> > that to me is somewhat unsolved. This is as follows:

> > OCA is requiring (and checking) if contributions are made by

> > contributors that have signed the ICLA / CLA. By signing these

> > documents one claims that the code he or she add to he baseline is

> > his

> > / her own in its entirety.

> > Now afaik S.A. itself (though publishing its core code in LGPLv3)

> > isn't

> > officially contributing to the OCA but other OCA contributors do.

> > This

> > means by pushing the OCB code these contributors already work in a

> > grey

> > zone because what they do is legally absolutely fine (i.e.

> > contributing

> > to LGPLed code) but they also inheretly hand over rights (that they

> > don't own) to the OCA in the first place.

> > I might be wrong but OCB is a special case and your contribution

> > would

> > be like OCB (as Holger just said) but it cannot be treated an

> > ordinary

> > contribution to an arbitrary OCA repo, at least if we as the

> > community

> > would retain the right to defend the IPR of the entire set of code

> > against uncompliant use (example Flectra).

> > With that having said, i kindly ask you to wait pushing the code

> > until

> > some other (prefierably long term contributors and members have

> > added

> > their interpretation of the legal case). Ususally our vice

> > president

> > Graeme has some nice and valuable thoughts on these matters.

> > Best and have a nice weekend

> > Frederik

> > 

> > Am Freitag, den 30.07.2021, 15:56 +0000 schrieb Radovan Skolnik:

> > > Holger,

> > > 

> > > thanx for an input. I initially thought to make it in a way so

> > > that

> > > both modules can work side-by-side. But that is probably pretty

> > > useless so your idea is actually pretty good and would make the

> > > module really small.

> > > 

> > > The code and templates I removed are for

> > > product.attribute.category

> > > for product.attribute to group them. I think I cannot (can I?)

> > > disable the code so the additional object/table/column will be

> > > there.

> > > However I would like to disable the templates relating to these

> > > so

> > > they do not confuse the user. According to a Google search it can

> > > be

> > > done in this way:

> > > 

> > > <record id="full_external_id_of_the_template" model="ir.ui.view">

> > > 

> > >     <field name="active" eval="False"/>

> > > 

> > > </record>

> > > 

> > > If I uninstall my module will the active statu return to its

> > > previous

> > > state? Should I use anything like that or just document in the

> > > readme

> > > that the product.attribute.category is useless while using

> > > custom.info?

> > > 

> > > Best regards

> > > 

> > > Radovan

> > > 

> > > On piatok 30. júla 2021 13:47:19 CEST Holger Brunn wrote:

> > > > > Would such module be acceptable for OCA? Any comments

> > > > > are welcome. Best regards

> > > > 

> > > > shouldn't be very different than backporting an Odoo SA module,

> > > 

> > > right?

> > > 

> > > https://github.com/OCA/odoo-community.org/blob/master/website/Contribution

> > > /

> > > 

> > > > CONTRIBUTING.rst#backporting-odoo-modules

> > > > But if there's so little changes, why can't you just depend on

> > > > the

> > > 

> > > module

> > > 

> > > > and change what's to be changed in your code?

> > > > _______________________________________________

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

> > > >  [1]

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

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

> > > > 

> > > > 

> > > > 

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

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

> > > 

> > > _______________________________________________

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

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

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

> > 

> > --

> > Dr.-Ing. Frederik Kramer

> > Geschäftsführer

> > initOS GmbH

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

> > 

> > _______________________________________________

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

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

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

> > 

> > 

> > 

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

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

> 

> 

> 

-- 
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. - 11:36 - 31 Jul 2021
    • Re: New module derived from Odoo CE licensing/credits question 
      Frederik,

it will be interesting to hear on this licensing-vise. Regarding this:

> but they also inheretly hand over rights (that they

> don't own) to the OCA in the first place.
From my understanding you can fork/modify all you want provided you keep the 
original author and license as well and distribute such work further. For me 
this seems like this scenario: someone (in this case S.A.) publishes module 
under LGPLv3. Someone else (in this case me) takes it, modifies its 
functionality retaining original copyright as well and submits it to be 
included in some other project (OCA) with the same licensing. I fail to see 
where a problem could be in this scenario. But I am not alawyer ;-)

However what Holger suggested is probably much better approach. My module 
will:
1) depend on the Odoo one
2) only modify stuff that is different
3) disable what is not needed from the original one

This will provide pretty simple/dense module.

Best regards

	Radovan

On piatok 30. júla 2021 18:17:04 CEST Frederik Kramer wrote:

> Hi Radovan,

> i tend to agree to what Holger just said, but you hit a general problem

> that to me is somewhat unsolved. This is as follows:

> OCA is requiring (and checking) if contributions are made by

> contributors that have signed the ICLA / CLA. By signing these

> documents one claims that the code he or she add to he baseline is his

> / her own in its entirety.

> Now afaik S.A. itself (though publishing its core code in LGPLv3) isn't

> officially contributing to the OCA but other OCA contributors do. This

> means by pushing the OCB code these contributors already work in a grey

> zone because what they do is legally absolutely fine (i.e. contributing

> to LGPLed code) but they also inheretly hand over rights (that they

> don't own) to the OCA in the first place.

> I might be wrong but OCB is a special case and your contribution would

> be like OCB (as Holger just said) but it cannot be treated an ordinary

> contribution to an arbitrary OCA repo, at least if we as the community

> would retain the right to defend the IPR of the entire set of code

> against uncompliant use (example Flectra).

> With that having said, i kindly ask you to wait pushing the code until

> some other (prefierably long term contributors and members have added

> their interpretation of the legal case). Ususally our vice president

> Graeme has some nice and valuable thoughts on these matters.

> Best and have a nice weekend

> Frederik

> 

> Am Freitag, den 30.07.2021, 15:56 +0000 schrieb Radovan Skolnik:

> > Holger,

> > 

> > thanx for an input. I initially thought to make it in a way so that

> > both modules can work side-by-side. But that is probably pretty

> > useless so your idea is actually pretty good and would make the

> > module really small.

> > 

> > The code and templates I removed are for product.attribute.category

> > for product.attribute to group them. I think I cannot (can I?)

> > disable the code so the additional object/table/column will be there.

> > However I would like to disable the templates relating to these so

> > they do not confuse the user. According to a Google search it can be

> > done in this way:

> > 

> > <record id="full_external_id_of_the_template" model="ir.ui.view">

> > 

> >     <field name="active" eval="False"/>

> > 

> > </record>

> > 

> > If I uninstall my module will the active statu return to its previous

> > state? Should I use anything like that or just document in the readme

> > that the product.attribute.category is useless while using

> > custom.info?

> > 

> > Best regards

> > 

> > Radovan

> > 

> > On piatok 30. júla 2021 13:47:19 CEST Holger Brunn wrote:

> > > > Would such module be acceptable for OCA? Any comments

> > > > are welcome. Best regards

> > > 

> > > shouldn't be very different than backporting an Odoo SA module,

> > 

> > right?

> > 

> > https://github.com/OCA/odoo-community.org/blob/master/website/Contribution

> > /

> > 

> > > CONTRIBUTING.rst#backporting-odoo-modules

> > > But if there's so little changes, why can't you just depend on the

> > 

> > module

> > 

> > > and change what's to be changed in your code?

> > > _______________________________________________

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

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

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

> > > 

> > > 

> > > 

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

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

> > 

> > _______________________________________________

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

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

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

> 

> --

> Dr.-Ing. Frederik Kramer

> Geschäftsführer

> initOS GmbH

> 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

> 

> _______________________________________________

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

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

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

> 

> 

> 

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

> [2] https://odoo-community.org/groups?unsubscribe
      by Radovan Skolnik - 06:31 - 30 Jul 2021
    • Re: New module derived from Odoo CE licensing/credits question 
      Hi Radovan, 

i tend to agree to what Holger just said, but you hit a general problem
that to me is somewhat unsolved. This is as follows:

OCA is requiring (and checking) if contributions are made by
contributors that have signed the ICLA / CLA. By signing these
documents one claims that the code he or she add to he baseline is his
/ her own in its entirety. 

Now afaik S.A. itself (though publishing its core code in LGPLv3) isn't
officially contributing to the OCA but other OCA contributors do. This
means by pushing the OCB code these contributors already work in a grey
zone because what they do is legally absolutely fine (i.e. contributing
to LGPLed code) but they also inheretly hand over rights (that they
don't own) to the OCA in the first place. 

I might be wrong but OCB is a special case and your contribution would
be like OCB (as Holger just said) but it cannot be treated an ordinary
contribution to an arbitrary OCA repo, at least if we as the community
would retain the right to defend the IPR of the entire set of code
against uncompliant use (example Flectra).

With that having said, i kindly ask you to wait pushing the code until
some other (prefierably long term contributors and members have added
their interpretation of the legal case). Ususally our vice president
Graeme has some nice and valuable thoughts on these matters.

Best and have a nice weekend

Frederik 

Am Freitag, den 30.07.2021, 15:56 +0000 schrieb Radovan Skolnik:

> Holger,

>  

> thanx for an input. I initially thought to make it in a way so that

> both modules can work side-by-side. But that is probably pretty

> useless so your idea is actually pretty good and would make the

> module really small.

>  

> The code and templates I removed are for product.attribute.category

> for product.attribute to group them. I think I cannot (can I?)

> disable the code so the additional object/table/column will be there.

> However I would like to disable the templates relating to these so

> they do not confuse the user. According to a Google search it can be

> done in this way:

>  

> <record id="full_external_id_of_the_template" model="ir.ui.view">

>         <field name="active" eval="False"/>

> </record>

>  

> If I uninstall my module will the active statu return to its previous

> state? Should I use anything like that or just document in the readme

> that the product.attribute.category is useless while using

> custom.info?

>  

> Best regards

>  

> Radovan

>  

> On piatok 30. júla 2021 13:47:19 CEST Holger Brunn wrote:

> > > Would such module be acceptable for OCA? Any comments

> > > are welcome. Best regards

> >

> > shouldn't be very different than backporting an Odoo SA module,

> right?

> > 

> https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/

> > CONTRIBUTING.rst#backporting-odoo-modules

> > But if there's so little changes, why can't you just depend on the

> module

> > and change what's to be changed in your code?

> > _______________________________________________

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

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

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

> >

> >

> >

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

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

>  

>  

> _______________________________________________

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

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

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

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
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. - 06:15 - 30 Jul 2021
    • Re: New module derived from Odoo CE licensing/credits question 
      > The code and templates I removed are for product.attribute.category for

> product.attribute to group them. I think I cannot (can I?) disable the code

> so the additional object/table/column will be there. However I would like

> to disable the templates relating to these so they do not confuse the user.

> According to a Google search it can be done in this way:

you can rewrite any qweb template with inheritance before it's evaluated, so 
probably you can have some xpath and change the t-attributes, but


> <record id="full_external_id_of_the_template" model="ir.ui.view">

> <field name="active" eval="False"/>

> </record>

this seems much cleaner to me if it's the intention of this module to undo 
something the other module does entirely.


> If I uninstall my module will the active statu return to its previous state?

> Should I use anything like that or just document in the readme that the

> product.attribute.category is useless while using custom.info?

it doesn't, but you can add an uninstall_hook to your module that sets the 
active flag again.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 06:15 - 30 Jul 2021

      1 attachments 1 attachments

      signature.asc

  • Propose Jordi Ballester as PSC in several areas
    Hi,

    Most of you know Jordi, he has been part of the OCA board several years. As part of the board he had "superpowers" and was able to manage any repository so there was no much need to be included as PSC of many repos (even when he was effectively doing it), now that he is not in the board anymore, he doesn't belong to any PSC group and cannot help with the maintenance. I would like to propose him as PSC of the following areas:

    - Purchase

    Thumbs up for all or some?

    Thank you!

    Regards,

    --
    Lois Rilo Antelo
    Odoo consultant at ForgeFlow S.L.
    lois.rilo@forgeflow.com | https://www.forgeflow.com
    Twitter: /LoisRForgeFlow


          

    The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
    by Lois Rilo Antelo - 11:20 - 29 Jul 2021

    14 replies 14 replies

  • Propose João Marques as PSC for several areas
    Hi all,

    It's been a while since my colleague João is with us, and he has done a lot of work in several areas, so I'm requesting if you consider his inclusion in the proper PSCs. Here you have the pull requests he has made on such PSCs:

    Tools:

    https://github.com/OCA/calendar/pull/29
    https://github.com/OCA/interface-github/pull/73
    https://github.com/OCA/interface-github/pull/72
    https://github.com/OCA/odoo-module-migrator/pull/55
    https://github.com/OCA/odoo-module-migrator/pull/53
    https://github.com/OCA/server-auth/pull/250
    https://github.com/OCA/server-auth/pull/249
    https://github.com/OCA/server-auth/pull/242
    https://github.com/OCA/server-auth/pull/241
    https://github.com/OCA/server-tools/pull/1920
    https://github.com/OCA/server-ux/pull/365

    Document:

    https://github.com/OCA/dms/pull/115
    https://github.com/OCA/dms/pull/47

    But also a lot of reviews:

    https://github.com/OCA/dms/pull/51
    https://github.com/OCA/dms/pull/67
    https://github.com/OCA/dms/pull/71
    https://github.com/OCA/dms/pull/75
    https://github.com/OCA/dms/pull/92
    https://github.com/OCA/dms/pull/100
    https://github.com/OCA/dms/pull/112

    Banking:

    https://github.com/OCA/account-payment/pull/427
    https://github.com/OCA/account-payment/pull/401
    https://github.com/OCA/account-payment/pull/384
    https://github.com/OCA/account-payment/pull/383
    https://github.com/OCA/account-reconcile/pull/370
    https://github.com/OCA/account-reconcile/pull/367
    https://github.com/OCA/bank-payment/pull/817
    https://github.com/OCA/bank-payment/pull/816
    https://github.com/OCA/bank-payment/pull/802
    https://github.com/OCA/bank-payment/pull/798
    https://github.com/OCA/bank-payment/pull/797
    https://github.com/OCA/bank-payment/pull/796
    https://github.com/OCA/bank-payment/pull/795
    https://github.com/OCA/bank-payment/pull/786
    https://github.com/OCA/bank-payment/pull/783
    https://github.com/OCA/bank-payment/pull/782
    https://github.com/OCA/bank-statement-import/pull/365
    https://github.com/OCA/bank-statement-import/pull/354
    https://github.com/OCA/bank-statement-import/pull/322

    Accounting:

    https://github.com/OCA/account-financial-reporting/pull/783
    https://github.com/OCA/account-financial-reporting/pull/782
    https://github.com/OCA/account-financial-reporting/pull/781
    https://github.com/OCA/account-financial-reporting/pull/780
    https://github.com/OCA/account-financial-reporting/pull/777
    https://github.com/OCA/account-financial-reporting/pull/775
    https://github.com/OCA/account-financial-reporting/pull/758
    https://github.com/OCA/account-financial-reporting/pull/749
    https://github.com/OCA/account-financial-tools/pull/1183
    https://github.com/OCA/account-financial-tools/pull/1151
    https://github.com/OCA/account-financial-tools/pull/1112
    https://github.com/OCA/account-invoice-reporting/pull/166
    https://github.com/OCA/account-invoice-reporting/pull/155
    https://github.com/OCA/account-invoice-reporting/pull/152
    https://github.com/OCA/account-invoicing/pull/978
    https://github.com/OCA/account-invoicing/pull/976
    https://github.com/OCA/account-invoicing/pull/908
    https://github.com/OCA/account-invoicing/pull/895
    https://github.com/OCA/account-invoicing/pull/856
    https://github.com/OCA/credit-control/pull/115
    https://github.com/OCA/account-analytic/pull/366


    Thanks for considering it.


    Regards.

    by Pedro M. Baeza - 10:00 - 29 Jul 2021

    12 replies 12 replies

  • New set of module "Requests".
    Dear community,

    Currently I am working on a set of modules which we call "Requests" for a project. And want to check whether there is interest in these modules.

    At the surface it is quite similar to the "Approvals" of Odoo Enterprise. But in more detail it is like Approvals + Goodies of OCA. So I would say, it is a much better version of the Approvals.

    The current list of modules are,
    • requests --> the base module. You can think of it as the envelope where the user will put in their one or many requests and pass through the approval process in one go.
    • requests_tier_validation -> extend request for base_tier_validation
    • requests_exception -> extend request for base_exception
    • requests_custom_info -> extend request for base_custom_info
    • requests_operating_unit -> extend for operating_unit
    • requests_???
    And more documents that can be in the request envelope.
    • requests_hr_expense -> allow adding expense inside the request envelope
    • requests_hr_advance --> allow adding employee advance inside the request envelope
    • requests_purchase_request -> allow adding PR inside the request envelope
    • requests_???
    Small organizations may not need this, but I think bigger organizations that need more control might find it useful, whether it is Expense Request, Purchase Request, Vacation Request, or even Request to create master data, etc...
    • As a central place for all requests, and approval progress (instead of going through many documents).
    • Streamline the way users go through approval process (by using tier validation, or any other extension in the future)
    • Approval can be done for the combined amounts of all their requests for the same, ie.., Trip. (instead of fragmented by document)
    • The request (as a template) controls how data in documents are filled. For example, a "Taxi Expense Request", helps create an Expense Sheet with all data filled, except amount.

    image.png

    image.png

    My question is, which Repo should these modules go to? Or should it has a new repo. (I think it is more employee self service like).

    Thanks
    Kitti U.
    by Kitti Upariphutthiphong - 09:01 - 29 Jul 2021

    2 attachments 2 attachments

    image.png
    image.png

    12 replies 12 replies

  • odoo13 unittest: installed modules not available while testing 
    Hi there

I try to add some functionality to the payroll.

Now when I try to access the payroll stuff from within a test like so:

self.env['hr.payroll.structure']

I get a traceback:

Traceback (most recent call last):
   Debug Console, prompt 68, line 1
     import base64
   File 
"/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/api.py", 
line 463, in __getitem__
     return self.registry[model_name]._browse(self, (), ())
   File 
"/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/modules/registry.py", 
line 177, in __getitem__
     return self.models[model_name]
builtins.KeyError: 'hr.payroll.structure'

However, when I do exactly the same when not being in a unittest, everything 
works fine.

What could be the reason?

I am running on an ubuntu:

Distributor ID:    Ubuntu
Description:    Ubuntu 20.04.2 LTS
Release:    20.04
Codename:    focal

using Python:

python
Python 3.8.2 (default, Feb 25 2020, 13:04:52)
[GCC 9.2.1 20200224] on linux

thanks for your input

Robert
    by robert - 05:36 - 28 Jul 2021

    4 replies 4 replies

    • solved:Re: odoo13 unittest: installed modules not available while testing
      On 29.07.21 10:41, Petar Najman wrote:
      Looks like dependency issue.
      Check if module in which you created this TestCase has dependency to module hr_payroll

      that was the cause

      thanks

      robert

      by robert - 12:21 - 29 Jul 2021
    • Re: odoo13 unittest: installed modules not available while testing
      Hi,

      Looks like dependency issue.
      Check if module in which you created this TestCase has dependency to module hr_payroll

      Regards,

      Petar Najman
      Office: +381 11 328 17 18
      Mobile: +381 60 625 62 62
      Email: petar.najman@modoolar.com
      Web: www.modoolar.com



      On Thu, Jul 29, 2021 at 10:31 AM robert@redo2oo.ch <robert@redo2oo.ch> wrote:
      Thanks Simone
      On 29.07.21 08:42, Simone Orsi wrote:
      Hi,

      without your test class it is hard to guess what's wrong ;)

      Can you provide it?
      Here it is, with some explanations

      import base64
      from odoo.tests import common
      """
      # started with:
      bin/odoo -c etc/odoo.cfg
      # stopped in the debugger:
      self.env.cr.dbname
      'odoo13'
      self.env['hr.payroll.structure']
      hr.payroll.structure()
      # started with:
      bin/odoo -c etc/odoo.cfg -u aba_connector --test-enable --stop-after-ini
      # stopped in the debugger:
      self.env.cr.dbname
      'odoo13'
      self.env['hr.payroll.structure']
      Traceback (most recent call last):
      Debug Console, prompt 80, line 1
      import base64
      File "/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/api.py", line 463, in __getitem__
      return self.registry[model_name]._browse(self, (), ())
      File "/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/modules/registry.py", line 177, in __getitem__
      return self.models[model_name]
      builtins.KeyError: 'hr.payroll.structure'
      """
      class TestEmployee(common.TransactionCase):
      def setUp(self):
      # add env on cls and many other things
      super(TestEmployee, self).setUp()
      user_id = self.env["res.users"].search([])[0].id
      emp = self.env["hr.employee"].search(
      [("name", "=", "Abigail Peterson")]
      ) # demo data
      if not emp:
      emp = self.env["hr.employee"].search([("user_id", "=", 2)])
      if not emp:
      emp = self.env["hr.employee"].create({"user_id": user_id, "name": "Fritz"})
      self.emp = emp
      def test_can_open(self):
      records = self.env["hr.employee"].search([])
      # payroll is installed
      # nevertheless the following line crashes
      # if I add that same line outside of a test
      # it loads fine
      structure = self.env["hr.payroll.structure"] # <------------------- dies
      assert records

      Bests

      On Wed, Jul 28, 2021 at 5:37 PM robert@redo2oo.ch <robert@redo2oo.ch> wrote:
      Hi there

I try to add some functionality to the payroll.

Now when I try to access the payroll stuff from within a test like so:

self.env['hr.payroll.structure']

I get a traceback:

Traceback (most recent call last):
   Debug Console, prompt 68, line 1
     import base64
   File 
"/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/api.py", 
line 463, in __getitem__
     return self.registry[model_name]._browse(self, (), ())
   File 
"/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/modules/registry.py", 
line 177, in __getitem__
     return self.models[model_name]
builtins.KeyError: 'hr.payroll.structure'

However, when I do exactly the same when not being in a unittest, everything 
works fine.

What could be the reason?

I am running on an ubuntu:

Distributor ID:    Ubuntu
Description:    Ubuntu 20.04.2 LTS
Release:    20.04
Codename:    focal

using Python:

python
Python 3.8.2 (default, Feb 25 2020, 13:04:52)
[GCC 9.2.1 20200224] on linux

thanks for your input

Robert

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

      _______________________________________________
      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 Petar Najman - 10:40 - 29 Jul 2021
    • Re: odoo13 unittest: installed modules not available while testing
      Thanks Simone
      On 29.07.21 08:42, Simone Orsi wrote:
      Hi,

      without your test class it is hard to guess what's wrong ;)

      Can you provide it?
      Here it is, with some explanations

      import base64
      from odoo.tests import common
      """
      # started with:
      bin/odoo -c etc/odoo.cfg
      # stopped in the debugger:
      self.env.cr.dbname
      'odoo13'
      self.env['hr.payroll.structure']
      hr.payroll.structure()
      # started with:
      bin/odoo -c etc/odoo.cfg -u aba_connector --test-enable --stop-after-ini
      # stopped in the debugger:
      self.env.cr.dbname
      'odoo13'
      self.env['hr.payroll.structure']
      Traceback (most recent call last):
      Debug Console, prompt 80, line 1
      import base64
      File "/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/api.py", line 463, in __getitem__
      return self.registry[model_name]._browse(self, (), ())
      File "/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/modules/registry.py", line 177, in __getitem__
      return self.models[model_name]
      builtins.KeyError: 'hr.payroll.structure'
      """
      class TestEmployee(common.TransactionCase):
      def setUp(self):
      # add env on cls and many other things
      super(TestEmployee, self).setUp()
      user_id = self.env["res.users"].search([])[0].id
      emp = self.env["hr.employee"].search(
      [("name", "=", "Abigail Peterson")]
      ) # demo data
      if not emp:
      emp = self.env["hr.employee"].search([("user_id", "=", 2)])
      if not emp:
      emp = self.env["hr.employee"].create({"user_id": user_id, "name": "Fritz"})
      self.emp = emp
      def test_can_open(self):
      records = self.env["hr.employee"].search([])
      # payroll is installed
      # nevertheless the following line crashes
      # if I add that same line outside of a test
      # it loads fine
      structure = self.env["hr.payroll.structure"] # <------------------- dies
      assert records

      Bests

      On Wed, Jul 28, 2021 at 5:37 PM robert@redo2oo.ch <robert@redo2oo.ch> wrote:
      Hi there

I try to add some functionality to the payroll.

Now when I try to access the payroll stuff from within a test like so:

self.env['hr.payroll.structure']

I get a traceback:

Traceback (most recent call last):
   Debug Console, prompt 68, line 1
     import base64
   File 
"/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/api.py", 
line 463, in __getitem__
     return self.registry[model_name]._browse(self, (), ())
   File 
"/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/modules/registry.py", 
line 177, in __getitem__
     return self.models[model_name]
builtins.KeyError: 'hr.payroll.structure'

However, when I do exactly the same when not being in a unittest, everything 
works fine.

What could be the reason?

I am running on an ubuntu:

Distributor ID:    Ubuntu
Description:    Ubuntu 20.04.2 LTS
Release:    20.04
Codename:    focal

using Python:

python
Python 3.8.2 (default, Feb 25 2020, 13:04:52)
[GCC 9.2.1 20200224] on linux

thanks for your input

Robert

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

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


      by robert - 10:31 - 29 Jul 2021
    • Re: odoo13 unittest: installed modules not available while testing
      Hi,

      without your test class it is hard to guess what's wrong ;)

      Can you provide it?

      Bests

      On Wed, Jul 28, 2021 at 5:37 PM robert@redo2oo.ch <robert@redo2oo.ch> wrote:
      Hi there

I try to add some functionality to the payroll.

Now when I try to access the payroll stuff from within a test like so:

self.env['hr.payroll.structure']

I get a traceback:

Traceback (most recent call last):
   Debug Console, prompt 68, line 1
     import base64
   File 
"/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/api.py", 
line 463, in __getitem__
     return self.registry[model_name]._browse(self, (), ())
   File 
"/home/robert/projects/odoo13/odoo13/downloads/odoo-13.0.post20201211/odoo/modules/registry.py", 
line 177, in __getitem__
     return self.models[model_name]
builtins.KeyError: 'hr.payroll.structure'

However, when I do exactly the same when not being in a unittest, everything 
works fine.

What could be the reason?

I am running on an ubuntu:

Distributor ID:    Ubuntu
Description:    Ubuntu 20.04.2 LTS
Release:    20.04
Codename:    focal

using Python:

python
Python 3.8.2 (default, Feb 25 2020, 13:04:52)
[GCC 9.2.1 20200224] on linux

thanks for your input

Robert

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi. - 08:40 - 29 Jul 2021
  • Proposing myself for Logistics PSC 
    Hi everyone,

I would like to be part of the Logistics PSC. I contribute to OCA for 
some years now and lately I was especially involved in the WMS stack.

https://github.com/sebalix/

https://github.com/OCA/wms/pulls?q=is%3Apr+author%3Asebalix+sort%3Aupdated-desc+
https://github.com/OCA/stock-logistics-workflow/pulls?q=is%3Apr+author%3Asebalix+sort%3Aupdated-desc+
https://github.com/OCA/delivery-carrier/pulls?q=is%3Apr+author%3Asebalix+sort%3Aupdated-desc+

Kind regards,


-- 
Sébastien Alix
Business Solutions Odoo Developer

Camptocamp France SA
https://www.camptocamp.com/
    by Sébastien Alix - 05:45 - 26 Jul 2021

    11 replies 11 replies

  • Consulting about Offline Surveys
    Hi there!

    I have a client that needs to take surveys using the survey module. The issue is that he will need to take surveys offline. Is there any odoo app to do that?

    I mean, a way to take surveys in offline mode and then synchronize data with the odoo server.

    Thanks in advance.

    Regards,

    Mohamed Zohdy

    Application Consultant

    Mobile:

    (+2) 01100592993

    Email:

    mohamed.zohdy@newsmartegypt.com

    Website:

    www.newsmartegypt.com

    Address:

    92 Omar Ibn El Khattab Street, Heliopolis, Cairo, Egypt

    by "Mohamed zohdy" <mohamed.zohdy@newsmartegypt.com> - 03:55 - 25 Jul 2021

    1 attachments 1 attachments

    image001.png

    1 replies 1 replies

    • Re: Consulting about Offline Surveys
      Dear Mohamed, 

      thanks for asking.
      I am not aware that the module is capable of doing this nor that the common offline capable mobile apps for odoo, available from third parties like BHCs myodoo.com would be able to do this oob. They might help customizing it, however. Another ways could be the chrome/chromium browser capabilites that helps odoo to become somewhat offline capable. The timesheet app is having such capabilites. 

      We did quite some extensions for the survey module as well, since it lacks a lot of needed features, for instance that you can backup and restore the questionaire (Which you will admire when it is loosing data,which the standard app sometimes did), and that you can copy parts of the questionaire, that shall be reused (good for bigger questionaires) as well as as custom color management  that can be adapted for your corporate design  and multilanguage for a questionaire - a most wanted feature.  These are online only, however. 

      Best, Joe

      Von: "Mohamed zohdy" <mohamed.zohdy@newsmartegypt.com>
      An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
      Gesendet: Sonntag, 25. Juli 2021 15:57:02
      Betreff: Consulting about Offline Surveys

      Hi there!

      I have a client that needs to take surveys using the survey module. The issue is that he will need to take surveys offline. Is there any odoo app to do that?

      I mean, a way to take surveys in offline mode and then synchronize data with the odoo server.

      Thanks in advance.

      Regards,

      Mohamed Zohdy

      Application Consultant

      Mobile:

      (+2) 01100592993

      Email:

      mohamed.zohdy@newsmartegypt.com

      Website:

      www.newsmartegypt.com

      Address:

      92 Omar Ibn El Khattab Street, Heliopolis, Cairo, Egypt

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


      by Joerg Lorenz. - 08:30 - 25 Jul 2021
  • Account Asset Management: Manual editing / entry of depreciation board
    Dear OCA contributors,

    We are introducing the ability to manually alter the depreciation board of an asset. 

    Some companies may need to manage a custom depreciation board because the depreciation schedule is too custom, or because it may have evolved over time and cannot follow a single method. In those cases it's better to manage a manual depreciation schedule.

    I am organizing a video conference today at 12PM CET to explain those changes. You can join here:  https://meet.google.com/dgw-bahk-nby

    The associated PR is here: https://github.com/OCA/account-financial-tools/pull/1208

    Feel free to join!

    Regards,
    --
    Jordi Ballester Alomar 
    CEO & Founder  
    Spain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89


          

    The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
    by Jordi Ballester Alomar - 10:15 - 23 Jul 2021
  • Computed customer lead time
    Hello all,

    I am at a third project where we need a feature that seems to be missing in Odoo and OCA or I'm missing something really bad here.

    Customer lead time is set in default Odoo as a static value on the product variant and it just adds this value in days on top when confirming the sales order (without working days but OCA supplier_calendar can help here). 

    All the other values which delay a delivery (vendor lead time, delivery lead time, security days etc) work backward i.e: to deliver order X to the customer you have to set a desired delivery date to which you get the date when you SHOULD order to achieve it and not the way around.

    It happens many times that we need this computation from today in order to give estimates to backend users of when a delivery will be made or for frontend users on the website.

    Does anyone know of any module or feature I'm not aware of? What am I missing? :)

    Regards,
    Paul
    by Paul Catinean - 09:56 - 23 Jul 2021
  • Translation in Odoo and OCA
    Dear OCA friends,

    I'm about to start an initiative to improve the French translation of Odoo v14 (official and OCA modules), which is currently very poor compared to other languages before the release of v15. My experience on this topic is very limited, so I have several questions and I'm interested in some advice from translation communities of other languages.

    Experience/Advice
    ==============
    I'm interested by the experience of other Odoo translation communities that achieve high coverage and high quality (but not where only 1 company makes all the translation work) :
    - How are you organised ?
    - How do you ensure that translations are "coherent" among official and OCA modules ? For example, making sure that "Currency" is always translated by "Devise" and not by "Monnaie". Or how to translate "Quantity on hand" vs "Available quantity" (in the current French translation of Odoo, these 2 terms have the same translation which is a big problem !!!).
    - Are translations mostly done by developers or by non-developers ?
    - How do you motivate translators ?
    - What are the best practice for translation communities on Odoo/OCA ?

    OCA modules
    ============
    I only found this page, which gives very little information https://odoo-community.org/page/translate
    Here are my questions :
    - what is the delay between translation in Weblate and commit on Github (it seems very fast ; commits seem to be done on a daily basis...)
    - Does a moderation/review take place before commit on Github for untranslated terms ? (seems that the answer is "no") and when we change/improve a translation ?
    - are there different access rights for translation of a particular language ? If yes, who is the "master" for French language ?

    Official modules
    =============
    For the official modules, there is a wiki page which gives a lot of information :
    I read that there are 3 levels of access rights :
    1) translator
    2) reviewer
    3) coordinator
    In my Transifex profile, it says :

    lang French of the team "Odoo Translators"

    So I guess I'm at the first level. Do some of you see "Odoo Reviewers'" or "Odoo Coordinator" on your profile page ? How can I know who is the Coordinator for the French language ?
    On the wiki page, it says that Reviewers "Can approve translation suggestions from Translators". But, when I translate some odoo strings in Transifex, it seems that my changes are commited without review. Or is it only when I change an existing translation ? All these access rights are not clear to me.

    I remember that, a few years ago, there was a page on a wiki or Etherpad, where there was some guidelines/instructions for the French translation : this page said for example that "Currency" should always be translated by "Devise" (and not "Monnaie"), etc... But I don't find this page any more...

    Thanks in advance for your answers !

    --
    Alexis de Lattre
    Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
    Mail : alexis.delattre@akretion.com
    by Alexis de Lattre - 12:26 - 22 Jul 2021

    4 replies 4 replies

    • Re: Translation in Odoo and OCA
      Hi,

      I am currently trying to automate translation of my website data by using gengo module, but unsuccessfully.

      Are some of you already doing this ?
      - as soon as data is created from a user (blog, event, product)
      - trigger translation for all active languages
        or trigger automated translation of all not-yet-translated values by a job nightly.

      Which tool do you use ? Gengo or other ?

      Thanks in advance for your help.

      On Fri, Jul 23, 2021 at 11:47 AM Xavier Brochard <xavier@alternatif.org> wrote:
      I work on translations in other project, rarely in Odoo.
Something missing in Odoo Transifex is translator's background on french 
language and open discussion. Users should also be implied (specially 
women), as it looks like tranlations are quickly made by Odoo experts 
rather than «poorly trained in Odoo» users.

---
Librement,
Xavier Brochard xavier@alternatif.org
La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre 
Rosnay)

Le 22.07.2021 12:27, Alexis de Lattre a écrit :


> Dear OCA friends,


> 


> I'm about to start an initiative to improve the French translation of


> Odoo v14 (official and OCA modules), which is currently very poor


> compared to other languages before the release of v15. My experience


> on this topic is very limited, so I have several questions and I'm


> interested in some advice from translation communities of other


> languages.


> 


> Experience/Advice


> ==============


> I'm interested by the experience of other Odoo translation communities


> that achieve high coverage and high quality (but not where only 1


> company makes all the translation work) :


> - How are you organised ?


> 


> - How do you ensure that translations are "coherent" among official


> and OCA modules ? For example, making sure that "Currency" is always


> translated by "Devise" and not by "Monnaie". Or how to translate


> "Quantity on hand" vs "Available quantity" (in the current French


> translation of Odoo, these 2 terms have the same translation which is


> a big problem !!!).


> 


> - Are translations mostly done by developers or by non-developers ?


> - How do you motivate translators ?


> - What are the best practice for translation communities on Odoo/OCA ?


> 


> OCA modules


> ============


> I only found this page, which gives very little information


> https://odoo-community.org/page/translate


> Here are my questions :


> - what is the delay between translation in Weblate and commit on


> Github (it seems very fast ; commits seem to be done on a daily


> basis...)


> - Does a moderation/review take place before commit on Github for


> untranslated terms ? (seems that the answer is "no") and when we


> change/improve a translation ?


> - are there different access rights for translation of a particular


> language ? If yes, who is the "master" for French language ?


> 


> Official modules


> =============


> 


> For the official modules, there is a wiki page which gives a lot of


> information :


> https://github.com/odoo/odoo/wiki/Translations


> I read that there are 3 levels of access rights :


> 1) translator


> 2) reviewer


> 3) coordinator


> In my Transifex profile, it says :


> 


> lang French of the team "Odoo Translators"


> 


> So I guess I'm at the first level. Do some of you see "Odoo


> Reviewers'" or "Odoo Coordinator" on your profile page ? How can I


> know who is the Coordinator for the French language ?


> 


> On the wiki page, it says that Reviewers "Can approve translation


> suggestions from Translators". But, when I translate some odoo strings


> in Transifex, it seems that my changes are commited without review. Or


> is it only when I change an existing translation ? All these access


> rights are not clear to me.


> 


> I remember that, a few years ago, there was a page on a wiki or


> Etherpad, where there was some guidelines/instructions for the French


> translation : this page said for example that "Currency" should always


> be translated by "Devise" (and not "Monnaie"), etc... But I don't find


> this page any more...

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



      --
      Mathieu CANNESSON
      by mathieu - 07:30 - 23 Jul 2021
    • Re: Translation in Odoo and OCA 
      I work on translations in other project, rarely in Odoo.
Something missing in Odoo Transifex is translator's background on french 
language and open discussion. Users should also be implied (specially 
women), as it looks like tranlations are quickly made by Odoo experts 
rather than «poorly trained in Odoo» users.

---
Librement,
Xavier Brochard xavier@alternatif.org
La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre 
Rosnay)

Le 22.07.2021 12:27, Alexis de Lattre a écrit :

> Dear OCA friends,

> 

> I'm about to start an initiative to improve the French translation of

> Odoo v14 (official and OCA modules), which is currently very poor

> compared to other languages before the release of v15. My experience

> on this topic is very limited, so I have several questions and I'm

> interested in some advice from translation communities of other

> languages.

> 

> Experience/Advice

> ==============

> I'm interested by the experience of other Odoo translation communities

> that achieve high coverage and high quality (but not where only 1

> company makes all the translation work) :

> - How are you organised ?

> 

> - How do you ensure that translations are "coherent" among official

> and OCA modules ? For example, making sure that "Currency" is always

> translated by "Devise" and not by "Monnaie". Or how to translate

> "Quantity on hand" vs "Available quantity" (in the current French

> translation of Odoo, these 2 terms have the same translation which is

> a big problem !!!).

> 

> - Are translations mostly done by developers or by non-developers ?

> - How do you motivate translators ?

> - What are the best practice for translation communities on Odoo/OCA ?

> 

> OCA modules

> ============

> I only found this page, which gives very little information

> https://odoo-community.org/page/translate

> Here are my questions :

> - what is the delay between translation in Weblate and commit on

> Github (it seems very fast ; commits seem to be done on a daily

> basis...)

> - Does a moderation/review take place before commit on Github for

> untranslated terms ? (seems that the answer is "no") and when we

> change/improve a translation ?

> - are there different access rights for translation of a particular

> language ? If yes, who is the "master" for French language ?

> 

> Official modules

> =============

> 

> For the official modules, there is a wiki page which gives a lot of

> information :

> https://github.com/odoo/odoo/wiki/Translations

> I read that there are 3 levels of access rights :

> 1) translator

> 2) reviewer

> 3) coordinator

> In my Transifex profile, it says :

> 

> lang French of the team "Odoo Translators"

> 

> So I guess I'm at the first level. Do some of you see "Odoo

> Reviewers'" or "Odoo Coordinator" on your profile page ? How can I

> know who is the Coordinator for the French language ?

> 

> On the wiki page, it says that Reviewers "Can approve translation

> suggestions from Translators". But, when I translate some odoo strings

> in Transifex, it seems that my changes are commited without review. Or

> is it only when I change an existing translation ? All these access

> rights are not clear to me.

> 

> I remember that, a few years ago, there was a page on a wiki or

> Etherpad, where there was some guidelines/instructions for the French

> translation : this page said for example that "Currency" should always

> be translated by "Devise" (and not "Monnaie"), etc... But I don't find

> this page any more...
      by xavier - 11:46 - 23 Jul 2021
    • RE: Translation in Odoo and OCA

      This is how I do it:

      I use poedit to create or update translations locally.

      I only work on the "fr" versions since I noticed that only the fr.po files are taken into account during the installation of the modules, (not the fr_FR) (maybe I missed something ?)

      Once the translation is done, I test it locally by importing the created fr.po file in Odoo and I check that the texts are consistent in the menus and forms.

      Then, I import the fr.po file on translation.odoo-community.org by using the "Files/upload translation" (« Fichiers/Téléverser la traduction ») function.

      Sometimes I get comments on my translations (example : sbi on MIS-Builder) and I correct accordingly.

       

      For the moment, I don't dare to work on the official modules. There are few missing terms and when it is the case I correct locally (I know, it is not good...).

       

      Have  a nice day

       

      Yves Le Doeuff

       

      Email: y.ledoeuff@alliasys.fr

      Description : Description : Description : F:\Alliasys\Communication\logos\alliasys\alliasys_SLOGAN.jpg

      www.alliasys.fr

      Tél. 02 23 20 03 25 – Fax. 02 23 20 03 26

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

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

       

       

       

      De : Alexis de Lattre [mailto:alexis.delattre@akretion.com]
      Envoyé : jeudi 22 juillet 2021 12:28
      À : Contributors
      Objet : Translation in Odoo and OCA

       

      Dear OCA friends,

       

      I'm about to start an initiative to improve the French translation of Odoo v14 (official and OCA modules), which is currently very poor compared to other languages before the release of v15. My experience on this topic is very limited, so I have several questions and I'm interested in some advice from translation communities of other languages.

       

      Experience/Advice

      ==============

      I'm interested by the experience of other Odoo translation communities that achieve high coverage and high quality (but not where only 1 company makes all the translation work) :

      - How are you organised ?

      - How do you ensure that translations are "coherent" among official and OCA modules ? For example, making sure that "Currency" is always translated by "Devise" and not by "Monnaie". Or how to translate "Quantity on hand" vs "Available quantity" (in the current French translation of Odoo, these 2 terms have the same translation which is a big problem !!!).

      - Are translations mostly done by developers or by non-developers ?

      - How do you motivate translators ?

      - What are the best practice for translation communities on Odoo/OCA ?

       

      OCA modules

      ============

      I only found this page, which gives very little information https://odoo-community.org/page/translate

      Here are my questions :

      - what is the delay between translation in Weblate and commit on Github (it seems very fast ; commits seem to be done on a daily basis...)

      - Does a moderation/review take place before commit on Github for untranslated terms ? (seems that the answer is "no") and when we change/improve a translation ?

      - are there different access rights for translation of a particular language ? If yes, who is the "master" for French language ?

       

      Official modules

      =============

      For the official modules, there is a wiki page which gives a lot of information :

      I read that there are 3 levels of access rights :

      1) translator

      2) reviewer

      3) coordinator

      In my Transifex profile, it says :

       

      lang French of the team "Odoo Translators"

       

      So I guess I'm at the first level. Do some of you see "Odoo Reviewers'" or "Odoo Coordinator" on your profile page ? How can I know who is the Coordinator for the French language ?

      On the wiki page, it says that Reviewers "Can approve translation suggestions from Translators". But, when I translate some odoo strings in Transifex, it seems that my changes are commited without review. Or is it only when I change an existing translation ? All these access rights are not clear to me.

       

      I remember that, a few years ago, there was a page on a wiki or Etherpad, where there was some guidelines/instructions for the French translation : this page said for example that "Currency" should always be translated by "Devise" (and not "Monnaie"), etc... But I don't find this page any more...

       

      Thanks in advance for your answers !

       

      --

      Alexis de Lattre
      Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
      Mail : alexis.delattre@akretion.com

      by Yves Le Doeuff - 02:51 - 22 Jul 2021

      1 attachments 1 attachments

      image003.jpg
    • Re: Translation in Odoo and OCA
      My answers are more about my translation workflow.

      Experience/Advice
      ==============
      I'm translating all our modules by myself.
      I always reuse existing translations when possible even if not coherent since Users are used to these words.

      OCA modules
      ============

      All my translations are done using poedit.
      To use its translation suggestion feature, you can pre-fill it with existing po files.

      I create a "compendium" of all existing translations (from openerp 6.1 -> odoo 12.0)
      find ./ -name "fr.po" -not -path "*/test*/*" -o -name "fr_FR.po" -not -path "*/test*/*" | xargs msgcat --use-first | msgattrib --translated --no-wrap -o ./odoo_fr.po

      image.png

      To translate an OCA module,I'm exporting a po file using Weblate
      image.png

      And I'm reimporting it after the translation is done.
      image.png

      If the module was already translated using poedit or if you have imported the po file, you can use the pre-translate to go faster.
      image.png

      If you need to have your changes published immediately to the github repository, you can force it using the "Push" button.

      image.png

      Official modules
      =============
      I only use the Transifex web tool.
      I'm only fixing some missing or invalid translations, most of the time to fix format issues like missing leading or ending space.

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


      Le jeu. 22 juil. 2021 à 12:27, Alexis de Lattre <alexis.delattre@akretion.com> a écrit :
      Dear OCA friends,

      I'm about to start an initiative to improve the French translation of Odoo v14 (official and OCA modules), which is currently very poor compared to other languages before the release of v15. My experience on this topic is very limited, so I have several questions and I'm interested in some advice from translation communities of other languages.

      Experience/Advice
      ==============
      I'm interested by the experience of other Odoo translation communities that achieve high coverage and high quality (but not where only 1 company makes all the translation work) :
      - How are you organised ?
      - How do you ensure that translations are "coherent" among official and OCA modules ? For example, making sure that "Currency" is always translated by "Devise" and not by "Monnaie". Or how to translate "Quantity on hand" vs "Available quantity" (in the current French translation of Odoo, these 2 terms have the same translation which is a big problem !!!).
      - Are translations mostly done by developers or by non-developers ?
      - How do you motivate translators ?
      - What are the best practice for translation communities on Odoo/OCA ?

      OCA modules
      ============
      I only found this page, which gives very little information https://odoo-community.org/page/translate
      Here are my questions :
      - what is the delay between translation in Weblate and commit on Github (it seems very fast ; commits seem to be done on a daily basis...)
      - Does a moderation/review take place before commit on Github for untranslated terms ? (seems that the answer is "no") and when we change/improve a translation ?
      - are there different access rights for translation of a particular language ? If yes, who is the "master" for French language ?

      Official modules
      =============
      For the official modules, there is a wiki page which gives a lot of information :
      I read that there are 3 levels of access rights :
      1) translator
      2) reviewer
      3) coordinator
      In my Transifex profile, it says :

      lang French of the team "Odoo Translators"

      So I guess I'm at the first level. Do some of you see "Odoo Reviewers'" or "Odoo Coordinator" on your profile page ? How can I know who is the Coordinator for the French language ?
      On the wiki page, it says that Reviewers "Can approve translation suggestions from Translators". But, when I translate some odoo strings in Transifex, it seems that my changes are commited without review. Or is it only when I change an existing translation ? All these access rights are not clear to me.

      I remember that, a few years ago, there was a page on a wiki or Etherpad, where there was some guidelines/instructions for the French translation : this page said for example that "Currency" should always be translated by "Devise" (and not "Monnaie"), etc... But I don't find this page any more...

      Thanks in advance for your answers !

      --
      Alexis de Lattre
      Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
      Mail : alexis.delattre@akretion.com

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

      by "Yann Papouin" <ypa@decgroupe.com> - 01:06 - 22 Jul 2021

      5 attachments 5 attachments

      image.png
      image.png
      image.png
      image.png
      image.png
  • Changes in Odoo v14 
    Dear all

is anybody of you aware of a near complete collection of changes
(functionality, code / api) between Odoo major versions (ideally
regularly maintained). Specifically v13 to v14? I know there are a
couple of websites out there that do bits and pieces of it but what i
am searching for, is some sort of collective review of the community
(e.g. in a OCA wiki page). any answer on the matter is appreciated 

Cheers Frederik
 

-- 
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. - 09:11 - 21 Jul 2021

    2 replies 2 replies

    • Re: Changes in Odoo v14 
      Hi Graeme, 

thanks for your thoughts. Concerning the enterprise migration logs are
you aware of any public space where people share insights from these
logs or is the only way to obtain those really going through this
lenghty and unreliable offical process ourselfes ;-)

Best Frederik 

Am Mittwoch, den 21.07.2021, 07:32 +0000 schrieb Graeme Gellatly:

> Hi,

> 

> Generally Odoo release notes are most authoritative and complete.

> Also for technical specifics OCA Migration Guides and the issues and

> notes in Openupgrade repo are good guides.

> 

> Finally the instructions to fix all the mess caused by Odoo

> enterprise migration gives a few hints, as do the enterprise

> migration logs. 

> 

> For code/ideas taken from OCA, twitter on release day :)

> 

> On Wed, Jul 21, 2021 at 7:12 PM Frederik Kramer <

> frederik.kramer@initos.com> wrote:

> > Dear all

> > 

> > is anybody of you aware of a near complete collection of changes

> > (functionality, code / api) between Odoo major versions (ideally

> > regularly maintained). Specifically v13 to v14? I know there are a

> > couple of websites out there that do bits and pieces of it but what

> > i

> > am searching for, is some sort of collective review of the

> > community

> > (e.g. in a OCA wiki page). any answer on the matter is appreciated 

> > 

> > Cheers Frederik

> >  

> > 

> > 

> > -- 

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

> > 

> > _______________________________________________

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

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

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

> 

> _______________________________________________

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

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

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

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
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. - 10:30 - 21 Jul 2021
    • Re: Changes in Odoo v14
      Hi,

      Generally Odoo release notes are most authoritative and complete. Also for technical specifics OCA Migration Guides and the issues and notes in Openupgrade repo are good guides.

      Finally the instructions to fix all the mess caused by Odoo enterprise migration gives a few hints, as do the enterprise migration logs. 

      For code/ideas taken from OCA, twitter on release day :)

      On Wed, Jul 21, 2021 at 7:12 PM Frederik Kramer <frederik.kramer@initos.com> wrote:
      Dear all

is anybody of you aware of a near complete collection of changes
(functionality, code / api) between Odoo major versions (ideally
regularly maintained). Specifically v13 to v14? I know there are a
couple of websites out there that do bits and pieces of it but what i
am searching for, is some sort of collective review of the community
(e.g. in a OCA wiki page). any answer on the matter is appreciated 

Cheers Frederik
 


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

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

      by Graeme Gellatly - 09:31 - 21 Jul 2021
  • Produce multiple products from one component

    Dear Community,

    For the second time, we are requested by customers to make Odoo produce multiple products from a single component (when mrp is basically doing the other way around : 1 product and some side products from multiple components)

    First time was by wood industry, from a single trunk they produce at once various planks of different sizes. At that time we answered that we were not in a position to handle this need.

    Second time is for food industry, from a single fish, they will make at once various fillets or blocks of different sizes. This time we should put in place a solution for that.

    Later on we should look at how to plan/automate from SO the quantities and sizes to be produced.

    The fact that the same functional need coming from 2 different industries is brought to us, makes me think that we could go for a generic solution that could fit both needs. Also I suppose that this need may have already been solved by some of you ?

    Do you know of any company / person / module implementing this need ?
    Otherwise I should raise an RFC as issue on manufacture repo to functionnally describe the need and collect your inputs/comments/remarks before starting development.

    Thanks for your help !
    Best Regards,
    Rémi
    SCOP Le Filament

    by Rémi Cazenave - 08:06 - 19 Jul 2021

    5 replies 5 replies

    • Re: Produce multiple products from one component
      Hi Rémi,

      It seems native "Unbuild Orders" is the perfect tool for your request.

      Bonne journée

      David BEAL
      Consultant ERP Odoo


      Le lun. 19 juil. 2021 à 15:52, Yoshi Tashiro <tashiro@quartile.co> a écrit :
      As far as I understand, there is no logic to distribute the production cost to the by-product using Odoo's standard function.

      A recent inquiry I got from a potential client was about implanting parts and cutting out multiple circuit boards out of a large board.  Would be happy to know if there is a good solution.

      -- 
      Yoshi Tashiro


      On Mon, Jul 19, 2021 at 4:06 PM Tom <tom@sunflowerweb.nl> wrote:
      Doesnt "mrp_byproduct" already solve this case? IMO it doesnt require multiple compoments as an input, can also be just one

      Jul 19, 2021 08:08:01 Rémi CAZENAVE - Le Filament <remi@le-filament.com>:

      Dear Community,

      For the second time, we are requested by customers to make Odoo produce multiple products from a single component (when mrp is basically doing the other way around : 1 product and some side products from multiple components)

      First time was by wood industry, from a single trunk they produce at once various planks of different sizes. At that time we answered that we were not in a position to handle this need.

      Second time is for food industry, from a single fish, they will make at once various fillets or blocks of different sizes. This time we should put in place a solution for that.

      Later on we should look at how to plan/automate from SO the quantities and sizes to be produced.

      The fact that the same functional need coming from 2 different industries is brought to us, makes me think that we could go for a generic solution that could fit both needs. Also I suppose that this need may have already been solved by some of you ?

      Do you know of any company / person / module implementing this need ?
      Otherwise I should raise an RFC as issue on manufacture repo to functionnally describe the need and collect your inputs/comments/remarks before starting development.

      Thanks for your help !
      Best Regards,
      Rémi
      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

      by David BEAL - 08:11 - 19 Jul 2021
    • Re: Produce multiple products from one component
      As far as I understand, there is no logic to distribute the production cost to the by-product using Odoo's standard function.

      A recent inquiry I got from a potential client was about implanting parts and cutting out multiple circuit boards out of a large board.  Would be happy to know if there is a good solution.

      -- 
      Yoshi Tashiro


      On Mon, Jul 19, 2021 at 4:06 PM Tom <tom@sunflowerweb.nl> wrote:
      Doesnt "mrp_byproduct" already solve this case? IMO it doesnt require multiple compoments as an input, can also be just one

      Jul 19, 2021 08:08:01 Rémi CAZENAVE - Le Filament <remi@le-filament.com>:

      Dear Community,

      For the second time, we are requested by customers to make Odoo produce multiple products from a single component (when mrp is basically doing the other way around : 1 product and some side products from multiple components)

      First time was by wood industry, from a single trunk they produce at once various planks of different sizes. At that time we answered that we were not in a position to handle this need.

      Second time is for food industry, from a single fish, they will make at once various fillets or blocks of different sizes. This time we should put in place a solution for that.

      Later on we should look at how to plan/automate from SO the quantities and sizes to be produced.

      The fact that the same functional need coming from 2 different industries is brought to us, makes me think that we could go for a generic solution that could fit both needs. Also I suppose that this need may have already been solved by some of you ?

      Do you know of any company / person / module implementing this need ?
      Otherwise I should raise an RFC as issue on manufacture repo to functionnally describe the need and collect your inputs/comments/remarks before starting development.

      Thanks for your help !
      Best Regards,
      Rémi
      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 Yoshi Tashiro - 03:51 - 19 Jul 2021
    • Re: Produce multiple products from one component

      Поздрав,
      Росен Владимиров
      +359886100204


      На пн, 19.07.2021 г. в 9:07 ч. Rémi CAZENAVE - Le Filament <remi@le-filament.com> написа:

      Dear Community,

      For the second time, we are requested by customers to make Odoo produce multiple products from a single component (when mrp is basically doing the other way around : 1 product and some side products from multiple components)

      First time was by wood industry, from a single trunk they produce at once various planks of different sizes. At that time we answered that we were not in a position to handle this need.

      Second time is for food industry, from a single fish, they will make at once various fillets or blocks of different sizes. This time we should put in place a solution for that.

      Later on we should look at how to plan/automate from SO the quantities and sizes to be produced.

      The fact that the same functional need coming from 2 different industries is brought to us, makes me think that we could go for a generic solution that could fit both needs. Also I suppose that this need may have already been solved by some of you ?

      Do you know of any company / person / module implementing this need ?
      Otherwise I should raise an RFC as issue on manufacture repo to functionnally describe the need and collect your inputs/comments/remarks before starting development.

      Thanks for your help !
      Best Regards,
      Rémi
      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 Rosen Vladimirov - 09:46 - 19 Jul 2021
    • Re: Produce multiple products from one component 
      Haven't worked with any of these but the discussion caught my attention so I 
went to check the modules. mrp_byproduct existed up until 12.0, in 13.0 it was 
merge with/into mrp module.

Just my $0.02

Best regards

	Radovan Skolnik

On pondelok 19. júla 2021 9:06:50 CEST Tom wrote:

> Doesnt "mrp_byproduct" already solve this case? IMO it doesnt require

> multiple compoments as an input, can also be just one

> 

> 

> Jul 19, 2021 08:08:01 Rémi CAZENAVE - Le Filament <remi@le-filament.com>:

> 

> Dear Community, For the second time, we are requested by customers to make

> Odoo produce multiple products from a single component (when mrp is

> basically doing the other way around : 1 product and some side products

> from multiple components) First time was by wood industry, from a single

> trunk they produce at once various planks of different sizes. At that time

> we answered that we were not in a position to handle this need. Second time

> is for food industry, from a single fish, they will make at once various

> fillets or blocks of different sizes. This time we should put in place a

> solution for that. Later on we should look at how to plan/automate from SO

> the quantities and sizes to be produced. The fact that the same functional

> need coming from 2 different industries is brought to us, makes me think

> that we could go for a generic solution that could fit both needs. Also I

> suppose that this need may have already been solved by some of you ? Do you

> know of any company / person / module implementing this need ? Otherwise I

> should raise an RFC as issue on manufacture repo to functionnally describe

> the need and collect your inputs/comments/remarks before starting

> development. Thanks for your help ! Best Regards, Rémi SCOP Le Filament

> 

> _______________________________________________ Mailing-List:

> https://odoo-community.org/groups/contributors-15 [1]  Post to:

> mailto:contributors@odoo-community.org Unsubscribe:

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

> 

> 

> 

> _______________________________________________

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

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

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

> 

> 

> 

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

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

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

> [4] https://odoo-community.org/groups?unsubscribe
      by Radovan Skolnik - 09:15 - 19 Jul 2021
    • Re: Produce multiple products from one component
      Doesnt "mrp_byproduct" already solve this case? IMO it doesnt require multiple compoments as an input, can also be just one

      Jul 19, 2021 08:08:01 Rémi CAZENAVE - Le Filament <remi@le-filament.com>:

      Dear Community,

      For the second time, we are requested by customers to make Odoo produce multiple products from a single component (when mrp is basically doing the other way around : 1 product and some side products from multiple components)

      First time was by wood industry, from a single trunk they produce at once various planks of different sizes. At that time we answered that we were not in a position to handle this need.

      Second time is for food industry, from a single fish, they will make at once various fillets or blocks of different sizes. This time we should put in place a solution for that.

      Later on we should look at how to plan/automate from SO the quantities and sizes to be produced.

      The fact that the same functional need coming from 2 different industries is brought to us, makes me think that we could go for a generic solution that could fit both needs. Also I suppose that this need may have already been solved by some of you ?

      Do you know of any company / person / module implementing this need ?
      Otherwise I should raise an RFC as issue on manufacture repo to functionnally describe the need and collect your inputs/comments/remarks before starting development.

      Thanks for your help !
      Best Regards,
      Rémi
      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 - 09:06 - 19 Jul 2021
  • Prevent 2 modules from testing together in OCA repo.
    Hello,

    When we have 2 module that's will failed when tested together. In OCA repo, are there ways to ensure not to run tests together?

    I remember it is about setting in travis.yaml? but can't find the sample. (Also in the future if we move to github action, how to?

    Thank you,
    by Kitti Upariphutthiphong - 07:26 - 17 Jul 2021

    3 replies 3 replies

  • Migration Folders during migration in OCA Modules
    Hi all,

    Increasingly I am facing an issue with both OpenUpgrade and Enterprise migrations in relation to migrations folders. We have a practice of deleting them whenever a module is migrated.

    So my question is why?

    Let me outline a few issues on one side and hope I can be enlightened of the other side.

    Client is on version 8.0.1 of mis_builder. They migrate using OpenUpgrade and it skips the very important 8.0.2 migration.

    Another client chose to use Openupgrade only for core modules for intervening versions. This is essentially the same issue as an enterprise migration of 2 versions. You get the database back without 3rd party modules migrated.

    The latest module version only contains scripts for 1 version. So you spend hours hunting through finding the scripts, forking repos etc to get the scripts you need.

    But also I ask myself if we couldn't reduce multiversion migration time if a current version ran multiple folders. But then again, Odoo enterprise migration does all modules for a version, then moves to the next version so perhaps not feasible.
    by Graeme Gellatly - 01:20 - 15 Jul 2021

    2 replies 2 replies

    • Re: Migration Folders during migration in OCA Modules
      Yes, a pre-requisite is to have the previous version up to date before starting the migration, and if you run a migration across several versions in between, you have to manually launch the intermediate version scripts. It's what you have if you go through the enterprise path. I doubt Odoo performs all the migrations in one step, but it would be a version per version migration, but you only see the final result of the black box.

      It's not possible to keep all the migration scripts across versions due to several reasons:

      - "Logistic" one: keeping in sync such migration scripts across versions is a pain. If you perform a fix on v12 migration scripts, would you sincerely do the same patch on v13 and v14?
      - And the main one: there are data transformations that aren't idempotent (for example, the renaming of a column), which means that running them several times will lead to errors. This combined with the pre/post/end mechanism, makes a non deterministic scenario where you will need to add a lot of control logic - or it will be directly impossible- to be handled across several versions. Example:

      - On v12, you have 12.0.1.0.0 and 12.0.2.0.0 with scripts.
      - On v13, you have 13.0.1.0.0 with scripts.

      Migrating from v11 to v13, if all the scripts are in v13 (12.0.1.0.0, 12.0.2.0.0, 13.0.1.0.0 and 13.0.2.0.0), and you are not accessing v12 migration cycle, you will get this execution pipeline:

      - Run 12.0.1.0.0 pre-migration
      - Run 12.0.2.0.0 pre-migration
      - Run 13.0.1.0.0 pre-migration
      - Run 12.0.1.0.0 post-migration
      - Run 12.0.2.0.0 post-migration
      - Run 13.0.1.0.0 post-migration

      Running with OpenUpgrade on each version, the execution pipeline is:

      - Run 12.0.1.0.0 pre-migration
      - Run 12.0.2.0.0 pre-migration
      - Run 12.0.1.0.0 post-migration
      - Run 12.0.2.0.0 post-migration
      <new migration cycle>
      - Run 13.0.1.0.0 pre-migration
      - Run 13.0.1.0.0 post-migration

      The only way is to manually re-create the same sequence. And this, expecting that there's no other dependent modules that perform operations on the expected pipeline.

      More things to take into account: OCA module migration scripts are settled on expected renamed columns by OpenUpgrade, so we don't know how enterprise migration scripts are letting data, and thus, you will probably need to adapt existing migration scripts. Example: on the migration from 12 to 13, account.invoice model is merged with account.move. On OpenUpgrade, we created the columns `old_invoice_id` and `old_invoice_line_id` to link the previous record, and a lot of migration scripts rely on these columns for transferring information from old invoices to new moves.

      Conclusion: I have resigned to use enterprise migration services, even on enterprise instances, and always do it through OpenUpgrade.

      Regards.
      by Pedro M. Baeza - 02:30 - 15 Jul 2021
    • Re: Migration Folders during migration in OCA Modules 
      Op 7/15/21 om 1:21 AM schreef Graeme Gellatly:

> Client is on version 8.0.1 of mis_builder. They migrate using 

> OpenUpgrade and it skips the very important 8.0.2 migration.
I don't fully grasp your other issue, but here I always just install all 
the newest modules first (easy to do if you use gitaggregator) and run 
'odoo -u base', before starting OpenUpgrade.
      by Tom Blauwendraat - 10:05 - 15 Jul 2021
  • Propose Alba Riera as PSC for Donation
    I would like to propose Alba as PSC on Donation. She has made some PRs for the migration to 13.0 and I think a new PSC would be great in order to minimize the open PRs
     
     
    Kind regards
     
    Enric Tobella Alomar




    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.
    by Enric Tobella Alomar - 09:31 - 14 Jul 2021

    5 replies 5 replies

    • Re: Propose Alba Riera as PSC for Donation
      Le mer. 14 juil. 2021 à 11:27, Lois Rilo Antelo <lois.rilo@forgeflow.com> a écrit :
      +1 It seems some more hands will help to manage the repository

      Yes, good idea, we need more active PSC on the donation project ! Let's welcome Alba as PSC.

      --
      Alexis de Lattre
       
      by Alexis de Lattre - 11:35 - 15 Jul 2021
    • Re: Propose Alba Riera as PSC for Donation
      +1 It seems some more hands will help to manage the repository

      El mié, 14 jul 2021 a las 11:17, Enric Tobella Alomar (<etobella@creublanca.es>) escribió:
      I know, but in this specific case, there is only one member on the PSC and there is not many answers from there :(
       
       
       
      Enric Tobella Alomar
      Desarrollo
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 1621)
       
       
      From: "Pedro M. Baeza (Tecnativa)" <pedro.baeza@tecnativa.com>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 14 Jul 2021 07:37:17 -0000
      Subject: Re: Propose Alba Riera as PSC for Donation
       
      +1 as a general feeling, although only existing PSCs can vote for this.
       
      Regards.
      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe




      Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
      pueden contener información reservada y/o confidencial, destinada exclusivamente
      para el uso del destinatario o la persona responsable de entregarlo al mismo,
      estando su uso no autorizado prohibido legalmente.
      Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
      salvo ratificación escrita por ambas partes. En caso de su recepción por error,
      rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
      o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
      a su eliminación.

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



      --
      Lois Rilo Antelo
      Odoo consultant at ForgeFlow S.L.
      by Lois Rilo Antelo - 11:25 - 14 Jul 2021
    • Re: Propose Alba Riera as PSC for Donation
      I know, but in this specific case, there is only one member on the PSC and there is not many answers from there :(
       
       
       
      Enric Tobella Alomar
      Desarrollo
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 1621)
       
       
      From: "Pedro M. Baeza (Tecnativa)" <pedro.baeza@tecnativa.com>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 14 Jul 2021 07:37:17 -0000
      Subject: Re: Propose Alba Riera as PSC for Donation
       
      +1 as a general feeling, although only existing PSCs can vote for this.
       
      Regards.
      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe




      Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
      pueden contener información reservada y/o confidencial, destinada exclusivamente
      para el uso del destinatario o la persona responsable de entregarlo al mismo,
      estando su uso no autorizado prohibido legalmente.
      Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
      salvo ratificación escrita por ambas partes. En caso de su recepción por error,
      rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
      o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
      a su eliminación.
      by Enric Tobella Alomar - 11:16 - 14 Jul 2021

      1 attachments 1 attachments

      CB 70anys Gris _ CB+ Color H RGB.png
    • Re: Propose Alba Riera as PSC for Donation
      +1 as a general feeling, although only existing PSCs can vote for this.

      Regards.
      by Pedro M. Baeza - 09:36 - 14 Jul 2021
    • Re: Propose Alba Riera as PSC for Donation
      +1



      ----- Original message -----
      From: Enric Tobella Alomar <etobella@creublanca.es>
      Subject: Propose Alba Riera as PSC for Donation
      Date: Wednesday, July 14, 2021 10:31

      I would like to propose Alba as PSC on Donation. She has made some PRs for the migration to 13.0 and I think a new PSC would be great in order to minimize the open PRs
       
       
      Kind regards
       
      Enric Tobella Alomar




      Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
      pueden contener información reservada y/o confidencial, destinada exclusivamente
      para el uso del destinatario o la persona responsable de entregarlo al mismo,
      estando su uso no autorizado prohibido legalmente.
      Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
      salvo ratificación escrita por ambas partes. En caso de su recepción por error,
      rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
      o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
      a su eliminación.

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


      by Yves Goldberg - 09:36 - 14 Jul 2021
  • OCA Days 2021 - RFQ - Video Post Production
    Hello OCA Contributors,

    As you know we are gearing up for OCA Days 2021 Online.

    As we did last year we want to be able to share the presentations after the event, to do so we need video post production.
    Please find the link to the RFQ for OCA Days 2021 - Video Post Production here.

    To register your interest or ask any questions at all please send to rfq@odoo-community.org
     Warmest regards,
    Rebecca
    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 01:40 - 14 Jul 2021