Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • OCA 2020 AGA - starts next week with the Delegates Campaign

    Hello OCA Contributors,

    I hope this year has been treating you well. We are looking forward to seeing many of you online at the OCA Days next week.

    I am writing to let you know that the 2020 Annual General Assembly will commence on Monday 12th October:
    • the first step is for current paid members to apply for delegate candidacy 
    • following this the existing paid delegates will vote for 10 new delegates
    • once we have our new delegates, all delegates new and existing will be able to apply for OCA board candidacy and vote in the AGA.
    If this is something you have been thinking about please make sure your membership is up to date and look out for the details on how to apply as a delegate next week.

    Any questions, please get in touch.
    Warmest regards,
    Rebecca

    -- 
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 04:10 - 8 Oct 2020
  • New PMS Proposal

    Hi!

    We have been working for two years on a Property Management System on Odoo. These modules are used to manage reservations for establishments of all kinds, hotels, tourist apartments, rural houses...
    and we have 42 establishments in production for two years (including Sada Marina in Galicia where the OCA 2019 codesprint was made! ;)

    We are currently committed to a major refactoring and upgrade to V14 of the entire base, we are working on it, and we will have it ready for December.

    The work for December includes:

    1. Reservations Management
    2. Revenue Prices
    3. Onboard Services
    4. Completed generic API REST based on odoo-connectos -thanks!!- (availability, reservations, restrictions, partners, pricelists, smartlocks)
    5. Specific implementation API with Channel Manager Wubook (what allow us connect with booking.com, expedia and many other OTAs..
    6. Customer Portal for Pre-Check in and invoice wizard


    Specifically, this is the repository on which the refactoring is being worked: https://github.com/commitsun/pms

    The original repository, base for the refactoring and which is currently in production on V11 is: https://github.com/hootel/hootel

    The work will still be WIP for the OCA days, but it would make me very happy to see it at OCA from there.

    The current vertical-hotel repository is incompatible with the development of this pms, and although when we started working on this project, two years ago, we tried to do it from the current vertical hotel (of those not yet in OCA), we had to start from zero for not being able to make this development compatible with the structure and flows that we have been learning in the sector (for example, to connect it with sales channels such as booking.com, expedia, etc ...). I do not know if the option of having two independent repositories is valid, but it is the only one that occurs to me to be able to transfer this work to OCA.

    I hope it is possible to see a new pms repository in OCA from the 15th of this month, any doubt or question, you tell me



    Thank you very much for your attention and for all your work that has made this project possible!

    by Darío Lodeiros - 10:25 - 6 Oct 2020

    15 replies 15 replies

    • Re: New PMS Proposal
      Thanks Simone!
      I will create a 14.0 branch and a Pr with the current work on WIP.


      El mar., 20 oct. 2020 a las 16:47, Simone Orsi (<simahawk@gmail.com>) escribió:
      Hello Dario,


      There's no branch yet, you are free to set up the ones you like.

      You can bootstrap the repo using https://github.com/OCA/oca-addons-repo-template

      If you have any issues/questions let us know.

      Cheers,

      On Tue, Oct 6, 2020 at 10:26 PM dario <dario@commitsun.com> wrote:

      Hi!

      We have been working for two years on a Property Management System on Odoo. These modules are used to manage reservations for establishments of all kinds, hotels, tourist apartments, rural houses...
      and we have 42 establishments in production for two years (including Sada Marina in Galicia where the OCA 2019 codesprint was made! ;)

      We are currently committed to a major refactoring and upgrade to V14 of the entire base, we are working on it, and we will have it ready for December.

      The work for December includes:

      1. Reservations Management
      2. Revenue Prices
      3. Onboard Services
      4. Completed generic API REST based on odoo-connectos -thanks!!- (availability, reservations, restrictions, partners, pricelists, smartlocks)
      5. Specific implementation API with Channel Manager Wubook (what allow us connect with booking.com, expedia and many other OTAs..
      6. Customer Portal for Pre-Check in and invoice wizard


      Specifically, this is the repository on which the refactoring is being worked: https://github.com/commitsun/pms

      The original repository, base for the refactoring and which is currently in production on V11 is: https://github.com/hootel/hootel

      The work will still be WIP for the OCA days, but it would make me very happy to see it at OCA from there.

      The current vertical-hotel repository is incompatible with the development of this pms, and although when we started working on this project, two years ago, we tried to do it from the current vertical hotel (of those not yet in OCA), we had to start from zero for not being able to make this development compatible with the structure and flows that we have been learning in the sector (for example, to connect it with sales channels such as booking.com, expedia, etc ...). I do not know if the option of having two independent repositories is valid, but it is the only one that occurs to me to be able to transfer this work to OCA.

      I hope it is possible to see a new pms repository in OCA from the 15th of this month, any doubt or question, you tell me



      Thank you very much for your attention and for all your work that has made this project possible!

      _______________________________________________
      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, Freelance 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 dariodafoz - 08:45 - 21 Oct 2020
    • Re: New PMS Proposal
      +1 

      Rafael Blasco <rafael.blasco@tecnativa.com> schrieb am Do. 15. Okt. 2020 um 20:47:

      +1

       

      De: dario [mailto:dario@commitsun.com]
      Enviado el: martes, 6 de octubre de 2020 22:27
      Para: Contributors <contributors@odoo-community.org>
      Asunto: New PMS Proposal

       

      Hi!

      We have been working for two years on a Property Management System on Odoo. These modules are used to manage reservations for establishments of all kinds, hotels, tourist apartments, rural houses...
      and we have 42 establishments in production for two years (including Sada Marina in Galicia where the OCA 2019 codesprint was made! ;)

      We are currently committed to a major refactoring and upgrade to V14 of the entire base, we are working on it, and we will have it ready for December.

      The work for December includes:

      1. Reservations Management
      2. Revenue Prices
      3. Onboard Services
      4. Completed generic API REST based on odoo-connectos -thanks!!- (availability, reservations, restrictions, partners, pricelists, smartlocks)
      5. Specific implementation API with Channel Manager Wubook (what allow us connect with booking.com, expedia and many other OTAs..
      6. Customer Portal for Pre-Check in and invoice wizard


      Specifically, this is the repository on which the refactoring is being worked: https://github.com/commitsun/pms

      The original repository, base for the refactoring and which is currently in production on V11 is: https://github.com/hootel/hootel

      The work will still be WIP for the OCA days, but it would make me very happy to see it at OCA from there.

      The current vertical-hotel repository is incompatible with the development of this pms, and although when we started working on this project, two years ago, we tried to do it from the current vertical hotel (of those not yet in OCA), we had to start from zero for not being able to make this development compatible with the structure and flows that we have been learning in the sector (for example, to connect it with sales channels such as booking.com, expedia, etc ...). I do not know if the option of having two independent repositories is valid, but it is the only one that occurs to me to be able to transfer this work to OCA.

      I hope it is possible to see a new pms repository in OCA from the 15th of this month, any doubt or question, you tell me



      Thank you very much for your attention and for all your work that has made this project possible!

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

      --
      --
      facebook
      		twitter
      		linkedin

      Jens Holze

      Geschäftsführer (des besten Teams ever)

      bloopark systems GmbH & Co. KG

      		+49 391 563069-10
      		jholze@bloopark.de
      		www.bloopark.de
      		Beethovenstr. 4, 39106 Magdeburg
      by Jens Holze - 08:36 - 21 Oct 2020
    • Re: New PMS Proposal

      +1

      El 6/10/20 a las 22:26, dario escribió:

      Hi!

      We have been working for two years on a Property Management System on Odoo. These modules are used to manage reservations for establishments of all kinds, hotels, tourist apartments, rural houses...
      and we have 42 establishments in production for two years (including Sada Marina in Galicia where the OCA 2019 codesprint was made! ;)

      We are currently committed to a major refactoring and upgrade to V14 of the entire base, we are working on it, and we will have it ready for December.

      The work for December includes:

      1. Reservations Management
      2. Revenue Prices
      3. Onboard Services
      4. Completed generic API REST based on odoo-connectos -thanks!!- (availability, reservations, restrictions, partners, pricelists, smartlocks)
      5. Specific implementation API with Channel Manager Wubook (what allow us connect with booking.com, expedia and many other OTAs..
      6. Customer Portal for Pre-Check in and invoice wizard


      Specifically, this is the repository on which the refactoring is being worked: https://github.com/commitsun/pms

      The original repository, base for the refactoring and which is currently in production on V11 is: https://github.com/hootel/hootel

      The work will still be WIP for the OCA days, but it would make me very happy to see it at OCA from there.

      The current vertical-hotel repository is incompatible with the development of this pms, and although when we started working on this project, two years ago, we tried to do it from the current vertical hotel (of those not yet in OCA), we had to start from zero for not being able to make this development compatible with the structure and flows that we have been learning in the sector (for example, to connect it with sales channels such as booking.com, expedia, etc ...). I do not know if the option of having two independent repositories is valid, but it is the only one that occurs to me to be able to transfer this work to OCA.

      I hope it is possible to see a new pms repository in OCA from the 15th of this month, any doubt or question, you tell me



      Thank you very much for your attention and for all your work that has made this project possible!

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

      --
      Ignacio Ibeas
      Acysos S.L. (www.acysos.com)
      Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
      Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
      Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
      Github (http://www.github.com/acysos)
      Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
      C/ Miguel Astrain 18, 1º Oficina A
      31006 Pamplona, Navarra.
      ignacio@acysos.com
      Tel. 948238905
      ---------------------- // -------------------
      La información contenida en este mensaje de correo electrónico es
      confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
      acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
      persona a la que va dirigido, cualquier divulgación, copia o distribución de
      la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
      tomada o dejada de tomar basada en la información contenida en este mensaje
      queda prohibida y puede ser ilegal.
      The information in this e-mail is confidential and may be legally privileged.
      It is intended solely for the addressee. Access to this e-mail by anyone is
      unauthorised. If you are not the intended recipient, any disclousure,
      copying, distribuition or any action taken or omited to be taken in reliance
      on it, is prohibited and may be unlawful.
      by Ignacio Ibeas - 05:35 - 20 Oct 2020
    • Re: New PMS Proposal
      Hello Dario,


      There's no branch yet, you are free to set up the ones you like.

      You can bootstrap the repo using https://github.com/OCA/oca-addons-repo-template

      If you have any issues/questions let us know.

      Cheers,

      On Tue, Oct 6, 2020 at 10:26 PM dario <dario@commitsun.com> wrote:

      Hi!

      We have been working for two years on a Property Management System on Odoo. These modules are used to manage reservations for establishments of all kinds, hotels, tourist apartments, rural houses...
      and we have 42 establishments in production for two years (including Sada Marina in Galicia where the OCA 2019 codesprint was made! ;)

      We are currently committed to a major refactoring and upgrade to V14 of the entire base, we are working on it, and we will have it ready for December.

      The work for December includes:

      1. Reservations Management
      2. Revenue Prices
      3. Onboard Services
      4. Completed generic API REST based on odoo-connectos -thanks!!- (availability, reservations, restrictions, partners, pricelists, smartlocks)
      5. Specific implementation API with Channel Manager Wubook (what allow us connect with booking.com, expedia and many other OTAs..
      6. Customer Portal for Pre-Check in and invoice wizard


      Specifically, this is the repository on which the refactoring is being worked: https://github.com/commitsun/pms

      The original repository, base for the refactoring and which is currently in production on V11 is: https://github.com/hootel/hootel

      The work will still be WIP for the OCA days, but it would make me very happy to see it at OCA from there.

      The current vertical-hotel repository is incompatible with the development of this pms, and although when we started working on this project, two years ago, we tried to do it from the current vertical hotel (of those not yet in OCA), we had to start from zero for not being able to make this development compatible with the structure and flows that we have been learning in the sector (for example, to connect it with sales channels such as booking.com, expedia, etc ...). I do not know if the option of having two independent repositories is valid, but it is the only one that occurs to me to be able to transfer this work to OCA.

      I hope it is possible to see a new pms repository in OCA from the 15th of this month, any doubt or question, you tell me



      Thank you very much for your attention and for all your work that has made this project possible!

      _______________________________________________
      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, Freelance in love with open source.
      by Simone Orsi - 04:46 - 20 Oct 2020
    • RE: New PMS Proposal

      +1

       

      De: dario [mailto:dario@commitsun.com]
      Enviado el: martes, 6 de octubre de 2020 22:27
      Para: Contributors <contributors@odoo-community.org>
      Asunto: New PMS Proposal

       

      Hi!

      We have been working for two years on a Property Management System on Odoo. These modules are used to manage reservations for establishments of all kinds, hotels, tourist apartments, rural houses...
      and we have 42 establishments in production for two years (including Sada Marina in Galicia where the OCA 2019 codesprint was made! ;)

      We are currently committed to a major refactoring and upgrade to V14 of the entire base, we are working on it, and we will have it ready for December.

      The work for December includes:

      1. Reservations Management
      2. Revenue Prices
      3. Onboard Services
      4. Completed generic API REST based on odoo-connectos -thanks!!- (availability, reservations, restrictions, partners, pricelists, smartlocks)
      5. Specific implementation API with Channel Manager Wubook (what allow us connect with booking.com, expedia and many other OTAs..
      6. Customer Portal for Pre-Check in and invoice wizard


      Specifically, this is the repository on which the refactoring is being worked: https://github.com/commitsun/pms

      The original repository, base for the refactoring and which is currently in production on V11 is: https://github.com/hootel/hootel

      The work will still be WIP for the OCA days, but it would make me very happy to see it at OCA from there.

      The current vertical-hotel repository is incompatible with the development of this pms, and although when we started working on this project, two years ago, we tried to do it from the current vertical hotel (of those not yet in OCA), we had to start from zero for not being able to make this development compatible with the structure and flows that we have been learning in the sector (for example, to connect it with sales channels such as booking.com, expedia, etc ...). I do not know if the option of having two independent repositories is valid, but it is the only one that occurs to me to be able to transfer this work to OCA.

      I hope it is possible to see a new pms repository in OCA from the 15th of this month, any doubt or question, you tell me



      Thank you very much for your attention and for all your work that has made this project possible!

      by Rafael Blasco (Moduon) - 08:46 - 15 Oct 2020

  • OCA Days - Zoom hosts - we need your help
    Hello OCA Contributors,

    We need a bit of extra help for the OCA Days.

    We do need a few more hosts/moderators - basically we need two people on each track throughout the day (we have 2 tracks). The plan is to break this into 3-4 hour blocks through the day to share the load.

    We need one person to run the technical side and one person to moderate the talks.

    If you feel you are able to help out over the OCA Days to do this please get in touch ASAP and I will add you to the list.

    I look forward to hearing from you.
    Warm regards,
    Rebecca


    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 04:06 - 6 Oct 2020

    2 replies 2 replies

    • Re: OCA Days - Zoom hosts - we need your help
      Hi Rebecca,

      I could be available on 15th from 8h:30 to 13:30 preferably as techie..

      Regards,

      Laurent

      --
      Laurent Mignon
      Senior software engineer

      Tel: +32 2 8883148
      Email: laurent.mignon@acsone.eu

      Acsone sa/nv
      Waterloo Atrium | Drève Richelle 167/2 | B-1410 Waterloo

      Génie Civil du Val Benoit, Quai Banning 6 | B-4000 Liège 
      RPM Bruxelles 0835.207.216 RPR Brussel 

      Acsone SA, Succursale de Luxembourg
      22, Zone Industrielle
      | L-8287 Kehlen, Luxembourg
      TVA LU24733605
      | RCS B160400

      On Thu, Oct 8, 2020 at 12:47 AM Rebecca Gellatly <rebecca@o4sb.com> wrote:
      HI folks,

      Please see the link for the Hosts/Moderator/Techie schedule.

      I am guessing the best change over time of hosts will be during the breaks.
      Have a look and see what suits you best, we'll get some training/testing blocks set up over the next few days to go over things.

      Hopefully the spreadsheet is pretty clear - any questions  just ask.
      Once we have confirmed hosts I'll set up a separate email group.

      Thanks,
      Rebecca

      On Wed, Oct 7, 2020 at 3:05 AM Rebecca Gellatly <rebecca@o4sb.com> wrote:
      Hello OCA Contributors,

      We need a bit of extra help for the OCA Days.

      We do need a few more hosts/moderators - basically we need two people on each track throughout the day (we have 2 tracks). The plan is to break this into 3-4 hour blocks through the day to share the load.

      We need one person to run the technical side and one person to moderate the talks.

      If you feel you are able to help out over the OCA Days to do this please get in touch ASAP and I will add you to the list.

      I look forward to hearing from you.
      Warm regards,
      Rebecca


      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association


      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association

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

      by Laurent Mignon - 08:06 - 8 Oct 2020
    • Re: OCA Days - Zoom hosts - we need your help
      HI folks,

      Please see the link for the Hosts/Moderator/Techie schedule.

      I am guessing the best change over time of hosts will be during the breaks.
      Have a look and see what suits you best, we'll get some training/testing blocks set up over the next few days to go over things.

      Hopefully the spreadsheet is pretty clear - any questions  just ask.
      Once we have confirmed hosts I'll set up a separate email group.

      Thanks,
      Rebecca

      On Wed, Oct 7, 2020 at 3:05 AM Rebecca Gellatly <rebecca@o4sb.com> wrote:
      Hello OCA Contributors,

      We need a bit of extra help for the OCA Days.

      We do need a few more hosts/moderators - basically we need two people on each track throughout the day (we have 2 tracks). The plan is to break this into 3-4 hour blocks through the day to share the load.

      We need one person to run the technical side and one person to moderate the talks.

      If you feel you are able to help out over the OCA Days to do this please get in touch ASAP and I will add you to the list.

      I look forward to hearing from you.
      Warm regards,
      Rebecca


      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association


      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association
      by Rebecca Gellatly - 12:45 - 8 Oct 2020
  • [Delivery]: Scan packages instead of products in Shipping
    Hi all contributors, 

    In Odoo 13 CE, I have implemented the 3 steps delivery process.
    In this process we scan products or the picking itself in order to manage quantities...
    In Pack, products are packed in packages so that in Ship, operators should scan the packages and make sure everything is Ok. That is to say, at this level, operators shouldn't scan products of each package because: 

    1- Package is already done and Zebra labels are already printed and attached.
    2- Even if 1 is not done, scanning all products again is time consuming and should be held by package scanning only. (Each package has its EAN-13)

    I have searched in OCA modules for a module that meets this feature but couldn't find any. 
    Maybe i did not look well into the modules.. 
    Does anyone have an idea ? Any lead is appreciated.

    Regards.


    ᐧ
    by bdmibra - 11:30 - 5 Oct 2020

    1 replies 1 replies

  • black version upgrade for v14 ? 
    Hi contributors,

I have a question for you, before creating the 14.0 branches. (I hope
it will not degenerate into a religious war, but I want to ask
nevertheless :)

The black code formatter we use has a new version that, among other
fixes and improvements, resolves the infamous trailing comma issue
[1]. It also does some reformatting in the docstrings. When we use it,
it therefore applies some different code reformatting here and there.

In the long run, using it is definitely a good thing. In the short
term I'm not so sure, hence this message.

So I see 3 possibilities:

1. keep black to the same version in 13 and 14 and wait until black
hits 1.0 to upgrade

This is the less disruptive approach right now but we need to continue
coping with the trailing comma "bug". This postpones the moment when
we will need to decide between options 2 and 3 below (possibly
involving more branches).

2. upgrade black now in 13 and 14

We can automate that but it will have the drawback of making some
existing 13.0 green PRs unmergeable, requiring manual intervention on
them before merging.

3. upgrade black in 14 and keep 13 as is, let PSC upgrade manually in
13 if they want to.

With this approach there will be some code formatting differences
between branches 13 and 14 which may make code migration slightly more
difficult, and may create some cherry-pick conflicts in forward- and
backports.

What are your thoughts / vote? In doubt, update
.pre-commit-config.yaml in your favorite repo to replace 19.10b0 with
20.8b1 and run "pre-commit run -a" to see what it does exactly.

[Note A similar reasoning exists for prettier but it mostly impacts
javascript-heavy repos only. So there I believe it's ok to upgrade
prettier in 14 and keep it as is in 13, especially since there were
some hacks necessary to use it in 13 that we don't want to carry over
in 14]

-sbi

[1] https://black.readthedocs.io/en/stable/the_black_code_style.html?highlight=comma#the-magic-trailing-comma
    by Stéphane Bidoul - 02:21 - 4 Oct 2020

    11 replies 11 replies

    • Re: black version upgrade for v14 ?
      So 3 it is.

      Thanks for the feedback. I'll create the branches tomorrow.

      -sbi

      Le lun. 5 oct. 2020 à 20:12, Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com.mx> a écrit :
      +1, I agree with #3


      El dom., 4 de oct. de 2020 a la(s) 23:41, Saran Limpajitkutaporn (saranl@ecosoft.co.th) escribió:
      +1, I agree with #3

      On Mon, Oct 5, 2020 at 7:12 AM Jean-Charles Drubay <jc@komit-consulting.com> wrote:
      +1 for #3


      On Sun, Oct 4, 2020 at 9:32 PM Simone Orsi <simahawk@gmail.com> wrote:
      +1 for #3

      On Sun, Oct 4, 2020, 14:22 Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Hi contributors,

I have a question for you, before creating the 14.0 branches. (I hope
it will not degenerate into a religious war, but I want to ask
nevertheless :)

The black code formatter we use has a new version that, among other
fixes and improvements, resolves the infamous trailing comma issue
[1]. It also does some reformatting in the docstrings. When we use it,
it therefore applies some different code reformatting here and there.

In the long run, using it is definitely a good thing. In the short
term I'm not so sure, hence this message.

So I see 3 possibilities:

1. keep black to the same version in 13 and 14 and wait until black
hits 1.0 to upgrade

This is the less disruptive approach right now but we need to continue
coping with the trailing comma "bug". This postpones the moment when
we will need to decide between options 2 and 3 below (possibly
involving more branches).

2. upgrade black now in 13 and 14

We can automate that but it will have the drawback of making some
existing 13.0 green PRs unmergeable, requiring manual intervention on
them before merging.

3. upgrade black in 14 and keep 13 as is, let PSC upgrade manually in
13 if they want to.

With this approach there will be some code formatting differences
between branches 13 and 14 which may make code migration slightly more
difficult, and may create some cherry-pick conflicts in forward- and
backports.

What are your thoughts / vote? In doubt, update
.pre-commit-config.yaml in your favorite repo to replace 19.10b0 with
20.8b1 and run "pre-commit run -a" to see what it does exactly.

[Note A similar reasoning exists for prettier but it mostly impacts
javascript-heavy repos only. So there I believe it's ok to upgrade
prettier in 14 and keep it as is in 13, especially since there were
some hacks necessary to use it in 13 that we don't want to carry over
in 14]

-sbi

[1] https://black.readthedocs.io/en/stable/the_black_code_style.html?highlight=comma#the-magic-trailing-comma

      _______________________________________________
      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 - 10:05 - 5 Oct 2020
    • Re: black version upgrade for v14 ?
      +1, I agree with #3


      El dom., 4 de oct. de 2020 a la(s) 23:41, Saran Limpajitkutaporn (saranl@ecosoft.co.th) escribió:
      +1, I agree with #3

      On Mon, Oct 5, 2020 at 7:12 AM Jean-Charles Drubay <jc@komit-consulting.com> wrote:
      +1 for #3


      On Sun, Oct 4, 2020 at 9:32 PM Simone Orsi <simahawk@gmail.com> wrote:
      +1 for #3

      On Sun, Oct 4, 2020, 14:22 Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Hi contributors,

I have a question for you, before creating the 14.0 branches. (I hope
it will not degenerate into a religious war, but I want to ask
nevertheless :)

The black code formatter we use has a new version that, among other
fixes and improvements, resolves the infamous trailing comma issue
[1]. It also does some reformatting in the docstrings. When we use it,
it therefore applies some different code reformatting here and there.

In the long run, using it is definitely a good thing. In the short
term I'm not so sure, hence this message.

So I see 3 possibilities:

1. keep black to the same version in 13 and 14 and wait until black
hits 1.0 to upgrade

This is the less disruptive approach right now but we need to continue
coping with the trailing comma "bug". This postpones the moment when
we will need to decide between options 2 and 3 below (possibly
involving more branches).

2. upgrade black now in 13 and 14

We can automate that but it will have the drawback of making some
existing 13.0 green PRs unmergeable, requiring manual intervention on
them before merging.

3. upgrade black in 14 and keep 13 as is, let PSC upgrade manually in
13 if they want to.

With this approach there will be some code formatting differences
between branches 13 and 14 which may make code migration slightly more
difficult, and may create some cherry-pick conflicts in forward- and
backports.

What are your thoughts / vote? In doubt, update
.pre-commit-config.yaml in your favorite repo to replace 19.10b0 with
20.8b1 and run "pre-commit run -a" to see what it does exactly.

[Note A similar reasoning exists for prettier but it mostly impacts
javascript-heavy repos only. So there I believe it's ok to upgrade
prettier in 14 and keep it as is in 13, especially since there were
some hacks necessary to use it in 13 that we don't want to carry over
in 14]

-sbi

[1] https://black.readthedocs.io/en/stable/the_black_code_style.html?highlight=comma#the-magic-trailing-comma

      _______________________________________________
      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 Jesús Alan Ramos Rodriguez - 08:10 - 5 Oct 2020
    • Re: black version upgrade for v14 ?
      +1, I agree with #3

      On Mon, Oct 5, 2020 at 7:12 AM Jean-Charles Drubay <jc@komit-consulting.com> wrote:
      +1 for #3


      On Sun, Oct 4, 2020 at 9:32 PM Simone Orsi <simahawk@gmail.com> wrote:
      +1 for #3

      On Sun, Oct 4, 2020, 14:22 Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Hi contributors,

I have a question for you, before creating the 14.0 branches. (I hope
it will not degenerate into a religious war, but I want to ask
nevertheless :)

The black code formatter we use has a new version that, among other
fixes and improvements, resolves the infamous trailing comma issue
[1]. It also does some reformatting in the docstrings. When we use it,
it therefore applies some different code reformatting here and there.

In the long run, using it is definitely a good thing. In the short
term I'm not so sure, hence this message.

So I see 3 possibilities:

1. keep black to the same version in 13 and 14 and wait until black
hits 1.0 to upgrade

This is the less disruptive approach right now but we need to continue
coping with the trailing comma "bug". This postpones the moment when
we will need to decide between options 2 and 3 below (possibly
involving more branches).

2. upgrade black now in 13 and 14

We can automate that but it will have the drawback of making some
existing 13.0 green PRs unmergeable, requiring manual intervention on
them before merging.

3. upgrade black in 14 and keep 13 as is, let PSC upgrade manually in
13 if they want to.

With this approach there will be some code formatting differences
between branches 13 and 14 which may make code migration slightly more
difficult, and may create some cherry-pick conflicts in forward- and
backports.

What are your thoughts / vote? In doubt, update
.pre-commit-config.yaml in your favorite repo to replace 19.10b0 with
20.8b1 and run "pre-commit run -a" to see what it does exactly.

[Note A similar reasoning exists for prettier but it mostly impacts
javascript-heavy repos only. So there I believe it's ok to upgrade
prettier in 14 and keep it as is in 13, especially since there were
some hacks necessary to use it in 13 that we don't want to carry over
in 14]

-sbi

[1] https://black.readthedocs.io/en/stable/the_black_code_style.html?highlight=comma#the-magic-trailing-comma

      _______________________________________________
      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 saranl - 06:40 - 5 Oct 2020
    • Re: black version upgrade for v14 ?
      +1 for #3


      On Sun, Oct 4, 2020 at 9:32 PM Simone Orsi <simahawk@gmail.com> wrote:
      +1 for #3

      On Sun, Oct 4, 2020, 14:22 Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Hi contributors,

I have a question for you, before creating the 14.0 branches. (I hope
it will not degenerate into a religious war, but I want to ask
nevertheless :)

The black code formatter we use has a new version that, among other
fixes and improvements, resolves the infamous trailing comma issue
[1]. It also does some reformatting in the docstrings. When we use it,
it therefore applies some different code reformatting here and there.

In the long run, using it is definitely a good thing. In the short
term I'm not so sure, hence this message.

So I see 3 possibilities:

1. keep black to the same version in 13 and 14 and wait until black
hits 1.0 to upgrade

This is the less disruptive approach right now but we need to continue
coping with the trailing comma "bug". This postpones the moment when
we will need to decide between options 2 and 3 below (possibly
involving more branches).

2. upgrade black now in 13 and 14

We can automate that but it will have the drawback of making some
existing 13.0 green PRs unmergeable, requiring manual intervention on
them before merging.

3. upgrade black in 14 and keep 13 as is, let PSC upgrade manually in
13 if they want to.

With this approach there will be some code formatting differences
between branches 13 and 14 which may make code migration slightly more
difficult, and may create some cherry-pick conflicts in forward- and
backports.

What are your thoughts / vote? In doubt, update
.pre-commit-config.yaml in your favorite repo to replace 19.10b0 with
20.8b1 and run "pre-commit run -a" to see what it does exactly.

[Note A similar reasoning exists for prettier but it mostly impacts
javascript-heavy repos only. So there I believe it's ok to upgrade
prettier in 14 and keep it as is in 13, especially since there were
some hacks necessary to use it in 13 that we don't want to carry over
in 14]

-sbi

[1] https://black.readthedocs.io/en/stable/the_black_code_style.html?highlight=comma#the-magic-trailing-comma

      _______________________________________________
      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 Jean-Charles Drubay - 02:10 - 5 Oct 2020
    • Re: black version upgrade for v14 ?
      +1 for #3

      On Sun, Oct 4, 2020, 14:22 Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Hi contributors,

I have a question for you, before creating the 14.0 branches. (I hope
it will not degenerate into a religious war, but I want to ask
nevertheless :)

The black code formatter we use has a new version that, among other
fixes and improvements, resolves the infamous trailing comma issue
[1]. It also does some reformatting in the docstrings. When we use it,
it therefore applies some different code reformatting here and there.

In the long run, using it is definitely a good thing. In the short
term I'm not so sure, hence this message.

So I see 3 possibilities:

1. keep black to the same version in 13 and 14 and wait until black
hits 1.0 to upgrade

This is the less disruptive approach right now but we need to continue
coping with the trailing comma "bug". This postpones the moment when
we will need to decide between options 2 and 3 below (possibly
involving more branches).

2. upgrade black now in 13 and 14

We can automate that but it will have the drawback of making some
existing 13.0 green PRs unmergeable, requiring manual intervention on
them before merging.

3. upgrade black in 14 and keep 13 as is, let PSC upgrade manually in
13 if they want to.

With this approach there will be some code formatting differences
between branches 13 and 14 which may make code migration slightly more
difficult, and may create some cherry-pick conflicts in forward- and
backports.

What are your thoughts / vote? In doubt, update
.pre-commit-config.yaml in your favorite repo to replace 19.10b0 with
20.8b1 and run "pre-commit run -a" to see what it does exactly.

[Note A similar reasoning exists for prettier but it mostly impacts
javascript-heavy repos only. So there I believe it's ok to upgrade
prettier in 14 and keep it as is in 13, especially since there were
some hacks necessary to use it in 13 that we don't want to carry over
in 14]

-sbi

[1] https://black.readthedocs.io/en/stable/the_black_code_style.html?highlight=comma#the-magic-trailing-comma

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

      by Simone Orsi - 04:30 - 4 Oct 2020

  • New PSC: Animal
    Hello,

    I need to manage a pets register in my neighborhood with information like species, races, size, color, name, photo and owner. I didn't find anything in the OCA or maybe I missed something...

    Is anyone interested to contribute? I think we could host modules for veterinarians, petcare businesses, zoos, circuses, farms, national parks, etc...

    What do you think?

    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
    by Maxime Chambreuil - 08:25 - 3 Oct 2020

    4 replies 4 replies

  • [26137] Usage of Py3o templating engine in Odoo projects 
    Dear contributors,
we wanted to have the ability to generate sales and invoice documents 
based on document templates in one of our Odoo projects.
For this purpose, we decided to give the template engine Py3o a try. In 
the end, we came up with some questions
we would like to ask you.


* Have you been able to realize a similar workflow compared to the 
application Microsoft Sharepoint? If that is the case, how did you do this?
* What means did you use the store the data Py3o needs to access during 
filling the template?
* In which way did you store an already generated generated report?

We are looking forward to your feedback and thank you for this in advance.

Best regards,
Manuel


-- 
Mit freundlichen Grüßen

Manuel Engel
Trainee Anwendungsentwicklung


initOS GmbH
An der Eisenbahn 1
21224 Rosengarten

Phone:   +49 4105 56156-22
Fax:     +49 4105 56156-10

Email:   manuel.engel@initos.com
Web:     http://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 Manuel Engel - 02:15 - 2 Oct 2020

    1 replies 1 replies

    • Re: [26137] Usage of Py3o templating engine in Odoo projects 
      Thanks Manuel, 

to clarify the questions at stake of my colleague a bit more precise:

An ERP-System is meant to be the single source of truth.
That's why we we would ideally retain all the structured data
components (e.g. price, uom,...) that go into a Py3o report in the
first place parsed back in the ERP-system (of course with changed
content if it got changed in the Word / LibreOffice world). 

Actually this is what Sharepoint is trying to cover. So our questions
are:

Are there use cases out there that use Py3o to generate odt documents,
let the user manipulate its content in a visual way and store back at
least the structured part of the information "on safe" in the system
and if yes where an how?

For now and for us Py3o is seems to be too clumsy for that and the
technical challenges to solve too vast so that we can hardly imagine
that somebody ever tried to use it in such a use case, but we are
definitely eager to know and would love to hear about alternatives.

An no doing the entire unstructured part of a potential report document
in 1..n text field in the Odoo backend isn't a really god idea either,
we think.

Best Frederik

Am Freitag, den 02.10.2020, 12:16 +0000 schrieb Manuel Engel:

> Dear contributors,

> we wanted to have the ability to generate sales and invoice

> documents 

> based on document templates in one of our Odoo projects.

> For this purpose, we decided to give the template engine Py3o a try.

> In 

> the end, we came up with some questions

> we would like to ask you.

> 

> 

> * Have you been able to realize a similar workflow compared to the 

> application Microsoft Sharepoint? If that is the case, how did you do

> this?

> * What means did you use the store the data Py3o needs to access

> during 

> filling the template?

> * In which way did you store an already generated generated report?

> 

> We are looking forward to your feedback and thank you for this in

> advance.

> 

> Best regards,

> Manuel

> 

> 

> -- 

> Mit freundlichen Grüßen

> 

> Manuel Engel

> Trainee Anwendungsentwicklung

> 

> 

> initOS GmbH

> An der Eisenbahn 1

> 21224 Rosengarten

> 

> Phone:   +49 4105 56156-22

> Fax:     +49 4105 56156-10

> 

> Email:   manuel.engel@initos.com

> Web:     http://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

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

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
      by Frederik Kramer - 03:26 - 2 Oct 2020
  • Functional question : how to add reminder fee with account_credit_control?
    Hello,

    I'd like to know if it's possible to add reminder fee to an open invoiced, when I already sent reminders through the account_credit_control module?
    (for Odoo Commynity version 9)

    It seems impossible. When I click on "cancel", I got this message:
    "You cannot cancel this invoice.
    A payment reminder has already been sent to the customer.
    You must create a credit note and issue a new invoice."

    What would be the right process?
    It seems heavy to create a specific invoice only to charge the customer with the reminder fees.

    But he's non installable.

    Or do you use other reminder tools?
    The one from Alexis (https://github.com/akretion/overdue-reminder)? I don't see such functionnality (yet?).

    Thanks for your feedback!
    --
    Virginie
    0477/64.17.20

    by Virginie Dewulf. - 11:11 - 2 Oct 2020

    1 replies 1 replies

  • V14.0 branches 
    Hi all,

do somebody knows when the 14.0 branches will be created, is there some
work that needs to be done on the generation script?



Regards, 
Mihai Fekete

NextERP Romania S.R.L.
600B, Peciu Nou, Romania

E-mail: feketemihai@nexterp.ro
Telefon: 0788-749989
Website: https://nexterp.ro id="-x-evo-selection-start-marker">
    by Mihai Fekete - 06:26 - 1 Oct 2020

    1 replies 1 replies

  • Pull request modifying two modules? 
    Hello,

Is the Odoo bot capable handle a PR changing more than one module?
For example, if I add a fix involving two modules at the same time, will 
it be able to properly bump the versions of both of them?

Asking for a friend. (Not really.)

Thanks
Daniel
    by Daniel Reis - 05:05 - 1 Oct 2020

    3 replies 3 replies

    • Re: Pull request modifying two modules?
      Yeah, of course there are scenarios where it makes sense to not split the PR, so go ahead!

      Regards.
      by Pedro M. Baeza - 05:55 - 1 Oct 2020
    • Re: Pull request modifying two modules? 
      Thank you Pedro, I'll be sure to let my friend know that ;-)

Seriously now, it is a fix in two closely related modules, and I don't 
see a case where one could be merged and the other not.
Two PRs world would be more confusing than helpful.
Still, making it in separate commits seems wise advice.

Thanks
Daniel


On 01/10/2020 16:12, Pedro M. Baeza (Tecnativa) wrote:

> Yes, bot does it correctly thanks to the great work of Stephane Bidoul :)

>

> Now, about the guidelines, you can do that on a PR if the task is very 

> related. Think if a separation in several commits is advisable or not 

> anyway.

>

> Regards.

>

> _______________________________________________

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

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

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

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

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

>
      by Daniel Reis - 05:50 - 1 Oct 2020
    • Re: Pull request modifying two modules?
      Yes, bot does it correctly thanks to the great work of Stephane Bidoul :)

      Now, about the guidelines, you can do that on a PR if the task is very related. Think if a separation in several commits is advisable or not anyway.

      Regards.
      by Pedro M. Baeza - 05:11 - 1 Oct 2020
  • Embed existing PDF into QWeb report 
    Dear contributors,

i have a client that requests to add their terms and conditions* as part
of the order report as the last page, but they have some order specific
data and specific styling around, so I can’t just append static pages at
the end of the report.

I am looking for a solution to embed PDF* into the QWeb report.
Quick search on the internet gave no result.

My best bet idea (not yet tested however) would be to convert the PDF to
embed into SVG and embed this and try out if wkhtmltopdf can handle this.

Any better ideas?

Bonus question:
Is there something readymade to append existing PDF to the PDF generated
by QWeb reports?

Thanks. Regards, Peter




* Terms and conditions is a PDF document I could store as attachment or
static file into the module in this case.
    by Pete Hahn - 02:10 - 1 Oct 2020

    7 replies 7 replies

  • Snippet examples
    Hi

    This might be the wrong email list but pointers appreciated...

    Working on a small website project and one requirement is making a page with some airbnb properties. So I was adding the HTML from Airbnb for each one, but it is cumbersome so I wanted to make a snippet where one could edit the description and the property ID. But I have not been able to find a working description of how to create a snippet for the website builder, let alone one that has editable properties like that. An alternative to adding each property as a snippet would be to make a domain object with the info and then display that on a page, but have not come across any easy examples of web views for that either...

    Torvald Baade Bringsvor
    Bringsvor Consulting AS - Consulting and Odoo implementor

    Tel (+47) 4548 2848
    by Torvald Bringsvor - 10:56 - 1 Oct 2020

    4 replies 4 replies

    • Re: Snippet examples
      Hi Simone

      Yes, I have seen it but I got a bit lost at the options. The thing is that my data is so static that it could just as well be entered by the website editor, but I'm not sure if I can do that, technically. So I think I will follow the route of the Odoo Experience presentation and render the data serverside.

      -Torvald


      fre. 2. okt. 2020 kl. 06:57 skrev Simone Orsi <simahawk@gmail.com>:

      On Thu, Oct 1, 2020 at 10:57 AM Torvald Baade Bringsvor <torvald@bringsvor.com> wrote:
      Hi

      This might be the wrong email list but pointers appreciated...

      Working on a small website project and one requirement is making a page with some airbnb properties. So I was adding the HTML from Airbnb for each one, but it is cumbersome so I wanted to make a snippet where one could edit the description and the property ID. But I have not been able to find a working description of how to create a snippet for the website builder, let alone one that has editable properties like that. An alternative to adding each property as a snippet would be to make a domain object with the info and then display that on a page, but have not come across any easy examples of web views for that either...

      Torvald Baade Bringsvor
      Bringsvor Consulting AS - Consulting and Odoo implementor

      Tel (+47) 4548 2848

      _______________________________________________
      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, Freelance 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 Torvald Bringsvor - 11:16 - 4 Oct 2020
    • Re: Snippet examples

      On Thu, Oct 1, 2020 at 10:57 AM Torvald Baade Bringsvor <torvald@bringsvor.com> wrote:
      Hi

      This might be the wrong email list but pointers appreciated...

      Working on a small website project and one requirement is making a page with some airbnb properties. So I was adding the HTML from Airbnb for each one, but it is cumbersome so I wanted to make a snippet where one could edit the description and the property ID. But I have not been able to find a working description of how to create a snippet for the website builder, let alone one that has editable properties like that. An alternative to adding each property as a snippet would be to make a domain object with the info and then display that on a page, but have not come across any easy examples of web views for that either...

      Torvald Baade Bringsvor
      Bringsvor Consulting AS - Consulting and Odoo implementor

      Tel (+47) 4548 2848

      _______________________________________________
      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, Freelance in love with open source.
      by Simone Orsi - 06:56 - 2 Oct 2020
    • Re: Snippet examples
      Thanks Benjamin. I'm a bit rusty on the Odoo development these days, guess it's time to get back in the game.

      You mean a snippet like this could live in the OCA/website repo somewhere? Ok, will have a look.

      And thanks for the info on the talk, I am attending the Odoo XP so will check that out.

      -Torvald




      tor. 1. okt. 2020 kl. 11:17 skrev Benjamin Brich <b.brich@humanilog.org>:

      Hi Torvald,

       

      You can check this repo to get some inspiration: https://github.com/OCA/website/ There are a couple of great examples for building snippets.

       

      Furthermore there is a talk about ‘How to develop Building Blocks’ today at 5 pm CET live @ odoo xp.

       

      I hope this helps. Don’t forget the issue and PR for your new snippet in the github repo.

       

      warm Regards

       

      Ben

       

      Benjamin Brich
      Humanitarian Logistics Organisation e.V. (HLO)
      Phone: +49 40 228686751
      Cell: +49 160 97467007
      b.brich@humanilog.org

      Winsbergring 2
      22525 Hamburg
      Germany

      www.humanilog.org

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

      by Torvald Bringsvor - 11:36 - 1 Oct 2020
    • AW: Snippet examples

      Hi Torvald,

       

      You can check this repo to get some inspiration: https://github.com/OCA/website/ There are a couple of great examples for building snippets.

       

      Furthermore there is a talk about ‘How to develop Building Blocks’ today at 5 pm CET live @ odoo xp.

       

      I hope this helps. Don’t forget the issue and PR for your new snippet in the github repo.

       

      warm Regards

       

      Ben

       

      Benjamin Brich
      Humanitarian Logistics Organisation e.V. (HLO)
      Phone: +49 40 228686751
      Cell: +49 160 97467007
      b.brich@humanilog.org

      Winsbergring 2
      22525 Hamburg
      Germany

      www.humanilog.org

      by Benjamin Brich - 11:16 - 1 Oct 2020
  • RFQ for OCA Days 2020 Video Post Production
    Hello OCA Contributors,

    As you know the OCA Days 2020 Online are coming up.

    Please find attached the RFQ for Video Post Production - it is a quick turnaround with quotes due in by October 7th.

    We look forward to hearing from you.
    Warmest regards,
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 07:36 - 30 Sep 2020

    1 attachments 1 attachments

    RFQ - OCA Days Video Post Production.pdf
  • Modules migration v14
    Hi all,

    When I see this commit https://github.com/odoo/odoo/commit/6835aeb0de6895f7f4d6b23e0b4654465ef21d6a I ask myself if this can lead to an opportunity to have dedicated tool (library) to automate some migration tasks in our OCA modules.

    At least the execution of this kind of tool could be executed locally during manual migration, then manual checks, fix and manual commit.

    I know there are individual initiatives on this topic but I think it could go under the OCA umbrella and be promoted in the migration guide.

    What do you think?

    What are the existing libraries ? Which one could go towards OCA ?

    Thanks for your idea

    Regards

    David BEAL - akretion.com
    Consultant
    Odoo Intégration / Développement
    by David BEAL - 03:45 - 30 Sep 2020

    7 replies 7 replies

    • Re: Modules migration v14

      On Wed, Sep 30, 2020 at 4:22 PM Houssine BAKKALI <houssine@coopiteasy.be> wrote:

      +1

      On 30/09/2020 16:12, Frederik Kramer wrote:
      +1 already shared it in my team!

Am Mittwoch, den 30.09.2020, 14:07 +0000 schrieb Simone Orsi:


> https://pypi.org/project/odoo-module-migrator/


> 


> I tried it a bunch of times and it definitely does the dirty job. 


> We should work on a roadmap and give it some love.


> 


> Thanks Sylvain, BTW :)


> 


> On Wed, Sep 30, 2020 at 3:52 PM Alexandre Fayolle <


> alexandre.fayolle@camptocamp.com> wrote:


> > Sylvain Legal started something, if I remember well.


> > 


> > 


> > 


> > On 30/09/2020 15:46, David Beal wrote:


> > 


> > 


> > > Hi all,


> > 


> > 


> > > 


> > 


> > 


> > > When I see this commit


> > 


> > 


> > > 


> > https://github.com/odoo/odoo/commit/6835aeb0de6895f7f4d6b23e0b4654465ef21d6a


> > 


> > 


> > > I ask myself if this can lead to an opportunity to have dedicated


> > tool


> > 


> > 


> > > (library) to automate some migration tasks in our OCA modules.


> > 


> > 


> > > 


> > 


> > 


> > > At least the execution of this kind of tool could be executed


> > locally


> > 


> > 


> > > during manual migration, then manual checks, fix and manual


> > commit.


> > 


> > 


> > > 


> > 


> > 


> > > I know there are individual initiatives on this topic but I think


> > it


> > 


> > 


> > > could go under the OCA umbrella and be promoted in the migration


> > guide.


> > 


> > 


> > > 


> > 


> > 


> > > What do you think?


> > 


> > 


> > > 


> > 


> > 


> > > What are the existing libraries ? Which one could go towards OCA


> > ?


> > 


> > 


> > > 


> > 


> > 


> > > Thanks for your idea


> > 


> > 


> > > 


> > 


> > 


> > > Regards


> > 


> > 


> > > 


> > 


> > 


> > > David BEAL - akretion.com <http://akretion.com>


> > 


> > 


> > > Consultant


> > 


> > 


> > > Odoo Intégration / Développement


> > 


> > 


> > > 


> > 


> > 


> > > _______________________________________________


> > 


> > 


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


> > 


> > 


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


> > 


> > 


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


> > 


> > 


> > > 


> > 


> > 


> > 


> > 


> > -- 


> > Alexandre Fayolle


> > Chef de Projet


> > Tel : +33 4 58 48 20 30


> > 


> > Camptocamp France SAS


> > 18 rue du Lac Saint André


> > 73 370 Le Bourget-du-Lac


> > France


> > 


> > http://www.camptocamp.com


> > _______________________________________________


> > 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
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe



      Avast logo

      This email has been checked for viruses by Avast antivirus software.
      www.avast.com


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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, Freelance in love with open source.
      by Simone Orsi - 04:51 - 30 Sep 2020
    • Re: Modules migration v14

      +1

      On 30/09/2020 16:12, Frederik Kramer wrote:
      +1 already shared it in my team!

Am Mittwoch, den 30.09.2020, 14:07 +0000 schrieb Simone Orsi:

> https://pypi.org/project/odoo-module-migrator/

> 

> I tried it a bunch of times and it definitely does the dirty job. 

> We should work on a roadmap and give it some love.

> 

> Thanks Sylvain, BTW :)

> 

> On Wed, Sep 30, 2020 at 3:52 PM Alexandre Fayolle <

> alexandre.fayolle@camptocamp.com> wrote:

> > Sylvain Legal started something, if I remember well.

> > 

> > 

> > 

> > On 30/09/2020 15:46, David Beal wrote:

> > 

> > 

> > > Hi all,

> > 

> > 

> > > 

> > 

> > 

> > > When I see this commit

> > 

> > 

> > > 

> > https://github.com/odoo/odoo/commit/6835aeb0de6895f7f4d6b23e0b4654465ef21d6a

> > 

> > 

> > > I ask myself if this can lead to an opportunity to have dedicated

> > tool

> > 

> > 

> > > (library) to automate some migration tasks in our OCA modules.

> > 

> > 

> > > 

> > 

> > 

> > > At least the execution of this kind of tool could be executed

> > locally

> > 

> > 

> > > during manual migration, then manual checks, fix and manual

> > commit.

> > 

> > 

> > > 

> > 

> > 

> > > I know there are individual initiatives on this topic but I think

> > it

> > 

> > 

> > > could go under the OCA umbrella and be promoted in the migration

> > guide.

> > 

> > 

> > > 

> > 

> > 

> > > What do you think?

> > 

> > 

> > > 

> > 

> > 

> > > What are the existing libraries ? Which one could go towards OCA

> > ?

> > 

> > 

> > > 

> > 

> > 

> > > Thanks for your idea

> > 

> > 

> > > 

> > 

> > 

> > > Regards

> > 

> > 

> > > 

> > 

> > 

> > > David BEAL - akretion.com <http://akretion.com>

> > 

> > 

> > > Consultant

> > 

> > 

> > > Odoo Intégration / Développement

> > 

> > 

> > > 

> > 

> > 

> > > _______________________________________________

> > 

> > 

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

> > 

> > 

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

> > 

> > 

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

> > 

> > 

> > > 

> > 

> > 

> > 

> > 

> > -- 

> > Alexandre Fayolle

> > Chef de Projet

> > Tel : +33 4 58 48 20 30

> > 

> > Camptocamp France SAS

> > 18 rue du Lac Saint André

> > 73 370 Le Bourget-du-Lac

> > France

> > 

> > http://www.camptocamp.com

> > _______________________________________________

> > 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
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe



      Avast logo

      This email has been checked for viruses by Avast antivirus software.
      www.avast.com


      by Houssine BAKKALI - 04:21 - 30 Sep 2020
    • Re: Modules migration v14 
      +1 already shared it in my team!

Am Mittwoch, den 30.09.2020, 14:07 +0000 schrieb Simone Orsi:

> https://pypi.org/project/odoo-module-migrator/

> 

> I tried it a bunch of times and it definitely does the dirty job. 

> We should work on a roadmap and give it some love.

> 

> Thanks Sylvain, BTW :)

> 

> On Wed, Sep 30, 2020 at 3:52 PM Alexandre Fayolle <

> alexandre.fayolle@camptocamp.com> wrote:

> > Sylvain Legal started something, if I remember well.

> > 

> > 

> > 

> > On 30/09/2020 15:46, David Beal wrote:

> > 

> > 

> > > Hi all,

> > 

> > 

> > > 

> > 

> > 

> > > When I see this commit

> > 

> > 

> > > 

> > https://github.com/odoo/odoo/commit/6835aeb0de6895f7f4d6b23e0b4654465ef21d6a

> > 

> > 

> > > I ask myself if this can lead to an opportunity to have dedicated

> > tool

> > 

> > 

> > > (library) to automate some migration tasks in our OCA modules.

> > 

> > 

> > > 

> > 

> > 

> > > At least the execution of this kind of tool could be executed

> > locally

> > 

> > 

> > > during manual migration, then manual checks, fix and manual

> > commit.

> > 

> > 

> > > 

> > 

> > 

> > > I know there are individual initiatives on this topic but I think

> > it

> > 

> > 

> > > could go under the OCA umbrella and be promoted in the migration

> > guide.

> > 

> > 

> > > 

> > 

> > 

> > > What do you think?

> > 

> > 

> > > 

> > 

> > 

> > > What are the existing libraries ? Which one could go towards OCA

> > ?

> > 

> > 

> > > 

> > 

> > 

> > > Thanks for your idea

> > 

> > 

> > > 

> > 

> > 

> > > Regards

> > 

> > 

> > > 

> > 

> > 

> > > David BEAL - akretion.com <http://akretion.com>

> > 

> > 

> > > Consultant

> > 

> > 

> > > Odoo Intégration / Développement

> > 

> > 

> > > 

> > 

> > 

> > > _______________________________________________

> > 

> > 

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

> > 

> > 

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

> > 

> > 

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

> > 

> > 

> > > 

> > 

> > 

> > 

> > 

> > -- 

> > Alexandre Fayolle

> > Chef de Projet

> > Tel : +33 4 58 48 20 30

> > 

> > Camptocamp France SAS

> > 18 rue du Lac Saint André

> > 73 370 Le Bourget-du-Lac

> > France

> > 

> > http://www.camptocamp.com

> > _______________________________________________

> > 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 - 04:11 - 30 Sep 2020
    • Re: Modules migration v14
      You're right,

      IHMO, I'm in favour to push this library to OCA to have more traction and add more features on v14 version

      Bonne journée


      David BEAL - akretion.com
      Consultant
      Odoo Intégration / Développement


      Le mer. 30 sept. 2020 à 16:02, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
      On Wed, Sep 30, 2020 at 3:52 PM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
      Sylvain Legal started something, if I remember well.


      -sbi

      _______________________________________________
      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 - 04:11 - 30 Sep 2020
    • Re: Modules migration v14

      I tried it a bunch of times and it definitely does the dirty job.
      We should work on a roadmap and give it some love.

      Thanks Sylvain, BTW :)

      On Wed, Sep 30, 2020 at 3:52 PM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
      Sylvain Legal started something, if I remember well.



On 30/09/2020 15:46, David Beal wrote:


> Hi all,


> 


> When I see this commit


> https://github.com/odoo/odoo/commit/6835aeb0de6895f7f4d6b23e0b4654465ef21d6a


> I ask myself if this can lead to an opportunity to have dedicated tool


> (library) to automate some migration tasks in our OCA modules.


> 


> At least the execution of this kind of tool could be executed locally


> during manual migration, then manual checks, fix and manual commit.


> 


> I know there are individual initiatives on this topic but I think it


> could go under the OCA umbrella and be promoted in the migration guide.


> 


> What do you think?


> 


> What are the existing libraries ? Which one could go towards OCA ?


> 


> Thanks for your idea


> 


> Regards


> 


> David BEAL - akretion.com <http://akretion.com>


> Consultant


> Odoo Intégration / Développement


> 


> _______________________________________________


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


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


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


> 




-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

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

http://www.camptocamp.com

      _______________________________________________
      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, Freelance in love with open source.
      by Simone Orsi - 04:06 - 30 Sep 2020

  • OCA Weblate, how to add new language?
    Dear community,

    We like to translate our localization. I checked on Weblate and see only English


    How can I add more language?

    Thank you!
    Kitti
    by Kitti Upariphutthiphong - 12:11 - 30 Sep 2020

    4 replies 4 replies

    • Re: OCA Weblate, how to add new language?
      OK thanks!

      On Wed, Sep 30, 2020 at 8:12 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Hi Kitti,

      You are not currently in any translators group. Please send an e-mail to transbot@odoo-community.org requesting the languages you want to translate to.

      Best regards,

      -sbi

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

      On Wed, Sep 30, 2020 at 3:07 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
      Looks like I don't have the permission. How can I have it?

      image.png

      On Wed, Sep 30, 2020 at 7:01 PM Enric Tobella <etobella@creublanca.es> wrote:
      You need to add the language on each component.
       
      Select the module and then, you will see the button "Start new translation"
       
       
      Kind regards,
       
      Enric Tobella Alomar
       
      Centros Médicos Creu Blanca
      Tel: 902 202 230
       
      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.
       
      From: "Kitti Upariphutthiphong" <kittiu@ecosoft.co.th>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 30 Sep 2020 10:12:16 -0000
      Subject: OCA Weblate, how to add new language?
       
      Dear community,
       
      We like to translate our localization. I checked on Weblate and see only English
       
       
      How can I add more language?
       
      Thank you!
      Kitti
      _______________________________________________
      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

      _______________________________________________
      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 - 03:21 - 30 Sep 2020
    • Re: OCA Weblate, how to add new language?
      Hi Kitti,

      You are not currently in any translators group. Please send an e-mail to transbot@odoo-community.org requesting the languages you want to translate to.

      Best regards,

      -sbi

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

      On Wed, Sep 30, 2020 at 3:07 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
      Looks like I don't have the permission. How can I have it?

      image.png

      On Wed, Sep 30, 2020 at 7:01 PM Enric Tobella <etobella@creublanca.es> wrote:
      You need to add the language on each component.
       
      Select the module and then, you will see the button "Start new translation"
       
       
      Kind regards,
       
      Enric Tobella Alomar
       
      Centros Médicos Creu Blanca
      Tel: 902 202 230
       
      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.
       
      From: "Kitti Upariphutthiphong" <kittiu@ecosoft.co.th>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 30 Sep 2020 10:12:16 -0000
      Subject: OCA Weblate, how to add new language?
       
      Dear community,
       
      We like to translate our localization. I checked on Weblate and see only English
       
       
      How can I add more language?
       
      Thank you!
      Kitti
      _______________________________________________
      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

      _______________________________________________
      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 - 03:11 - 30 Sep 2020
    • Re: OCA Weblate, how to add new language?
      Looks like I don't have the permission. How can I have it?

      image.png

      On Wed, Sep 30, 2020 at 7:01 PM Enric Tobella <etobella@creublanca.es> wrote:
      You need to add the language on each component.
       
      Select the module and then, you will see the button "Start new translation"
       
       
      Kind regards,
       
      Enric Tobella Alomar
       
      Centros Médicos Creu Blanca
      Tel: 902 202 230
       
      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.
       
      From: "Kitti Upariphutthiphong" <kittiu@ecosoft.co.th>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 30 Sep 2020 10:12:16 -0000
      Subject: OCA Weblate, how to add new language?
       
      Dear community,
       
      We like to translate our localization. I checked on Weblate and see only English
       
       
      How can I add more language?
       
      Thank you!
      Kitti
      _______________________________________________
      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

      by Kitti Upariphutthiphong - 03:06 - 30 Sep 2020

      1 attachments 1 attachments

      image.png
    • Re: OCA Weblate, how to add new language?
      You need to add the language on each component.
       
      Select the module and then, you will see the button "Start new translation"
       
       
      Kind regards,
       
      Enric Tobella Alomar
      etobella@creublanca.es
       
      Centros Médicos Creu Blanca
      Tel: 902 202 230
       
      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.
       
      From: "Kitti Upariphutthiphong" <kittiu@ecosoft.co.th>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 30 Sep 2020 10:12:16 -0000
      Subject: OCA Weblate, how to add new language?
       
      Dear community,
       
      We like to translate our localization. I checked on Weblate and see only English
       
       
      How can I add more language?
       
      Thank you!
      Kitti
      _______________________________________________
      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 - 02:00 - 30 Sep 2020

      1 attachments 1 attachments

      imagen.png
  • alternative to SIGN (enterprise): drag placeholders onto a PDF
    Hello OCA,

    - I am looking for an alternative to enterprise's SIGN module.
    Would you know if there is a community module that let graphically add fields to an uploaded pdf file?
    This would be a nice addition to our https://github.com/oca/contract project.

    - is there a useful open source library you know of or should it build from scratch?
    I've found a post (https://stackoverflow.com/questions/31932016/how-to-drag-placeholders-onto-a-pdf) showing achieving this using pdf.js with interact.js


    TIA





     --
    Yves Goldberg
    odoo| Official Partner - OCA delegate
    Open Source ERP, CRM & CMS
    T +972 (3) 720 8818
    M +972 (55) 966 1405
    T +32 (2) 588 2500
     
     
    --

    by Yves Goldberg - 01:30 - 28 Sep 2020

    1 replies 1 replies

    • Re: alternative to SIGN (enterprise): drag placeholders onto a PDF
       
      This creates a widget for signatures and then you can include the image inside the PDF
       
      Enric Tobella Alomar
      etobella@creublanca.es
       
      Centros Médicos Creu Blanca
      Tel: 902 202 230
       
      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.
       
      From: "Yves Goldberg" <yves@ygol.com>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Mon, 28 Sep 2020 11:31:58 -0000
      Subject: alternative to SIGN (enterprise): drag placeholders onto a PDF
       
      Hello OCA,
       
      - I am looking for an alternative to enterprise's SIGN module.
      Would you know if there is a community module that let graphically add fields to an uploaded pdf file?
      This would be a nice addition to our https://github.com/oca/contract project.
       
      - is there a useful open source library you know of or should it build from scratch?
      I've found a post (https://stackoverflow.com/questions/31932016/how-to-drag-placeholders-onto-a-pdf) showing achieving this using pdf.js with interact.js
       
       
      TIA
       
       
       
       
       
       --
      Yves Goldberg
      odoo| Official Partner - OCA delegate
      Open Source ERP, CRM & CMS
       
       
      T +972 (3) 720 8818
      M +972 (55) 966 1405
      T +32 (2) 588 2500
       
       
      --
       
      _______________________________________________
      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 - 03:46 - 28 Sep 2020
  • Confirm unsubscription from OCA channels
    Hello

    I received  a huge number of emails that say : I requested to be unsubscribed to the mailing lists of OCA (Which is not True) even to channels I'm not part of. Is someone else faced the same issue ?

    Thanks



    Othmane Ghandi
    ----------------------------------------------------------------------------------------------------------------------------------------------
    ''Where others see limitations, we see possibilities''
    "les bonnes choses viennent à ceux qui savent attendre. Les grandes choses viennent à ceux qui se lèvent et qui font tout pour y arriver"
    -----------------------------------------------------------------------------------------------------------------------------------------------
                                                        
    : othmane.ghandi
    : +49 17 632214006
     : +212 6 00 45 96 84
    by Othmane Ghandi - 11:43 - 28 Sep 2020

    13 replies 13 replies

  • Confirm unsubscription to OCA Days 2020
    Your Channel
    OCA Days 2020     		Odoo Community Association (OCA)
    Hello,

    You have requested to be unsubscribed to the mailing list OCA Days 2020.

    To confirm, please visit the following link: https://odoo-community.org/groups/unsubscribe/89/14323/cece955062dc7a6217b32cdf6d4e2e87.

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

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

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/oca-days-2020-89
    Post to: mailto:ocadays2020@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by "System" <root@example.com> - 11:28 - 28 Sep 2020
  • Confirm unsubscription to OpenUpgrade
    Your Channel
    OpenUpgrade     		Odoo Community Association (OCA)
    Hello,

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

    To confirm, please visit the following link: https://odoo-community.org/groups/unsubscribe/87/14323/60e2b0811070cc988316c12657a343be.

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

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

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

    by "System" <root@example.com> - 11:28 - 28 Sep 2020
  • Confirm unsubscription to Croatia
    Your Channel
    Croatia     		Odoo Community Association (OCA)
    Hello,

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

    To confirm, please visit the following link: https://odoo-community.org/groups/unsubscribe/86/14323/bea5da2386443cec0799f2ebf3d7141d.

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

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

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

    by "System" <root@example.com> - 11:27 - 28 Sep 2020