Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Odoo Google Drive/Spreadsheet depreciation
    Hi all,

    Just catching up concerning the depreciation of Odoo natives Google Drive & Spreadsheet functionalities following changes in OAuth flows on Google's end.

    We have a few clients using Google Drive integration through the template functionality and this module.

    Damien Bouvy in the PR was talking about an alternative for authentication with a Google Drive app. I am not sure about the work that would be required or the implications of such a setting... 

    Did anybody start looking at this for alternate solutions before we dive in on our own ?

    Thanks in advance!

    --
    Quentin Lavallee - Chargé de projets
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter
    by Quentin Lavallée-Bourdeau - 09:01 - 14 Sep 2022
  • Proposing myself for Accounting/Banking PSCs
    Hello fellow contributors

    It's been a few years I've been contributing to plenty of repositories for the OCA and since it seems to me that it's in the accounting related repositories that I've been most active (through PRs or code reviews, mostly in account-invoicing, account-reconcile, account-payment, ...), I'd be happy to help a bit more on these topics by proposing myself as PSC.

    With the OCA days approaching, I guess it could be good to have more people involved.

    My github handle for those would want to have a look at what I did: https://github.com/grindtildeath

    BTW, is there any reason to have two different PSCs for these projects?

    Best regards
    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Akim Juillerat
    Business solutions
    Software architect
    +41 62 544 03 78

    Camptocamp SA
    Leberngasse 21
    4600 Olten
    Switzerland
    +41 21 619 10 10
    by Akim Juillerat - 05:36 - 13 Sep 2022

    8 replies 8 replies

  • Stock Repositories splitting
    Hi all,


    In order to prepare the advent of v16 and to mitigate repositories growing, I want to request some repositories creation.

    • stock-logistics-warehouse:
      • stock_available
      • stock_orderpoint
      • stock_request
      • stock_vertical_lift
    If some of you see another useful repository that could miss and represent an interesting grouping per functional point of view, don't hesitate !

    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel - 10:25 - 7 Sep 2022

    20 replies 20 replies

    • Re: Stock Repositories splitting
      Many thanks!

      I'll do it right now

      On Fri, Oct 7, 2022 at 2:57 PM Simone Orsi <notifications@odoo-community.org> wrote:
      I created all repos. Can you take care of the bootstrap?

      On Fri, Oct 7, 2022 at 12:02 PM Roussel, Denis <notifications@odoo-community.org> wrote:
      Hi Simone,

      Here are they:

      stock-logistics-availability: This repository contains modules to provide more information about product stock availability in terms of quantities (immediately usable, potential, unreserved ones, ...).
      stock-logistics-orderpoint: This repository contains modules to extend reordering rules (available on warehouses locations) functionalities.
      stock-logistics-request: This repository contains modules to provide another way of creating stock movements. Provided as a dedicated application, users will be able to create their stock needs by product and location.
      stock-logistics-interfaces: This repository contains modules to manage vertical physical (such as Kardex Remstar, Modula, ...). lifts for stock internal locations.

      On Fri, Oct 7, 2022 at 11:56 AM Simone Orsi <notifications@odoo-community.org> wrote:
      Hi Denis,

      sorry I've been a bit under the weather for some weeks... and having OCA days + OXP next week does not help in this sense, as you know :D

      Which is the definitive list of these new repos? I see some discussion but it is kind of hard to pick which ones you agreed upon.

      Can you list them again pls?

      Thanks and CU soon :)
      S

      On Fri, Oct 7, 2022 at 8:57 AM Roussel, Denis <notifications@odoo-community.org> wrote:
      Gentle ping reminder @Board 

      On Mon, Oct 3, 2022 at 5:38 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
      Hi,

      In order to begin on good basis, it should be great to have new repos.

      Here are again the specifications:

      stock-logistics-availability: This repository contains modules to provide more information about product stock availability in terms of quantities (immediately usable, potential, unreserved ones, ...).
      stock-logistics-orderpoint: This repository contains modules to extend reordering rules (available on warehouses locations) functionalities.
      stock-logistics-request: This repository contains modules to provide another way of creating stock movements. Provided as a dedicated application, users will be able to create their stock needs by product and location.
      stock-logistics-interfaces: This repository contains modules to manage vertical physical (such as Kardex Remstar, Modula, ...). lifts for stock internal locations.

      On Thu, Sep 8, 2022 at 10:36 AM David Beal <notifications@odoo-community.org> wrote:
      Hello,

      On my side i never known if a module was in stock-logistics-workflow or stock-logistics-warehouse

      Good point to have more dedicated repositories well named

      As I see all stocks repos are prefixed stock-logistics ...
      Then it seems there is no added value for 'logistics' name (no help to understand the content)

      What if if we rename all prefix to stock only of those repositories

      I'm lazy and I prefer to write "cd stock-..." rather than "cd stock-logistics-..." all days of the year

      What do you think about this? Not lazy on your side ?

      Thanks

      Regards

      David BEAL
      Consultant ERP Odoo


      Le mer. 7 sept. 2022 à 13:42, Daniel Reis <notifications@odoo-community.org> a écrit :
      OK for me.

      On 07/09/22 12:17, Roussel, Denis wrote:
      Hi @Jacques-Etienne
      No problem for stock-logistics-interfaces. You know more the coverage of those modules. But doesn't it sound a little bit too generic ?

      I also thought about inventory modules. But from v15, Odoo has refactored the way inventories are done. There are currently no module of that kind in v15 branch either. Maybe we can wait and see on that one.

      I'd prefer keeping the habits of people for both well known ones. Warehouse is usually for 'static' representations of flows (base objects, ...). Workflow is usually for pickings/moves behaviours.
      As the first aim of my request is to lower the weight of repositories, merging both is quite unwanted.


      On Wed, Sep 7, 2022 at 1:06 PM Jacques-Etienne Baudoux <notifications@odoo-community.org> wrote:
      Maybe stock-logistics-interfaces instead of stock-logistics-lift and include the measuring devices modules
      And also stock-logistics-inventory ?
      What about the remaining modules in stock-logistics-warehouse? It's not always clear why a module is in stock-logistics-warehouse or in stock-logistics-workflow. Shouldn't stock-logistics-warehouse then be dropped in favor of stock-logistics-workflow ?

      J-E

      Le mer. 7 sept. 2022 à 11:42, Simone Orsi <notifications@odoo-community.org> a écrit :
      ah ok, well, using module names didn't sound as "new repo names" ;P

      I agree w/ the remarks by Holger and Daniel then.

      We could have
      • stock-logistics-availability
      • stock-logistics-orderpoint
      • stock-logistics-request
      • stock-logistics-lift

      On Wed, Sep 7, 2022 at 11:36 AM Roussel, Denis <notifications@odoo-community.org> wrote:
      @Holger of course hyphens in names

      For descriptions in repos, I can do it as soon as they are created.

      On Wed, Sep 7, 2022 at 11:27 AM Holger Brunn <notifications@odoo-community.org> wrote:
      > stock-logistics-warehouse:











> stock_available











> stock_orderpoint











> stock_request











> stock_vertical_lift

I rather like hyphens in repository names instead of underscores, and all 
current repos do that. So I'd suggest to do it the same with the new repos.

New ones are fine with me, still I think people proposing new repos should 
immediately provide a catchy description that can be placed to github and the 
oca db.












-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

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

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

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

      _______________________________________________
      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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg


      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

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

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

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

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg
      by Denis Roussel - 03:10 - 7 Oct 2022
    • Re: Stock Repositories splitting
      I created all repos. Can you take care of the bootstrap?

      On Fri, Oct 7, 2022 at 12:02 PM Roussel, Denis <notifications@odoo-community.org> wrote:
      Hi Simone,

      Here are they:

      stock-logistics-availability: This repository contains modules to provide more information about product stock availability in terms of quantities (immediately usable, potential, unreserved ones, ...).
      stock-logistics-orderpoint: This repository contains modules to extend reordering rules (available on warehouses locations) functionalities.
      stock-logistics-request: This repository contains modules to provide another way of creating stock movements. Provided as a dedicated application, users will be able to create their stock needs by product and location.
      stock-logistics-interfaces: This repository contains modules to manage vertical physical (such as Kardex Remstar, Modula, ...). lifts for stock internal locations.

      On Fri, Oct 7, 2022 at 11:56 AM Simone Orsi <notifications@odoo-community.org> wrote:
      Hi Denis,

      sorry I've been a bit under the weather for some weeks... and having OCA days + OXP next week does not help in this sense, as you know :D

      Which is the definitive list of these new repos? I see some discussion but it is kind of hard to pick which ones you agreed upon.

      Can you list them again pls?

      Thanks and CU soon :)
      S

      On Fri, Oct 7, 2022 at 8:57 AM Roussel, Denis <notifications@odoo-community.org> wrote:
      Gentle ping reminder @Board 

      On Mon, Oct 3, 2022 at 5:38 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
      Hi,

      In order to begin on good basis, it should be great to have new repos.

      Here are again the specifications:

      stock-logistics-availability: This repository contains modules to provide more information about product stock availability in terms of quantities (immediately usable, potential, unreserved ones, ...).
      stock-logistics-orderpoint: This repository contains modules to extend reordering rules (available on warehouses locations) functionalities.
      stock-logistics-request: This repository contains modules to provide another way of creating stock movements. Provided as a dedicated application, users will be able to create their stock needs by product and location.
      stock-logistics-interfaces: This repository contains modules to manage vertical physical (such as Kardex Remstar, Modula, ...). lifts for stock internal locations.

      On Thu, Sep 8, 2022 at 10:36 AM David Beal <notifications@odoo-community.org> wrote:
      Hello,

      On my side i never known if a module was in stock-logistics-workflow or stock-logistics-warehouse

      Good point to have more dedicated repositories well named

      As I see all stocks repos are prefixed stock-logistics ...
      Then it seems there is no added value for 'logistics' name (no help to understand the content)

      What if if we rename all prefix to stock only of those repositories

      I'm lazy and I prefer to write "cd stock-..." rather than "cd stock-logistics-..." all days of the year

      What do you think about this? Not lazy on your side ?

      Thanks

      Regards

      David BEAL
      Consultant ERP Odoo


      Le mer. 7 sept. 2022 à 13:42, Daniel Reis <notifications@odoo-community.org> a écrit :
      OK for me.

      On 07/09/22 12:17, Roussel, Denis wrote:
      Hi @Jacques-Etienne
      No problem for stock-logistics-interfaces. You know more the coverage of those modules. But doesn't it sound a little bit too generic ?

      I also thought about inventory modules. But from v15, Odoo has refactored the way inventories are done. There are currently no module of that kind in v15 branch either. Maybe we can wait and see on that one.

      I'd prefer keeping the habits of people for both well known ones. Warehouse is usually for 'static' representations of flows (base objects, ...). Workflow is usually for pickings/moves behaviours.
      As the first aim of my request is to lower the weight of repositories, merging both is quite unwanted.


      On Wed, Sep 7, 2022 at 1:06 PM Jacques-Etienne Baudoux <notifications@odoo-community.org> wrote:
      Maybe stock-logistics-interfaces instead of stock-logistics-lift and include the measuring devices modules
      And also stock-logistics-inventory ?
      What about the remaining modules in stock-logistics-warehouse? It's not always clear why a module is in stock-logistics-warehouse or in stock-logistics-workflow. Shouldn't stock-logistics-warehouse then be dropped in favor of stock-logistics-workflow ?

      J-E

      Le mer. 7 sept. 2022 à 11:42, Simone Orsi <notifications@odoo-community.org> a écrit :
      ah ok, well, using module names didn't sound as "new repo names" ;P

      I agree w/ the remarks by Holger and Daniel then.

      We could have
      • stock-logistics-availability
      • stock-logistics-orderpoint
      • stock-logistics-request
      • stock-logistics-lift

      On Wed, Sep 7, 2022 at 11:36 AM Roussel, Denis <notifications@odoo-community.org> wrote:
      @Holger of course hyphens in names

      For descriptions in repos, I can do it as soon as they are created.

      On Wed, Sep 7, 2022 at 11:27 AM Holger Brunn <notifications@odoo-community.org> wrote:
      > stock-logistics-warehouse:










> stock_available










> stock_orderpoint










> stock_request










> stock_vertical_lift

I rather like hyphens in repository names instead of underscores, and all 
current repos do that. So I'd suggest to do it the same with the new repos.

New ones are fine with me, still I think people proposing new repos should 
immediately provide a catchy description that can be placed to github and the 
oca db.











-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

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

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

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

      _______________________________________________
      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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg


      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

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

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi - 02:55 - 7 Oct 2022
    • Re: Stock Repositories splitting
      Hi Simone,

      Here are they:

      stock-logistics-availability: This repository contains modules to provide more information about product stock availability in terms of quantities (immediately usable, potential, unreserved ones, ...).
      stock-logistics-orderpoint: This repository contains modules to extend reordering rules (available on warehouses locations) functionalities.
      stock-logistics-request: This repository contains modules to provide another way of creating stock movements. Provided as a dedicated application, users will be able to create their stock needs by product and location.
      stock-logistics-interfaces: This repository contains modules to manage vertical physical (such as Kardex Remstar, Modula, ...). lifts for stock internal locations.

      On Fri, Oct 7, 2022 at 11:56 AM Simone Orsi <notifications@odoo-community.org> wrote:
      Hi Denis,

      sorry I've been a bit under the weather for some weeks... and having OCA days + OXP next week does not help in this sense, as you know :D

      Which is the definitive list of these new repos? I see some discussion but it is kind of hard to pick which ones you agreed upon.

      Can you list them again pls?

      Thanks and CU soon :)
      S

      On Fri, Oct 7, 2022 at 8:57 AM Roussel, Denis <notifications@odoo-community.org> wrote:
      Gentle ping reminder @Board 

      On Mon, Oct 3, 2022 at 5:38 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
      Hi,

      In order to begin on good basis, it should be great to have new repos.

      Here are again the specifications:

      stock-logistics-availability: This repository contains modules to provide more information about product stock availability in terms of quantities (immediately usable, potential, unreserved ones, ...).
      stock-logistics-orderpoint: This repository contains modules to extend reordering rules (available on warehouses locations) functionalities.
      stock-logistics-request: This repository contains modules to provide another way of creating stock movements. Provided as a dedicated application, users will be able to create their stock needs by product and location.
      stock-logistics-interfaces: This repository contains modules to manage vertical physical (such as Kardex Remstar, Modula, ...). lifts for stock internal locations.

      On Thu, Sep 8, 2022 at 10:36 AM David Beal <notifications@odoo-community.org> wrote:
      Hello,

      On my side i never known if a module was in stock-logistics-workflow or stock-logistics-warehouse

      Good point to have more dedicated repositories well named

      As I see all stocks repos are prefixed stock-logistics ...
      Then it seems there is no added value for 'logistics' name (no help to understand the content)

      What if if we rename all prefix to stock only of those repositories

      I'm lazy and I prefer to write "cd stock-..." rather than "cd stock-logistics-..." all days of the year

      What do you think about this? Not lazy on your side ?

      Thanks

      Regards

      David BEAL
      Consultant ERP Odoo


      Le mer. 7 sept. 2022 à 13:42, Daniel Reis <notifications@odoo-community.org> a écrit :
      OK for me.

      On 07/09/22 12:17, Roussel, Denis wrote:
      Hi @Jacques-Etienne
      No problem for stock-logistics-interfaces. You know more the coverage of those modules. But doesn't it sound a little bit too generic ?

      I also thought about inventory modules. But from v15, Odoo has refactored the way inventories are done. There are currently no module of that kind in v15 branch either. Maybe we can wait and see on that one.

      I'd prefer keeping the habits of people for both well known ones. Warehouse is usually for 'static' representations of flows (base objects, ...). Workflow is usually for pickings/moves behaviours.
      As the first aim of my request is to lower the weight of repositories, merging both is quite unwanted.


      On Wed, Sep 7, 2022 at 1:06 PM Jacques-Etienne Baudoux <notifications@odoo-community.org> wrote:
      Maybe stock-logistics-interfaces instead of stock-logistics-lift and include the measuring devices modules
      And also stock-logistics-inventory ?
      What about the remaining modules in stock-logistics-warehouse? It's not always clear why a module is in stock-logistics-warehouse or in stock-logistics-workflow. Shouldn't stock-logistics-warehouse then be dropped in favor of stock-logistics-workflow ?

      J-E

      Le mer. 7 sept. 2022 à 11:42, Simone Orsi <notifications@odoo-community.org> a écrit :
      ah ok, well, using module names didn't sound as "new repo names" ;P

      I agree w/ the remarks by Holger and Daniel then.

      We could have
      • stock-logistics-availability
      • stock-logistics-orderpoint
      • stock-logistics-request
      • stock-logistics-lift

      On Wed, Sep 7, 2022 at 11:36 AM Roussel, Denis <notifications@odoo-community.org> wrote:
      @Holger of course hyphens in names

      For descriptions in repos, I can do it as soon as they are created.

      On Wed, Sep 7, 2022 at 11:27 AM Holger Brunn <notifications@odoo-community.org> wrote:
      > stock-logistics-warehouse:









> stock_available









> stock_orderpoint









> stock_request









> stock_vertical_lift

I rather like hyphens in repository names instead of underscores, and all 
current repos do that. So I'd suggest to do it the same with the new repos.

New ones are fine with me, still I think people proposing new repos should 
immediately provide a catchy description that can be placed to github and the 
oca db.










-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

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

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

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

      _______________________________________________
      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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg


      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

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

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg
      by Denis Roussel - 12:01 - 7 Oct 2022
    • Re: Stock Repositories splitting
      Hi Denis,

      sorry I've been a bit under the weather for some weeks... and having OCA days + OXP next week does not help in this sense, as you know :D

      Which is the definitive list of these new repos? I see some discussion but it is kind of hard to pick which ones you agreed upon.

      Can you list them again pls?

      Thanks and CU soon :)
      S

      On Fri, Oct 7, 2022 at 8:57 AM Roussel, Denis <notifications@odoo-community.org> wrote:
      Gentle ping reminder @Board 

      On Mon, Oct 3, 2022 at 5:38 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
      Hi,

      In order to begin on good basis, it should be great to have new repos.

      Here are again the specifications:

      stock-logistics-availability: This repository contains modules to provide more information about product stock availability in terms of quantities (immediately usable, potential, unreserved ones, ...).
      stock-logistics-orderpoint: This repository contains modules to extend reordering rules (available on warehouses locations) functionalities.
      stock-logistics-request: This repository contains modules to provide another way of creating stock movements. Provided as a dedicated application, users will be able to create their stock needs by product and location.
      stock-logistics-interfaces: This repository contains modules to manage vertical physical (such as Kardex Remstar, Modula, ...). lifts for stock internal locations.

      On Thu, Sep 8, 2022 at 10:36 AM David Beal <notifications@odoo-community.org> wrote:
      Hello,

      On my side i never known if a module was in stock-logistics-workflow or stock-logistics-warehouse

      Good point to have more dedicated repositories well named

      As I see all stocks repos are prefixed stock-logistics ...
      Then it seems there is no added value for 'logistics' name (no help to understand the content)

      What if if we rename all prefix to stock only of those repositories

      I'm lazy and I prefer to write "cd stock-..." rather than "cd stock-logistics-..." all days of the year

      What do you think about this? Not lazy on your side ?

      Thanks

      Regards

      David BEAL
      Consultant ERP Odoo


      Le mer. 7 sept. 2022 à 13:42, Daniel Reis <notifications@odoo-community.org> a écrit :
      OK for me.

      On 07/09/22 12:17, Roussel, Denis wrote:
      Hi @Jacques-Etienne
      No problem for stock-logistics-interfaces. You know more the coverage of those modules. But doesn't it sound a little bit too generic ?

      I also thought about inventory modules. But from v15, Odoo has refactored the way inventories are done. There are currently no module of that kind in v15 branch either. Maybe we can wait and see on that one.

      I'd prefer keeping the habits of people for both well known ones. Warehouse is usually for 'static' representations of flows (base objects, ...). Workflow is usually for pickings/moves behaviours.
      As the first aim of my request is to lower the weight of repositories, merging both is quite unwanted.


      On Wed, Sep 7, 2022 at 1:06 PM Jacques-Etienne Baudoux <notifications@odoo-community.org> wrote:
      Maybe stock-logistics-interfaces instead of stock-logistics-lift and include the measuring devices modules
      And also stock-logistics-inventory ?
      What about the remaining modules in stock-logistics-warehouse? It's not always clear why a module is in stock-logistics-warehouse or in stock-logistics-workflow. Shouldn't stock-logistics-warehouse then be dropped in favor of stock-logistics-workflow ?

      J-E

      Le mer. 7 sept. 2022 à 11:42, Simone Orsi <notifications@odoo-community.org> a écrit :
      ah ok, well, using module names didn't sound as "new repo names" ;P

      I agree w/ the remarks by Holger and Daniel then.

      We could have
      • stock-logistics-availability
      • stock-logistics-orderpoint
      • stock-logistics-request
      • stock-logistics-lift

      On Wed, Sep 7, 2022 at 11:36 AM Roussel, Denis <notifications@odoo-community.org> wrote:
      @Holger of course hyphens in names

      For descriptions in repos, I can do it as soon as they are created.

      On Wed, Sep 7, 2022 at 11:27 AM Holger Brunn <notifications@odoo-community.org> wrote:
      > stock-logistics-warehouse:








> stock_available








> stock_orderpoint








> stock_request








> stock_vertical_lift

I rather like hyphens in repository names instead of underscores, and all 
current repos do that. So I'd suggest to do it the same with the new repos.

New ones are fine with me, still I think people proposing new repos should 
immediately provide a catchy description that can be placed to github and the 
oca db.









-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

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

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

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

      _______________________________________________
      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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg


      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi - 11:55 - 7 Oct 2022
    • Re: Stock Repositories splitting
      Gentle ping reminder @Board 

      On Mon, Oct 3, 2022 at 5:38 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
      Hi,

      In order to begin on good basis, it should be great to have new repos.

      Here are again the specifications:

      stock-logistics-availability: This repository contains modules to provide more information about product stock availability in terms of quantities (immediately usable, potential, unreserved ones, ...).
      stock-logistics-orderpoint: This repository contains modules to extend reordering rules (available on warehouses locations) functionalities.
      stock-logistics-request: This repository contains modules to provide another way of creating stock movements. Provided as a dedicated application, users will be able to create their stock needs by product and location.
      stock-logistics-interfaces: This repository contains modules to manage vertical physical (such as Kardex Remstar, Modula, ...). lifts for stock internal locations.

      On Thu, Sep 8, 2022 at 10:36 AM David Beal <notifications@odoo-community.org> wrote:
      Hello,

      On my side i never known if a module was in stock-logistics-workflow or stock-logistics-warehouse

      Good point to have more dedicated repositories well named

      As I see all stocks repos are prefixed stock-logistics ...
      Then it seems there is no added value for 'logistics' name (no help to understand the content)

      What if if we rename all prefix to stock only of those repositories

      I'm lazy and I prefer to write "cd stock-..." rather than "cd stock-logistics-..." all days of the year

      What do you think about this? Not lazy on your side ?

      Thanks

      Regards

      David BEAL
      Consultant ERP Odoo


      Le mer. 7 sept. 2022 à 13:42, Daniel Reis <notifications@odoo-community.org> a écrit :
      OK for me.

      On 07/09/22 12:17, Roussel, Denis wrote:
      Hi @Jacques-Etienne
      No problem for stock-logistics-interfaces. You know more the coverage of those modules. But doesn't it sound a little bit too generic ?

      I also thought about inventory modules. But from v15, Odoo has refactored the way inventories are done. There are currently no module of that kind in v15 branch either. Maybe we can wait and see on that one.

      I'd prefer keeping the habits of people for both well known ones. Warehouse is usually for 'static' representations of flows (base objects, ...). Workflow is usually for pickings/moves behaviours.
      As the first aim of my request is to lower the weight of repositories, merging both is quite unwanted.


      On Wed, Sep 7, 2022 at 1:06 PM Jacques-Etienne Baudoux <notifications@odoo-community.org> wrote:
      Maybe stock-logistics-interfaces instead of stock-logistics-lift and include the measuring devices modules
      And also stock-logistics-inventory ?
      What about the remaining modules in stock-logistics-warehouse? It's not always clear why a module is in stock-logistics-warehouse or in stock-logistics-workflow. Shouldn't stock-logistics-warehouse then be dropped in favor of stock-logistics-workflow ?

      J-E

      Le mer. 7 sept. 2022 à 11:42, Simone Orsi <notifications@odoo-community.org> a écrit :
      ah ok, well, using module names didn't sound as "new repo names" ;P

      I agree w/ the remarks by Holger and Daniel then.

      We could have
      • stock-logistics-availability
      • stock-logistics-orderpoint
      • stock-logistics-request
      • stock-logistics-lift

      On Wed, Sep 7, 2022 at 11:36 AM Roussel, Denis <notifications@odoo-community.org> wrote:
      @Holger of course hyphens in names

      For descriptions in repos, I can do it as soon as they are created.

      On Wed, Sep 7, 2022 at 11:27 AM Holger Brunn <notifications@odoo-community.org> wrote:
      > stock-logistics-warehouse:







> stock_available







> stock_orderpoint







> stock_request







> stock_vertical_lift

I rather like hyphens in repository names instead of underscores, and all 
current repos do that. So I'd suggest to do it the same with the new repos.

New ones are fine with me, still I think people proposing new repos should 
immediately provide a catchy description that can be placed to github and the 
oca db.








-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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



      --
      Simone Orsi

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

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

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

      _______________________________________________
      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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg


      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg
      by Denis Roussel - 08:55 - 7 Oct 2022

  • OCA Days 2022 Talk Proposals - submissions close today 31st August
    Hello OCA Contributors,

    Just a quick reminder that if you had a talk proposal to send through for OCA days 2022, today is the last day to do so.

    You can submit your presentation ideas here: https://odoo-community.org/event/oca-days-2022-liege-2022-10-10-2022-10-12-131/track_proposal

    We are looking forward to hearing about what people have been up to over the last year!

    Warmest regards,
    Rebecca
    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 11:45 - 31 Aug 2022

    7 replies 7 replies

  • Proposing myself as PSC for OCA/server-tools 
    Hi everyone,

Recently I've been quite active in the "server-tools" repo.

I see that regular maintainance is not being done (enough) by the 
current maintainers - understandable of course, because it's a big 
repository and everyone's busy, etc.

So I also want to be able to do it - merge approved MR's, fasttrack some 
really small changes, close duplicate MR's, that sort of thing.

Can I be a PSC of "server-tools"?

-Tom
    by Tom Blauwendraat - 05:55 - 22 Aug 2022

    13 replies 13 replies

  • OCA Days 2022 - Video Post Production RFQ
    Hello OCA Contributors,

    I hope this finds you all well!

    I wanted to share some information about our latest RFQS.
    • Graphic Designer RFQ 2022:
    • Pouce-Pied was successful in our recent RFQ for a Graphic Designer for 2022. We would like to thank ForgeFlow, Nathalie Lothier and Ariadna Dalmau for applying.
    We are looking forward to the collaboration ahead.
    Warmest regards,
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 04:11 - 22 Aug 2022
  • Re: Proposal to become PSC of module OCA/payroll
    As explained by Nicolás, +1 by my part in Payroll PSC.

    Regards.
    by Pedro M. Baeza - 05:56 - 17 Aug 2022

    6 replies 6 replies

    • Re: Proposal to become PSC of module OCA/payroll
      That helped a lot, thanks!
      He should get the invitation on the next sync.

      On Fri, Sep 2, 2022 at 9:22 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
      It seems his messages are not getting through the list, so he asked me to send here his email: nicolasrsande@gmail.com

      It should be in the OCA Odoo instance, as he has confirmed his subscription to the mailing list.

      Regards.

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi - 02:25 - 5 Sep 2022
    • Re: Proposal to become PSC of module OCA/payroll
      It seems his messages are not getting through the list, so he asked me to send here his email: nicolasrsande@gmail.com

      It should be in the OCA Odoo instance, as he has confirmed his subscription to the mailing list.

      Regards.
      by Pedro M. Baeza - 09:20 - 2 Sep 2022
    • Re: Proposal to become PSC of module OCA/payroll
      Hello,

      I didn't get the original message indeed.
      @Nicolas: I cannot find your user on our instance. Can you give me an email?

      Bests,
      S

      On Fri, Aug 19, 2022 at 10:57 AM Michael Telahun <notifications@odoo-community.org> wrote:

      +1 from me. Payroll needs more care and feeding :-) and Nicolas is an active contributor

      On 19/08/2022 09:22, Pedro M. Baeza wrote:
      Indeed it seems very weird. This is the original message (that I received being in direct copy):

      Nicolas Rodriguez Sande

      17 ago 2022, 17:53 (hace 2 días)


      para contributors, mí

      Hello, I'm submitting this email to become a candidate to PSC of the module OCA/payroll and also OCA/hr if needed. 

      In the last months I've been submitting a lot of changes to the module OCA/payroll which was orphaned for maintenance for a long time. I created the Argentinian localization for payroll and maintain that localization in my country, which depends of the OCA Payroll module, so last months i've been migrating some estructural and improvement changes that i developed for my country localization to the base module, so all the community can benefit from this enhancements and maintenance of the module. 

      Actually I'm one of the declared maintainers of the payroll modules. 

      Here I cc Mr. Pedro M. Baeza who I've been in contact with for the last few months to merge the changes that I submitted in my PRs and discussed opinions about the future of the module. 
      He explained to me about how OCA works and its governance laws. Also talked about being a candidate for PSC for the OCA/payroll module and suggested me to candidate for that position with his support.

      Since I've been really active in the module and plan to continue improving and submitting PRs, I think I would be a good fit to be the PSC of the repository. 

      About myself i can tell that i'm an informatic engineer and developer with 10 years of experience coding. I mainly work for my own business in Argentina and for my own consulting firm which covers a lot of areas of the industry in my country. I have a lot of experience as a business owner and accounting skills so I think that makes me a good developer for odoo modules because I can extract the business logic and translate into code without the hassle of bridging the functional and technical roles in this type of development. 

      Finally i hope you can take my proposal into account, at least for the OCA/payroll module but i don't discard a candidature for other modules too, because i have a lot of private codebase that i developed for odoo in all this time and i wish to open that to the world of the open source software, so all people could benefit of new and updated code and also a collaborative maintenance environment.

      You can see my history of movements in my GitHub account which i link here: 

      If you need more information or want to ask some questions I leave this channel open for any you will need or could help you with. 

      Kind Regards. 
      Nicolas.

      _______________________________________________
      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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi - 04:56 - 30 Aug 2022
    • Re: Proposal to become PSC of module OCA/payroll

      +1 from me. Payroll needs more care and feeding :-) and Nicolas is an active contributor

      On 19/08/2022 09:22, Pedro M. Baeza wrote:
      Indeed it seems very weird. This is the original message (that I received being in direct copy):

      Nicolas Rodriguez Sande

      17 ago 2022, 17:53 (hace 2 días)


      para contributors, mí

      Hello, I'm submitting this email to become a candidate to PSC of the module OCA/payroll and also OCA/hr if needed. 

      In the last months I've been submitting a lot of changes to the module OCA/payroll which was orphaned for maintenance for a long time. I created the Argentinian localization for payroll and maintain that localization in my country, which depends of the OCA Payroll module, so last months i've been migrating some estructural and improvement changes that i developed for my country localization to the base module, so all the community can benefit from this enhancements and maintenance of the module. 

      Actually I'm one of the declared maintainers of the payroll modules. 

      Here I cc Mr. Pedro M. Baeza who I've been in contact with for the last few months to merge the changes that I submitted in my PRs and discussed opinions about the future of the module. 
      He explained to me about how OCA works and its governance laws. Also talked about being a candidate for PSC for the OCA/payroll module and suggested me to candidate for that position with his support.

      Since I've been really active in the module and plan to continue improving and submitting PRs, I think I would be a good fit to be the PSC of the repository. 

      About myself i can tell that i'm an informatic engineer and developer with 10 years of experience coding. I mainly work for my own business in Argentina and for my own consulting firm which covers a lot of areas of the industry in my country. I have a lot of experience as a business owner and accounting skills so I think that makes me a good developer for odoo modules because I can extract the business logic and translate into code without the hassle of bridging the functional and technical roles in this type of development. 

      Finally i hope you can take my proposal into account, at least for the OCA/payroll module but i don't discard a candidature for other modules too, because i have a lot of private codebase that i developed for odoo in all this time and i wish to open that to the world of the open source software, so all people could benefit of new and updated code and also a collaborative maintenance environment.

      You can see my history of movements in my GitHub account which i link here: 

      If you need more information or want to ask some questions I leave this channel open for any you will need or could help you with. 

      Kind Regards. 
      Nicolas.

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

      by Raphael Makonnen - 10:55 - 19 Aug 2022
    • Re: Proposal to become PSC of module OCA/payroll
      Indeed it seems very weird. This is the original message (that I received being in direct copy):

      Nicolas Rodriguez Sande

      17 ago 2022, 17:53 (hace 2 días)

      para contributors, mí

      Hello, I'm submitting this email to become a candidate to PSC of the module OCA/payroll and also OCA/hr if needed. 

      In the last months I've been submitting a lot of changes to the module OCA/payroll which was orphaned for maintenance for a long time. I created the Argentinian localization for payroll and maintain that localization in my country, which depends of the OCA Payroll module, so last months i've been migrating some estructural and improvement changes that i developed for my country localization to the base module, so all the community can benefit from this enhancements and maintenance of the module. 

      Actually I'm one of the declared maintainers of the payroll modules. 

      Here I cc Mr. Pedro M. Baeza who I've been in contact with for the last few months to merge the changes that I submitted in my PRs and discussed opinions about the future of the module. 
      He explained to me about how OCA works and its governance laws. Also talked about being a candidate for PSC for the OCA/payroll module and suggested me to candidate for that position with his support.

      Since I've been really active in the module and plan to continue improving and submitting PRs, I think I would be a good fit to be the PSC of the repository. 

      About myself i can tell that i'm an informatic engineer and developer with 10 years of experience coding. I mainly work for my own business in Argentina and for my own consulting firm which covers a lot of areas of the industry in my country. I have a lot of experience as a business owner and accounting skills so I think that makes me a good developer for odoo modules because I can extract the business logic and translate into code without the hassle of bridging the functional and technical roles in this type of development. 

      Finally i hope you can take my proposal into account, at least for the OCA/payroll module but i don't discard a candidature for other modules too, because i have a lot of private codebase that i developed for odoo in all this time and i wish to open that to the world of the open source software, so all people could benefit of new and updated code and also a collaborative maintenance environment.

      You can see my history of movements in my GitHub account which i link here: 

      If you need more information or want to ask some questions I leave this channel open for any you will need or could help you with. 

      Kind Regards. 
      Nicolas.
      by Pedro M. Baeza - 08:21 - 19 Aug 2022

  • Single product description for sales, purchases, pickings...

    Hello Contributors!

     

    I’ve opened an issue to propose a new module to support single product description:

     

     

    If you are interested or you have solved before (I guess it! This is common!) please participate in https://github.com/OCA/stock-logistics-workflow/issues/1067

     

    Thank you

    Regards,

    Rafael

     

    by Rafael Blasco (Moduon) - 06:25 - 16 Aug 2022

    1 attachments 1 attachments

    image001.png
  • How do you solve invoicing period?

    Hello Contributors!

     

    I write because I don’t see a common straight solution (and user friendly) for this general use case.

     

    1.  

     

    Usually, I have been using the OCA module “sale_order_type” when a client have the need of defining invoicing periods like:

     

    • Monthly
    • B-weekly
    • Weekly
    • Daily

     

    With sale_order_type +plus+ sale_order_invoicing_grouping_criteria you can group by. This module allow multiple criterias.

     

    1.  

     

    In the other hand there is the OCA module “account_invoice_base_invoicing_mode”, this looks like more specific but it has a huge dependency (I don’t know why): depends: account, queue_job, sale

     

    With account_invoice_base_invoicing_mode +plus+ account_invoice_mode_monthly and other modules becomes the logic, but the customer cannot create their invoicing modes themselves, and need from us a new module each time.

     

     

    The usability (UX) in my mind looks like clients (users) have a field like “invoicing period” (like invoicing mode) where they can create monthly, weekly, etc. (like payment terms) and after that they can set it in the partners form (customers or supplier). And after that improve with more modules automatism.

     

    What do you think?

     

    I write here before opening an issue in GitHub (maybe sale-workflow, maybe account-invoicing).

     

     

    Thank you in advance

    Best regards

    Rafael

     

    by Rafael Blasco (Moduon) - 05:31 - 16 Aug 2022

    3 replies 3 replies

    • Re: How do you solve invoicing period?
      Hello Raphael,

      > With account_invoice_base_invoicing_mode +plus+ account_invoice_mode_monthly and other modules becomes the logic, but the customer cannot create their invoicing modes themselves, and need from us a new module each time.

      This is correct. That is for automatic invoicing according to the mode defined on the partner. You currently have the possibility to choose monthly, weekly and daily (v14 open PR). Each mode needs its module for the implementation.
      The generation of the invoice is done with a cron job that generates a queue job at a defined time. This allows to control the load and track what occurred with the job, and see the log in case of error.
      It also supports returns to generate credit notes.

      Kind regards
      J-E

      Le mar. 16 août 2022 à 17:32, Rafael Blasco <notifications@odoo-community.org> a écrit :

      Hello Contributors!

       

      I write because I don’t see a common straight solution (and user friendly) for this general use case.

       

      1.  

       

      Usually, I have been using the OCA module “sale_order_type” when a client have the need of defining invoicing periods like:

       

      • Monthly
      • B-weekly
      • Weekly
      • Daily

       

      With sale_order_type +plus+ sale_order_invoicing_grouping_criteria you can group by. This module allow multiple criterias.

       

      1.  

       

      In the other hand there is the OCA module “account_invoice_base_invoicing_mode”, this looks like more specific but it has a huge dependency (I don’t know why): depends: account, queue_job, sale

       

      With account_invoice_base_invoicing_mode +plus+ account_invoice_mode_monthly and other modules becomes the logic, but the customer cannot create their invoicing modes themselves, and need from us a new module each time.

       

       

      The usability (UX) in my mind looks like clients (users) have a field like “invoicing period” (like invoicing mode) where they can create monthly, weekly, etc. (like payment terms) and after that they can set it in the partners form (customers or supplier). And after that improve with more modules automatism.

       

      What do you think?

       

      I write here before opening an issue in GitHub (maybe sale-workflow, maybe account-invoicing).

       

       

      Thank you in advance

      Best regards

      Rafael

       

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

      by Jacques-Etienne Baudoux - 09:15 - 19 Aug 2022
    • Re: How do you solve invoicing period?
      Rafael,

      have a look at contract repository https://github.com/OCA/contract, contract module that allows for creation of invoices. With contract_sale_generation you can generate sale orders instead of invoices.

      Hope it helps

      Best regards

         Radovan

      From: notifications@odoo-community.org
      Sent: August 16, 2022 18:32
      To: contributors@odoo-community.org
      Reply-to: contributors@odoo-community.org
      Subject: How do you solve invoicing period?

      Hello Contributors!

       

      I write because I don’t see a common straight solution (and user friendly) for this general use case.

       

      1.  

       

      Usually, I have been using the OCA module “sale_order_type” when a client have the need of defining invoicing periods like:

       

      • Monthly
      • B-weekly
      • Weekly
      • Daily

       

      With sale_order_type +plus+ sale_order_invoicing_grouping_criteria you can group by. This module allow multiple criterias.

       

      1.  

       

      In the other hand there is the OCA module “account_invoice_base_invoicing_mode”, this looks like more specific but it has a huge dependency (I don’t know why): depends: account, queue_job, sale

       

      With account_invoice_base_invoicing_mode +plus+ account_invoice_mode_monthly and other modules becomes the logic, but the customer cannot create their invoicing modes themselves, and need from us a new module each time.

       

       

      The usability (UX) in my mind looks like clients (users) have a field like “invoicing period” (like invoicing mode) where they can create monthly, weekly, etc. (like payment terms) and after that they can set it in the partners form (customers or supplier). And after that improve with more modules automatism.

       

      What do you think?

       

      I write here before opening an issue in GitHub (maybe sale-workflow, maybe account-invoicing).

       

       

      Thank you in advance

      Best regards

      Rafael

       

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

      by Radovan Skolnik - 05:45 - 16 Aug 2022
    • Re: How do you solve invoicing period?

      Hello,

      I don't know if this is what you want, but I'm using date_range module, plus another one that creates months, quarters, semesters and years via ir.cron.

      Then, I added some date_range_id fields on account.move.line model.

      Regards,

      João Jerónimo


      Às 16:32 de 16/08/2022, Rafael Blasco escreveu:

      Hello Contributors!

       

      I write because I don’t see a common straight solution (and user friendly) for this general use case.

       

      1.  

       

      Usually, I have been using the OCA module “sale_order_type” when a client have the need of defining invoicing periods like:

       

      • Monthly
      • B-weekly
      • Weekly
      • Daily

       

      With sale_order_type +plus+ sale_order_invoicing_grouping_criteria you can group by. This module allow multiple criterias.

       

      1.  

       

      In the other hand there is the OCA module “account_invoice_base_invoicing_mode”, this looks like more specific but it has a huge dependency (I don’t know why): depends: account, queue_job, sale

       

      With account_invoice_base_invoicing_mode +plus+ account_invoice_mode_monthly and other modules becomes the logic, but the customer cannot create their invoicing modes themselves, and need from us a new module each time.

       

       

      The usability (UX) in my mind looks like clients (users) have a field like “invoicing period” (like invoicing mode) where they can create monthly, weekly, etc. (like payment terms) and after that they can set it in the partners form (customers or supplier). And after that improve with more modules automatism.

       

      What do you think?

       

      I write here before opening an issue in GitHub (maybe sale-workflow, maybe account-invoicing).

       

       

      Thank you in advance

      Best regards

      Rafael

       

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

      by j_j_b_o_devel - 05:41 - 16 Aug 2022
  • Call for Speakers - OCA Days 2022 - Deadline 31st August
    Hello OCA Contributors.

    We are so excited to see so many of you heading to the OCA Days in October. We are almost at capacity!
    I wanted to make sure you were aware that our "Call for Speakers" deadline is 31st of August.

    We have some great proposals that have been sent through already and we would love to have more! We want to hear about what you have been up to, have you got a new module to share, an update, a tutorial, a workshop, a great discussion topic.....?

    We want to know about it. Share your talk proposals here.

    We look forward to hearing from you.
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 03:31 - 16 Aug 2022
  • OCA Days 2022 - Info Blog Post
    Hello Dear OCA Contributors.

    I hope this email finds you all well.

    I wanted to draw your attention to our latest blog post with a few more details about the OCA Days. Please have a read here.

    Please note, that we only have 200 spaces (in past years we've only been able to sit around 150 in person, we are excited to be able to increase this), but we need to know who is coming and spaces are starting to fill up! Register here.

    We are so excited to hear your talk proposals too - the deadline is 31st August.

    We can't wait to see you in Liège!

    Warmest regards,
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 10:46 - 10 Aug 2022
  • Firebase integration with Odoo 
    Hello everybody,

for a potential project, we need to integrate Odoo with Firebase DB and 
create a lot of Endpoint to exchange data like customer, product, sale 
order and so on.

Has anyone done something similar?

Thanks


-- 

Stefano Sforzi
Tel (CH): +41 91 210 23 40
Tel (IT): +39 0331 158 7090
https://www.agilebg.com
    by stefano sforzi - 04:20 - 8 Aug 2022
  • Migrating custom modules of Point of Sale from v13 to v15
    Hi,

    We're trying to upgrade a custom module from v13 to v15. post_statement_id field which is included in class AccountBankStatementLine model via inheritance in point_of_sale module in Odoo Community addons v13 but it doesn't exist in v15 and this field is used in our custom module.

    What is replaced with pos_statement_id field of AccountBankStatementLine in v15?


    v13:
    in point_of_sale module:

    class AccountBankStatementLine(models.Model):
        _inherit = 'account.bank.statement.line'

        pos_statement_id = fields.Many2one('pos.order', string="POS statement", ondelete='cascade')



    custom module in v13:
    class POSOrder(models.Model):
        _inherit = 'pos.order'

        statement_ids = fields.One2many(
            'account.bank.statement.line',
            'pos_statement_id',
            string='Bank Payments',
            states={'draft': [('readonly', False)]},
            readonly=True)

    v15:
    No inherited account.bank.statement.line class and no pos_statement_id field
       
    I need a detailed description of how module designs changed from v13 to v15. There are several similar issues in our custom module. Could you please give some suggestions? Is there any descriptive document that explains how module structures changed to take into account for developers?


    Regards
    by duygutuncay - 10:50 - 22 Jul 2022
  • Procedure to create 16.0 branches
    Dear contributors,

    I'm starting to think about the process to create the 16.0 branches. And the more I think about it, the more I'm convinced we should do it by adding "installable": False in the module manifests, instead of creating empty branches.

    This would have several benefits:
    • Improve security. Indeed, currently migration PRs have a lot of commits and reviewers only look at the last 2 commits. By accident or malice, it would be easy for a contributor to sneak bad code in older commits, that would go unnoticed. As the community grows, I think this a very important topic.
    • Avoid CLA bot issues: currently, the CLA bot is flagging old commits that were ok at the time they were created, but may not be valid today as contributors may have changed email, or revoked their CLA.
    • Reduce oca-github-bot complexity: work has to be done to make the bot aware of other branches in migration PRs (notably to look-up maintainers). This would be unnecessary if a migration PR is a normal PR to an existing addon directory. On the contrary, the bot could even detect migration PRs automatically by noticing the change to the installable flag, so this could simplify some processes.
    • Slow git repo growth: by avoiding the recreation of identical commits in several branches we would slow down the git repo size increase.
    About the possible drawbacks, I am under the impression that all the reasons we had back then to create empty branches have faded away:
    • Today, Odoo and all the OCA tooling work perfectly well when there are addons marked as uninstallable. They are correctly ignored by linters, tests, and Odoo does not attempt to import the code.
    • Regarding discoverability, the addons table in the README shows a clear view of what is not migrated.
    The migration procedure and tools should continue to work as today, to pick up commits that would have been added after branching (basically the git-am process would simply work as it does today)

    All we'd need maybe is to agree on a process to remove modules that have not been migrated for several versions. But in a first approach, regular PRs to remove now useless modules would probably be sufficient.

    Are there any other arguments (pro or con) that I would have missed ?

    Looking forward to reading your feedback on this proposal.

    -Stéphane

    by Stéphane Bidoul - 12:45 - 20 Jul 2022

    36 replies 36 replies

    • Re: Procedure to create 16.0 branches
      Hi,

      I'm no techie, and don't pretend to deeply understand this stuff. Also not a PSC of any repo. I am not very personally affected by whatever decision is made here and will happily defer to any decision.

      Regards benefits of this approach, the first question I ask is can this be achieved in other ways. Usually people tell me it is impossible immediately. I won't argue back, just random thoughts.
      • Improve security. One thought regards nefarious commits injected into migration. Is this solvable in other ways? Something like an AST/semantic diff maybe or even just a regular diff against last release. In fact a regular diff against last release may identify missed commits too.  But anyway some kind of semantic diff outside of migration may be useful too as it would just ignore format changes. However, I think security is a separate important topic that needs a wider discussion regardless of whatever outcomes here are and we should be vigilant to those risks. But also as a reviewer, I think I'd rather review a semantic diff anyway. 
      • Avoid CLA bot issues: Do we really need to preserve ALL history every release - what about a squash merge - that maintains all the prior authors? Then maybe we can get an excpetion for that case in bot. For that 1 time ever you need a blame on a file 6 years ago, you can still traceback through versions.
      • Reduce oca-github-bot complexity: I actually thought that work was done already. But in any case, is the argument here valid? Because not all modules in prior repo(s) would be merged at time the new one is created. So don't you avoid the complexity, until you don't? Wouldn't we need the functionality regardless? I don't know, genuine question.
      • Slow git repo growth: As above for CLA Bot.

      My general feeling I am getting - 

      • Maintainers with tightly controlled, homogenous repos with a small number of maintainers and modules are in favour. These also tend to be "additive" repos, i.e. it is new functionality with not a lot of integration points. They also tend to be a bit more "technical". There is a very high likelihood of migration and also fairly rapidly. However, the contributors on those repos are more than capable of a 5 minute dance to do the port work.
      • PSC's with large heterogeneous repos with many modules and contributors aren't so much in favour. Of course in these repos there tends to be a LOT of flux from version to version. Place like product-attribute, sale-workflow. These are often "insertive" type modules, putting themselves in middle of business processes. Design changes, upstream functionality changes, lots of modules dropping, reappearing.

      I know for myself and some modules I have some involvement with.
      office 365 auth - hasn't changed between versions for 7 years. I don't even have any clients paying for it anymore - but 1 guy emails me once a year asking me to bump version number because it still works.
      partner statements - we did a big refactor for 11 or 12.0 maybe, a few minor changes for 13.0 accounting but less than you'd think because it is fundamentally just adding a couple reports.
      Now when I'm doing/reviewing those, I'll admit it does seem a bit wasteful this whole dance but it is no big deal.

      operating-unit - literally just a bunch of modules sticking a single field on a model, these are often awful to migrate because that happens in the middle of all sorts of functions, lots of interdependencies, stupid broken Odoo record rules. Plus they look easy, so often people seem to pick them for their first ever migration, review sucks on these and we get quite a few unexpected oversights. You really do need to download and test these PR's.
      I know it should make no difference, but my head just thinks better starting clean.

      sale-workflow/product-attribute type repos - honestly, a lot of the time in these repos it is about merging modules, deprecating modules, combining functionality, finding better repos as focus changes. I'm probably wrong, but I feel like prepopulating uninstallable is probably more work and missed opportunities.

      Anyway just my thoughts.

      But also, even if it is OK for 16, what about odd number version :) (This is a joke).

      On Thu, Jul 21, 2022 at 10:42 PM Pedro M. Baeza (Tecnativa) <notifications@odoo-community.org> wrote:
      > To make sure people reason about the correct arguments, let me emphasize again that the migration process would be strictly identical.

      Although theoretically you can use the same commands (but I repeat, I remember some problems in the past with this - I will try to dig on the history to find any -), what will happen for sure is that people forget to do/don't know such initial steps and appear that the migration pull request is correct, while it doesn't contain the missing commits, charging on the reviews to check this, so that's the real issue, together with other strong arguments like the IDE search, cleaning, etc.

      And I also agree having some repositories with one approach and another with the other approach is a mess. You have done the installable=False approach in the past for your specific repositories (mis-builder, storage, product-pim and queue mostly), because you do the migration yourself, not involving other contributors, but the rest of the repositories can't apply this method.

      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 Graeme Gellatly - 03:15 - 21 Jul 2022
    • Re: Procedure to create 16.0 branches
      > To make sure people reason about the correct arguments, let me emphasize again that the migration process would be strictly identical.

      Although theoretically you can use the same commands (but I repeat, I remember some problems in the past with this - I will try to dig on the history to find any -), what will happen for sure is that people forget to do/don't know such initial steps and appear that the migration pull request is correct, while it doesn't contain the missing commits, charging on the reviews to check this, so that's the real issue, together with other strong arguments like the IDE search, cleaning, etc.

      And I also agree having some repositories with one approach and another with the other approach is a mess. You have done the installable=False approach in the past for your specific repositories (mis-builder, storage, product-pim and queue mostly), because you do the migration yourself, not involving other contributors, but the rest of the repositories can't apply this method.

      Regards.
      by Pedro M. Baeza - 12:41 - 21 Jul 2022
    • Re: Procedure to create 16.0 branches
      To make sure people reason about the correct arguments, let me emphasize again that the migration process would be strictly identical.

      On Thu, Jul 21, 2022 at 11:26 AM LuisDaniel Lafaurie <notifications@odoo-community.org> wrote:
      Hello everyone,

      I agree with what Rémi has just explained.

      It wouldn't be wise to put more pressure on the migration process for the ones (PSCs and/or reviewers) working more actively on that subject.

      Keeping the current method will be the best option so far, IMHO.

      Thus, my vote is -1

      Thanks,
       

      On Thu, 21 Jul 2022 at 10:02, Rémi CAZENAVE - Le Filament <notifications@odoo-community.org> wrote:

      Hi all,

      I like better the current method (having only working/tested/maintained modules in each branch) for the following reasons :
      - I find it easier to see what is available un a given version, what would still need to be migrated, and also to get an idea of which versions are being actively used (though I guess I could look at READMEs, migration issues and overall statistics to get the same info)
      - on each Odoo instance we deploy we download specific branch and having lots of unusable code would increase bandwidth and storage (although mostly text that could be compressed, so probably not dramatic neither)

      I agree that the process to migrate a module from one version to another is not really easy (at least the first times), but I understand that it would still probably need to be done in order to make sure you get the latest commits from previous branch. I am afraid that this would often be forgotten if not strictly necessary in migration process, and for sure we do not want to transfer this extra burden of checking for each PR whether based on latest commits or not to reviewers / PSC.

      Last, I am not in favour of having 2 different processes that can be applied per repo, since it would increase complexity for understanding why 2 repos are not behaving the same, and we may lose newcomers (but also for people not so much involved in OCA) - although here again I understand from discussions this is already the case for some repos.

      My 2 cents...

      Best Regards,
      Rémi CAZENAVE
      SCOP Le Filament

      Le July 21, 2022 3:52:02 AM UTC, "Raphaël Valyi" <notifications@odoo-community.org> a écrit :
      Hello,

      My vote goes to the opt-in option at least unless Pedro get convinced, because going against the will of somebody processing such a large portion of the PRs would be a terrible shot in the feet.

      That being said, earlier Pedro raised the concern about the possibility to craft an attack commit inside a missing commit that would be cherry-picked just like with the current way of migrating. But:

      On Wed, Jul 20, 2022, 3:42 PM Roussel, Denis <notifications@odoo-community.org> wrote:
      To summarize:

      • commits SHA are different with current behaviour
      • commits SHA are equal with proposed one
      Denis could you confirm this SHA conservation could make us safe against such crafted attack commits in the middle of the missing commits that one would need to cherry-pick with the new procedure?

      This crafted commit attack thing is indeed extremely concerning...

      _______________________________________________
      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 - 12:05 - 21 Jul 2022
    • Re: Procedure to create 16.0 branches
      Hi,

      For the moment, I prefer the empty branches. The lifecycle of the module is really different from the lifecycle of major version releases.
      I think the focus should be on improving tools /workflows for keeping in sync modules across versions.


      Regards,

      Le jeu. 21 juil. 2022 à 10:02, Rémi CAZENAVE - Le Filament <notifications@odoo-community.org> a écrit :

      Hi all,

      I like better the current method (having only working/tested/maintained modules in each branch) for the following reasons :
      - I find it easier to see what is available un a given version, what would still need to be migrated, and also to get an idea of which versions are being actively used (though I guess I could look at READMEs, migration issues and overall statistics to get the same info)
      - on each Odoo instance we deploy we download specific branch and having lots of unusable code would increase bandwidth and storage (although mostly text that could be compressed, so probably not dramatic neither)

      I agree that the process to migrate a module from one version to another is not really easy (at least the first times), but I understand that it would still probably need to be done in order to make sure you get the latest commits from previous branch. I am afraid that this would often be forgotten if not strictly necessary in migration process, and for sure we do not want to transfer this extra burden of checking for each PR whether based on latest commits or not to reviewers / PSC.

      Last, I am not in favour of having 2 different processes that can be applied per repo, since it would increase complexity for understanding why 2 repos are not behaving the same, and we may lose newcomers (but also for people not so much involved in OCA) - although here again I understand from discussions this is already the case for some repos.

      My 2 cents...

      Best Regards,
      Rémi CAZENAVE
      SCOP Le Filament

      Le July 21, 2022 3:52:02 AM UTC, "Raphaël Valyi" <notifications@odoo-community.org> a écrit :
      Hello,

      My vote goes to the opt-in option at least unless Pedro get convinced, because going against the will of somebody processing such a large portion of the PRs would be a terrible shot in the feet.

      That being said, earlier Pedro raised the concern about the possibility to craft an attack commit inside a missing commit that would be cherry-picked just like with the current way of migrating. But:

      On Wed, Jul 20, 2022, 3:42 PM Roussel, Denis <notifications@odoo-community.org> wrote:
      To summarize:

      • commits SHA are different with current behaviour
      • commits SHA are equal with proposed one
      Denis could you confirm this SHA conservation could make us safe against such crafted attack commits in the middle of the missing commits that one would need to cherry-pick with the new procedure?

      This crafted commit attack thing is indeed extremely concerning...

      _______________________________________________
      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



      --
      Raphaël Reverdy
      Mobile +33 6 38 02 03 93
      Fixe +33 4 82 53 84 60
      by Raphaël Reverdy - 11:46 - 21 Jul 2022
    • Re: Procedure to create 16.0 branches

      Hi All,

      I am not in favor of this and most of this has already been said by others, but I want to re-iterate:

      1. It is currently easy to see at a glance the state of the branch and which modules have been migrated

      2. The current migration process for most modules is relatively easy

      3. If it hinders or causes friction for current OCA contributors and causes them to engage less in OCA it shouldn't be done. Period.

      4. The most important reason:

      Except for the few modules that are widely used most modules are migrated after 1+ years of the Odoo SA version release. Quite a few modules are also migrated after more than 1 Odoo SA version release. I.E. version 12 module skips 13 and is migrated to 14 and then someone else migrates it to 13. This will create chaos.

      I am also not in favor of an opt-in option because it's just an additional difference that we (developers and users) have to keep in mind (re: #1) and frankly the purported benefits do not outweigh the headaches it will cause.


      Regards,

      Mike.

      On 21/07/2022 12:12, Aarón Henríquez Quintana wrote:
      As a developer I love the way it is now.

      • You know clearly what is migrated, and all the history
      • Easy to track what is being migrated
      • The process is clean, and you get used to it very fast, barely 4 commands in git.
      • I think it is safe also, it is a responsibility of the repo maintainer that approves the PR to look at the code and check everything is correct.

      If we apply the proposal:

      • It is way more complex for developers, it open a bunch of possibilities:
        • If it was not in v15 at the time the 16.0 branch was created: in this case we will be doing the current procedure
        • If it was, and there is no improvement, then we will do a "normal" migration with 1 single commit, that's ok
        • if it was, but it was improved, we have to include those improvements as well, the diff is not reduced as well.
      • Deleted modules will create greater diffs.
      • If the module was deleted because no one wanted to use it, but later on someone decides to migrate it, the diff is going to be super huge.
      • It is going to be harder to know what is migrated, and being migrated, and what is not necessary.
      I understand the improvements of the change but I think those improvements are now important enough with respect to the drawbacks. 

      On Thu, 21 Jul 2022 at 10:02, Rémi CAZENAVE - Le Filament <notifications@odoo-community.org> wrote:

      Hi all,

      I like better the current method (having only working/tested/maintained modules in each branch) for the following reasons :
      - I find it easier to see what is available un a given version, what would still need to be migrated, and also to get an idea of which versions are being actively used (though I guess I could look at READMEs, migration issues and overall statistics to get the same info)
      - on each Odoo instance we deploy we download specific branch and having lots of unusable code would increase bandwidth and storage (although mostly text that could be compressed, so probably not dramatic neither)

      I agree that the process to migrate a module from one version to another is not really easy (at least the first times), but I understand that it would still probably need to be done in order to make sure you get the latest commits from previous branch. I am afraid that this would often be forgotten if not strictly necessary in migration process, and for sure we do not want to transfer this extra burden of checking for each PR whether based on latest commits or not to reviewers / PSC.

      Last, I am not in favour of having 2 different processes that can be applied per repo, since it would increase complexity for understanding why 2 repos are not behaving the same, and we may lose newcomers (but also for people not so much involved in OCA) - although here again I understand from discussions this is already the case for some repos.

      My 2 cents...

      Best Regards,
      Rémi CAZENAVE
      SCOP Le Filament

      Le July 21, 2022 3:52:02 AM UTC, "Raphaël Valyi" <notifications@odoo-community.org> a écrit :
      Hello,

      My vote goes to the opt-in option at least unless Pedro get convinced, because going against the will of somebody processing such a large portion of the PRs would be a terrible shot in the feet.

      That being said, earlier Pedro raised the concern about the possibility to craft an attack commit inside a missing commit that would be cherry-picked just like with the current way of migrating. But:

      On Wed, Jul 20, 2022, 3:42 PM Roussel, Denis <notifications@odoo-community.org> wrote:
      To summarize:

      • commits SHA are different with current behaviour
      • commits SHA are equal with proposed one

      Denis could you confirm this SHA conservation could make us safe against such crafted attack commits in the middle of the missing commits that one would need to cherry-pick with the new procedure?

      This crafted commit attack thing is indeed extremely concerning...

      _______________________________________________
      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 Raphael Makonnen - 11:41 - 21 Jul 2022

  • One stop shop (OSS) Tax with foreign fixed establishment
    Hi all,

    Has anymore already faced or/and solved the case where you need to apply the tax based on your fixed establishment providing the goods.
    My company is in country C only (no multi-company) and I have a warehouse in country C and D. So accounting is declared in country C, taxes are declared in country C and D according to their respective shipments.
    When the SO is placed, the shipping country is not known yet.
    If country D is shipping goods to a customer address in country D, this is a national delivery with the VAT of the delivery address country.
    If country D is shipping goods to a B2B EU customer address not in country D, this is an intracom delivery without VAT.
    Worst use case is if for one SO line of 10 units, you ship 4 from country C to country C (national delivery) and 6 from country D to country C (intracom delivery). You need an invoice for each delivering country and apply different tax while it's related to the same SO line.
    For B2C, the tax rate is always the one based on the customer delivery address but the declaration is done to the tax department of the delivering country.

    The 2 possible approaches I see are:
    - change the SO line at delivery to put the correct tax. But this could lead to SO line splitting and the SO does not reflect the original SO confirmation anymore. This can cause issues in the connections to e-commerce platforms. So I'm not in favor of it
    - change the tax set on the invoice at invoice generation. This will need to know what tax to apply, meaning we need to refine the qty_to_invoice to have one qty_to_invoice per delivering country.
    Of course, this should also work with returns and credit notes and the goods can be returned to a different country than the one that initially shipped the goods.

    Any input is welcome. I created this discussion here:

    Kind regards,
    Jacques-Etienne Baudoux
    by Jacques-Etienne Baudoux - 11:56 - 18 Jul 2022
  • Proposing myself as l10n-spain PSC
    Hi all,

    I would like to apply as PSC for https://github.com/OCA/l10n-spain

    At Studio73 we are working with Odoo since OpenERP 6.0 and we have contributed to some of the l10n-spain core modules.
    We are an experience team with the Spanish fiscal demands and we would like to help to our localization at the migration for next Odoo's release.

    My github account is
    https://github.com/fuentes73


    Best Regards,


    Pablo Fuentes
    Gerente - Ing. Informático
    pablo@studio73.es

    Consultoría Informática Studio 73 S.L.
     C/ Camí vell de l'estació, 6 Bajo Izquierda
    46870 - Ontinyent (Valencia)
    www.studio73.es - 96 191 12 79

    by Pablo Fuentes Rodríguez - 11:01 - 13 Jul 2022

    11 replies 11 replies

    • Re: Proposing myself as l10n-spain PSC
      Hi all.

      I don't want to be polemic, I just would like to have a decision based in good information and following answer of Pablo, I think he can help us with some more info.

      Pablo, I know you're the leader of a very skilled team. 
      To clarify this point to the rest of contributors, could you share with us github accounts of your developers and the sum of all their PRs in state closed?
      I mean the metric proposed by Pedro with

      In a quick review I can share this, with all of you.
      PRs closed and authored by:
      1) Actual PSCs in descending order
      Pedro, 216
      https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Apedrobaeza+is%3Aclosed+
      Acysos, 51
      https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Aacysos+is%3Aclosed+
      Omar, 42
      https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Aomar7r+is%3Aclosed+
      Cubells, 42
      https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Acubells+is%3Aclosed+
      Harald, 12
      https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3AHaraldPanten+is%3Aclosed+

      2) Other involved contributors
      Aritz, 132
      https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Aao-landoo+is%3Aclosed+
      Etobella, 76
      https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Aetobella+is%3Aclosed+

      3) Studio73, ???
      https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Afuentes73+is%3Aclosed
      6 + other members of this company

      Thanks.
      -----------------------------------------------------------
      Josean Soroa


      El jue, 14 jul 2022 a las 18:12, Pablo Fuentes (<notifications@odoo-community.org>) escribió:
      Hello everyone,

      Thank you all for your kind words. Just for the record.
      Although you might think that I do not have enough experience in l10n-spain, technically I do, and functionally I am well advised by my colleagues who have enough experience (1 lawyer and 3 tax advisors).
      So my proposal was on behalf of the Studio73 team because I am the one with the most availability.

      About very few contributions it's not compleatly fair. I'm behind most of my colleagues contributions during the analysis and internal review and this is dificult to measure but it's ok.

      Regardless, there is no problem by my side not to promote as a PSC.

      Thanks for your consideration.
      Best Regards,


      Pablo Fuentes
      Gerente - Ing. Informático
      pablo@studio73.es

      Consultoría Informática Studio 73 S.L.
       C/ Camí vell de l'estació, 6 Bajo Izquierda
      46870 - Ontinyent (Valencia)
      www.studio73.es - 96 191 12 79



      El jue, 14 jul 2022 a las 15:07, Enric Tobella Alomar (<notifications@odoo-community.org>) escribió:
      IMO, It is too soon for Pablo being a PSC member. You can check how many PRS he has done on OCA and it is not so much:
       
       
      Most of them are from long time ago and only 6 in l10n-spain.
       
      It is allways interesting to have PSCs, but I would prefer to see him more on action before.
       
      Kind regards,
       
      Enric Tobella Alomar
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 9611)
       
       
      From: Urtzi Pérez <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Thu, 14 Jul 2022 11:56:57 -0000
      Subject: Re: Proposing myself as l10n-spain PSC
       
      Hi,
       
      In my opinion Pablo is a +1 too.
       
      I agree with every point Josean has explained, and as the responsible of the spanish localization and member of the board of Aeodoo, I'd like to reinforce Josean's words saying that the projects we are facing this year will result in a large amount of contributions in short periods of time, so we'd need some efficiency in the deepest technical reviews most contributors can't do (mostly because of lack of experience).
       
      Pedro, I think the most important concept is to give the Spanish localization the push it needs. I'm sure that working with skilled people like Pablo could help you (and the other actual PSCs) to improve the  repository's health.
      Regards.
      ¿Nos dejas una reseña en Google My Business? Haz Clic Aquí
      Urtzi Pérez
      Departamento de desarrollo uperez@coninpe.es |  946 519 519
       
      Pol. Ind. Torrelarragoiti Parcela 8A- Pab. 10
       
      48170  Zamudio 
      Aviso legal: Este mensaje electrónico está dirigido únicamente a la(s) dirección(es)  indicadas anteriormente; el carácter confidencial, personal e intransferible del mismo  está protegido legalmente. Cualquier revelación, uso o reenvío no autorizado, completo o en parte, está prohibido. Si ha recibido este mensaje por equivocación, notifíquelo inmediatamente a la persona que lo ha enviado y borre el  mensaje original junto  con sus ficheros anexos sin leerlo ni grabarlo, total o parcialmente
       
      El jue, 14 jul 2022 a las 13:07, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
      They can contribute the same reviewing and proposing pull requests. The only difference is the right to trigger the merge command. What can't be done is someone that hasn't contributed a lot yet to the localization to have the same merits that someone that has done a lot along the years.
       
      This proposal can be reviewed in some time when the number of contributions will be significant.
       
      Regards.
      _______________________________________________
      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




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

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

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

      by Josean Soroa - 02:26 - 15 Jul 2022
    • Re: Proposing myself as l10n-spain PSC
      Hello everyone,

      Thank you all for your kind words. Just for the record.
      Although you might think that I do not have enough experience in l10n-spain, technically I do, and functionally I am well advised by my colleagues who have enough experience (1 lawyer and 3 tax advisors).
      So my proposal was on behalf of the Studio73 team because I am the one with the most availability.

      About very few contributions it's not compleatly fair. I'm behind most of my colleagues contributions during the analysis and internal review and this is dificult to measure but it's ok.

      Regardless, there is no problem by my side not to promote as a PSC.

      Thanks for your consideration.
      Best Regards,


      Pablo Fuentes
      Gerente - Ing. Informático
      pablo@studio73.es

      Consultoría Informática Studio 73 S.L.
       C/ Camí vell de l'estació, 6 Bajo Izquierda
      46870 - Ontinyent (Valencia)
      www.studio73.es - 96 191 12 79



      El jue, 14 jul 2022 a las 15:07, Enric Tobella Alomar (<notifications@odoo-community.org>) escribió:
      IMO, It is too soon for Pablo being a PSC member. You can check how many PRS he has done on OCA and it is not so much:
       
       
      Most of them are from long time ago and only 6 in l10n-spain.
       
      It is allways interesting to have PSCs, but I would prefer to see him more on action before.
       
      Kind regards,
       
      Enric Tobella Alomar
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 9611)
       
       
      From: Urtzi Pérez <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Thu, 14 Jul 2022 11:56:57 -0000
      Subject: Re: Proposing myself as l10n-spain PSC
       
      Hi,
       
      In my opinion Pablo is a +1 too.
       
      I agree with every point Josean has explained, and as the responsible of the spanish localization and member of the board of Aeodoo, I'd like to reinforce Josean's words saying that the projects we are facing this year will result in a large amount of contributions in short periods of time, so we'd need some efficiency in the deepest technical reviews most contributors can't do (mostly because of lack of experience).
       
      Pedro, I think the most important concept is to give the Spanish localization the push it needs. I'm sure that working with skilled people like Pablo could help you (and the other actual PSCs) to improve the  repository's health.
      Regards.
      ¿Nos dejas una reseña en Google My Business? Haz Clic Aquí
      Urtzi Pérez
      Departamento de desarrollo uperez@coninpe.es |  946 519 519
       
      Pol. Ind. Torrelarragoiti Parcela 8A- Pab. 10
       
      48170  Zamudio 
      Aviso legal: Este mensaje electrónico está dirigido únicamente a la(s) dirección(es)  indicadas anteriormente; el carácter confidencial, personal e intransferible del mismo  está protegido legalmente. Cualquier revelación, uso o reenvío no autorizado, completo o en parte, está prohibido. Si ha recibido este mensaje por equivocación, notifíquelo inmediatamente a la persona que lo ha enviado y borre el  mensaje original junto  con sus ficheros anexos sin leerlo ni grabarlo, total o parcialmente
       
      El jue, 14 jul 2022 a las 13:07, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
      They can contribute the same reviewing and proposing pull requests. The only difference is the right to trigger the merge command. What can't be done is someone that hasn't contributed a lot yet to the localization to have the same merits that someone that has done a lot along the years.
       
      This proposal can be reviewed in some time when the number of contributions will be significant.
       
      Regards.
      _______________________________________________
      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




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

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

      by Pablo Fuentes Rodríguez - 06:06 - 14 Jul 2022
    • Re: Proposing myself as l10n-spain PSC

      Helo,

      I'm agree with the Enric reply. For the moment nevative vote.

      Greetings

      El 14/7/22 a las 15:07, Enric Tobella Alomar escribió:
      IMO, It is too soon for Pablo being a PSC member. You can check how many PRS he has done on OCA and it is not so much:
       
       
      Most of them are from long time ago and only 6 in l10n-spain.
       
      It is allways interesting to have PSCs, but I would prefer to see him more on action before.
       
      Kind regards,
       
      Enric Tobella Alomar
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 9611)
       
       
      From: Urtzi Pérez <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Thu, 14 Jul 2022 11:56:57 -0000
      Subject: Re: Proposing myself as l10n-spain PSC
       
      Hi,
       
      In my opinion Pablo is a +1 too.
       
      I agree with every point Josean has explained, and as the responsible of the spanish localization and member of the board of Aeodoo, I'd like to reinforce Josean's words saying that the projects we are facing this year will result in a large amount of contributions in short periods of time, so we'd need some efficiency in the deepest technical reviews most contributors can't do (mostly because of lack of experience).
       
      Pedro, I think the most important concept is to give the Spanish localization the push it needs. I'm sure that working with skilled people like Pablo could help you (and the other actual PSCs) to improve the  repository's health.
      Regards.
      ¿Nos dejas una reseña en Google My Business? Haz Clic Aquí
      Urtzi Pérez
      Departamento de desarrollo uperez@coninpe.es |  946 519 519
       
      Pol. Ind. Torrelarragoiti Parcela 8A- Pab. 10
       
      48170  Zamudio 
      Aviso legal: Este mensaje electrónico está dirigido únicamente a la(s) dirección(es)  indicadas anteriormente; el carácter confidencial, personal e intransferible del mismo  está protegido legalmente. Cualquier revelación, uso o reenvío no autorizado, completo o en parte, está prohibido. Si ha recibido este mensaje por equivocación, notifíquelo inmediatamente a la persona que lo ha enviado y borre el  mensaje original junto  con sus ficheros anexos sin leerlo ni grabarlo, total o parcialmente
       
      El jue, 14 jul 2022 a las 13:07, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
      They can contribute the same reviewing and proposing pull requests. The only difference is the right to trigger the merge command. What can't be done is someone that hasn't contributed a lot yet to the localization to have the same merits that someone that has done a lot along the years.
       
      This proposal can be reviewed in some time when the number of contributions will be significant.
       
      Regards.
      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe




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

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

      --
      Ignacio Ibeas
      Acysos S.L. (www.acysos.com)
      Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
      Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
      Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
      Github (http://www.github.com/acysos)
      Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
      C/ Miguel Astrain 18, 1º Oficina A
      31006 Pamplona, Navarra.
      ignacio@acysos.com
      Tel. 948238905
      ---------------------- // -------------------
      La información contenida en este mensaje de correo electrónico es
      confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
      acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
      persona a la que va dirigido, cualquier divulgación, copia o distribución de
      la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
      tomada o dejada de tomar basada en la información contenida en este mensaje
      queda prohibida y puede ser ilegal.
      The information in this e-mail is confidential and may be legally privileged.
      It is intended solely for the addressee. Access to this e-mail by anyone is
      unauthorised. If you are not the intended recipient, any disclousure,
      copying, distribuition or any action taken or omited to be taken in reliance
      on it, is prohibited and may be unlawful.
      by Ignacio Ibeas - 06:06 - 14 Jul 2022
    • Re: Proposing myself as l10n-spain PSC
      IMO, It is too soon for Pablo being a PSC member. You can check how many PRS he has done on OCA and it is not so much:
       
       
      Most of them are from long time ago and only 6 in l10n-spain.
       
      It is allways interesting to have PSCs, but I would prefer to see him more on action before.
       
      Kind regards,
       
      Enric Tobella Alomar
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 9611)
       
       
      From: Urtzi Pérez <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Thu, 14 Jul 2022 11:56:57 -0000
      Subject: Re: Proposing myself as l10n-spain PSC
       
      Hi,
       
      In my opinion Pablo is a +1 too.
       
      I agree with every point Josean has explained, and as the responsible of the spanish localization and member of the board of Aeodoo, I'd like to reinforce Josean's words saying that the projects we are facing this year will result in a large amount of contributions in short periods of time, so we'd need some efficiency in the deepest technical reviews most contributors can't do (mostly because of lack of experience).
       
      Pedro, I think the most important concept is to give the Spanish localization the push it needs. I'm sure that working with skilled people like Pablo could help you (and the other actual PSCs) to improve the  repository's health.
      Regards.
      ¿Nos dejas una reseña en Google My Business? Haz Clic Aquí
      Urtzi Pérez
      Departamento de desarrollo uperez@coninpe.es |  946 519 519
       
      Pol. Ind. Torrelarragoiti Parcela 8A- Pab. 10
       
      48170  Zamudio 
      Aviso legal: Este mensaje electrónico está dirigido únicamente a la(s) dirección(es)  indicadas anteriormente; el carácter confidencial, personal e intransferible del mismo  está protegido legalmente. Cualquier revelación, uso o reenvío no autorizado, completo o en parte, está prohibido. Si ha recibido este mensaje por equivocación, notifíquelo inmediatamente a la persona que lo ha enviado y borre el  mensaje original junto  con sus ficheros anexos sin leerlo ni grabarlo, total o parcialmente
       
      El jue, 14 jul 2022 a las 13:07, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
      They can contribute the same reviewing and proposing pull requests. The only difference is the right to trigger the merge command. What can't be done is someone that hasn't contributed a lot yet to the localization to have the same merits that someone that has done a lot along the years.
       
      This proposal can be reviewed in some time when the number of contributions will be significant.
       
      Regards.
      _______________________________________________
      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




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

      1 attachments 1 attachments

      CB 70anys Gris _ CB+ Color H RGB.png
    • Re: Proposing myself as l10n-spain PSC
      Sorry, but only PSCs can approve new requests, so your opinion can be welcome, but you don't know and understand enough PSC rules and what meritocracy means.

      Regards.
      by Pedro M. Baeza - 02:06 - 14 Jul 2022

  • Proposing myself as l10n-spain PSC
    Hi all,

    I would like to apply as PSC for https://github.com/OCA/l10n-spain

    Main reason is I am an experienced developer and consultant in Spain, we are working with Odoo from 5.0 version (13 years of my life), first at Pexego with a lot of contributions in the early years of  the community and localization, and for the last 6 years at Comunitea.
    In the early years of OCA I belonged to core-commmiters github's group, I would like apporting to evolve more quickly our localization for next Odoo's version and contribute in the future fiscal demands.

    My github account is
    https://github.com/omar7r


    Thanks for considering my request and regards.

    Omar Castiñeira
    Comunitea Servicios Tecnológicos S.L.


    by Omar Castiñeira Saavedra - 10:01 - 13 Jul 2022

    11 replies 11 replies

  • Proposing myself as l10n-spain PSC
    Hi all,

    I would like to apply as PSC for https://github.com/OCA/l10n-spain

    Main reason is the big development we are doing from last year to cover Basque Country requirements (Fiscal Ticketbai and Batuz project).
    This task is not fully finished and we need a big push in next weeks.
    Also in next months we have a team working in localization for Canary Islands, with also specific fiscal rules.
    And in near future we expect to have important changes in rest of spanish fiscal rules.

    I have contributed in this repository by migrating different modules (mainly TicketBAI modules) for last two years and I have a developer profile.

    I have also been teaching other contributors how to correctly migrate different Spanish Localization modules to V15 in an event that was organized by the community a few months ago.

    My github account is https://github.com/ao-landoo

    Thanks for considering my request and regards.

    --
    Aritz Olea

    LANDOO - Sistemas de Información con Odoo
    Tel.: +34 943 568 663
    Zubiberri  bidea 31, pl. 2, ofic. 3
    Parque Empresarial Zuatzu, Edif. Urumea
    20018 Donostia, Gipuzkoa, Spain
    PARTNER OFICIAL ODOO "GOLD"
    (En junio-2021, #1 del ranking entre los 60 partners de España, ver en www.odoo.com/partners)
    CERTIFICADO ODOO V15, V14, V13, V12 y V11
    Entrevista en Odoo Experience 2019: https://www.youtube.com/watch?v=XMtCe8F7JUc
    by Aritz Olea - 09:11 - 13 Jul 2022

    20 replies 20 replies

    • Re: Proposing myself as l10n-spain PSC
      Just another precision. 
      I agree now we have no delays with merges in Basque localization, but that's because:
      - Pedro, you are helping a lot. Many thanks for your constant effort and compromise with community.
      -  development has nearly stoped after Logroño OCA days.
      Next weeks things are going to change and we want to be prepared.

      Thanks and regards 
      -----------------------------------------------------------
      Josean Soroa

      El vie., 15 jul. 2022 14:52, Pedro M. Baeza (Tecnativa) <notifications@odoo-community.org> escribió:
      Just one precision: it's not going to speed up anything, as the speed right now is immediate.

      El vie., 15 jul. 2022 14:41, Josean Soroa - Landoo <notifications@odoo-community.org> escribió:
      Hi.

      In this case I think we have a good solution using maintainers rights, so we are not going to follow with this discussion.
      In the mentoring project for v15, Aritz has mentored some modules not included in Basque localization and in the future he will continue this way, so we will talk about that in some months.

      For now, as mentioned by Pedro, establishing Aritz as maintainer will be enough to speed up the migrations to v14 and 15, we are planning for this month.
      Just for better comprehension of all, some light over very important details:
      - we were told by Pedro and Tobella (or thats what we understood) about the right of maintainers to merge their modules, but restricted to same branch. This is not a solution for us, because we need to merge migration of modules and this in different branch.
      - from Sylvain answer yesterday, we realized that 3 months there has been a new change in OCA rules, to allow maintainers do the same but also in different branches.
      That's perfect for us and I want to thank Sylvain for this key contribution.
      And for the rest of maintainers, take note of this new rule. Will be very useful.

      Regards.
      -----------------------------------------------------------
      Josean Soroa







      El jue, 14 jul 2022 a las 18:32, Pablo Fuentes (<notifications@odoo-community.org>) escribió:
      Hi, 

      I compleatly agree with Jairo's message and I don't agree with create a new repo just for the basque country just because of don't want to promote Aritz.
      If we talk about merits and meritocracy, Aritz has some... he is:

      Best Regards,

      El jue, 14 jul 2022 a las 18:02, Soporte Acysos (<notifications@odoo-community.org>) escribió:

      Hello,

      I'm the oldest PSC, but I know that now I'm less active.

      Negative vote.

      I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
      Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
      If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.

      Greetings,
      Ignacio

      El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
      Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

      Regards.

      El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
      Hi all,

      Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

      Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

      Regards.

      El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
      Hi Graeme,

      some precision inline.

      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
      Standard : (+33) 09.72.32.33.17
      Service Informatique : (+33) 09.73.79.64.40
      Astreinte Informatique : (+33) 06.81.85.61.43
      Member of the OCA (Odoo Community Association)


      Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      Hi Josean,

      You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

      FYI,
      - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)
      - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)

       
      Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

      But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

      On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
      Hi all.
      Excuse me for this long answer but the question is very important for us.
       
      My vote is +1 for Aritz.

      My reasons are very similar to the case of Pablo:
      - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
      - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
      - Aritz is one of the few developers who knows deeply Basque Country localization

      In are more deep explanation, I'm involved in this question by 3 different rules.
      - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
      From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
      - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
      This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
      - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.

      I hope other members of the community will agree with this point of view and will send a +1 to this applicant.

      Thanks.
      -----------------------------------------------------------
      Josean Soroa
      LANDOO SL - www.landoo.es
      -----------------------------------------------------------


      El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
      Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -1.

      Regards.

      _______________________________________________
      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



      --
      Aritz Olea
      LANDOO - Sistemas de Información con Odoo

      _______________________________________________
      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

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

      _______________________________________________
      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 Josean Soroa - 04:01 - 15 Jul 2022
    • Re: Proposing myself as l10n-spain PSC
      Just one precision: it's not going to speed up anything, as the speed right now is immediate.

      El vie., 15 jul. 2022 14:41, Josean Soroa - Landoo <notifications@odoo-community.org> escribió:
      Hi.

      In this case I think we have a good solution using maintainers rights, so we are not going to follow with this discussion.
      In the mentoring project for v15, Aritz has mentored some modules not included in Basque localization and in the future he will continue this way, so we will talk about that in some months.

      For now, as mentioned by Pedro, establishing Aritz as maintainer will be enough to speed up the migrations to v14 and 15, we are planning for this month.
      Just for better comprehension of all, some light over very important details:
      - we were told by Pedro and Tobella (or thats what we understood) about the right of maintainers to merge their modules, but restricted to same branch. This is not a solution for us, because we need to merge migration of modules and this in different branch.
      - from Sylvain answer yesterday, we realized that 3 months there has been a new change in OCA rules, to allow maintainers do the same but also in different branches.
      That's perfect for us and I want to thank Sylvain for this key contribution.
      And for the rest of maintainers, take note of this new rule. Will be very useful.

      Regards.
      -----------------------------------------------------------
      Josean Soroa







      El jue, 14 jul 2022 a las 18:32, Pablo Fuentes (<notifications@odoo-community.org>) escribió:
      Hi, 

      I compleatly agree with Jairo's message and I don't agree with create a new repo just for the basque country just because of don't want to promote Aritz.
      If we talk about merits and meritocracy, Aritz has some... he is:

      Best Regards,

      El jue, 14 jul 2022 a las 18:02, Soporte Acysos (<notifications@odoo-community.org>) escribió:

      Hello,

      I'm the oldest PSC, but I know that now I'm less active.

      Negative vote.

      I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
      Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
      If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.

      Greetings,
      Ignacio

      El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
      Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

      Regards.

      El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
      Hi all,

      Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

      Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

      Regards.

      El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
      Hi Graeme,

      some precision inline.

      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
      Standard : (+33) 09.72.32.33.17
      Service Informatique : (+33) 09.73.79.64.40
      Astreinte Informatique : (+33) 06.81.85.61.43
      Member of the OCA (Odoo Community Association)


      Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      Hi Josean,

      You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

      FYI,
      - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)
      - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)

       
      Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

      But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

      On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
      Hi all.
      Excuse me for this long answer but the question is very important for us.
       
      My vote is +1 for Aritz.

      My reasons are very similar to the case of Pablo:
      - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
      - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
      - Aritz is one of the few developers who knows deeply Basque Country localization

      In are more deep explanation, I'm involved in this question by 3 different rules.
      - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
      From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
      - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
      This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
      - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.

      I hope other members of the community will agree with this point of view and will send a +1 to this applicant.

      Thanks.
      -----------------------------------------------------------
      Josean Soroa
      LANDOO SL - www.landoo.es
      -----------------------------------------------------------


      El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
      Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -1.

      Regards.

      _______________________________________________
      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



      --
      Aritz Olea
      LANDOO - Sistemas de Información con Odoo

      _______________________________________________
      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

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

      _______________________________________________
      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 Pedro M. Baeza - 02:51 - 15 Jul 2022
    • Re: Proposing myself as l10n-spain PSC
      Hi.

      In this case I think we have a good solution using maintainers rights, so we are not going to follow with this discussion.
      In the mentoring project for v15, Aritz has mentored some modules not included in Basque localization and in the future he will continue this way, so we will talk about that in some months.

      For now, as mentioned by Pedro, establishing Aritz as maintainer will be enough to speed up the migrations to v14 and 15, we are planning for this month.
      Just for better comprehension of all, some light over very important details:
      - we were told by Pedro and Tobella (or thats what we understood) about the right of maintainers to merge their modules, but restricted to same branch. This is not a solution for us, because we need to merge migration of modules and this in different branch.
      - from Sylvain answer yesterday, we realized that 3 months there has been a new change in OCA rules, to allow maintainers do the same but also in different branches.
      That's perfect for us and I want to thank Sylvain for this key contribution.
      And for the rest of maintainers, take note of this new rule. Will be very useful.

      Regards.
      -----------------------------------------------------------
      Josean Soroa







      El jue, 14 jul 2022 a las 18:32, Pablo Fuentes (<notifications@odoo-community.org>) escribió:
      Hi, 

      I compleatly agree with Jairo's message and I don't agree with create a new repo just for the basque country just because of don't want to promote Aritz.
      If we talk about merits and meritocracy, Aritz has some... he is:

      Best Regards,

      El jue, 14 jul 2022 a las 18:02, Soporte Acysos (<notifications@odoo-community.org>) escribió:

      Hello,

      I'm the oldest PSC, but I know that now I'm less active.

      Negative vote.

      I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
      Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
      If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.

      Greetings,
      Ignacio

      El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
      Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

      Regards.

      El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
      Hi all,

      Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

      Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

      Regards.

      El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
      Hi Graeme,

      some precision inline.

      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
      Standard : (+33) 09.72.32.33.17
      Service Informatique : (+33) 09.73.79.64.40
      Astreinte Informatique : (+33) 06.81.85.61.43
      Member of the OCA (Odoo Community Association)


      Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      Hi Josean,

      You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

      FYI,
      - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)
      - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)

       
      Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

      But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

      On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
      Hi all.
      Excuse me for this long answer but the question is very important for us.
       
      My vote is +1 for Aritz.

      My reasons are very similar to the case of Pablo:
      - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
      - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
      - Aritz is one of the few developers who knows deeply Basque Country localization

      In are more deep explanation, I'm involved in this question by 3 different rules.
      - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
      From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
      - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
      This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
      - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.

      I hope other members of the community will agree with this point of view and will send a +1 to this applicant.

      Thanks.
      -----------------------------------------------------------
      Josean Soroa
      LANDOO SL - www.landoo.es
      -----------------------------------------------------------


      El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
      Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -1.

      Regards.

      _______________________________________________
      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



      --
      Aritz Olea
      LANDOO - Sistemas de Información con Odoo

      _______________________________________________
      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

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

      _______________________________________________
      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 Josean Soroa - 02:41 - 15 Jul 2022
    • Re: Proposing myself as l10n-spain PSC
      Hi, 

      I compleatly agree with Jairo's message and I don't agree with create a new repo just for the basque country just because of don't want to promote Aritz.
      If we talk about merits and meritocracy, Aritz has some... he is:

      Best Regards,

      El jue, 14 jul 2022 a las 18:02, Soporte Acysos (<notifications@odoo-community.org>) escribió:

      Hello,

      I'm the oldest PSC, but I know that now I'm less active.

      Negative vote.

      I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
      Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
      If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.

      Greetings,
      Ignacio

      El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
      Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

      Regards.

      El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
      Hi all,

      Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

      Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

      Regards.

      El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
      Hi Graeme,

      some precision inline.

      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
      Standard : (+33) 09.72.32.33.17
      Service Informatique : (+33) 09.73.79.64.40
      Astreinte Informatique : (+33) 06.81.85.61.43
      Member of the OCA (Odoo Community Association)


      Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      Hi Josean,

      You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

      FYI,
      - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)
      - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)

       
      Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

      But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

      On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
      Hi all.
      Excuse me for this long answer but the question is very important for us.
       
      My vote is +1 for Aritz.

      My reasons are very similar to the case of Pablo:
      - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
      - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
      - Aritz is one of the few developers who knows deeply Basque Country localization

      In are more deep explanation, I'm involved in this question by 3 different rules.
      - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
      From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
      - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
      This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
      - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.

      I hope other members of the community will agree with this point of view and will send a +1 to this applicant.

      Thanks.
      -----------------------------------------------------------
      Josean Soroa
      LANDOO SL - www.landoo.es
      -----------------------------------------------------------


      El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
      Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -1.

      Regards.

      _______________________________________________
      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



      --
      Aritz Olea
      LANDOO - Sistemas de Información con Odoo

      _______________________________________________
      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

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

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

      by Pablo Fuentes Rodríguez - 06:30 - 14 Jul 2022
    • Re: Proposing myself as l10n-spain PSC

      Hello,

      I'm the oldest PSC, but I know that now I'm less active.

      Negative vote.

      I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
      Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
      If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.

      Greetings,

      Ignacio


      El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
      Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

      Regards.

      El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
      Hi all,

      Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

      Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

      Regards.

      El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
      Hi Graeme,

      some precision inline.

      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
      Standard : (+33) 09.72.32.33.17
      Service Informatique : (+33) 09.73.79.64.40
      Astreinte Informatique : (+33) 06.81.85.61.43
      Member of the OCA (Odoo Community Association)


      Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      Hi Josean,

      You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

      FYI,
      - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)
      - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)

       
      Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

      But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

      On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
      Hi all.
      Excuse me for this long answer but the question is very important for us.
       
      My vote is +1 for Aritz.

      My reasons are very similar to the case of Pablo:
      - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
      - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
      - Aritz is one of the few developers who knows deeply Basque Country localization

      In are more deep explanation, I'm involved in this question by 3 different rules.
      - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
      From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
      - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
      This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
      - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.

      I hope other members of the community will agree with this point of view and will send a +1 to this applicant.

      Thanks.
      -----------------------------------------------------------
      Josean Soroa
      LANDOO SL - www.landoo.es
      -----------------------------------------------------------


      El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
      Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -1.

      Regards.

      _______________________________________________
      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



      --
      Aritz Olea
      LANDOO - Sistemas de Información con Odoo

      _______________________________________________
      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

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

  • Proposing myself as l10n-spain PSC 
    Hi all,

I would like to apply as PSC for https://github.com/OCA/l10n-spain

Main reason is the big development we are doing from last year to cover
Basque Country requirements (Fiscal Ticketbai and Batuz project).
This task is not fully finished and we need a big push in next weeks.
Also in next months we have a team working in localization for Canary
Islands, with also specific fiscal rules.
And in near future we expect to have important changes in rest of
spanish fiscal rules.

I have contributed in this repository for last years and I have a
developer and functional profile.


My github account is https://github.com/cubells

Thanks for considering my request and regards.

Vicent Cubells
Trey, kilobytes de soluciones



-- 
Atentament, cubells.
--
    by Vicent Cubells Peña - 09:01 - 13 Jul 2022

    12 replies 12 replies

    • Re: Proposing myself as l10n-spain PSC

      Hello,

      I also agree.

      Greetings


      El 13/7/22 a las 16:46, Enric Tobella Alomar escribió:
      I added you as member of the PSC team. GitHub invite should follow in the next 24h.
       
      Best regards
       
      Enric Tobella Alomar
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 9611)
       
       
      From: "cubells" <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 13 Jul 2022 07:02:10 -0000
      Subject: Proposing myself as l10n-spain PSC
        
      Hi all,

I would like to apply as PSC for https://github.com/OCA/l10n-spain

Main reason is the big development we are doing from last year to cover
Basque Country requirements (Fiscal Ticketbai and Batuz project).
This task is not fully finished and we need a big push in next weeks.
Also in next months we have a team working in localization for Canary
Islands, with also specific fiscal rules.
And in near future we expect to have important changes in rest of
spanish fiscal rules.

I have contributed in this repository for last years and I have a
developer and functional profile.


My github account is https://github.com/cubells

Thanks for considering my request and regards.

Vicent Cubells
Trey, kilobytes de soluciones



-- 
Atentament, cubells.
--




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

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

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

      Hello,

      Yes, I'm agree. He is great contributor.

      Greetings

      El 13/7/22 a las 16:46, Enric Tobella Alomar escribió:
      I added you as member of the PSC team. GitHub invite should follow in the next 24h.
       
      Best regards
       
      Enric Tobella Alomar
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 9611)
       
       
      From: "cubells" <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 13 Jul 2022 07:02:10 -0000
      Subject: Proposing myself as l10n-spain PSC
        
      Hi all,

I would like to apply as PSC for https://github.com/OCA/l10n-spain

Main reason is the big development we are doing from last year to cover
Basque Country requirements (Fiscal Ticketbai and Batuz project).
This task is not fully finished and we need a big push in next weeks.
Also in next months we have a team working in localization for Canary
Islands, with also specific fiscal rules.
And in near future we expect to have important changes in rest of
spanish fiscal rules.

I have contributed in this repository for last years and I have a
developer and functional profile.


My github account is https://github.com/cubells

Thanks for considering my request and regards.

Vicent Cubells
Trey, kilobytes de soluciones



-- 
Atentament, cubells.
--




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

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

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







      El mié, 13 jul 2022 a las 9:02, cubells (<notifications@odoo-community.org>) escribió:
      Hi all,

I would like to apply as PSC for https://github.com/OCA/l10n-spain

Main reason is the big development we are doing from last year to cover
Basque Country requirements (Fiscal Ticketbai and Batuz project).
This task is not fully finished and we need a big push in next weeks.
Also in next months we have a team working in localization for Canary
Islands, with also specific fiscal rules.
And in near future we expect to have important changes in rest of
spanish fiscal rules.

I have contributed in this repository for last years and I have a
developer and functional profile.


My github account is https://github.com/cubells

Thanks for considering my request and regards.

Vicent Cubells
Trey, kilobytes de soluciones




-- 
Atentament, cubells.
--

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

      by Josean Soroa - 12:51 - 14 Jul 2022
    • RE: Proposing myself as l10n-spain PSC

      Great news!!! 😊

       

      Thanks Vicent!

       

       

      De: Enric Tobella Alomar <notifications@odoo-community.org>
      Enviado el: miércoles, 13 de julio de 2022 16:47
      Para: Contributors <contributors@odoo-community.org>
      Asunto: Re: Proposing myself as l10n-spain PSC

       

      I added you as member of the PSC team. GitHub invite should follow in the next 24h.

       

      Best regards

       

      Enric Tobella Alomar

      Av. J. V. Foix 63

      08034 Barcelona

      Tlf.    932 522 522 (Ext. 9611)

       

       

      From: "cubells" <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 13 Jul 2022 07:02:10 -0000
      Subject: Proposing myself as l10n-spain PSC
        

       
      Hi all,
       
      I would like to apply as PSC for https://github.com/OCA/l10n-spain
       
      Main reason is the big development we are doing from last year to cover
      Basque Country requirements (Fiscal Ticketbai and Batuz project).
      This task is not fully finished and we need a big push in next weeks.
      Also in next months we have a team working in localization for Canary
      Islands, with also specific fiscal rules.
      And in near future we expect to have important changes in rest of
      spanish fiscal rules.
       
      I have contributed in this repository for last years and I have a
      developer and functional profile.
       
       
      My github account is https://github.com/cubells
       
      Thanks for considering my request and regards.
       
      Vicent Cubells
      Trey, kilobytes de soluciones
       
       
       
      -- 
      Atentament, cubells.
      --





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

      by Rafael Blasco (Moduon) - 11:50 - 14 Jul 2022
    • Re: Proposing myself as l10n-spain PSC
      I added you as member of the PSC team. GitHub invite should follow in the next 24h.
       
      Best regards
       
      Enric Tobella Alomar
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 9611)
       
       
      From: "cubells" <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Wed, 13 Jul 2022 07:02:10 -0000
      Subject: Proposing myself as l10n-spain PSC
        
      Hi all,

I would like to apply as PSC for https://github.com/OCA/l10n-spain

Main reason is the big development we are doing from last year to cover
Basque Country requirements (Fiscal Ticketbai and Batuz project).
This task is not fully finished and we need a big push in next weeks.
Also in next months we have a team working in localization for Canary
Islands, with also specific fiscal rules.
And in near future we expect to have important changes in rest of
spanish fiscal rules.

I have contributed in this repository for last years and I have a
developer and functional profile.


My github account is https://github.com/cubells

Thanks for considering my request and regards.

Vicent Cubells
Trey, kilobytes de soluciones



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




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

      1 attachments 1 attachments

      CB 70anys Gris _ CB+ Color H RGB.png

  • prior price before promotion
    Hi all,

    Does anyone have worked on the subject of a "base price" or "prior price" ?
    There is a EU Directive 2019/2161 about for it:

    > 2.   The prior price means the lowest price applied by the trader during a period of time not shorter than 30 days prior to the application of the price reduction.


    Regards,


    --
    Raphaël Reverdy
    Mobile +33 6 38 02 03 93
    Fixe +33 4 82 53 84 60
    by Raphaël Reverdy - 11:15 - 11 Jul 2022

    1 replies 1 replies

    • Re: prior price before promotion 
      Hi Raphael,

at least i haven't heard anything in that direction. But the folks 
working in grocery retail should know.

Best Frederik

Am 11.07.22 um 11:16 schrieb Raphaël Reverdy:

> Hi all,

> Does anyone have worked on the subject of a "base price" or "prior price" ?

> There is a EU Directive 2019/2161 about for it:

>> 2.   The prior price

> means the lowest price applied by the trader during a period of time not

> shorter than 30 days prior to the application of the price reduction.

> https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32019L2161#d1e776-7-1 [1]

> Regards,

>

> --

> Raphaël Reverdy

> Mobile +33 6 38 02 03 93

> Fixe +33 4 82 53 84 60

> _______________________________________________

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

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

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

>

>

>

> [1] https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32019L2161#d1e776-7-1

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

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

>

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Phone:  +49 4181 13503-12
Fax:    +49 4181 13503-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: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
      by Frederik Kramer - 11:46 - 11 Jul 2022