Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Re: TimeSheet with Client Signature

    El mar., 28 de ene. de 2020 a la(s) 20:42, David Arnold (dar@xoe.solutions) escribió:

    Hi All,


    Has anybody got an example app / info or use case for a timesheet app with client signing the entry (like delivery do on their mobile tracking solutions)?

    Else, any hint how to incorporate a signature field.in the app and (how to) deploy it?

    Best Regards,

    David A.

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



    --

    --
    Nhomar Hernandez
    CEO Vauxoo, Odoo Gold Partner.
    Site: http://vauxoo.com
    Twitter: @nhomar
    Github User: https://github.com/nhomar
    Skype: nhomar00 (Envia mail previo no lo superviso siempre).
    HangOut: nhomar@vauxoo.com
    Móvil: +52 4773933942
    (Whatsapp y telegram, intenta mejor telegram, whatsapp lo uso muy poco.)
    by Nhomar Hernández - 05:41 - 29 Jan 2020
  • TimeSheet with Client Signature

    Hi All,


    Has anybody got an example app / info or use case for a timesheet app with client signing the entry (like delivery do on their mobile tracking solutions)?

    Else, any hint how to incorporate a signature field.in the app and (how to) deploy it?

    Best Regards,

    David A.
    by dar - 03:41 - 29 Jan 2020
  • Re: Enable Price List using code
    You can do something like this:

    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236


    On Tue, Jan 28, 2020 at 3:26 PM Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello List,

    I struggle with a simple task. Well something that I thought would be simple.
    I would like to enable the Price Lists using xml or python. So I can test my data that rely on.

    I tried using get_values() in res.config.parameter, an XML record. Nothing stick.

    Would you have advice on how to achieve my quest?

    Thank you all,
    Jordi

    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

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

    by Maxime Chambreuil - 10:35 - 28 Jan 2020
  • Enable Price List using code
    Hello List,

    I struggle with a simple task. Well something that I thought would be simple.
    I would like to enable the Price Lists using xml or python. So I can test my data that rely on.

    I tried using get_values() in res.config.parameter, an XML record. Nothing stick.

    Would you have advice on how to achieve my quest?

    Thank you all,
    Jordi

    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    by Jordi Riera - 10:25 - 28 Jan 2020
  • Re: Pre-commit updates
    Thanks for the work, Jairo!

    Regards.
    by Pedro M. Baeza - 05:25 - 25 Jan 2020
  • Re: Pre-commit updates
    That's great news!

    Thank you so much for keep improving things. ;)

    On Fri, Jan 24, 2020, 9:02 PM Jairo Llopis <jairo.llopis@tecnativa.com> wrote:
    tl;dr: pre-commit is getting updated, expect conflicts in your PRs. XML and JS autoformatting!

    Hi community.

    As you might know, for v13 we took a big step forward in our coding standards introducing pre-commit in our workflow, which rewrites all python code in a beautiful-enough fashion.

    After the work we've done in https://github.com/OCA/maintainer-quality-tools/pull/618, our dear Stéphane Bidoul will soon update the pre-commit configuration and it will enable even more code automatic standardization.

    In this case, the main change comes from the inclusion of Prettier and ESLint --fix in our pipeline. They will take the job of prettifying code of these files:
    • .scss/.css
    • .js
    • .xml (via prettier plugin)
    • Others not so common in our codebase: .md, .html, .less, .yaml
    • Before you ask, files created or modified by bots are excluded from the reformat.
    • Only for v13+
    The case for JS is a little bit special in the sense that style changes will be done by Prettier, and AST changes will be done by ESLit, but ESLint still have some linter rules that are not autofixable, and in such case your commit will fail until you satisfy them manually.

    Given this will produce a big diff commit (just like isort+black did), I took this chance to update some of the tools that we were already using, so there could be a little more diff in python maybe. It shouldn't be too much.

    We hope this saves you a lot of time and pain when writing these files. Just write ugly & quick code, and pre-commit will handle the rest 😁

    How does this affect you?

    Really not much; just:
    1. Your open PRs could get conflicts. Rebase it and fix them as usual.
    2. Remember to do pre-commit install when you clone a repo.
    3. JS code might need an update to satisfy the linter.
    4. You are encouraged to enable eslint, black, prettier and editorconfig plugins in your favourite IDE, as you probably already did with flake8 and pylint. They should work out of the box, although pre-commit is the maximum authority regarding code reformatting because it works exactly the same in all envs.
    The change is planned for february 15th, although Stéphane will tell more details in this thread if needed (please) and I'm advancing it for web and website where the change is most interesting.

    Have a nice day!
    --
    Jairo Llopis

    _______________________________________________
    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 - 04:56 - 24 Jan 2020
  • Pre-commit updates
    tl;dr: pre-commit is getting updated, expect conflicts in your PRs. XML and JS autoformatting!

    Hi community.

    As you might know, for v13 we took a big step forward in our coding standards introducing pre-commit in our workflow, which rewrites all python code in a beautiful-enough fashion.

    After the work we've done in https://github.com/OCA/maintainer-quality-tools/pull/618, our dear Stéphane Bidoul will soon update the pre-commit configuration and it will enable even more code automatic standardization.

    In this case, the main change comes from the inclusion of Prettier and ESLint --fix in our pipeline. They will take the job of prettifying code of these files:
    • .scss/.css
    • .js
    • .xml (via prettier plugin)
    • Others not so common in our codebase: .md, .html, .less, .yaml
    • Before you ask, files created or modified by bots are excluded from the reformat.
    • Only for v13+
    The case for JS is a little bit special in the sense that style changes will be done by Prettier, and AST changes will be done by ESLit, but ESLint still have some linter rules that are not autofixable, and in such case your commit will fail until you satisfy them manually.

    Given this will produce a big diff commit (just like isort+black did), I took this chance to update some of the tools that we were already using, so there could be a little more diff in python maybe. It shouldn't be too much.

    We hope this saves you a lot of time and pain when writing these files. Just write ugly & quick code, and pre-commit will handle the rest 😁

    How does this affect you?

    Really not much; just:
    1. Your open PRs could get conflicts. Rebase it and fix them as usual.
    2. Remember to do pre-commit install when you clone a repo.
    3. JS code might need an update to satisfy the linter.
    4. You are encouraged to enable eslint, black, prettier and editorconfig plugins in your favourite IDE, as you probably already did with flake8 and pylint. They should work out of the box, although pre-commit is the maximum authority regarding code reformatting because it works exactly the same in all envs.
    The change is planned for february 15th, although Stéphane will tell more details in this thread if needed (please) and I'm advancing it for web and website where the change is most interesting.

    Have a nice day!
    --
    Jairo Llopis
    by Jairo Llopis - 03:01 - 24 Jan 2020
  • AW: Odoo2Odoo

    Hi all,

     

    I was one of the initiators of the odoo2odoo project. The idea and implementation dates back to ~2017.

    Back in the days we used the connector project for this and build a intercompany purchase process. Therefore we synced products, uom, etc. as well as IC PO -> SO.

    Sadly the project never made it to the OCA repo. The setup was in heavy use for ~3 years in a constellation with 5 different companies under odoo v8.

     

    Personally, I would do the same again. You don’t have to learn a new technology, you maintain a well known piece of software (i.e. Odoo) and can use your existing tooling and knowledge to build the solution.

     

    Regards

    Malte

     

     

    Von: Willem Hulshof <w.hulshof@magnus.nl>
    Gesendet: Mittwoch, 8. Januar 2020 20:42
    An: Contributors <contributors@odoo-community.org>
    Betreff: Re: Odoo2Odoo

     

    Ok, thanks!

    Verstuurd vanaf mijn iPhone



    Op 8 jan. 2020 om 18:27 heeft Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> het volgende geschreven:

    

    I prefer to avoid more pieces in the technology puzzle. That's why we choose Odoo for integrating all enterprise software in one place.

     

    Regards.

    by "Malte Jacobi (ODION)" <mj@odion.com> - 02:01 - 9 Jan 2020
  • Re: Odoo2Odoo
    Ok, thanks!

    Verstuurd vanaf mijn iPhone

    Op 8 jan. 2020 om 18:27 heeft Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> het volgende geschreven:

    
    I prefer to avoid more pieces in the technology puzzle. That's why we choose Odoo for integrating all enterprise software in one place.

    Regards.

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

    by Willem Hulshof - 08:40 - 8 Jan 2020
  • Re: Odoo2Odoo
    Hi all
    I have worked with Zato before and it's very good integration toolkit to have in your stack. But I think that in this case it's better to use an strong queue technology like RabbitMQ
    with different strategies of message diffusion patterns, also ZeroMQ will give you a lot of tools to build this kind of integration between one or multiple Odoo's. You could use Zato with RabbitMQ and many others message queue brokers but could let you with an spaghetti and references, also you will need to code Zato services to interact with Odoo models too, in a very clean API but sometimes it's better to directly integrate some external technology into Odoo like Odoo2Odoo it's doing but I prefers to use an strong message queue that allow me to build other stuffs around distributed patterns
    Best Regards

    On Wed, Jan 8, 2020 at 12:27 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
    I prefer to avoid more pieces in the technology puzzle. That's why we choose Odoo for integrating all enterprise software in one place.

    Regards.

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

    by Axel Mendoza - 07:06 - 8 Jan 2020
  • Re: Odoo2Odoo
    I prefer to avoid more pieces in the technology puzzle. That's why we choose Odoo for integrating all enterprise software in one place.

    Regards.
    by Pedro M. Baeza - 06:25 - 8 Jan 2020
  • Re: Odoo2Odoo
    Dear Pedro, 
    Why is that? I never heard of zato.io, but it looks like an interesting proposition?

    Verstuurd vanaf mijn iPhone

    Op 8 jan. 2020 om 17:47 heeft Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> het volgende geschreven:

    
    If I'm not mistaken, Odoo2odoo is an ESB, but implemented with the support of queue_job.

    I personally prefer to avoid external services like zato.io one.

    Regards.

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

    by Willem Hulshof - 06:11 - 8 Jan 2020
  • Re: Odoo2Odoo
    If I'm not mistaken, Odoo2odoo is an ESB, but implemented with the support of queue_job.

    I personally prefer to avoid external services like zato.io one.

    Regards.
    by Pedro M. Baeza - 05:46 - 8 Jan 2020
  • Re: Odoo2Odoo
    Hi Bruno,

    ESB principle, probably the best solution.

    In python https://zato.io

    and odoo


    Never used



    Bonne journée


    David BEAL - akretion.com
    Chef de projet
    Odoo Développement / Intégration


    Le mer. 8 janv. 2020 à 16:46, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> a écrit :
    Hi Bruno,


    For such a complex thing I guess you should look at an ESB setup.. Using connectors between odoo will soon be a nightmare to debug.

    My2cents,

    Joël

    On Wed, Jan 8, 2020 at 2:06 PM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    Many thanks Dominique, Simone and Sebastien,

    We already use job queue to manage datas from other software. I did not think of it for this requirement.

    To define in relation to your questions, requirements are:
    - step 1: bi directional synchronization on masterdatas as res.partners which can be asynchronous
    - step 2: extend to other models and process like sale/purchase, invoicing

    Have a nice day,


    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada



    Le mer. 8 janv. 2020 à 04:12, Sebastien Alix <seb@usr-src.org> a écrit :

    Hi Bruno,

    I worked on https://github.com/OCA/connector-odoo2odoo/pull/5 3 years ago (see the PR description for details).

    It is mainly a framework to sync any data models between Odoo instances (you can sync PO to SO if you want, or a SO line to an event if it makes sense). Up to you to write the business logic.

    It was deployed on a Odoo 8 for the backend (which drives the synchronization) and a Odoo 9 webshop for the node. It was working fine during test sessions, but I didn't get the chance to see the Go-Live in production.

    This framework would need to be migrated to the new connector API and get some tests + documentation for sure. If you know the connector it should be pretty straightforward to use it.

    Cheers

    Le 08/01/2020 à 08:47, Simone Orsi a écrit :
    Hi Bruno,

    what's your main use case? What do you want to keep in sync?

    I see that this repo has only some pending PRs, nothing got released yet.
    I'll ping Sébastien who worked on it, I bet he knows more about it.

    Cheers,


    On Wed, Jan 8, 2020 at 12:11 AM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    Hi community and Happy New Year!

    We plan a new project with multi-companies on distinct databases and servers.
    We noticed that https://github.com/OCA/connector-odoo2odoo seems seems to be on break.

    Do you use other ways or mitigation when you meet this requirement?

    Have a nice day and receive greetings from "Numigiens" ;-)

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    _______________________________________________
    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



    --


    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Joël Grand-Guillaume
    Department Head
    Business Solutions

    +41 21 619 10 28


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

    by David BEAL - 05:31 - 8 Jan 2020
  • Re: Odoo2Odoo
    Hi Bruno,


    For such a complex thing I guess you should look at an ESB setup.. Using connectors between odoo will soon be a nightmare to debug.

    My2cents,

    Joël

    On Wed, Jan 8, 2020 at 2:06 PM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    Many thanks Dominique, Simone and Sebastien,

    We already use job queue to manage datas from other software. I did not think of it for this requirement.

    To define in relation to your questions, requirements are:
    - step 1: bi directional synchronization on masterdatas as res.partners which can be asynchronous
    - step 2: extend to other models and process like sale/purchase, invoicing

    Have a nice day,


    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada



    Le mer. 8 janv. 2020 à 04:12, Sebastien Alix <seb@usr-src.org> a écrit :

    Hi Bruno,

    I worked on https://github.com/OCA/connector-odoo2odoo/pull/5 3 years ago (see the PR description for details).

    It is mainly a framework to sync any data models between Odoo instances (you can sync PO to SO if you want, or a SO line to an event if it makes sense). Up to you to write the business logic.

    It was deployed on a Odoo 8 for the backend (which drives the synchronization) and a Odoo 9 webshop for the node. It was working fine during test sessions, but I didn't get the chance to see the Go-Live in production.

    This framework would need to be migrated to the new connector API and get some tests + documentation for sure. If you know the connector it should be pretty straightforward to use it.

    Cheers

    Le 08/01/2020 à 08:47, Simone Orsi a écrit :
    Hi Bruno,

    what's your main use case? What do you want to keep in sync?

    I see that this repo has only some pending PRs, nothing got released yet.
    I'll ping Sébastien who worked on it, I bet he knows more about it.

    Cheers,


    On Wed, Jan 8, 2020 at 12:11 AM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    Hi community and Happy New Year!

    We plan a new project with multi-companies on distinct databases and servers.
    We noticed that https://github.com/OCA/connector-odoo2odoo seems seems to be on break.

    Do you use other ways or mitigation when you meet this requirement?

    Have a nice day and receive greetings from "Numigiens" ;-)

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    _______________________________________________
    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



    --


    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Joël Grand-Guillaume
    Department Head
    Business Solutions

    +41 21 619 10 28


    by Joël Grand Guillaume - 04:46 - 8 Jan 2020
  • Re: Odoo2Odoo
    Many thanks Dominique, Simone and Sebastien,

    We already use job queue to manage datas from other software. I did not think of it for this requirement.

    To define in relation to your questions, requirements are:
    - step 1: bi directional synchronization on masterdatas as res.partners which can be asynchronous
    - step 2: extend to other models and process like sale/purchase, invoicing

    Have a nice day,


    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada



    Le mer. 8 janv. 2020 à 04:12, Sebastien Alix <seb@usr-src.org> a écrit :

    Hi Bruno,

    I worked on https://github.com/OCA/connector-odoo2odoo/pull/5 3 years ago (see the PR description for details).

    It is mainly a framework to sync any data models between Odoo instances (you can sync PO to SO if you want, or a SO line to an event if it makes sense). Up to you to write the business logic.

    It was deployed on a Odoo 8 for the backend (which drives the synchronization) and a Odoo 9 webshop for the node. It was working fine during test sessions, but I didn't get the chance to see the Go-Live in production.

    This framework would need to be migrated to the new connector API and get some tests + documentation for sure. If you know the connector it should be pretty straightforward to use it.

    Cheers

    Le 08/01/2020 à 08:47, Simone Orsi a écrit :
    Hi Bruno,

    what's your main use case? What do you want to keep in sync?

    I see that this repo has only some pending PRs, nothing got released yet.
    I'll ping Sébastien who worked on it, I bet he knows more about it.

    Cheers,


    On Wed, Jan 8, 2020 at 12:11 AM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    Hi community and Happy New Year!

    We plan a new project with multi-companies on distinct databases and servers.
    We noticed that https://github.com/OCA/connector-odoo2odoo seems seems to be on break.

    Do you use other ways or mitigation when you meet this requirement?

    Have a nice day and receive greetings from "Numigiens" ;-)

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    _______________________________________________
    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 Bruno Joliveau - 02:06 - 8 Jan 2020
  • Re: Odoo2Odoo

    Hi Bruno,

    I worked on https://github.com/OCA/connector-odoo2odoo/pull/5 3 years ago (see the PR description for details).

    It is mainly a framework to sync any data models between Odoo instances (you can sync PO to SO if you want, or a SO line to an event if it makes sense). Up to you to write the business logic.

    It was deployed on a Odoo 8 for the backend (which drives the synchronization) and a Odoo 9 webshop for the node. It was working fine during test sessions, but I didn't get the chance to see the Go-Live in production.

    This framework would need to be migrated to the new connector API and get some tests + documentation for sure. If you know the connector it should be pretty straightforward to use it.

    Cheers

    Le 08/01/2020 à 08:47, Simone Orsi a écrit :
    Hi Bruno,

    what's your main use case? What do you want to keep in sync?

    I see that this repo has only some pending PRs, nothing got released yet.
    I'll ping Sébastien who worked on it, I bet he knows more about it.

    Cheers,


    On Wed, Jan 8, 2020 at 12:11 AM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    Hi community and Happy New Year!

    We plan a new project with multi-companies on distinct databases and servers.
    We noticed that https://github.com/OCA/connector-odoo2odoo seems seems to be on break.

    Do you use other ways or mitigation when you meet this requirement?

    Have a nice day and receive greetings from "Numigiens" ;-)

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    _______________________________________________
    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 usr-src.org - 10:11 - 8 Jan 2020
  • Re: Odoo documentation tool
    👍 +1


    On Wed, 8 Jan 2020 at 09:02, Simone Orsi <simahawk@gmail.com> wrote:
    Nice idea!

    I think this can stay together with the other tools in https://github.com/OCA/maintainer-tools

    On Tue, Jan 7, 2020 at 7:02 PM Renato Lima <renatonlima@gmail.com> wrote:
    +1
    Very good Pedro,


    I think this script has great potential to generate meta information and fill in some informations in README module file. About the license, you commented that he (former employee of Odoo S.A.) opened the code, do you think there would be a problem with Odoo S.A. about the license? If there is no problem, Do you think this script should be in a new repository in an existing repository? IMHO would make sense to leave this script in the OCA / maintainer-tools repo, because there is already a script to create the module readme (oca-gen-addon-readme)

    _______________________________________________
    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 Lorenzo Battistini. - 10:11 - 8 Jan 2020
  • Re: Odoo documentation tool
    Nice idea!

    I think this can stay together with the other tools in https://github.com/OCA/maintainer-tools

    On Tue, Jan 7, 2020 at 7:02 PM Renato Lima <renatonlima@gmail.com> wrote:
    +1
    Very good Pedro,


    I think this script has great potential to generate meta information and fill in some informations in README module file. About the license, you commented that he (former employee of Odoo S.A.) opened the code, do you think there would be a problem with Odoo S.A. about the license? If there is no problem, Do you think this script should be in a new repository in an existing repository? IMHO would make sense to leave this script in the OCA / maintainer-tools repo, because there is already a script to create the module readme (oca-gen-addon-readme)

    _______________________________________________
    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 - 09:00 - 8 Jan 2020
  • Re: Odoo2Odoo
    Hi Bruno,

    what's your main use case? What do you want to keep in sync?

    I see that this repo has only some pending PRs, nothing got released yet.
    I'll ping Sébastien who worked on it, I bet he knows more about it.

    Cheers,


    On Wed, Jan 8, 2020 at 12:11 AM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    Hi community and Happy New Year!

    We plan a new project with multi-companies on distinct databases and servers.
    We noticed that https://github.com/OCA/connector-odoo2odoo seems seems to be on break.

    Do you use other ways or mitigation when you meet this requirement?

    Have a nice day and receive greetings from "Numigiens" ;-)

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    _______________________________________________
    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 - 08:46 - 8 Jan 2020