Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

  • Escape python lint
    HI all,

    I've done this PR

    Yes a non academic one.
    I searched a way to escape ring bell from here 


    As I understand, only xml files can legitimates trigger these bypass.

    In my case it concerns python files.

    Maybe something I don't understood or a better way to display plain query

    Thanks a lot

    Bonne journée


    David BEAL - akretion.com
    Chef de projet
    Odoo Développement / Intégration
    by David BEAL - 07:05 - 23 Oct 2019

    4 replies 4 replies

  • Place to share knowledge/tools on deployment
    Hello list,

    During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
    The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

    How would you see it ?

    What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
    The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


    Let me know what you think

    Jordi


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

    Longueuil, Québec, Canada

    by Jordi Riera - 06:20 - 22 Oct 2019

    34 replies 34 replies

  • Newbe on Odoo
    Hello everyone,

    I consider myself Odoo fan, I know this software since version 6 named OpenERP, yes!! I'm old :D anyway I'm building up my own business "On-line Shop" and now is the time to implement Odoo. I have been playing with the 11 version but I know and I can see that the latest versions the company has been cutting off more and more modules, I looking to implement a fully operational Odoo using the CE version, I really don't care if it's not the latest version as far is working fine. Mu play is start and eventual in the future migrate to a better latest version. So I'm looking at some of your opinions regarding this, witch one you consider will be the best option for me to start. I can see that version 10 has most of the functionality just before things started to go south, one of the modules that I consider very important is the account module, after ver 10 the module is not there or limited.

    I really appreciate all your comments and goods advises.

    Regards,
    --
    --
    Harold g Luzardo b
    @Kickfliph
    GNU/Linux User #535193
    pub   2048R/0BCF3A23 2014-06-08
    Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23
    by Harold Burton - 03:05 - 19 Oct 2019

    13 replies 13 replies

    • Re: Newbe on Odoo 
      Hi Harold, 

i strongly support and quote Tims opinion on the matter as follows

Am Dienstag, den 22.10.2019, 15:52 +0000 schrieb Timothy Stonis:

> I think with CE v12 and some simple financial reports using MIS

> Builder, you can quickly get a basic company onto the platform

> including your accounting.

Small Remark: Technically simplicity doesn't mean you don't need domain
level expertise on domestic accounting standards but that should be
imho clear. MIS Builder is a great tool, easy to install, somewhat easy
to understand and learn and after all covering much more than Odoo
standard does! Acsone (Stephané) did a great job in inventing this!

Best Frederik


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

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
      by Frederik Kramer. - 06:20 - 22 Oct 2019
    • Re: Newbe on Odoo

      I'm sorry, but I would not recommend to anyone keeping your books in Excel. Maybe everything isn't quite there, but Odoo CE v12's "Show Full Accounting Features" would be a better option.

      Harold,

      You may be interested to read a blog post a wrote for OCA that gives you my experience starting with Odoo:

      https://odoo-community.org/blog/the-oca-blog-1/post/switching-to-odoo-one-company-s-journey-96

      I think with CE v12 and some simple financial reports using MIS Builder, you can quickly get a basic company onto the platform including your accounting. As others have said (and I say in my post), you probably need to spend some money for some help to guide you along and save you time.

      Tim


      October 21, 2019 10:16 PM, "Dominique k" <dominique.k@elico-corp.com.sg> wrote:
      If you just start, keep it even simpler:
      Odoo CE12 (or 13), use the invoicing of Odoo
      the rest of your accounting --> use Excel for your cashbook
      Regards,
      Dominique
      On Tue, 22 Oct 2019 at 10:07, Harold luzardo <haroldburtonl@gmail.com> wrote:
      Hello everyone,
      Thanks a lot for all your opinions and ideas I really appreciate, I will try to narrow down this and see if it's possible for me to get the best of all your ideas and propositions. So for someone that's starting something for nothing "ME" I'm looking to use Odoo CE in "the beginning" once my little project is able to pay the monthly rent of having all in Odoo EE cloud I'll say that I made it, but in the mid-time, I'm ready to struggle and learn. So this is what I get compile from you all, install V12 or above; this way the migration will not be so painful. Now, it's Ok if I do so using CE?, it's because for now my budget it 0 and I can't afford Odoo cloud, so I'm thinking CE V12+OCA modules and pay someone to do the accounting management, and do the future migration to EE, is this viable? please let me know what it's your perspective.
      Regards,
      On Mon, Oct 21, 2019 at 2:02 AM Nhomar Hernández <nhomar@vauxoo.com> wrote:
      El dom., 20 de oct. de 2019 a la(s) 02:42, Graeme Gellatly (gdgellatly@gmail.com) escribió:
      Apart from a couple of reports that never really worked there really isn't any difference in accounting features over community versions.
      On v8 you need oca, on v13 you need oca
      And on v14, 15, 16....
      But it is not a matter of OCA no-OCA or EE no-EE
      You can always (and I recommend) use both for a serious solution...
      Only one either put you in the uncomfortable situation of paying more for services (just OCA) or less features (just EE).
      On my side, I think even SaaS for v >> 12.0 is really a proper solution for little- medium firms for their accounting solutions.
      On Sun, 20 Oct 2019, 7:52 PM Kitti Upariphutthiphong, <kittiu@ecosoft.co.th> wrote:
      Hello,
      I just want to confirm that Odoo CE + OCA modules can be much better than EE even on accounting.
      Many time, OCA module surpass features provided by EE itself. Many features was in OCA long time before it end up in Odoo.
      Problem is OCA is hidden gems, which is also a problem for new people (every new search end in EE landing page).
      At least in our country, same problem, most people think about CE as a not workable ERP. From v11, many Odooer jump ship to FlectraHQ because of this. Few people heard about OCA, even fewer know what OCA is all about.
      It is like, you are in the gang (being part of OCA), or you are not :).
      Back to your questions, IMHO,
      • For quick fix, hire a competent consultant from OCA, feel free to ask here.
      • For long term, yourself become an OCA member. You will learn a lot from OCA (my own experience).
      Good luck,
      Kitti
      On Sat, Oct 19, 2019 at 11:16 PM Nhomar Hernández <nhomar@vauxoo.com> wrote:
      Hello.
      Try it yourself. Just the timesheet of 4 people here answering you can pay 3 monts of licences.
      - GO to: odoo.com/trial
      - Create a site.
      - Add your problem is solved.
      YES, you will have problems (who doesn't).
      YES, you will receive solutions.
      Instead argument/discuss with not-paid people your individual problems found or with your pear at the office, each time you have a doubt hire a proper consultant (that's the way this world works, you know **money*** :-)).
      I promise you will expend less than what you will expend trying create Frankenstein with community, in other hand you will face a proper support to Odoo itself (the original creator) and to the community while you buy consultancy from them (the ones that will create + modules for you).
      Our freedom is not a matter of money, is a matter of quality and access to the code :-)
      About Accounting in odoo 13.0-12.0 (the one you will find as trial in the saas): It is really nice, but may be you will need a few weeks to end the stabilization (no big deal for your use case).
      I hope it helps.
      El vie., 18 de oct. de 2019 a la(s) 20:07, Harold luzardo (haroldburtonl@gmail.com) escribió:
      Hello everyone,
      I consider myself Odoo fan, I know this software since version 6 named OpenERP, yes!! I'm old :D anyway I'm building up my own business "On-line Shop" and now is the time to implement Odoo. I have been playing with the 11 version but I know and I can see that the latest versions the company has been cutting off more and more modules, I looking to implement a fully operational Odoo using the CE version, I really don't care if it's not the latest version as far is working fine. Mu play is start and eventual in the future migrate to a better latest version. So I'm looking at some of your opinions regarding this, witch one you consider will be the best option for me to start. I can see that version 10 has most of the functionality just before things started to go south, one of the modules that I consider very important is the account module, after ver 10 the module is not there or limited.
      I really appreciate all your comments and goods advises.
      Regards,
      --
      --
      Harold g Luzardo b
      @Kickfliph
      GNU/Linux User #535193
      pub 2048R/0BCF3A23 2014-06-08
      Key fingerprint = 842E 986F 2A7B A507 4F0B 4A0F A73D 5885 0BCF 3A23

      _______________________________________________
      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.)

      _______________________________________________
      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



      --

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

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



      --
      --
      Harold g Luzardo b
      @Kickfliph
      GNU/Linux User #535193
      pub 2048R/0BCF3A23 2014-06-08
      Key fingerprint = 842E 986F 2A7B A507 4F0B 4A0F A73D 5885 0BCF 3A23

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

      by Timothy Stonis - 05:51 - 22 Oct 2019
    • Re: Newbe on Odoo
      If you just start, keep it even simpler:

      Odoo CE12 (or 13), use the invoicing of Odoo
      the rest of your accounting --> use Excel for your cashbook

      Regards,

      Dominique 


      On Tue, 22 Oct 2019 at 10:07, Harold luzardo <haroldburtonl@gmail.com> wrote:
      Hello everyone,

      Thanks a lot for all your opinions and ideas I really appreciate, I will try to narrow down this and see if it's possible for me to get the best of all your ideas and propositions. So for someone that's starting something for nothing "ME" I'm looking to use Odoo CE in "the beginning" once my little project is able to pay the monthly rent of having all in Odoo EE cloud I'll say that I made it, but in the mid-time, I'm ready to struggle and learn. So this is what I get compile from you all, install V12 or above; this way the migration will not be so painful. Now, it's Ok if I do so using CE?, it's because for now my budget it 0 and I can't afford Odoo cloud, so I'm thinking CE V12+OCA modules and pay someone to do the accounting management, and do the future migration to EE, is this viable? please let me know what it's your perspective.

      Regards,

      On Mon, Oct 21, 2019 at 2:02 AM Nhomar Hernández <nhomar@vauxoo.com> wrote:


      El dom., 20 de oct. de 2019 a la(s) 02:42, Graeme Gellatly (gdgellatly@gmail.com) escribió:
      Apart from a couple of reports that never really worked there really isn't any difference in accounting features over community versions. 

      On v8 you need oca, on v13 you need oca


      And on v14, 15, 16....

      But it is not a matter of OCA no-OCA or EE no-EE

      You can always (and I recommend) use both for a serious solution...

      Only one either put you in the uncomfortable situation of paying more for services (just OCA) or less features (just EE).

      On my side, I think even SaaS for v >> 12.0 is really a proper solution for little- medium firms for their accounting solutions.


      On Sun, 20 Oct 2019, 7:52 PM Kitti Upariphutthiphong, <kittiu@ecosoft.co.th> wrote:
      Hello,

      I just want to confirm that Odoo CE + OCA modules can be much better than EE even on accounting.

      Many time, OCA module surpass features provided by EE itself. Many features was in OCA long time before it end up in Odoo.
      Problem is OCA is hidden gems, which is also a problem for new people (every new search end in EE landing page).

      At least in our country, same problem, most people think about CE as a not workable ERP. From v11, many Odooer jump ship to FlectraHQ because of this. Few people heard about OCA, even fewer know what OCA is all about.

      It is like, you are in the gang (being part of OCA), or you are not :).

      Back to your questions, IMHO,
      • For quick fix, hire a competent consultant from OCA, feel free to ask here.
      • For long term, yourself become an OCA member. You will learn a lot from OCA (my own experience).

      Good luck,
      Kitti

      On Sat, Oct 19, 2019 at 11:16 PM Nhomar Hernández <nhomar@vauxoo.com> wrote:
      Hello.

      Try it yourself. Just the timesheet of 4 people here answering you can pay 3 monts of licences.

      - Create a site.
      - Add your problem is solved.

      YES, you will have problems (who doesn't).
      YES,  you will receive solutions.

      Instead argument/discuss with not-paid people your individual problems found or with your pear at the office, each time you have a doubt hire a proper consultant (that's the way this world works, you know **money*** :-)).

      I promise you will expend less than what you will expend trying create Frankenstein with community, in other hand you will face a proper support to Odoo itself (the original creator) and to the community while you buy consultancy from them (the ones that will create + modules for you).

      Our freedom is not a matter of money, is a matter of quality and access to the code :-)

      About Accounting in odoo 13.0-12.0 (the one you will find as trial in the saas): It is really nice, but may be you will need a few weeks to end the stabilization (no big deal for your use case).

      I hope it helps.

      El vie., 18 de oct. de 2019 a la(s) 20:07, Harold luzardo (haroldburtonl@gmail.com) escribió:
      Hello everyone,

      I consider myself Odoo fan, I know this software since version 6 named OpenERP, yes!! I'm old :D anyway I'm building up my own business "On-line Shop" and now is the time to implement Odoo. I have been playing with the 11 version but I know and I can see that the latest versions the company has been cutting off more and more modules, I looking to implement a fully operational Odoo using the CE version, I really don't care if it's not the latest version as far is working fine. Mu play is start and eventual in the future migrate to a better latest version. So I'm looking at some of your opinions regarding this, witch one you consider will be the best option for me to start. I can see that version 10 has most of the functionality just before things started to go south, one of the modules that I consider very important is the account module, after ver 10 the module is not there or limited.

      I really appreciate all your comments and goods advises.

      Regards,
      --
      --
      Harold g Luzardo b
      @Kickfliph
      GNU/Linux User #535193
      pub   2048R/0BCF3A23 2014-06-08
      Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23

      _______________________________________________
      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.)

      _______________________________________________
      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



      --

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

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



      --
      --
      Harold g Luzardo b
      @Kickfliph
      GNU/Linux User #535193
      pub   2048R/0BCF3A23 2014-06-08
      Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23

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

      by dominique.k - 04:16 - 22 Oct 2019
    • Re: Newbe on Odoo
      Hello everyone,

      Thanks a lot for all your opinions and ideas I really appreciate, I will try to narrow down this and see if it's possible for me to get the best of all your ideas and propositions. So for someone that's starting something for nothing "ME" I'm looking to use Odoo CE in "the beginning" once my little project is able to pay the monthly rent of having all in Odoo EE cloud I'll say that I made it, but in the mid-time, I'm ready to struggle and learn. So this is what I get compile from you all, install V12 or above; this way the migration will not be so painful. Now, it's Ok if I do so using CE?, it's because for now my budget it 0 and I can't afford Odoo cloud, so I'm thinking CE V12+OCA modules and pay someone to do the accounting management, and do the future migration to EE, is this viable? please let me know what it's your perspective.

      Regards,

      On Mon, Oct 21, 2019 at 2:02 AM Nhomar Hernández <nhomar@vauxoo.com> wrote:


      El dom., 20 de oct. de 2019 a la(s) 02:42, Graeme Gellatly (gdgellatly@gmail.com) escribió:
      Apart from a couple of reports that never really worked there really isn't any difference in accounting features over community versions. 

      On v8 you need oca, on v13 you need oca


      And on v14, 15, 16....

      But it is not a matter of OCA no-OCA or EE no-EE

      You can always (and I recommend) use both for a serious solution...

      Only one either put you in the uncomfortable situation of paying more for services (just OCA) or less features (just EE).

      On my side, I think even SaaS for v >> 12.0 is really a proper solution for little- medium firms for their accounting solutions.


      On Sun, 20 Oct 2019, 7:52 PM Kitti Upariphutthiphong, <kittiu@ecosoft.co.th> wrote:
      Hello,

      I just want to confirm that Odoo CE + OCA modules can be much better than EE even on accounting.

      Many time, OCA module surpass features provided by EE itself. Many features was in OCA long time before it end up in Odoo.
      Problem is OCA is hidden gems, which is also a problem for new people (every new search end in EE landing page).

      At least in our country, same problem, most people think about CE as a not workable ERP. From v11, many Odooer jump ship to FlectraHQ because of this. Few people heard about OCA, even fewer know what OCA is all about.

      It is like, you are in the gang (being part of OCA), or you are not :).

      Back to your questions, IMHO,
      • For quick fix, hire a competent consultant from OCA, feel free to ask here.
      • For long term, yourself become an OCA member. You will learn a lot from OCA (my own experience).

      Good luck,
      Kitti

      On Sat, Oct 19, 2019 at 11:16 PM Nhomar Hernández <nhomar@vauxoo.com> wrote:
      Hello.

      Try it yourself. Just the timesheet of 4 people here answering you can pay 3 monts of licences.

      - Create a site.
      - Add your problem is solved.

      YES, you will have problems (who doesn't).
      YES,  you will receive solutions.

      Instead argument/discuss with not-paid people your individual problems found or with your pear at the office, each time you have a doubt hire a proper consultant (that's the way this world works, you know **money*** :-)).

      I promise you will expend less than what you will expend trying create Frankenstein with community, in other hand you will face a proper support to Odoo itself (the original creator) and to the community while you buy consultancy from them (the ones that will create + modules for you).

      Our freedom is not a matter of money, is a matter of quality and access to the code :-)

      About Accounting in odoo 13.0-12.0 (the one you will find as trial in the saas): It is really nice, but may be you will need a few weeks to end the stabilization (no big deal for your use case).

      I hope it helps.

      El vie., 18 de oct. de 2019 a la(s) 20:07, Harold luzardo (haroldburtonl@gmail.com) escribió:
      Hello everyone,

      I consider myself Odoo fan, I know this software since version 6 named OpenERP, yes!! I'm old :D anyway I'm building up my own business "On-line Shop" and now is the time to implement Odoo. I have been playing with the 11 version but I know and I can see that the latest versions the company has been cutting off more and more modules, I looking to implement a fully operational Odoo using the CE version, I really don't care if it's not the latest version as far is working fine. Mu play is start and eventual in the future migrate to a better latest version. So I'm looking at some of your opinions regarding this, witch one you consider will be the best option for me to start. I can see that version 10 has most of the functionality just before things started to go south, one of the modules that I consider very important is the account module, after ver 10 the module is not there or limited.

      I really appreciate all your comments and goods advises.

      Regards,
      --
      --
      Harold g Luzardo b
      @Kickfliph
      GNU/Linux User #535193
      pub   2048R/0BCF3A23 2014-06-08
      Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23

      _______________________________________________
      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.)

      _______________________________________________
      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



      --

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

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



      --
      --
      Harold g Luzardo b
      @Kickfliph
      GNU/Linux User #535193
      pub   2048R/0BCF3A23 2014-06-08
      Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23
      by Harold Burton - 04:06 - 22 Oct 2019
    • Re: Newbe on Odoo


      El dom., 20 de oct. de 2019 a la(s) 02:42, Graeme Gellatly (gdgellatly@gmail.com) escribió:
      Apart from a couple of reports that never really worked there really isn't any difference in accounting features over community versions. 

      On v8 you need oca, on v13 you need oca


      And on v14, 15, 16....

      But it is not a matter of OCA no-OCA or EE no-EE

      You can always (and I recommend) use both for a serious solution...

      Only one either put you in the uncomfortable situation of paying more for services (just OCA) or less features (just EE).

      On my side, I think even SaaS for v >> 12.0 is really a proper solution for little- medium firms for their accounting solutions.


      On Sun, 20 Oct 2019, 7:52 PM Kitti Upariphutthiphong, <kittiu@ecosoft.co.th> wrote:
      Hello,

      I just want to confirm that Odoo CE + OCA modules can be much better than EE even on accounting.

      Many time, OCA module surpass features provided by EE itself. Many features was in OCA long time before it end up in Odoo.
      Problem is OCA is hidden gems, which is also a problem for new people (every new search end in EE landing page).

      At least in our country, same problem, most people think about CE as a not workable ERP. From v11, many Odooer jump ship to FlectraHQ because of this. Few people heard about OCA, even fewer know what OCA is all about.

      It is like, you are in the gang (being part of OCA), or you are not :).

      Back to your questions, IMHO,
      • For quick fix, hire a competent consultant from OCA, feel free to ask here.
      • For long term, yourself become an OCA member. You will learn a lot from OCA (my own experience).

      Good luck,
      Kitti

      On Sat, Oct 19, 2019 at 11:16 PM Nhomar Hernández <nhomar@vauxoo.com> wrote:
      Hello.

      Try it yourself. Just the timesheet of 4 people here answering you can pay 3 monts of licences.

      - Create a site.
      - Add your problem is solved.

      YES, you will have problems (who doesn't).
      YES,  you will receive solutions.

      Instead argument/discuss with not-paid people your individual problems found or with your pear at the office, each time you have a doubt hire a proper consultant (that's the way this world works, you know **money*** :-)).

      I promise you will expend less than what you will expend trying create Frankenstein with community, in other hand you will face a proper support to Odoo itself (the original creator) and to the community while you buy consultancy from them (the ones that will create + modules for you).

      Our freedom is not a matter of money, is a matter of quality and access to the code :-)

      About Accounting in odoo 13.0-12.0 (the one you will find as trial in the saas): It is really nice, but may be you will need a few weeks to end the stabilization (no big deal for your use case).

      I hope it helps.

      El vie., 18 de oct. de 2019 a la(s) 20:07, Harold luzardo (haroldburtonl@gmail.com) escribió:
      Hello everyone,

      I consider myself Odoo fan, I know this software since version 6 named OpenERP, yes!! I'm old :D anyway I'm building up my own business "On-line Shop" and now is the time to implement Odoo. I have been playing with the 11 version but I know and I can see that the latest versions the company has been cutting off more and more modules, I looking to implement a fully operational Odoo using the CE version, I really don't care if it's not the latest version as far is working fine. Mu play is start and eventual in the future migrate to a better latest version. So I'm looking at some of your opinions regarding this, witch one you consider will be the best option for me to start. I can see that version 10 has most of the functionality just before things started to go south, one of the modules that I consider very important is the account module, after ver 10 the module is not there or limited.

      I really appreciate all your comments and goods advises.

      Regards,
      --
      --
      Harold g Luzardo b
      @Kickfliph
      GNU/Linux User #535193
      pub   2048R/0BCF3A23 2014-06-08
      Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23

      _______________________________________________
      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.)

      _______________________________________________
      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



      --

      --
      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 - 08:01 - 21 Oct 2019

  • XAdES in Odoo
    Hi All,

    After evaluating a couple of solutions, I decided to work on a PR to incorporate 
    XAdES signing into signxml library, which seems to be one of the better known
    xml signature libraries and is used in sime odoo EDI implementations (eg. PE).

    Please find the link below:


    Please touch ground if you would like to sponsor one of the marked items, as I'll
    only proceed to implement the MVP necessary for my own purpose.

    Nevertheless, it is designed to produce, both, fully conformant and interoperable
    XAdES signatures as per the defined ETSI base line and extended signature levels.


    Best Regards,

    David A.


    by dar - 11:11 - 18 Oct 2019

    7 replies 7 replies

  • [RFC] marketplaces connector module 
    Hello

We are working on a little maketplaces connector for small companies. It 
connects Odoo with a feed provider which will transform data to export towards 
marketplaces, prices comparators, etc. Everything is done with CSV files 
export-import because a lot of feed provider, specially small ones, work like 
this.
It was previously discussed in Roadmap Odoo 13 for retail industry :
https://github.com/odoo/odoo/issues/28179#issuecomment-462323744 
(and next comments).

First step is to have something working with Iziflux, a little french feed 
provider. But... How does field mapping should be build ? 
I ask because looking at OCA/connector-lengow (Lengow is a big feed provider), 
a lot of code is not Lengow related, but field mapping is hard-coded in a file. 
It's a pity.
I don't care if first step use hard-coded mapping. But later I would like to 
have something as generic as possible because all feed providers use nearly 
the same data and thus the connector should be easily adaptable.

Should we use a form ?
or simply a CSV to put in the module directory ?
or hard coding is good ?
or something else ?

(please CC me)

-- 
Librement,
Xavier Brochard / zeroheure
« La liberté est à l'homme ce que les ailes sont à l'oiseau » 
(Jean-Pierre Rosnay)
    by xavier - 04:10 - 18 Oct 2019

    1 replies 1 replies

    • Re: [RFC] marketplaces connector module 
      Hi Xavier, 

hardcoded mappings are easily getting a huge mess. I'd definitely
suggest a "per feed" export mapping that can be configured using the
backend.

Best Frederik

Am Freitag, den 18.10.2019, 14:11 +0000 schrieb Xavier Brochard:

> Hello

> 

> We are working on a little maketplaces connector for small companies.

> It 

> connects Odoo with a feed provider which will transform data to

> export towards 

> marketplaces, prices comparators, etc. Everything is done with CSV

> files 

> export-import because a lot of feed provider, specially small ones,

> work like 

> this.

> It was previously discussed in Roadmap Odoo 13 for retail industry :

> https://github.com/odoo/odoo/issues/28179#issuecomment-462323744 

> (and next comments).

> 

> First step is to have something working with Iziflux, a little french

> feed 

> provider. But... How does field mapping should be build ? 

> I ask because looking at OCA/connector-lengow (Lengow is a big feed

> provider), 

> a lot of code is not Lengow related, but field mapping is hard-coded

> in a file. 

> It's a pity.

> I don't care if first step use hard-coded mapping. But later I would

> like to 

> have something as generic as possible because all feed providers use

> nearly 

> the same data and thus the connector should be easily adaptable.

> 

> Should we use a form ?

> or simply a CSV to put in the module directory ?

> or hard coding is good ?

> or something else ?

> 

> (please CC me)

> 

> -- 

> Librement,

> Xavier Brochard / zeroheure

> « La liberté est à l'homme ce que les ailes sont à l'oiseau » 

> (Jean-Pierre Rosnay)

> 

> 

> _______________________________________________

> 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:26 - 18 Oct 2019
  • Becoming a PSC of OCA/storage
    Hi

    I would like to propose myself as PSC/Maintainer of OCA/storage. I'm an active contributor on this repo and only @sebastienbeau is part of this PSC at this moment.

    Regards

    lmi
    by Laurent Mignon - 01:21 - 18 Oct 2019

    14 replies 14 replies

  • Odoo to Odoo data migration tools

    Hello,

     

    I have more than one customer request to merge several single-company databases into a single multi-company database.

    The usual approaches all mean some level of data loss.

     

    Since the database schemas are the same, I’m wondering if it would be feasible to have a tool that would copy the data at the database level, while properly handling the record ids conversion.

     

    I’ve worked before with a tool that deal with that kind of problem – Anybox’s Anygrate.

    So I could have a try at a second generation of that tool.

     

    I wonder about other ideas?

     

    Thanks

    Daniel Reis

     

    by Daniel Reis <dreis.pt@hotmail.com> - 03:51 - 15 Oct 2019

    2 replies 2 replies

    • Re: Odoo to Odoo data migration tools
      Hi all,

      We have simple library that allows to transfer data between Odoo databases via XML-RPC or JSON-RPC.
      All you need is to define transfer schema and run data-transfer.
      It was used to transfer data (sales and purchases) from Odoo 7.0 to Odoo 9.0

      This library is available here: https://github.com/crnd-inc/odoo-transfer-lib

      вт, 15 жовт. 2019 о 20:42 Graeme Gellatly <gdgellatly@gmail.com> пише:
      The first generation would be fine of anygrate IF there arent too many duplicate records requiring discrimination you could get it all done in a just a few attempts. Config file the lot. I have an advanced fork of it somewhere optimized for speed and this kind of case, although I never tried it for merging multiple companies it should work.

      Main issue will be computed tree fields and sequences which will have to be dropped and recreated. Plus id sequences bumped. Ir property can also be a bit tricky. 

      On Wed, 16 Oct 2019, 2:51 AM Daniel Reis, <dreis.pt@hotmail.com> wrote:

      Hello,

       

      I have more than one customer request to merge several single-company databases into a single multi-company database.

      The usual approaches all mean some level of data loss.

       

      Since the database schemas are the same, I’m wondering if it would be feasible to have a tool that would copy the data at the database level, while properly handling the record ids conversion.

       

      I’ve worked before with a tool that deal with that kind of problem – Anybox’s Anygrate.

      So I could have a try at a second generation of that tool.

       

      I wonder about other ideas?

       

      Thanks

      Daniel Reis

       

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

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

      by dmytro.katyukha - 11:41 - 16 Oct 2019
    • Re: Odoo to Odoo data migration tools
      The first generation would be fine of anygrate IF there arent too many duplicate records requiring discrimination you could get it all done in a just a few attempts. Config file the lot. I have an advanced fork of it somewhere optimized for speed and this kind of case, although I never tried it for merging multiple companies it should work.

      Main issue will be computed tree fields and sequences which will have to be dropped and recreated. Plus id sequences bumped. Ir property can also be a bit tricky. 

      On Wed, 16 Oct 2019, 2:51 AM Daniel Reis, <dreis.pt@hotmail.com> wrote:

      Hello,

       

      I have more than one customer request to merge several single-company databases into a single multi-company database.

      The usual approaches all mean some level of data loss.

       

      Since the database schemas are the same, I’m wondering if it would be feasible to have a tool that would copy the data at the database level, while properly handling the record ids conversion.

       

      I’ve worked before with a tool that deal with that kind of problem – Anybox’s Anygrate.

      So I could have a try at a second generation of that tool.

       

      I wonder about other ideas?

       

      Thanks

      Daniel Reis

       

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

      by Graeme Gellatly - 07:40 - 15 Oct 2019
  • XSLT for Odoo Studio
    Hi Folks,

    I wrote a little stylesheet to transform Odoo Studio prototypes into raw python code.

    If you are interested, 
    • please check it out
    • propose improvements

    BR,

    David A.
    by dar - 05:50 - 14 Oct 2019
  • Runbot restart 
    Hello all,

I'm performing a server update on the runbot servers this morning. This
will require a reboot of the servers. Recent builds will be manually
rebuilt, but this will take a little time to get back.

Thanks for your patience.



-- 
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
    by Alexandre Fayolle - 09:31 - 13 Oct 2019

    8 replies 8 replies

  • Suggested ways for deploying odoo through docker-odoo-project
    Hi folks,

    I’m currently using camptocamp’s docker-odoo-project and akretion’s ak tool for local development and testing. It works like charm, thank you guys for building the great tools.

    I have one question though.  Why do we need either use on-build base image or COPY instruction in our own Dockerfile to copy the files and folders into container while we’ve already set the volume like `./odoo:/odoo` in the `docker-compose.yml` file. Is it a redundant job, or did I miss any point here? My guess is that when we copy everything in the container, we can build our own project specific docker image to be used in deployment process. This leads to my second question. How can we use the docker-odoo-project for deployment process? Simple ideas, suggestions or a sophisticated container orchestrating solutions are all welcomed, Thank you very much in advance.

    Best regards,

    Tony Gu 
    Skype: digitalsatori  Tel:56473822
    Mobile: 13386068213




    by Tony - 03:50 - 13 Oct 2019

    2 replies 2 replies

    • Re: Suggested ways for deploying odoo through docker-odoo-project
      Dear Guewen,

      Thank you very much for the enlightenment. That makes good sense. I will try to implement the CI process as you mentioned and follow your suggested workflow. 

      Best regards,

      Tony Gu 
      Skype: digitalsatori  Tel:56473822
      Mobile: 13386068213




      2019年10月14日 下午2:26，Guewen Baconnier <guewen.baconnier@camptocamp.com> 写道：

      Hi,

      When you work in dev locally, you wouldn't really need to COPY the files in the docker image, as, as you say, there is the volume.
      However, as soon as you want to deploy, you should not use the git repository anymore.
      The workflow we use is to build the image in CI (hence the COPY), run the tests in a container started from the new image, when tests are successful, the image is pushed to a registry. From there, the image can be deployed to test/staging/production environments.

      Guewen


      On Sun, Oct 13, 2019 at 3:51 AM Tony Gu <tony@openerp.cn> wrote:
      Hi folks,

      I’m currently using camptocamp’s docker-odoo-project and akretion’s ak tool for local development and testing. It works like charm, thank you guys for building the great tools.

      I have one question though.  Why do we need either use on-build base image or COPY instruction in our own Dockerfile to copy the files and folders into container while we’ve already set the volume like `./odoo:/odoo` in the `docker-compose.yml` file. Is it a redundant job, or did I miss any point here? My guess is that when we copy everything in the container, we can build our own project specific docker image to be used in deployment process. This leads to my second question. How can we use the docker-odoo-project for deployment process? Simple ideas, suggestions or a sophisticated container orchestrating solutions are all welcomed, Thank you very much in advance.

      Best regards,

      Tony Gu 
      Skype: digitalsatori  Tel:56473822
      Mobile: 13386068213




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


      by Tony - 01:01 - 14 Oct 2019
    • Re: Suggested ways for deploying odoo through docker-odoo-project
      Hi,

      When you work in dev locally, you wouldn't really need to COPY the files in the docker image, as, as you say, there is the volume.
      However, as soon as you want to deploy, you should not use the git repository anymore.
      The workflow we use is to build the image in CI (hence the COPY), run the tests in a container started from the new image, when tests are successful, the image is pushed to a registry. From there, the image can be deployed to test/staging/production environments.

      Guewen


      On Sun, Oct 13, 2019 at 3:51 AM Tony Gu <tony@openerp.cn> wrote:
      Hi folks,

      I’m currently using camptocamp’s docker-odoo-project and akretion’s ak tool for local development and testing. It works like charm, thank you guys for building the great tools.

      I have one question though.  Why do we need either use on-build base image or COPY instruction in our own Dockerfile to copy the files and folders into container while we’ve already set the volume like `./odoo:/odoo` in the `docker-compose.yml` file. Is it a redundant job, or did I miss any point here? My guess is that when we copy everything in the container, we can build our own project specific docker image to be used in deployment process. This leads to my second question. How can we use the docker-odoo-project for deployment process? Simple ideas, suggestions or a sophisticated container orchestrating solutions are all welcomed, Thank you very much in advance.

      Best regards,

      Tony Gu 
      Skype: digitalsatori  Tel:56473822
      Mobile: 13386068213




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

      by Guewen Baconnier - 08:25 - 14 Oct 2019
  • New library to migrate Odoo module code "odoo-migrate"
    Dear OCA Contributors,

    I am working on a migration from 8.0 to 12.0.
    For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)
    A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).

    I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the command
    pip3 install odoo-migrate

    Once installed, you can run the following command (other options are available)
    odoo-migrate -m my_module_name -i 8.0 -t 12.0

    It is based on the OCA recommendations available on this wiki.
    In addition to performing recurring operations,
    - the library also execute the weird format-patch command which I never remember (if asked).
    - it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)
    - it calls black for recent version
    - it realize commits

    1) If you're interested by such tool, you can review or test this project.

    2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.

    3) if some OCA members are OK, I can transfer this project under OCA umbrella.

    thank you for your feedback.

    kind regards.


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

    17 replies 17 replies

    • Re: New library to migrate Odoo module code "odoo-migrate"
      Hi Lois,

      Thanks for your interest.

      The project is still in a GRAP repository. I applied some remarks from the OCA community. (renaming project, add test, etc...)
      There are others contributions. Mainly from Acsone and akretion guys.

      The github repo is here : https://github.com/grap/odoo-module-migrator/ and available on Pypi :

      Feel free to participate and give feedback !

      I think that the project will be soon mature to move under OCA umbrella.

      regards.

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


      Le jeu. 21 nov. 2019 à 16:57, Lois Rilo Antelo <lois.rilo@eficent.com> a écrit :
      Hi all,

      Sorry I'm late to the party, this is a very interesting idea! Has it evolved since the last message? Is it already under OCA? Can somebody point me where the source code is now?

      Best regards,

      El lun., 14 oct. 2019 a las 19:02, Sylvain LE GAL (<sylvain.legal@grap.coop>) escribió:
      Hi all,

      First thanks all for your enthusiasm !

      About the name, OK to rename it. I'm not sure that if you want to rename the lib, or the command. For exemple, for git aggregator feature. The lib is named git-aggregator, and the command is gitaggregate. Can we continue the discussion here ?

      About the repository, if I understand correctly, it should be great to be under OCA umbrella, and in a stand-alone repository as proposed by Pedro and Stephane bidoul. Let's go renaming first, and moving owner of the lib after.

      The last week-end, I worked to integrate tests. Now, it includes tests that checks that initial V8 module are correctly migrated in V13. So I guess that it allows people to contribute avoiding regression.
      I also added tools to log (warning, error) if the migrated module depends on obsolete module based on the OpenUpgrade documentation.

      About the evolution, david Arnold, I did not feel the need to use pybowler for the time being, but feel free to make a Pull request using pybowler, if you want.

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


      Le lun. 14 oct. 2019 à 17:37, David Arnold <dar@xoe.solutions> a écrit :
      PS: As long as the tool strictly works on the workdir and does not attempt to interfere with database migration, the scope is clear, and the need is there :)

      On Mon, Oct 14, 2019 at 10:25 AM David Arnold <dar@xoe.solutions> wrote:
      Hi Silvain,

      there was coming something to my mind, I'd like to share.
      Some time ago, I worked with pybowler, which is a code transformar on the python grammar level.
      Like regex without the "regular" in it.

      It is super convenient to write certain transform scripts, And I'd suggest to use it for your library, as it is very easy to extend and very powerful.
      It would also be easy to make contributions and once community grows familiar with python grammar expressions, then it might unleash unprecedented productivity for OCA maintenance tasks and beyond.


      Based on facebook's excellent pybowler library.

      Best Regards,

      David A.

      On Fri, Oct 11, 2019 at 5:39 PM David Arnold <dar@xoe.solutions> wrote:
      +1 stephane comment about standalone
      +1 about resist feature creep

      Hasn't there been some proposal going around to have OCA-libs as a Github orga for those standalone projects to be hosted / promoted?

      There is python-xmlsig and python-xades from Eric and many others too.

      El vie., 11 oct. 2019, 9:16 a.m., Simone Orsi <simahawk@gmail.com> escribió:
      Nice! Thanks Sylvain.

      +1 for standalone project as well :)

      On Fri, Oct 11, 2019 at 2:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      +1 to keep it a standalone project. I'd rather see the good parts of OCA/maintainer-tools become standalone projects too.

      Regarding growing features, be strong Sylvain, resist scope creep :) Do one thing and do it well!

      -sbi


      On Fri, Oct 11, 2019 at 2:47 PM David Arnold <dar@xoe.solutions> wrote:
      Re: Do you plan to grow features or is it limited to make those repetitive tasks more scriptable?

      On Fri, Oct 11, 2019 at 3:12 AM David Beal <david.beal@akretion.com> wrote:
      génial


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


      Le jeu. 10 oct. 2019 à 18:12, Sylvain LE GAL <sylvain.legal@grap.coop> a écrit :
      Dear OCA Contributors,

      I am working on a migration from 8.0 to 12.0.
      For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)
      A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).

      I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the command
      pip3 install odoo-migrate

      Once installed, you can run the following command (other options are available)
      odoo-migrate -m my_module_name -i 8.0 -t 12.0

      It is based on the OCA recommendations available on this wiki.
      In addition to performing recurring operations,
      - the library also execute the weird format-patch command which I never remember (if asked).
      - it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)
      - it calls black for recent version
      - it realize commits

      1) If you're interested by such tool, you can review or test this project.

      2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.

      3) if some OCA members are OK, I can transfer this project under OCA umbrella.

      thank you for your feedback.

      kind regards.


      Sylvain LE GAL - Twitter
      GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
      Site Web | FramaSphere | Facebook
      3 Grande rue des Feuillants, 69001 Lyon
      Bureau : (+33) 09.72.32.33.17 - Astreinte : (+33) 06.81.85.61.43
      Member of the OCA (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

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

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

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

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

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

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



      --
      Lois Rilo Antelo
      Eficent Business and IT Consulting Services, S.L.
      (+34) 679052448 | lois.rilo@eficent.com | http://www.eficent.com
      Twitter: lreficent_erp

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

      by Sylvain LE GAL - 03:10 - 26 Nov 2019
    • Re: New library to migrate Odoo module code "odoo-migrate"
      Hi all,

      Sorry I'm late to the party, this is a very interesting idea! Has it evolved since the last message? Is it already under OCA? Can somebody point me where the source code is now?

      Best regards,

      El lun., 14 oct. 2019 a las 19:02, Sylvain LE GAL (<sylvain.legal@grap.coop>) escribió:
      Hi all,

      First thanks all for your enthusiasm !

      About the name, OK to rename it. I'm not sure that if you want to rename the lib, or the command. For exemple, for git aggregator feature. The lib is named git-aggregator, and the command is gitaggregate. Can we continue the discussion here ?

      About the repository, if I understand correctly, it should be great to be under OCA umbrella, and in a stand-alone repository as proposed by Pedro and Stephane bidoul. Let's go renaming first, and moving owner of the lib after.

      The last week-end, I worked to integrate tests. Now, it includes tests that checks that initial V8 module are correctly migrated in V13. So I guess that it allows people to contribute avoiding regression.
      I also added tools to log (warning, error) if the migrated module depends on obsolete module based on the OpenUpgrade documentation.

      About the evolution, david Arnold, I did not feel the need to use pybowler for the time being, but feel free to make a Pull request using pybowler, if you want.

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


      Le lun. 14 oct. 2019 à 17:37, David Arnold <dar@xoe.solutions> a écrit :
      PS: As long as the tool strictly works on the workdir and does not attempt to interfere with database migration, the scope is clear, and the need is there :)

      On Mon, Oct 14, 2019 at 10:25 AM David Arnold <dar@xoe.solutions> wrote:
      Hi Silvain,

      there was coming something to my mind, I'd like to share.
      Some time ago, I worked with pybowler, which is a code transformar on the python grammar level.
      Like regex without the "regular" in it.

      It is super convenient to write certain transform scripts, And I'd suggest to use it for your library, as it is very easy to extend and very powerful.
      It would also be easy to make contributions and once community grows familiar with python grammar expressions, then it might unleash unprecedented productivity for OCA maintenance tasks and beyond.


      Based on facebook's excellent pybowler library.

      Best Regards,

      David A.

      On Fri, Oct 11, 2019 at 5:39 PM David Arnold <dar@xoe.solutions> wrote:
      +1 stephane comment about standalone
      +1 about resist feature creep

      Hasn't there been some proposal going around to have OCA-libs as a Github orga for those standalone projects to be hosted / promoted?

      There is python-xmlsig and python-xades from Eric and many others too.

      El vie., 11 oct. 2019, 9:16 a.m., Simone Orsi <simahawk@gmail.com> escribió:
      Nice! Thanks Sylvain.

      +1 for standalone project as well :)

      On Fri, Oct 11, 2019 at 2:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      +1 to keep it a standalone project. I'd rather see the good parts of OCA/maintainer-tools become standalone projects too.

      Regarding growing features, be strong Sylvain, resist scope creep :) Do one thing and do it well!

      -sbi


      On Fri, Oct 11, 2019 at 2:47 PM David Arnold <dar@xoe.solutions> wrote:
      Re: Do you plan to grow features or is it limited to make those repetitive tasks more scriptable?

      On Fri, Oct 11, 2019 at 3:12 AM David Beal <david.beal@akretion.com> wrote:
      génial


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


      Le jeu. 10 oct. 2019 à 18:12, Sylvain LE GAL <sylvain.legal@grap.coop> a écrit :
      Dear OCA Contributors,

      I am working on a migration from 8.0 to 12.0.
      For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)
      A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).

      I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the command
      pip3 install odoo-migrate

      Once installed, you can run the following command (other options are available)
      odoo-migrate -m my_module_name -i 8.0 -t 12.0

      It is based on the OCA recommendations available on this wiki.
      In addition to performing recurring operations,
      - the library also execute the weird format-patch command which I never remember (if asked).
      - it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)
      - it calls black for recent version
      - it realize commits

      1) If you're interested by such tool, you can review or test this project.

      2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.

      3) if some OCA members are OK, I can transfer this project under OCA umbrella.

      thank you for your feedback.

      kind regards.


      Sylvain LE GAL - Twitter
      GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
      Site Web | FramaSphere | Facebook
      3 Grande rue des Feuillants, 69001 Lyon
      Bureau : (+33) 09.72.32.33.17 - Astreinte : (+33) 06.81.85.61.43
      Member of the OCA (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

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

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

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

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

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

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



      --
      Lois Rilo Antelo
      Eficent Business and IT Consulting Services, S.L.
      (+34) 679052448 | lois.rilo@eficent.com | http://www.eficent.com
      Twitter: lreficent_erp
      by Lois Rilo Antelo - 04:56 - 21 Nov 2019
    • Re: New library to migrate Odoo module code "odoo-migrate"
      Hi all,

      First thanks all for your enthusiasm !

      About the name, OK to rename it. I'm not sure that if you want to rename the lib, or the command. For exemple, for git aggregator feature. The lib is named git-aggregator, and the command is gitaggregate. Can we continue the discussion here ?

      About the repository, if I understand correctly, it should be great to be under OCA umbrella, and in a stand-alone repository as proposed by Pedro and Stephane bidoul. Let's go renaming first, and moving owner of the lib after.

      The last week-end, I worked to integrate tests. Now, it includes tests that checks that initial V8 module are correctly migrated in V13. So I guess that it allows people to contribute avoiding regression.
      I also added tools to log (warning, error) if the migrated module depends on obsolete module based on the OpenUpgrade documentation.

      About the evolution, david Arnold, I did not feel the need to use pybowler for the time being, but feel free to make a Pull request using pybowler, if you want.

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


      Le lun. 14 oct. 2019 à 17:37, David Arnold <dar@xoe.solutions> a écrit :
      PS: As long as the tool strictly works on the workdir and does not attempt to interfere with database migration, the scope is clear, and the need is there :)

      On Mon, Oct 14, 2019 at 10:25 AM David Arnold <dar@xoe.solutions> wrote:
      Hi Silvain,

      there was coming something to my mind, I'd like to share.
      Some time ago, I worked with pybowler, which is a code transformar on the python grammar level.
      Like regex without the "regular" in it.

      It is super convenient to write certain transform scripts, And I'd suggest to use it for your library, as it is very easy to extend and very powerful.
      It would also be easy to make contributions and once community grows familiar with python grammar expressions, then it might unleash unprecedented productivity for OCA maintenance tasks and beyond.


      Based on facebook's excellent pybowler library.

      Best Regards,

      David A.

      On Fri, Oct 11, 2019 at 5:39 PM David Arnold <dar@xoe.solutions> wrote:
      +1 stephane comment about standalone
      +1 about resist feature creep

      Hasn't there been some proposal going around to have OCA-libs as a Github orga for those standalone projects to be hosted / promoted?

      There is python-xmlsig and python-xades from Eric and many others too.

      El vie., 11 oct. 2019, 9:16 a.m., Simone Orsi <simahawk@gmail.com> escribió:
      Nice! Thanks Sylvain.

      +1 for standalone project as well :)

      On Fri, Oct 11, 2019 at 2:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      +1 to keep it a standalone project. I'd rather see the good parts of OCA/maintainer-tools become standalone projects too.

      Regarding growing features, be strong Sylvain, resist scope creep :) Do one thing and do it well!

      -sbi


      On Fri, Oct 11, 2019 at 2:47 PM David Arnold <dar@xoe.solutions> wrote:
      Re: Do you plan to grow features or is it limited to make those repetitive tasks more scriptable?

      On Fri, Oct 11, 2019 at 3:12 AM David Beal <david.beal@akretion.com> wrote:
      génial


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


      Le jeu. 10 oct. 2019 à 18:12, Sylvain LE GAL <sylvain.legal@grap.coop> a écrit :
      Dear OCA Contributors,

      I am working on a migration from 8.0 to 12.0.
      For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)
      A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).

      I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the command
      pip3 install odoo-migrate

      Once installed, you can run the following command (other options are available)
      odoo-migrate -m my_module_name -i 8.0 -t 12.0

      It is based on the OCA recommendations available on this wiki.
      In addition to performing recurring operations,
      - the library also execute the weird format-patch command which I never remember (if asked).
      - it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)
      - it calls black for recent version
      - it realize commits

      1) If you're interested by such tool, you can review or test this project.

      2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.

      3) if some OCA members are OK, I can transfer this project under OCA umbrella.

      thank you for your feedback.

      kind regards.


      Sylvain LE GAL - Twitter
      GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
      Site Web | FramaSphere | Facebook
      3 Grande rue des Feuillants, 69001 Lyon
      Bureau : (+33) 09.72.32.33.17 - Astreinte : (+33) 06.81.85.61.43
      Member of the OCA (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

      _______________________________________________
      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 Sylvain LE GAL - 07:00 - 14 Oct 2019
    • Re: New library to migrate Odoo module code "odoo-migrate"
      PS: As long as the tool strictly works on the workdir and does not attempt to interfere with database migration, the scope is clear, and the need is there :)

      On Mon, Oct 14, 2019 at 10:25 AM David Arnold <dar@xoe.solutions> wrote:
      Hi Silvain,

      there was coming something to my mind, I'd like to share.
      Some time ago, I worked with pybowler, which is a code transformar on the python grammar level.
      Like regex without the "regular" in it.

      It is super convenient to write certain transform scripts, And I'd suggest to use it for your library, as it is very easy to extend and very powerful.
      It would also be easy to make contributions and once community grows familiar with python grammar expressions, then it might unleash unprecedented productivity for OCA maintenance tasks and beyond.


      Based on facebook's excellent pybowler library.

      Best Regards,

      David A.

      On Fri, Oct 11, 2019 at 5:39 PM David Arnold <dar@xoe.solutions> wrote:
      +1 stephane comment about standalone
      +1 about resist feature creep

      Hasn't there been some proposal going around to have OCA-libs as a Github orga for those standalone projects to be hosted / promoted?

      There is python-xmlsig and python-xades from Eric and many others too.

      El vie., 11 oct. 2019, 9:16 a.m., Simone Orsi <simahawk@gmail.com> escribió:
      Nice! Thanks Sylvain.

      +1 for standalone project as well :)

      On Fri, Oct 11, 2019 at 2:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      +1 to keep it a standalone project. I'd rather see the good parts of OCA/maintainer-tools become standalone projects too.

      Regarding growing features, be strong Sylvain, resist scope creep :) Do one thing and do it well!

      -sbi


      On Fri, Oct 11, 2019 at 2:47 PM David Arnold <dar@xoe.solutions> wrote:
      Re: Do you plan to grow features or is it limited to make those repetitive tasks more scriptable?

      On Fri, Oct 11, 2019 at 3:12 AM David Beal <david.beal@akretion.com> wrote:
      génial


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


      Le jeu. 10 oct. 2019 à 18:12, Sylvain LE GAL <sylvain.legal@grap.coop> a écrit :
      Dear OCA Contributors,

      I am working on a migration from 8.0 to 12.0.
      For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)
      A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).

      I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the command
      pip3 install odoo-migrate

      Once installed, you can run the following command (other options are available)
      odoo-migrate -m my_module_name -i 8.0 -t 12.0

      It is based on the OCA recommendations available on this wiki.
      In addition to performing recurring operations,
      - the library also execute the weird format-patch command which I never remember (if asked).
      - it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)
      - it calls black for recent version
      - it realize commits

      1) If you're interested by such tool, you can review or test this project.

      2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.

      3) if some OCA members are OK, I can transfer this project under OCA umbrella.

      thank you for your feedback.

      kind regards.


      Sylvain LE GAL - Twitter
      GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
      Site Web | FramaSphere | Facebook
      3 Grande rue des Feuillants, 69001 Lyon
      Bureau : (+33) 09.72.32.33.17 - Astreinte : (+33) 06.81.85.61.43
      Member of the OCA (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

      _______________________________________________
      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 dar - 05:36 - 14 Oct 2019
    • Re: New library to migrate Odoo module code "odoo-migrate"
      Hi Silvain,

      there was coming something to my mind, I'd like to share.
      Some time ago, I worked with pybowler, which is a code transformar on the python grammar level.
      Like regex without the "regular" in it.

      It is super convenient to write certain transform scripts, And I'd suggest to use it for your library, as it is very easy to extend and very powerful.
      It would also be easy to make contributions and once community grows familiar with python grammar expressions, then it might unleash unprecedented productivity for OCA maintenance tasks and beyond.


      Based on facebook's excellent pybowler library.

      Best Regards,

      David A.

      On Fri, Oct 11, 2019 at 5:39 PM David Arnold <dar@xoe.solutions> wrote:
      +1 stephane comment about standalone
      +1 about resist feature creep

      Hasn't there been some proposal going around to have OCA-libs as a Github orga for those standalone projects to be hosted / promoted?

      There is python-xmlsig and python-xades from Eric and many others too.

      El vie., 11 oct. 2019, 9:16 a.m., Simone Orsi <simahawk@gmail.com> escribió:
      Nice! Thanks Sylvain.

      +1 for standalone project as well :)

      On Fri, Oct 11, 2019 at 2:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      +1 to keep it a standalone project. I'd rather see the good parts of OCA/maintainer-tools become standalone projects too.

      Regarding growing features, be strong Sylvain, resist scope creep :) Do one thing and do it well!

      -sbi


      On Fri, Oct 11, 2019 at 2:47 PM David Arnold <dar@xoe.solutions> wrote:
      Re: Do you plan to grow features or is it limited to make those repetitive tasks more scriptable?

      On Fri, Oct 11, 2019 at 3:12 AM David Beal <david.beal@akretion.com> wrote:
      génial


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


      Le jeu. 10 oct. 2019 à 18:12, Sylvain LE GAL <sylvain.legal@grap.coop> a écrit :
      Dear OCA Contributors,

      I am working on a migration from 8.0 to 12.0.
      For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)
      A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).

      I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the command
      pip3 install odoo-migrate

      Once installed, you can run the following command (other options are available)
      odoo-migrate -m my_module_name -i 8.0 -t 12.0

      It is based on the OCA recommendations available on this wiki.
      In addition to performing recurring operations,
      - the library also execute the weird format-patch command which I never remember (if asked).
      - it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)
      - it calls black for recent version
      - it realize commits

      1) If you're interested by such tool, you can review or test this project.

      2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.

      3) if some OCA members are OK, I can transfer this project under OCA umbrella.

      thank you for your feedback.

      kind regards.


      Sylvain LE GAL - Twitter
      GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
      Site Web | FramaSphere | Facebook
      3 Grande rue des Feuillants, 69001 Lyon
      Bureau : (+33) 09.72.32.33.17 - Astreinte : (+33) 06.81.85.61.43
      Member of the OCA (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

      _______________________________________________
      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 dar - 05:31 - 14 Oct 2019

  • Little bounty proposals : Payment plugin and feed export 
    Hello

I'm looking for someone to code ! I think it is simple but too long or too 
difficult for me. My budget is very small : around 1000€
There is two projects, all free (GPL) :

1. Port the Lyra / Payzen Odoo payment acquirer to #13. It is an international 
payment solution, their plugin is already available with Odoo 10 to 12 and 
need to be adapted to version #13. https://github.com/lyra/plugin-odoo
See https://payzen.eu/ and https://lyra.com/ for information on their solution

2. We need a very basical solution to connect to multi-channel feed 
distribution services (typicaly to sell  across many marketplaces). Our target 
is Iziflux (France only), but it should be possibly customized to other feeds. 
We need to export products and stocks and to import sales with customers data 
periodicaly.
A CSV export-import based on odoo-connector will do the job in most cases.


-- 
Librement,
Xavier Brochard / zeroheure
« La liberté est à l'homme ce que les ailes sont à l'oiseau » 
(Jean-Pierre Rosnay)
    by xavier - 05:26 - 9 Oct 2019
  • CodeTriage "app"
    Hello,

    Maybe some of you already know CodeTriage. 
    For those who don't know it yet, it's a platform that allow you to receive (by mail) some bugs (github issues) of public project to help them handle those issues. 
    Here is a page explaining what's this app for: https://www.codetriage.com/what

    I noticed Odoo is there: https://www.codetriage.com/odoo/odoo

    Seems the public GitHub repo has to register to appear in the list of projects to help.

    Question: Do you think it's worth it for OCA repo to register to this app? 

    IMHO, if some OCA repo were registered there, I would subscribe.
    What about you?

    Have a nice day

    Cheers,

    -- 
    Damien Crier
    Camptocamp France SAS
    18 rue du Lac Saint André
    Savoie Technolac - Bâtiment Le Dauphin
    F-73370 Le Bourget du Lac
    
http://www.camptocamp.com
    by Damien Crier - 09:11 - 8 Oct 2019

    3 replies 3 replies

    • Re: CodeTriage "app"
      My main issue is kind of similar to pedro.

      Oca repos are arbitrary collections of topic modules. Some repos are closely associated with particular authors, partners and maintainers, e.g donation, queue some are all sorts.

      We would be better I think using a specific issue template format that a bot can determine who best to triage to. Could even be as simple as just reading an ini style format in a repo root.

      I saw a good pr/ issue template on the pylint repo the other day.

      On Tue, 8 Oct 2019, 10:47 PM Alexandre Fayolle, <alexandre.fayolle@camptocamp.com> wrote:
      Is there a way to 'tag' blueprint issues or 'work needed' issues to get
CodeTriage to work on this?

Is there a way to get CodeTriage to look for "needs review" pull requests?

Alexandre

On 08/10/2019 11:22, Pedro M. Baeza (Tecnativa) wrote:


> Thanks for the initiative, Damien,


> 


> I have subscribed to Odoo one to see how it works.


> 


> The initial cons I see are:


> 


> 1. We have a lot of repos, not one, and constantly growing.


> 2. A lot of issues belongs to blueprints or migration tracking, so they


> don't apply directly to this process.


> 


> Regards.


> 


> _______________________________________________


> 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

      by Graeme Gellatly - 08:36 - 8 Oct 2019
    • CodeTriage "app" 
      Is there a way to 'tag' blueprint issues or 'work needed' issues to get
CodeTriage to work on this?

Is there a way to get CodeTriage to look for "needs review" pull requests?

Alexandre

On 08/10/2019 11:22, Pedro M. Baeza (Tecnativa) wrote:

> Thanks for the initiative, Damien,

> 

> I have subscribed to Odoo one to see how it works.

> 

> The initial cons I see are:

> 

> 1. We have a lot of repos, not one, and constantly growing.

> 2. A lot of issues belongs to blueprints or migration tracking, so they

> don't apply directly to this process.

> 

> Regards.

> 

> _______________________________________________

> 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
      by Alexandre Fayolle - 11:45 - 8 Oct 2019
    • Re: CodeTriage "app"
      Thanks for the initiative, Damien,

      I have subscribed to Odoo one to see how it works.

      The initial cons I see are:

      1. We have a lot of repos, not one, and constantly growing.
      2. A lot of issues belongs to blueprints or migration tracking, so they don't apply directly to this process.

      Regards.
      by Pedro M. Baeza - 11:21 - 8 Oct 2019
  • 2019 OCA Extra Delegates Campaign is NOW OPEN

    Dear OCA Contributors,


    As you may be aware the decision to run an extra campaign to fill the remaining 7 Delegate positions for this year has been made. 

    The 3 new Delegates from the earlier election were: 
    • Yves Goldberg
    • Simone Orsi
    • Sergio Teruel Albert
    The new campaign is now open and will run from today until the 18th of October, 2019. The current Board Member and Financial Auditor Campaign will be suspended until October 28th, 2019.

    Why?


    There are 10 places each year for new Delegates. This year's previous election only had 3 new Delegates elected leaving 7 positions to be filled.

    The Delegate Assembly is the Association’s supreme authority. Each Delegate member is entitled to one vote at the Delegate Assembly. Decisions of the Delegate Assembly are taken by a majority vote of the Delegate members present and voting. For further details, please read the Bylaws.


    How?


    To apply as a candidate, you have to:

    The campaign will be closed on October 18th, 2019.


    Then what?


    The vote will be open from October 19th to October 25th, 2019: Current OCA Delegates will vote for 7 new Delegates among the candidates.


    The results of the election will be announced on October 26th, 2019.


    The 10 new Delegates and existing Delegates will then take part in:

    • the 2019 OCA Board Member Campaign from October 28th to November 8th, 2019.

    • the 2019 OCA Financial Auditor Campaign from October 28th to November 8th, 2019.

    • the 2019 General Assembly from November 11th to November 22nd, 2019.


    Should you have any questions, please get in touch.


    Warm regards,

    Rebecca--
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 01:26 - 8 Oct 2019

    1 replies 1 replies

    • Re: 2019 OCA Extra Delegates Campaign is NOW OPEN
      Rebecca I have passed the invoices for the 3 membership to our finance team, as soon as they pay, we can postulate as delegates, after that all we have to do is fill the form? 


      It is asking to be logged in order to do it and we do not have users :D

      Let me know

      Thanks!



      El mar., 8 de oct. de 2019 a la(s) 01:27, Rebecca Gellatly (rebecca@o4sb.com) escribió:

      Dear OCA Contributors,


      As you may be aware the decision to run an extra campaign to fill the remaining 7 Delegate positions for this year has been made. 

      The 3 new Delegates from the earlier election were: 
      • Yves Goldberg
      • Simone Orsi
      • Sergio Teruel Albert
      The new campaign is now open and will run from today until the 18th of October, 2019. The current Board Member and Financial Auditor Campaign will be suspended until October 28th, 2019.

      Why?


      There are 10 places each year for new Delegates. This year's previous election only had 3 new Delegates elected leaving 7 positions to be filled.

      The Delegate Assembly is the Association’s supreme authority. Each Delegate member is entitled to one vote at the Delegate Assembly. Decisions of the Delegate Assembly are taken by a majority vote of the Delegate members present and voting. For further details, please read the Bylaws.


      How?


      To apply as a candidate, you have to:

      The campaign will be closed on October 18th, 2019.


      Then what?


      The vote will be open from October 19th to October 25th, 2019: Current OCA Delegates will vote for 7 new Delegates among the candidates.


      The results of the election will be announced on October 26th, 2019.


      The 10 new Delegates and existing Delegates will then take part in:

      • the 2019 OCA Board Member Campaign from October 28th to November 8th, 2019.

      • the 2019 OCA Financial Auditor Campaign from October 28th to November 8th, 2019.

      • the 2019 General Assembly from November 11th to November 22nd, 2019.


      Should you have any questions, please get in touch.


      Warm regards,

      Rebecca--
      Rebecca Gellatly
      General Secretary
      Odoo Community Association

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

      by Gonzalo Ruzafa - 02:21 - 8 Oct 2019
  • Linting for 13.0 branches (using black and pre-commit)
    Dear contributors,

    Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.

    This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.

    In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.

    At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.

    TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:
    • run Black before committing your code on the 13.0 branches
    • sort imports (stdlib, odoo, odoo.addons, local imports)
    • To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
    If you are interested in practical details and the rationale, read on.

    pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:
    • installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
    • you then run "pre-commit install" after cloning a repository
    • lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
    • some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
    • all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
    • a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
    The proposed configuration includes the following linters:
    • black, with default options (to facilitate usage)
    • auto fix trailing whitespace
    • auto fix newline at end of files
    • detect debug statements
    • flake8 with same options as before (except line length which is now the 88 black default)
    • pyupgrade, to encourage python 3 idioms
    • pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
    • pylint with all checks (optional + mandatory), not failing
    • isort to automatically sort imports (except in __init__.py where import order might be significant)
    • run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
    You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,
    • checkout these branches
    • run 'pre-commit install'
    • start committing lint failures to see the effect.
    If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/files

    In practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.

    When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.

    Looking forward to reading your feedback.

    Best regards,

    -sbi


    by Stéphane Bidoul - 12:56 - 7 Oct 2019

    18 replies 18 replies

    • Re: Linting for 13.0 branches (using black and pre-commit)

      On Mon, Oct 14, 2019 at 4:42 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Dear contributors,

      The new configurations are in place for the 13.0 branches.

      The blog post has all the details.

      Side note: the travis configuration has been reset to default on all 13.0 branches, so if there was a specific config for your repo, it needs to be reapplied manually as the module are migrated.

      Let us know of any issue / question.

      Enjoy!

      -sbi


      On Tue, Oct 8, 2019 at 9:56 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
      +1

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



      On Tue, Oct 8, 2019 at 12:52 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
      +1

      Le lun. 7 oct. 2019 à 18:12, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :
      +1 from "Numigiens"

      Have a good day from Canada!
      Bruno Joliveau - Architecte applications - Président
      NUMIGI SOLUTIONS INC.
      (514) 317-7944

      Longueuil, Québec, Canada



      Le lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
      Dear contributors,

      Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.

      This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.

      In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.

      At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.

      TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:
      • run Black before committing your code on the 13.0 branches
      • sort imports (stdlib, odoo, odoo.addons, local imports)
      • To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
      If you are interested in practical details and the rationale, read on.

      pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:
      • installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
      • you then run "pre-commit install" after cloning a repository
      • lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
      • some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
      • all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
      • a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
      The proposed configuration includes the following linters:
      • black, with default options (to facilitate usage)
      • auto fix trailing whitespace
      • auto fix newline at end of files
      • detect debug statements
      • flake8 with same options as before (except line length which is now the 88 black default)
      • pyupgrade, to encourage python 3 idioms
      • pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
      • pylint with all checks (optional + mandatory), not failing
      • isort to automatically sort imports (except in __init__.py where import order might be significant)
      • run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
      You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,
      • checkout these branches
      • run 'pre-commit install'
      • start committing lint failures to see the effect.
      If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/files

      In practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.

      When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.

      Looking forward to reading your feedback.

      Best regards,

      -sbi


      _______________________________________________
      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 dar - 05:41 - 14 Oct 2019
    • Re: Linting for 13.0 branches (using black and pre-commit)
      Dear contributors,

      The new configurations are in place for the 13.0 branches.

      The blog post has all the details.

      Side note: the travis configuration has been reset to default on all 13.0 branches, so if there was a specific config for your repo, it needs to be reapplied manually as the module are migrated.

      Let us know of any issue / question.

      Enjoy!

      -sbi


      On Tue, Oct 8, 2019 at 9:56 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
      +1

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



      On Tue, Oct 8, 2019 at 12:52 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
      +1

      Le lun. 7 oct. 2019 à 18:12, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :
      +1 from "Numigiens"

      Have a good day from Canada!
      Bruno Joliveau - Architecte applications - Président
      NUMIGI SOLUTIONS INC.
      (514) 317-7944

      Longueuil, Québec, Canada



      Le lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
      Dear contributors,

      Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.

      This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.

      In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.

      At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.

      TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:
      • run Black before committing your code on the 13.0 branches
      • sort imports (stdlib, odoo, odoo.addons, local imports)
      • To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
      If you are interested in practical details and the rationale, read on.

      pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:
      • installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
      • you then run "pre-commit install" after cloning a repository
      • lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
      • some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
      • all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
      • a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
      The proposed configuration includes the following linters:
      • black, with default options (to facilitate usage)
      • auto fix trailing whitespace
      • auto fix newline at end of files
      • detect debug statements
      • flake8 with same options as before (except line length which is now the 88 black default)
      • pyupgrade, to encourage python 3 idioms
      • pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
      • pylint with all checks (optional + mandatory), not failing
      • isort to automatically sort imports (except in __init__.py where import order might be significant)
      • run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
      You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,
      • checkout these branches
      • run 'pre-commit install'
      • start committing lint failures to see the effect.
      If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/files

      In practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.

      When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.

      Looking forward to reading your feedback.

      Best regards,

      -sbi


      _______________________________________________
      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 - 11:41 - 14 Oct 2019
    • Re: Linting for 13.0 branches (using black and pre-commit)
      +1

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



      On Tue, Oct 8, 2019 at 12:52 PM Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
      +1

      Le lun. 7 oct. 2019 à 18:12, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :
      +1 from "Numigiens"

      Have a good day from Canada!
      Bruno Joliveau - Architecte applications - Président
      NUMIGI SOLUTIONS INC.
      (514) 317-7944

      Longueuil, Québec, Canada



      Le lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
      Dear contributors,

      Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.

      This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.

      In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.

      At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.

      TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:
      • run Black before committing your code on the 13.0 branches
      • sort imports (stdlib, odoo, odoo.addons, local imports)
      • To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
      If you are interested in practical details and the rationale, read on.

      pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:
      • installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
      • you then run "pre-commit install" after cloning a repository
      • lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
      • some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
      • all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
      • a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
      The proposed configuration includes the following linters:
      • black, with default options (to facilitate usage)
      • auto fix trailing whitespace
      • auto fix newline at end of files
      • detect debug statements
      • flake8 with same options as before (except line length which is now the 88 black default)
      • pyupgrade, to encourage python 3 idioms
      • pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
      • pylint with all checks (optional + mandatory), not failing
      • isort to automatically sort imports (except in __init__.py where import order might be significant)
      • run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
      You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,
      • checkout these branches
      • run 'pre-commit install'
      • start committing lint failures to see the effect.
      If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/files

      In practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.

      When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.

      Looking forward to reading your feedback.

      Best regards,

      -sbi


      _______________________________________________
      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 Maxime Chambreuil - 09:56 - 8 Oct 2019
    • Re: Linting for 13.0 branches (using black and pre-commit)
      +1

      Le lun. 7 oct. 2019 à 18:12, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :
      +1 from "Numigiens"

      Have a good day from Canada!
      Bruno Joliveau - Architecte applications - Président
      NUMIGI SOLUTIONS INC.
      (514) 317-7944

      Longueuil, Québec, Canada



      Le lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
      Dear contributors,

      Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.

      This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.

      In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.

      At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.

      TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:
      • run Black before committing your code on the 13.0 branches
      • sort imports (stdlib, odoo, odoo.addons, local imports)
      • To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
      If you are interested in practical details and the rationale, read on.

      pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:
      • installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
      • you then run "pre-commit install" after cloning a repository
      • lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
      • some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
      • all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
      • a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
      The proposed configuration includes the following linters:
      • black, with default options (to facilitate usage)
      • auto fix trailing whitespace
      • auto fix newline at end of files
      • detect debug statements
      • flake8 with same options as before (except line length which is now the 88 black default)
      • pyupgrade, to encourage python 3 idioms
      • pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
      • pylint with all checks (optional + mandatory), not failing
      • isort to automatically sort imports (except in __init__.py where import order might be significant)
      • run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
      You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,
      • checkout these branches
      • run 'pre-commit install'
      • start committing lint failures to see the effect.
      If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/files

      In practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.

      When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.

      Looking forward to reading your feedback.

      Best regards,

      -sbi


      _______________________________________________
      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 Joël Grand Guillaume - 07:46 - 8 Oct 2019
    • Re: Linting for 13.0 branches (using black and pre-commit)
      +1 from "Numigiens"

      Have a good day from Canada!
      Bruno Joliveau - Architecte applications - Président
      NUMIGI SOLUTIONS INC.
      (514) 317-7944

      Longueuil, Québec, Canada



      Le lun. 7 oct. 2019 à 06:56, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
      Dear contributors,

      Following a recent conversation on twitter, and further talks during #OCAdays, there seems to be a wide interest for using Black [1] as a code formatter for OCA code.

      This post explains the proposed approach to implement it in OCA, as well as several improvements to code linting tools.

      In a nutshell, Black is a python code formatter that quickly gained traction in the Python community in the last couple of years. It formats the code for you with a predefined set of rules and almost no options so as to free your mind for more important matters.

      At #OCAdays, we discussed on how to put it in practice, and it was proposed to take the opportunity of this change to introduce pre-commit [2] as the linting framework for OCA in the 13.0 branches.

      TL;DR: If you are not interested in the nitty gritty details, the only change you will need to remember compared to your current workflow is:
      • run Black before committing your code on the 13.0 branches
      • sort imports (stdlib, odoo, odoo.addons, local imports)
      • To save time, install pre-commit and run pre-commit install after cloning an OCA repository on the 13.0 branch. Linting, running black and sorting imports will be done automatically for you when you commit. You can also run it manually with 'pre-commit run --all-files'.
      If you are interested in practical details and the rationale, read on.

      pre-commit is a tool that lets contributors easily run lint checks locally in a consistent and reproducible manner. These checks are then run again by Travis to be sure conventions are enforced. In principle this is similar to what we are doing now with MQT LINT_CHECK="1", with the following beneficial differences:
      • installation of the linters locally is easier: only one tool needs to be installed on developer's machines: pre-commit, which will then take care of installing all the required linters for you
      • you then run "pre-commit install" after cloning a repository
      • lint checks are then run automatically when creating a commit locally so you can detect errors much earlier, without having to wait for Travis to detect them for you
      • some linters (such as Black, and the import sorter) fix the code for you, so you immediately have the diff available with all fixes to commit
      • all configurations are stored locally in the repository using default configuration files (.pylintrc, .flake8, etc); this means your favorite IDE will pick them up automatically to give you assistance in detecting and fixing errors
      • a wide variety of pre-commit plugins exist, which means we can easily benefit from them and progressively add more in the future
      The proposed configuration includes the following linters:
      • black, with default options (to facilitate usage)
      • auto fix trailing whitespace
      • auto fix newline at end of files
      • detect debug statements
      • flake8 with same options as before (except line length which is now the 88 black default)
      • pyupgrade, to encourage python 3 idioms
      • pylint with mandatory checks (with some more mandatory checks than before, for v13 only)
      • pylint with all checks (optional + mandatory), not failing
      • isort to automatically sort imports (except in __init__.py where import order might be significant)
      • run eslint as a pre-commit hook, with the same configuration as pylint-odoo except that all checks are warnings. This is the same as what pylint-odoo does (javascript checks are not blocking).
      You can see an example configuration in the storage project [3], the queue project [4] as well as partner-contact [5]. Look for the following files: .pre-commit-config.yaml, .flake8, .pylintrc, .eslintrc. Also look at the updated .travis.yml to see how pre-commit is run. To try it out,
      • checkout these branches
      • run 'pre-commit install'
      • start committing lint failures to see the effect.
      If you have suggestions to make on the linter configurations, you can make them on this MQT PR: https://github.com/OCA/maintainer-quality-tools/pull/613/files

      In practice, if there are no objections, the plan is to setup this configuration on all 13.0 branches this week, while there are not too many v13 modules merged. To do this, I will push all linter configuration files to 13.0 branches, as well as resetting the travis configuration to the default.

      When the configurations will need to evolve later, the maintenance of these configuration files will become a bot task. As before, there will be no possibility to configure linting rules per repo.

      Looking forward to reading your feedback.

      Best regards,

      -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 Bruno Joliveau - 06:10 - 7 Oct 2019

  • [OXP] Odoo Merge Sprint 
    Dear OCA developers,

If you are coming to our Odoo Experience[1] event this week (just after
the OCA Code Sprint), don't forget to come see us at the Merge Sprint
room (in the Hocaille room).
This will be the occasion to meet the Odoo developers and review
together your pull requests and contribution to the source code of Odoo.

Check the event page[2] for details.
There is an agenda published there to meet developers specialised in
specific applications, this way you are sure to meet somebody that will
be able to answer your questions.

See you there,

Martin

[1]
https://www.odoo.com/event/odoo-experience-2019-2019-09-30-2019-10-04-1629/page/oxp19-homepage
[2]
https://www.odoo.com/event/odoo-experience-2019-2019-09-30-2019-10-04-1629/page/oxp19-merge-sprint


-- 
Martin Trigaux
Odoo
https://odoo.com
https://github.com/mart-e
    by Martin Trigaux - 01:56 - 1 Oct 2019

    1 replies 1 replies

    • Re: [OXP] Odoo Merge Sprint
      Other awesome initiative!

      I know where I'm going to be whole event, hehe.

      See you soon!
      by Pedro M. Baeza - 02:36 - 1 Oct 2019
  • Propose Héctor Villarreal as PSC of purchases
    Hi all,

    Here is his Github account. He has actively participated with a lot of contributions at purchase-workflow repository in the newest versions: https://github.com/OCA/purchase-workflow/pulls/hveficent and has migrated to latest version purchase_request among others.

    Regards,

    --
    Lois Rilo Antelo
    Eficent Business and IT Consulting Services, S.L.
    (+34) 679052448 | lois.rilo@eficent.com | http://www.eficent.com
    Twitter: lreficent_erp
    by Lois Rilo Antelo - 06:26 - 30 Sep 2019

    8 replies 8 replies

  • Souheil Bejaoui for project & service PSC
    I want to propose https://github.com/sbejaoui for this PSC as he has been working a lot on all the contract stuff. You can see some os his PRs in:


    Regards.
    by Pedro M. Baeza - 04:26 - 30 Sep 2019

    10 replies 10 replies

  • 13.0 Migration instructions
    Dear community,

    In https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-13.0 there’s “Squash administrative commits (if any) with the previous commit for reducing commit noise.”
    It should be understood as “Squash with previous administrative commits” or “Squash with any previous commit”?

    Kind regards,
    Alexey
    by Alexey Pelykh <alexey.pelykh@gmail.com> - 12:41 - 30 Sep 2019

    3 replies 3 replies

    • Re: 13.0 Migration instructions
      Yeah, thanks for the clarification.

      And now even with translations, the commit is done with GitHub login of each translator, so we shouldn't squash them together (unless same author) for preserving authorship.

      Regards.
      by Pedro M. Baeza - 02:41 - 4 Oct 2019
    • Re: 13.0 Migration instructions
      To keep in mind, we are talking only about administrative commits that were created due to the previous commit.

      We should only squash commits if it was clearly identified after a "real" commit and in clear relation with that commit by the ocabot or a maintainer.


      Because for translation commits when migrating to 12.0 we squashed all in one for updates from Transifex.
      In this case it's not relevant to squash them to the previous commit.
      It could add big noise to a simple fix commit of 2 lines that doesn't affect the translation terms.

      Regards,
      Yannick Vaucher
      Business Solutions Architect

      Camptocamp SA
      PSE A, CH-1015 Lausanne
      Phone: +41 21 619 10 30
      Office: +41 21 619 10 10


      On Mon, 30 Sep 2019 at 15:07, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
      The idea is to merge them with the first "real commit".

      Imagine this commit history (from more recent to older):

      [UPD] README.rst
      Update translation files
      [MIG] xxxx: Migration to version 12.0

      Squashing all of them with the migration commit doesn't lose the commit history meaning.

      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 Yannick Payot - 02:31 - 4 Oct 2019
    • Re: 13.0 Migration instructions
      The idea is to merge them with the first "real commit".

      Imagine this commit history (from more recent to older):

      [UPD] README.rst
      Update translation files
      [MIG] xxxx: Migration to version 12.0

      Squashing all of them with the migration commit doesn't lose the commit history meaning.

      Regards.
      by Pedro M. Baeza - 03:06 - 30 Sep 2019
  • Kenyan Localization Repo
    Hello Contributors,

    I would like to publish my work to OCA (l10n-kenya), I have created some modules for Kenyan Localization.

    Thanks.

    Duncan Kiplangat,
    Sunflower IT.
    by Kiplangat Dan <kiplangatdan@gmail.com> - 11:35 - 30 Sep 2019

    1 replies 1 replies