Skip to Content

Contributors

  • Re: l10n-italy on apps.odoo.com
    Hi Pedro and board friends,
    Is it possible to give the Italy PSC access to Italy repo management at apps?
    So we could at least remove this burden from the board and check by ourselves licenses issues while fixing them.
    Thanks


    Il giorno mar 11 feb 2020, 19:52 Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> ha scritto:
    Although I'm not anymore in charge of OCA's community management, I give a hand to my colleagues at board that are very busy with the rest of the OCA stuff (you should really apply in next votings for giving a hand too) for telling you that the problem are license conflicts:


  • l10n_it_fiscal_document_type: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    fiscal_epos_print: The license GPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_account_tax_kind: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_account_balance_report: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_causali_pagamento: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_website_sale_fiscalcode: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_vat_statement_communication: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_in_purchase is updated before its dependency l10n_it_fatturapa_in. Throw back to the end of the queue.
    l10n_it_withholding_tax_payment is updated before its dependency l10n_it_withholding_tax. Throw back to the end of the queue.
    l10n_it_fatturapa_export_zip is updated before its dependency l10n_it_fatturapa_out. Throw back to the end of the queue.
    l10n_it_invoices_data_communication: unmet dependency l10n_it_fiscal_document_type for series 12.0
    l10n_it_fatturapa_out_stamp is updated before its dependency l10n_it_fatturapa_out. Throw back to the end of the queue.
    l10n_it_fatturapa_out_wt is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_out_triple_discount is updated before its dependency l10n_it_fatturapa_out. Throw back to the end of the queue.
    l10n_it_fatturapa_in_rc is updated before its dependency l10n_it_fatturapa_in. Throw back to the end of the queue.
    l10n_it_corrispettivi_fatturapa_out is updated before its dependency l10n_it_fatturapa_out. Throw back to the end of the queue.
    l10n_it_website_sale_corrispettivi is updated before its dependency l10n_it_website_sale_fatturapa. Throw back to the end of the queue.
    l10n_it_sdi_channel is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_out is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_in is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_out_ddt: unmet dependency l10n_it_fatturapa_out for series 12.0
    l10n_it_website_portal_fatturapa is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_pec: unmet dependency l10n_it_fatturapa_out for series 12.0
    l10n_it_fatturapa: unmet dependency l10n_it_account_tax_kind for series 12.0
    l10n_it_withholding_tax_causali is updated before its dependency l10n_it_withholding_tax. Throw back to the end of the queue.
    l10n_it_pos_fatturapa: unmet dependency l10n_it_fatturapa for series 12.0
    l10n_it_website_portal_fatturapa_sale: unmet dependency l10n_it_website_portal_fatturapa for series 12.0
    l10n_it_website_sale_fatturapa: unmet dependency l10n_it_fatturapa for series 12.0
    l10n_it_withholding_tax: unmet dependency l10n_it_fatturapa for series 12.0
    l10n_it_invoices_data_communication_fatturapa: unmet dependency l10n_it_invoices_data_communication for series 12.0

  • l10n_it_fiscal_document_type: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_account_tax_kind: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_withholding_tax_causali: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_in: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out_ddt: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_pec: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out_stamp: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_ddt_delivery: unmet dependency delivery_carrier_partner for series 11.0

  • account_invoice_entry_date: Module not installable
    l10n_it_prima_nota_cassa: Module not installable
    l10n_it_fiscal_document_type: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    account_invoice_sequential_dates: Module not installable
    l10n_it_base_crm: Module not installable
    account_central_journal: Module not installable
    l10n_it_partially_deductible_vat: Module not installable
    l10n_it_account_tax_kind: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_CEE_balance_generic: Module not installable
    l10n_it_bill_of_entry: Module not installable
    l10n_it_fatturapa: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_withholding_tax_causali: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    account_invoice_report_ddt_group: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_vat_registries_cash_basis: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_website_sale_fiscalcode: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_invoices_data_communication: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fiscalcode_invoice: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out_ddt: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out_stamp: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_in_rc is updated before its dependency l10n_it_fatturapa_in. Throw back to the end of the queue.
    l10n_it_fatturapa_in: unmet dependency l10n_it_withholding_tax_causali for series 10.0
    l10n_it_fatturapa_pec: unmet dependency l10n_it_fatturapa_in for series 10.0
    l10n_it_pos_fatturapa: unmet dependency pos_partner_firstname for series 10.0
    l10n_it_invoices_data_communication_fatturapa: unmet dependency l10n_it_invoices_data_communication for series 10.0
    l10n_it_fatturapa_in_purchase: unmet dependency l10n_it_fatturapa_in for series 10.0
    l10n_it_fatturapa_export_zip: unmet dependency l10n_it_fatturapa_in for series 10.0
    l10n_it_fatturapa_out_wt: unmet dependency l10n_it_withholding_tax_causali for series 10.0

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


    by Lorenzo Battistini. - 10:26 - 12 Feb 2020
  • Re: Proposing Lois Rilo as PSC for server-ux
    Hi Lois,

    I just added you to the team.

    Note an alternative to joining a large PSC is to become a declared maintainer on modules you care about. This gives merge permissions via /ocabot merge.

    -sbi


    On Wed, Feb 12, 2020 at 5:21 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
    +1

    On Wed, Feb 12, 2020 at 5:12 PM Jay Vora <vora.jay@serpentcs.com> wrote:
    +1

    On Wed, Feb 12, 2020 at 9:07 PM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
    Hi all,

    I would like to help maintain pulls requests and issues at server-ux. I've contributed as author and core maintainer of base_tier_validation and there are several related PR still open that I would like to push forward. I also contributed to document_quick_access addons and would like to help on migration and reviews.

    I see the only team with rights in that repo is "Tools maintainers". I wouldn't need to be part of such wide group, but I also understand that segregating the PSC teams even more is not a good approach for maintainability reasons. Any of those two options would be good for me.

    Regards,

    --
    Lois Rilo Antelo - Odoo consultant at ForgeFlow
    twitter: @LoisRForgeFlow

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



    --

    Technology Services @ www.serpentcs.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


     
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com

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



    --


    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Joël Grand-Guillaume
    Department Head
    Business Solutions

    +41 21 619 10 28


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


    by Stéphane Bidoul - 08:56 - 12 Feb 2020
  • Re: Proposing "Pimolnat" as PSC for Logistics
    Hello Pimolnat,

    The wrong contact was linked to the team. I merged your contacts, and it should be synced within 12 hours.

    Best regards,

    -sbi

    On Tue, Feb 11, 2020 at 4:02 AM Pimolnat Suntian <pimolnat.s@outlook.com> wrote:
    Hello Stéphane,

    I didn't receive anything, I have checked spam folder too.

    May you please have a look?

    Thanks,

    Pimolnat Suntian


    From: Stéphane Bidoul <stephane.bidoul@acsone.eu>
    Sent: Wednesday, February 5, 2020 7:06:57 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Proposing "Pimolnat" as PSC for Logistics
     
    Hello Pimolnat,

    I added you to the Logistics PSC. You should receive the GitHub notification within 24h.

    Best regards,

    -sbi

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

    On Wed, Feb 5, 2020 at 5:22 AM Pimolnat Suntian <pimolnat.s@outlook.com> wrote:
    Thank you so much. I registered on odoo-community.org. My account name is Pimolnat S.

    Regards,

    Pimolnat Suntian


    From: Stéphane Bidoul <stephane.bidoul@acsone.eu>
    Sent: Wednesday, February 5, 2020 3:47 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Proposing "Pimolnat" as PSC for Logistics
     
    Pimolnat could you register on odoo-community.org so I can add you to the team?

    Best regards,

    -sbi

    On Mon, Feb 3, 2020 at 3:27 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
    +1
    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236


    On Mon, Feb 3, 2020 at 2:22 AM <admin@ygol.com> wrote:
    +1

    --
    Yves Goldberg

    ----- Original message -----
    From: Kitti Upariphutthiphong <kittiu@ecosoft.co.th>
    Subject: Proposing "Pimolnat" as PSC for Logistics
    Date: Monday, February 03, 2020 08:57

    Dear community,

    I would like to propose my team member, Pimolnat, https://github.com/ps-tubtim, as the PSC of Logistics

    Pimpolnat has actively participate in OCA for various repository, and can be more focus on Logistics in helping in more reviews and migrations.

    Thank you!

    _______________________________________________


    _______________________________________________
    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

    _______________________________________________
    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 Stéphane Bidoul - 08:56 - 12 Feb 2020
  • RE: stock.picking very slow and some are not validating

    We have had similar – we have a client receiving ~400 lines on a PO. There are issues around average cost calculation. Our solution was to make the receipting a background process and receipt line by line – that way if anything happens to a product during the receipt cycle you don’t get a full roll back.

     

    Contact me below if you would like to discuss further.

     

     

    Regards

     

     

    Kevin McMenamin

    ERP Capability Manager, Solnet

     +64 22 651 3753 | +64 9 977 5805 | Visit our blog | Connect on LinkedIn

     

     

     

     

     

     

    From: MD Tanzilul Hasan Khan <ponkhi403@gmail.com>
    Sent: Monday, 3 February 2020 8:02 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: stock.picking very slow and some are not validating

     

    Hello Contributors,

     

    We are using Odoo 11 for a retail chain. They have over 60 POS locations (and increasing across the country) and over 17000 products (also increasing).

     

    Recently, for past two months, we are facing strange problem. The retail chain do purchase order once in a month to the vendor and the PO contains over hundreds of products. They are using lot based tracking. When we are receiving products with lot number it takes forever to validate. Even some pickings are stuck and can't be validated. We tried all the possible workarounds but still no luck. There are no errors too.

     

    The instance is running on AWS with RDS. RDS configuration:
    PostgreSQL - 10.10
    4 vcpu x 16 GB RAM
    100 GB SSD
    IOPS: 100 * 3 = 300

     

    How can we validate the stock.pickings? Any idea or thoughts appreciated.

     

    Best Regards,

    MD. Tanzilul Hasan Khan

    Attention: This email may contain information intended for the sole use of the original recipient. Please respect this when sharing or disclosing this email's contents with any third party. If you believe you have received this email in error, please delete it and notify the sender or postmaster@solnetsolutions.co.nz as soon as possible. The content of this email does not necessarily reflect the views of Solnet Solutions Ltd.

    by Kevin McMenamin - 08:51 - 12 Feb 2020
  • Re: Proposing Lois Rilo as PSC for server-ux
    +1

    On Wed, Feb 12, 2020 at 5:12 PM Jay Vora <vora.jay@serpentcs.com> wrote:
    +1

    On Wed, Feb 12, 2020 at 9:07 PM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
    Hi all,

    I would like to help maintain pulls requests and issues at server-ux. I've contributed as author and core maintainer of base_tier_validation and there are several related PR still open that I would like to push forward. I also contributed to document_quick_access addons and would like to help on migration and reviews.

    I see the only team with rights in that repo is "Tools maintainers". I wouldn't need to be part of such wide group, but I also understand that segregating the PSC teams even more is not a good approach for maintainability reasons. Any of those two options would be good for me.

    Regards,

    --
    Lois Rilo Antelo - Odoo consultant at ForgeFlow
    twitter: @LoisRForgeFlow

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



    --

    Technology Services @ www.serpentcs.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


     
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com

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



    --


    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Joël Grand-Guillaume
    Department Head
    Business Solutions

    +41 21 619 10 28



    by Joël Grand Guillaume - 05:20 - 12 Feb 2020
  • Re: Proposing Lois Rilo as PSC for server-ux
    👍

    On Wed, 12 Feb 2020 at 17:06, Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
    +1

    On 12 Feb 2020, at 08:56, Moises Lopez <moylop260@vauxoo.com> wrote:

    +1

    On Wed, Feb 12, 2020 at 9:37 AM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
    Hi all,

    I would like to help maintain pulls requests and issues at server-ux. I've contributed as author and core maintainer of base_tier_validation and there are several related PR still open that I would like to push forward. I also contributed to document_quick_access addons and would like to help on migration and reviews.

    I see the only team with rights in that repo is "Tools maintainers". I wouldn't need to be part of such wide group, but I also understand that segregating the PSC teams even more is not a good approach for maintainability reasons. Any of those two options would be good for me.

    Regards,


    --
    Lois Rilo Antelo - Odoo consultant at ForgeFlow
    twitter: @LoisRForgeFlow

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

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

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


    by Aarón Henríquez - 05:16 - 12 Feb 2020
  • Re: Proposing Lois Rilo as PSC for server-ux
    +1

    On Wed, Feb 12, 2020 at 9:07 PM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
    Hi all,

    I would like to help maintain pulls requests and issues at server-ux. I've contributed as author and core maintainer of base_tier_validation and there are several related PR still open that I would like to push forward. I also contributed to document_quick_access addons and would like to help on migration and reviews.

    I see the only team with rights in that repo is "Tools maintainers". I wouldn't need to be part of such wide group, but I also understand that segregating the PSC teams even more is not a good approach for maintainability reasons. Any of those two options would be good for me.

    Regards,

    --
    Lois Rilo Antelo - Odoo consultant at ForgeFlow
    twitter: @LoisRForgeFlow

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



    --

    Technology Services @ www.serpentcs.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


     
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com


    by Jay Vora - 05:11 - 12 Feb 2020
  • Re: Proposing Lois Rilo as PSC for server-ux
    +1

    On 12 Feb 2020, at 08:56, Moises Lopez <moylop260@vauxoo.com> wrote:

    +1

    On Wed, Feb 12, 2020 at 9:37 AM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
    Hi all,

    I would like to help maintain pulls requests and issues at server-ux. I've contributed as author and core maintainer of base_tier_validation and there are several related PR still open that I would like to push forward. I also contributed to document_quick_access addons and would like to help on migration and reviews.

    I see the only team with rights in that repo is "Tools maintainers". I wouldn't need to be part of such wide group, but I also understand that segregating the PSC teams even more is not a good approach for maintainability reasons. Any of those two options would be good for me.

    Regards,


    --
    Lois Rilo Antelo - Odoo consultant at ForgeFlow
    twitter: @LoisRForgeFlow

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

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


    by Alexey Pelykh <alexey.pelykh@gmail.com> - 05:06 - 12 Feb 2020
  • Re: Proposing Lois Rilo as PSC for server-ux


    On Wed, Feb 12, 2020 at 4:37 PM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
    Hi all,

    I would like to help maintain pulls requests and issues at server-ux. I've contributed as author and core maintainer of base_tier_validation and there are several related PR still open that I would like to push forward. I also contributed to document_quick_access addons and would like to help on migration and reviews.

    I see the only team with rights in that repo is "Tools maintainers". I wouldn't need to be part of such wide group, but I also understand that segregating the PSC teams even more is not a good approach for maintainability reasons. Any of those two options would be good for me.

    +1
     
    --

    by Alex Comba. - 05:06 - 12 Feb 2020
  • Re: Proposing Lois Rilo as PSC for server-ux
    +1

    On Wed, Feb 12, 2020 at 9:37 AM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
    Hi all,

    I would like to help maintain pulls requests and issues at server-ux. I've contributed as author and core maintainer of base_tier_validation and there are several related PR still open that I would like to push forward. I also contributed to document_quick_access addons and would like to help on migration and reviews.

    I see the only team with rights in that repo is "Tools maintainers". I wouldn't need to be part of such wide group, but I also understand that segregating the PSC teams even more is not a good approach for maintainability reasons. Any of those two options would be good for me.

    Regards,


    --
    Lois Rilo Antelo - Odoo consultant at ForgeFlow
    twitter: @LoisRForgeFlow

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

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

    by Moisés López Calderón - 04:55 - 12 Feb 2020
  • Re: Proposing Lois Rilo as PSC for server-ux
    +1
     
    Enric Tobella Alomar
    etobella@creublanca.es




    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 - 04:51 - 12 Feb 2020
  • Re: Proposing Lois Rilo as PSC for server-ux
    Great for me.

    by Pedro M. Baeza - 04:41 - 12 Feb 2020
  • Proposing Lois Rilo as PSC for server-ux
    Hi all,

    I would like to help maintain pulls requests and issues at server-ux. I've contributed as author and core maintainer of base_tier_validation and there are several related PR still open that I would like to push forward. I also contributed to document_quick_access addons and would like to help on migration and reviews.

    I see the only team with rights in that repo is "Tools maintainers". I wouldn't need to be part of such wide group, but I also understand that segregating the PSC teams even more is not a good approach for maintainability reasons. Any of those two options would be good for me.

    Regards,

    --
    Lois Rilo Antelo - Odoo consultant at ForgeFlow
    twitter: @LoisRForgeFlow

    by Lois Rilo Antelo - 04:35 - 12 Feb 2020
  • Re: Can Odoo create asset on Stock IN, instead on Invoice Post?
    Thank you Dominique,

    Thanks for the concise answer. Make sense to me ;)

    On Wed, Feb 12, 2020, 2:07 PM Dominique k <dominique.k@elico-corp.com.sg> wrote:
    my 2 cents:

    In general, I would say that odoo warehouse is for "Operations", such as trading, or logistic services. The warehouse module is not well suited for asset management, hence, creating a "financial asset" (meaning a depreciation board) from the incoming shipment does not seem a good idea:
    - if the business has genuine inventory, mixing asset with inventory items is a bit messy/chaotic
    - if the business does not use the inventory module (e.g. service company), then installing the warehouse module is an overkill

    Regards,


    On Wed, 12 Feb 2020 at 14:37, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    Hi community,

    As we know, about Asset in Odoo. Normally, asset is created when Invoice is posted.

    AFIK, other ERP system will create asset on Stock In. Which make more sense to me. What is your opinion about this?

    Are there OCA modules that did that?

    Thank you!

    _______________________________________________
    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 Kitti Upariphutthiphong - 01:51 - 12 Feb 2020
  • Re: Help on Email Marketing
    Hello Daniel,

    as far as i know, you could insert fields via website_builder..
    But my last looking after this app was a while ago..

    ___________________________________
    Maik Steinfeld

    Tel:     +49 (0) 3831 - 44557 - 00
    Mobil: +49 (0) 176 92 62 08 87
    E-Mail: m.steinfeld@intero-technologies.de

    Intero Technologies GmbH
    Heinrich-Heine-Ring 76
    D - 18435 Stralsund 
    Tel:    +49 (0) 3831 - 44 55 7 - 0
    Fax:   +49 (0) 3831 - 44 55 7 - 79 

    Internet: www.intero-technologies.de
    Facebook: facebook.com/interotechnologies

    Intero Technologies GmbH | Firmensitz: Stralsund, Heinrich-Heine-Ring 76, 18435 Stralsund , Deutschland | Registergericht: Amtsgericht Stralsund, HRB 7076 | Geschäftsführer: Frank Löffler, Lars Lifson | USt-Ident.Nr. DE 251251697

    This eMail and its content is dedicated to the intended recipient only. If you have received it in error please contact the sender immediately by fax or return eMail. Please then delete the eMail and any copies of it.


    Von: "Daniel Reis" <dgreis@sapo.pt>
    An: "Contributors" <contributors@odoo-community.org>
    Gesendet: Mittwoch, 12. Februar 2020 11:52:04
    Betreff: Help on Email Marketing

    Hello community,
    
    To be honest, the Email Marketing App is not something I have used before.
    I was expecting it to be like an upgraded version of email templates, 
    but AFAICS it uses a fixed QWeb template, and you can't add dynamic 
    fields, like the Contact's name of job/function.
    
    Am I missing something?
    If not, has anyone worked on some module to allow rendering dynamic 
    fields on the outgoing email, similarly to email templates?
    
    
    Thank is advance for your insights
    Daniel Reis
    

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



    by Maik Steinfeld - 12:16 - 12 Feb 2020
  • RE: Help on Email Marketing

    Please use like ${object.name} for name

     

    From: Daniel Reis <dgreis@sapo.pt>
    Sent: Wednesday, February 12, 2020 4:22 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: Help on Email Marketing

     

    Hello community,

     

    To be honest, the Email Marketing App is not something I have used before.

    I was expecting it to be like an upgraded version of email templates, 

    but AFAICS it uses a fixed QWeb template, and you can't add dynamic 

    fields, like the Contact's name of job/function.

     

    Am I missing something?

    If not, has anyone worked on some module to allow rendering dynamic 

    fields on the outgoing email, similarly to email templates?

     

     

    Thank is advance for your insights

    Daniel Reis


    by Manish Mannan - 12:15 - 12 Feb 2020
  • Help on Email Marketing
    Hello community,
    
    To be honest, the Email Marketing App is not something I have used before.
    I was expecting it to be like an upgraded version of email templates, 
    but AFAICS it uses a fixed QWeb template, and you can't add dynamic 
    fields, like the Contact's name of job/function.
    
    Am I missing something?
    If not, has anyone worked on some module to allow rendering dynamic 
    fields on the outgoing email, similarly to email templates?
    
    
    Thank is advance for your insights
    Daniel Reis
    

    by Daniel Reis <dgreis@sapo.pt> - 11:50 - 12 Feb 2020
  • Re: Can Odoo create asset on Stock IN, instead on Invoice Post?
    my 2 cents:

    In general, I would say that odoo warehouse is for "Operations", such as trading, or logistic services. The warehouse module is not well suited for asset management, hence, creating a "financial asset" (meaning a depreciation board) from the incoming shipment does not seem a good idea:
    - if the business has genuine inventory, mixing asset with inventory items is a bit messy/chaotic
    - if the business does not use the inventory module (e.g. service company), then installing the warehouse module is an overkill

    Regards,


    On Wed, 12 Feb 2020 at 14:37, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    Hi community,

    As we know, about Asset in Odoo. Normally, asset is created when Invoice is posted.

    AFIK, other ERP system will create asset on Stock In. Which make more sense to me. What is your opinion about this?

    Are there OCA modules that did that?

    Thank you!

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


    by dominique.k - 08:06 - 12 Feb 2020
  • Can Odoo create asset on Stock IN, instead on Invoice Post?
    Hi community,

    As we know, about Asset in Odoo. Normally, asset is created when Invoice is posted.

    AFIK, other ERP system will create asset on Stock In. Which make more sense to me. What is your opinion about this?

    Are there OCA modules that did that?

    Thank you!

    by Kitti Upariphutthiphong - 07:36 - 12 Feb 2020
  • Re: l10n-italy on apps.odoo.com
    Although I'm not anymore in charge of OCA's community management, I give a hand to my colleagues at board that are very busy with the rest of the OCA stuff (you should really apply in next votings for giving a hand too) for telling you that the problem are license conflicts:


  • l10n_it_fiscal_document_type: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    fiscal_epos_print: The license GPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_account_tax_kind: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_account_balance_report: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_causali_pagamento: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_website_sale_fiscalcode: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_vat_statement_communication: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_in_purchase is updated before its dependency l10n_it_fatturapa_in. Throw back to the end of the queue.
    l10n_it_withholding_tax_payment is updated before its dependency l10n_it_withholding_tax. Throw back to the end of the queue.
    l10n_it_fatturapa_export_zip is updated before its dependency l10n_it_fatturapa_out. Throw back to the end of the queue.
    l10n_it_invoices_data_communication: unmet dependency l10n_it_fiscal_document_type for series 12.0
    l10n_it_fatturapa_out_stamp is updated before its dependency l10n_it_fatturapa_out. Throw back to the end of the queue.
    l10n_it_fatturapa_out_wt is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_out_triple_discount is updated before its dependency l10n_it_fatturapa_out. Throw back to the end of the queue.
    l10n_it_fatturapa_in_rc is updated before its dependency l10n_it_fatturapa_in. Throw back to the end of the queue.
    l10n_it_corrispettivi_fatturapa_out is updated before its dependency l10n_it_fatturapa_out. Throw back to the end of the queue.
    l10n_it_website_sale_corrispettivi is updated before its dependency l10n_it_website_sale_fatturapa. Throw back to the end of the queue.
    l10n_it_sdi_channel is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_out is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_in is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_out_ddt: unmet dependency l10n_it_fatturapa_out for series 12.0
    l10n_it_website_portal_fatturapa is updated before its dependency l10n_it_fatturapa. Throw back to the end of the queue.
    l10n_it_fatturapa_pec: unmet dependency l10n_it_fatturapa_out for series 12.0
    l10n_it_fatturapa: unmet dependency l10n_it_account_tax_kind for series 12.0
    l10n_it_withholding_tax_causali is updated before its dependency l10n_it_withholding_tax. Throw back to the end of the queue.
    l10n_it_pos_fatturapa: unmet dependency l10n_it_fatturapa for series 12.0
    l10n_it_website_portal_fatturapa_sale: unmet dependency l10n_it_website_portal_fatturapa for series 12.0
    l10n_it_website_sale_fatturapa: unmet dependency l10n_it_fatturapa for series 12.0
    l10n_it_withholding_tax: unmet dependency l10n_it_fatturapa for series 12.0
    l10n_it_invoices_data_communication_fatturapa: unmet dependency l10n_it_invoices_data_communication for series 12.0

  • l10n_it_fiscal_document_type: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_account_tax_kind: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_withholding_tax_causali: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_in: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out_ddt: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_pec: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out_stamp: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_ddt_delivery: unmet dependency delivery_carrier_partner for series 11.0

  • account_invoice_entry_date: Module not installable
    l10n_it_prima_nota_cassa: Module not installable
    l10n_it_fiscal_document_type: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    account_invoice_sequential_dates: Module not installable
    l10n_it_base_crm: Module not installable
    account_central_journal: Module not installable
    l10n_it_partially_deductible_vat: Module not installable
    l10n_it_account_tax_kind: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_CEE_balance_generic: Module not installable
    l10n_it_bill_of_entry: Module not installable
    l10n_it_fatturapa: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_withholding_tax_causali: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    account_invoice_report_ddt_group: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_vat_registries_cash_basis: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_website_sale_fiscalcode: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_invoices_data_communication: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fiscalcode_invoice: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out_ddt: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_out_stamp: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply to the licenses compatibility. See our FAQ at https://apps.odoo.com/apps/faq#maintainer_faq_04 .
    l10n_it_fatturapa_in_rc is updated before its dependency l10n_it_fatturapa_in. Throw back to the end of the queue.
    l10n_it_fatturapa_in: unmet dependency l10n_it_withholding_tax_causali for series 10.0
    l10n_it_fatturapa_pec: unmet dependency l10n_it_fatturapa_in for series 10.0
    l10n_it_pos_fatturapa: unmet dependency pos_partner_firstname for series 10.0
    l10n_it_invoices_data_communication_fatturapa: unmet dependency l10n_it_invoices_data_communication for series 10.0
    l10n_it_fatturapa_in_purchase: unmet dependency l10n_it_fatturapa_in for series 10.0
    l10n_it_fatturapa_export_zip: unmet dependency l10n_it_fatturapa_in for series 10.0
    l10n_it_fatturapa_out_wt: unmet dependency l10n_it_withholding_tax_causali for series 10.0


by Pedro M. Baeza - 07:51 - 11 Feb 2020