Skip to Content

Contributors

  • Re: Sorry, i'm not familiar with git
    On 19/01/2023 00:57, Francesco Ballerini wrote:
    Invalid title for commit: ' [FIX] product: add explicit copy arg to property_product_pricelist'

    Hello,

    This one is because you have a space in the beginning of the commit message, " [FIX]" instead of "[FIX]" ;-)
    But don't worry about it if you are not sure how to amend your commit, we can handle it for you if needed.

    Martin


    by Martin Trigaux - 08:31 - 19 Jan 2023
  • Fwd: Sorry, i'm not familiar with git
    Also, I just realized that PR is for Odoo itself, so it's not directly related to OCA. Sorry for the misunderstanding.

    by Francesco Ballerini - 01:31 - 19 Jan 2023
  • Fwd: Sorry, i'm not familiar with git
    Forgot the link to PR. 

    Thanks in advance,
    Francesco Ballerini

    --------------
    Hi everyone, I am discovering git/github/Pull Requests and I am receiving this error. 
    Basically I wanted to ask how can I fix this, but most importantly I want to excuse because I think that I forced pushed while trying to fix it. 
    Not sure if force pushing can really cause problems in protected branches, but I have read it's a really bad practice. 
    I suddenly panicked like I never did, of course, and immediately cancelled PR and made it new. But the error is still here. Not sure about the error, what could I do in this situation? 


    Invalid title for commit: ' [FIX] product: add explicit copy arg to property_product_pricelist'
    Thanks in advance,
    Francesco Ballerini

    by Francesco Ballerini - 01:06 - 19 Jan 2023
  • Sorry, i'm not familiar with git
    Hi everyone, I am discovering git/github/Pull Requests and I am receiving this error. 

    Basically I wanted to ask how can I fix this, but most importantly I want to excuse because I think that I forced pushed while trying to fix it. 

    Not sure if force pushing can really cause problems in protected branches, but I have read it's a really bad practice. 

    I suddenly panicked like I never did, of course, and immediately cancelled PR and made it new. But the error is still here. Not sure about the error, what could I do in this situation? 


    Invalid title for commit: ' [FIX] product: add explicit copy arg to property_product_pricelist'
    Thanks in advance,
    Francesco Ballerini

    by Francesco Ballerini - 12:56 - 19 Jan 2023
  • Re: Multi-company > one default bank account


    Le 18/01/2023 à 16:12, Moshchot Coop a écrit :
    Dear Contributors,
     
    We are a young distributed devops coop, part of Bar Kayma  - a nonprofit cooperative cultural fiscal hosting consortium from Jerusalem - and a fresh member of OCA, very looking forward to becoming a contributing party to the commons. 

    Recently we started the project of implementing our fiscal hosting frameworks on self hosted  Odoo with the end-goal of developing  our vertical solution of fiscal sponsorship and self management for Non-Profit Projects for social economy peers (basically an Odoo-based OpenCollective.com equivalent) to be shared with the OCA. 

    To our understanding using Multi-Company logic is the best fit for our purposes, including the need of inter-company billing, however as a fiscal host we must be able to set one default bank account (of the main/parent company) for all the children companies.

    Hi. do you mean that your child companies share the same accounting configuration ? Journals, account, taxes ? If yes, I developped in my company (GRAP) a verticalization for that purpose. (the name is CAE in France) You can take a look here and send me a message if you think that it could be mutualized. https://github.com/grap/odoo-addons-cae

    Regards.

    So with a lot of inspiration from OCA/Cooperative we started customising and extending Accounting to our needs and for V16 - but still can’t figure out how to make it work properly.

    We tried to set it as a default attribute from inherited account.move model & form, & res.partner.bank, and also muted restriction in res.bank to allow different companies have the same bank account. This however doesn’t seem to work.

    We also tried to set a default bank account value in payment mode, but we couldn’t make the parent's mode be accessible for daughter companies.

    Are we using a wrong approach to the problem?  Or deprecated methods? Had someone already ported any relevant parts of the vertical cooperative  accounting to  v16?

    We would appreciate any help, advice, suggestions, or working examples on how to add this feature without reinventing the wheel.

    Thank you in advance,
    Lena & Talia

    Moshchot Coop
    A DISTRIBUTED OPEN SOURCE COOPERATIVE



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

    -- 
    Sylvain LE GAL
    - GRAP, service informatique
    - 3 Grande rue des Feuillants 69001 LYON, 09.72.32.33.17
    - Astreinte : 06.81.85.61.43 // informatique@grap.coop

    by Sylvain LE GAL - 05:05 - 18 Jan 2023
  • Re: Multi-company > one default bank account
    > To our understanding using Multi-Company logic is the best fit for our
    
    > purposes, including the need of inter-company billing, however as a fiscal
    
    > host we must be able to set one default bank account (of the main/parent
    
    > company) for all the children companies.
    
    note that multicompany separates entities to some degree, but as soon as you 
    allow any user of the child companies access to the configuration, they can 
    undo all of this. The same if you install modules that allow users to run 
    code.
    
    
    > We tried to set it as a default attribute from inherited account.move model
    
    > & form, & res.partner.bank, and also muted restriction in res.bank to allow
    
    > different companies have the same bank account. This however doesn’t seem
    
    > to work.
    
    links to code are much more helpful than verbal descriptions
     
    
    > We also tried to set a default bank account value in payment mode, but we
    
    > couldn’t make the parent's mode be accessible for daughter companies.
    
    did you change
    https://github.com/OCA/bank-payment/blob/16.0/account_payment_mode/security/
    account_payment_mode.xml#L7
    ?
    
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

    by Holger Brunn - 04:55 - 18 Jan 2023
  • Multi-company > one default bank account
    Dear Contributors,
     
    We are a young distributed devops coop, part of Bar Kayma  - a nonprofit cooperative cultural fiscal hosting consortium from Jerusalem - and a fresh member of OCA, very looking forward to becoming a contributing party to the commons. 

    Recently we started the project of implementing our fiscal hosting frameworks on self hosted  Odoo with the end-goal of developing  our vertical solution of fiscal sponsorship and self management for Non-Profit Projects for social economy peers (basically an Odoo-based OpenCollective.com equivalent) to be shared with the OCA. 

    To our understanding using Multi-Company logic is the best fit for our purposes, including the need of inter-company billing, however as a fiscal host we must be able to set one default bank account (of the main/parent company) for all the children companies.

    So with a lot of inspiration from OCA/Cooperative we started customising and extending Accounting to our needs and for V16 - but still can’t figure out how to make it work properly.

    We tried to set it as a default attribute from inherited account.move model & form, & res.partner.bank, and also muted restriction in res.bank to allow different companies have the same bank account. This however doesn’t seem to work.

    We also tried to set a default bank account value in payment mode, but we couldn’t make the parent's mode be accessible for daughter companies.

    Are we using a wrong approach to the problem?  Or deprecated methods? Had someone already ported any relevant parts of the vertical cooperative  accounting to  v16?

    We would appreciate any help, advice, suggestions, or working examples on how to add this feature without reinventing the wheel.

    Thank you in advance,
    Lena & Talia

    Moshchot Coop
    A DISTRIBUTED OPEN SOURCE COOPERATIVE




    by "Moshchot Coop" <tali@moshchot.org> - 04:10 - 18 Jan 2023
  • Re: booking of resources

    On 17 Jan 2023, at 20:56, hugues de keyzer wrote:

    hello, dear contributors!

    one of our clients needs a solution for managing bookings of rooms in a building (for events like conferences, parties, etc.). they have several rooms that can be booked, and each booking can have options involving objects or people, like a video projector, waiters, tables, chairs, plates and cutlery,…

    some objects are identified individually (like video projectors), while others can be considered as always available in infinite quantity (like tables, chairs, plates and cutlery) and only the amount matters.

    bookings would be created manually (on the back-end side) by our client after communicating with their customers (by e-mail, telephone,…). for each booking, a sale order should be made, and the price should depend on the room, the duration and the chosen options. the bookings (and thus availability) of each room, person, and individually identified object (like a video projector) should be visible in a calendar, and booking conflicts must be avoided.

    do you have any advice on how to implement this without reinventing the wheel?

    we looked into the resource_booking module, which seems mostly great overall, but quickly faced a constraint: a resource.booking can only book one resource.booking.combination. a combination is a fixed list of resources, and combinations must be created manually. i’m not sure how it’s supposed to be used.

    if only one resource.booking is created for a customer booking, this means that the booking and all its options must be represented by one combination. for example, if there are 4 rooms, 3 video projectors and 5 people that can be combined freely, 96 combinations (including the “no video projector” and “no waiter” choice) must be created (and each of them must be added to at least one resource.booking.type to be selectable). moreover, the client would need to search through all of these to find the desired one. and what if there could be multiple waiters? this feels awkward. also, availability is only visible per combination, not per resource, so it is not very useful. however, it seems that availability conflicts are checked per resource, but in case of conflict, no information is given about which resource is not available.

    another option is to create one combination per resource, and create multiple resource.bookings (with the same date and the same partner) for one customer booking. this is more flexible, but there are no direct links between all of these bookings. what if the customer wants to change the date or cancel the booking?

    for billing, sale_resource_booking allows to link a product to a resource.booking.combination, so one product is needed for each combination. it also allows to generate a sale order from a resource booking type (so combination and dates must be selected afterwards), but i didn’t find a way to do it from a booking, which would be more useful.

    i understand why using combinations can be useful (as a compound for common use cases), and this is maybe a good technical decision (because it can avoid duplication), but i think that as they are, it seems that, in many cases, they get in the way instead of helping. am i maybe missing something obvious?

    here are some possibilities i’m currently considering:

    1. use one resource.booking per booking, but hide the combinations from the user (using a wizard, for example). the user would select all desired resources, and a matching combination would be used if one exists, or one would be created on the fly.
    2. use multiple resource.bookings per booking (one for each resource), create one combination per resource, and find a way to link resource.bookings together.
    3. extend resource.booking by allowing multiple combinations to be booked per booking (instead of only one), and create one combination per resource.
    4. extend resource.booking by allowing multiple resources to be booked directly per booking (instead of a combination), and don’t use combinations.

    for objects considered as always available, use a product, and extend resource.booking by allowing multiple products (with a quantity) to be linked to a booking, or simply add them directly to the generated sale order.

    i’m pretty sure that this resource booking use case is quite common, and having a generic solution that works for most cases would be useful. do you have any ideas about all this?

    cheers,

    hugues de keyzer
    coop it easy

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

    Another option besides resource.booking would be to just use the rental modules
    and add all rooms and individual objects as products in Odoo.
    You can then use products packs and product sets to create combinations or
    standard offers of the base products.

    Olaf
    --
    Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com
    Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
    Geschäftsführer: Olaf Wagner | Sitz: Berlin
    Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194


    by Olaf Wagner - 09:51 - 18 Jan 2023
  • Re: booking of resources
    Hi, Hugues,

    You can expand current resource_booking for adding the concept of "quantity of a resource" for not having to declare each of them individually, and also add a resource type. Then, both can be added to the resource combination for not needing to declare such an amount of combinations. I think it's not so hard to plug both features into the current module and will prevent you from reinventing the wheel.

    Regards.

    by Pedro M. Baeza - 09:26 - 18 Jan 2023
  • booking of resources

    hello, dear contributors!

    one of our clients needs a solution for managing bookings of rooms in a building (for events like conferences, parties, etc.). they have several rooms that can be booked, and each booking can have options involving objects or people, like a video projector, waiters, tables, chairs, plates and cutlery,…

    some objects are identified individually (like video projectors), while others can be considered as always available in infinite quantity (like tables, chairs, plates and cutlery) and only the amount matters.

    bookings would be created manually (on the back-end side) by our client after communicating with their customers (by e-mail, telephone,…). for each booking, a sale order should be made, and the price should depend on the room, the duration and the chosen options. the bookings (and thus availability) of each room, person, and individually identified object (like a video projector) should be visible in a calendar, and booking conflicts must be avoided.

    do you have any advice on how to implement this without reinventing the wheel?

    we looked into the resource_booking module, which seems mostly great overall, but quickly faced a constraint: a resource.booking can only book one resource.booking.combination. a combination is a fixed list of resources, and combinations must be created manually. i’m not sure how it’s supposed to be used.

    if only one resource.booking is created for a customer booking, this means that the booking and all its options must be represented by one combination. for example, if there are 4 rooms, 3 video projectors and 5 people that can be combined freely, 96 combinations (including the “no video projector” and “no waiter” choice) must be created (and each of them must be added to at least one resource.booking.type to be selectable). moreover, the client would need to search through all of these to find the desired one. and what if there could be multiple waiters? this feels awkward. also, availability is only visible per combination, not per resource, so it is not very useful. however, it seems that availability conflicts are checked per resource, but in case of conflict, no information is given about which resource is not available.

    another option is to create one combination per resource, and create multiple resource.bookings (with the same date and the same partner) for one customer booking. this is more flexible, but there are no direct links between all of these bookings. what if the customer wants to change the date or cancel the booking?

    for billing, sale_resource_booking allows to link a product to a resource.booking.combination, so one product is needed for each combination. it also allows to generate a sale order from a resource booking type (so combination and dates must be selected afterwards), but i didn’t find a way to do it from a booking, which would be more useful.

    i understand why using combinations can be useful (as a compound for common use cases), and this is maybe a good technical decision (because it can avoid duplication), but i think that as they are, it seems that, in many cases, they get in the way instead of helping. am i maybe missing something obvious?

    here are some possibilities i’m currently considering:

    1. use one resource.booking per booking, but hide the combinations from the user (using a wizard, for example). the user would select all desired resources, and a matching combination would be used if one exists, or one would be created on the fly.
    2. use multiple resource.bookings per booking (one for each resource), create one combination per resource, and find a way to link resource.bookings together.
    3. extend resource.booking by allowing multiple combinations to be booked per booking (instead of only one), and create one combination per resource.
    4. extend resource.booking by allowing multiple resources to be booked directly per booking (instead of a combination), and don’t use combinations.

    for objects considered as always available, use a product, and extend resource.booking by allowing multiple products (with a quantity) to be linked to a booking, or simply add them directly to the generated sale order.

    i’m pretty sure that this resource booking use case is quite common, and having a generic solution that works for most cases would be useful. do you have any ideas about all this?

    cheers,

    hugues de keyzer
    coop it easy


    by hugues - 08:55 - 17 Jan 2023
  • Re: Proposing PSC l10n-thailand
    Thank you for the good news. I will try my best.

    On Tue, Jan 17, 2023 at 4:42 PM Kitti Upariphutthiphong <notifications@odoo-community.org> wrote:
    Thank you Simone :)

    On Tue, Jan 17, 2023 at 2:52 PM Simone Orsi <notifications@odoo-community.org> wrote:
    Hello,

    @Kitti that's fine ;)

    @Saran I added you you the PSC. You'll get an invitation as soon as the sync happens.

    Bests

    On Tue, Jan 17, 2023 at 6:49 AM Kitti Upariphutthiphong <notifications@odoo-community.org> wrote:
    Saran is the most active in the l10n-thailand for now also migrating from version to version.

    Definitely +1

    I understand that we don't have enough maintainers to justify the vote as it is a local repo. @Stéphane Bidoul may be we need your help?

    Thank you!


    On Wed, Jan 11, 2023 at 1:37 PM Tharathip Chaweewongphan <notifications@odoo-community.org> wrote:
    You have many contribute in l10n-thailand repository, I agree with you to PSC :)

    ในวันที่ พ. 11 ม.ค. 2023 เวลา 13:27 Saran Limpajitkutaporn <notifications@odoo-community.org> เขียนว่า:
    Hello everyone,

    I was one of the developers of l10n-thailand repository. I would like to propose myself as a PSC l10n-thailand for improving and migrating.

    My github account: Saran440 

    Thank you,
    Saran Lim.

    _______________________________________________
    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



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


    by saranl - 02:36 - 17 Jan 2023
  • Re: Proposing PSC l10n-thailand
    Thank you Simone :)

    On Tue, Jan 17, 2023 at 2:52 PM Simone Orsi <notifications@odoo-community.org> wrote:
    Hello,

    @Kitti that's fine ;)

    @Saran I added you you the PSC. You'll get an invitation as soon as the sync happens.

    Bests

    On Tue, Jan 17, 2023 at 6:49 AM Kitti Upariphutthiphong <notifications@odoo-community.org> wrote:
    Saran is the most active in the l10n-thailand for now also migrating from version to version.

    Definitely +1

    I understand that we don't have enough maintainers to justify the vote as it is a local repo. @Stéphane Bidoul may be we need your help?

    Thank you!


    On Wed, Jan 11, 2023 at 1:37 PM Tharathip Chaweewongphan <notifications@odoo-community.org> wrote:
    You have many contribute in l10n-thailand repository, I agree with you to PSC :)

    ในวันที่ พ. 11 ม.ค. 2023 เวลา 13:27 Saran Limpajitkutaporn <notifications@odoo-community.org> เขียนว่า:
    Hello everyone,

    I was one of the developers of l10n-thailand repository. I would like to propose myself as a PSC l10n-thailand for improving and migrating.

    My github account: Saran440 

    Thank you,
    Saran Lim.

    _______________________________________________
    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



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


    by Kitti Upariphutthiphong - 10:40 - 17 Jan 2023
  • Re: Proposing PSC l10n-thailand
    Hello,

    @Kitti that's fine ;)

    @Saran I added you you the PSC. You'll get an invitation as soon as the sync happens.

    Bests

    On Tue, Jan 17, 2023 at 6:49 AM Kitti Upariphutthiphong <notifications@odoo-community.org> wrote:
    Saran is the most active in the l10n-thailand for now also migrating from version to version.

    Definitely +1

    I understand that we don't have enough maintainers to justify the vote as it is a local repo. @Stéphane Bidoul may be we need your help?

    Thank you!


    On Wed, Jan 11, 2023 at 1:37 PM Tharathip Chaweewongphan <notifications@odoo-community.org> wrote:
    You have many contribute in l10n-thailand repository, I agree with you to PSC :)

    ในวันที่ พ. 11 ม.ค. 2023 เวลา 13:27 Saran Limpajitkutaporn <notifications@odoo-community.org> เขียนว่า:
    Hello everyone,

    I was one of the developers of l10n-thailand repository. I would like to propose myself as a PSC l10n-thailand for improving and migrating.

    My github account: Saran440 

    Thank you,
    Saran Lim.

    _______________________________________________
    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



    --
    Simone Orsi

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

    by Simone Orsi - 08:50 - 17 Jan 2023
  • Re: Proposing PSC l10n-thailand
    Saran is the most active in the l10n-thailand for now also migrating from version to version.

    Definitely +1

    I understand that we don't have enough maintainers to justify the vote as it is a local repo. @Stéphane Bidoul may be we need your help?

    Thank you!


    On Wed, Jan 11, 2023 at 1:37 PM Tharathip Chaweewongphan <notifications@odoo-community.org> wrote:
    You have many contribute in l10n-thailand repository, I agree with you to PSC :)

    ในวันที่ พ. 11 ม.ค. 2023 เวลา 13:27 Saran Limpajitkutaporn <notifications@odoo-community.org> เขียนว่า:
    Hello everyone,

    I was one of the developers of l10n-thailand repository. I would like to propose myself as a PSC l10n-thailand for improving and migrating.

    My github account: Saran440 

    Thank you,
    Saran Lim.

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

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


    by Kitti Upariphutthiphong - 06:46 - 17 Jan 2023
  • Re: OCA Module to visualize attachment in tree view
    The screenshot is not shown. It seems it's something from the Odoo mailing lists.

    There's no such module in OCA AFAIK.

    Regards.

    by Pedro M. Baeza - 05:31 - 13 Jan 2023
  • OCA Module to visualize attachment in tree view

    hi all,

    I'd like to have the possibility to display a column in a tree view with the number of attachment related to the item.

    something like that :

    Ideally, I'd like

    - to have the attachment quantity field stored to have the possibility to filter items with attachment(s)

    - to have a widget="attachment" to have the possibility to open quickly the attachment(s) with a minimal number of click.

    do you know if such feature exists in OCA ?

    Thanks !


    -- 
    Sylvain LE GAL
    - GRAP, service informatique
    - 3 Grande rue des Feuillants 69001 LYON, 09.72.32.33.17
    - Astreinte : 06.81.85.61.43 // informatique@grap.coop

    by Sylvain LE GAL - 05:25 - 13 Jan 2023
  • Re: Proposing PSC l10n-thailand
    You have many contribute in l10n-thailand repository, I agree with you to PSC :)

    ในวันที่ พ. 11 ม.ค. 2023 เวลา 13:27 Saran Limpajitkutaporn <notifications@odoo-community.org> เขียนว่า:
    Hello everyone,

    I was one of the developers of l10n-thailand repository. I would like to propose myself as a PSC l10n-thailand for improving and migrating.

    My github account: Saran440 

    Thank you,
    Saran Lim.

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


    by tharathipc - 07:36 - 11 Jan 2023
  • Proposing PSC l10n-thailand
    Hello everyone,

    I was one of the developers of l10n-thailand repository. I would like to propose myself as a PSC l10n-thailand for improving and migrating.

    My github account: Saran440 

    Thank you,
    Saran Lim.

    by saranl - 07:25 - 11 Jan 2023
  • Re: Packaging management repository
    product pack is not related.

    Here, it is packaging management for warehouse operations (the box you put products into). 'Put in pack' related operations.

    On Tue, Jan 10, 2023 at 10:31 AM Daniel Reis <notifications@odoo-community.org> wrote:
    There is also this:
    https://github.com/OCA/product-pack

    To assist contributors finding the right repo, they need a good README description stating their scope, and listing "neighbor" repos that are candidates for modules that are close but out of scope.

    Thanks
    Daniel

    On 10/01/23 08:37, Roussel, Denis wrote:
    Hi all,


    I'm questioning about a repository for packaging management as some have added great modules to enhance experience at that level but splitted in several repos (warehouse/workflow/wms)

    Currently, we inherited an historical repository which is under-used due to its weird naming 'stock-logistics-tracking'. As Odoo in early versions named Packages as 'stock.tracking' : https://github.com/odoo/odoo/blob/6.1/addons/stock/stock.py#L474

    I see several approaches but I wanted the advice of wise people:

    - Rename 'stock-logistics-tracking' repository into 'stock-logistics-packaging' (which is not as easy as it seems to be, I suppose).
    - Create the new repository
    - Keeping the old one, adding all the stuff to be clearer : better README, better repo description, ... (easiest one).


    Thanks for your feedback

    --

    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



    --

    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:36 - 10 Jan 2023
  • Re: Packaging management repository
    There is also this:
    https://github.com/OCA/product-pack

    To assist contributors finding the right repo, they need a good README description stating their scope, and listing "neighbor" repos that are candidates for modules that are close but out of scope.

    Thanks
    Daniel

    On 10/01/23 08:37, Roussel, Denis wrote:
    Hi all,


    I'm questioning about a repository for packaging management as some have added great modules to enhance experience at that level but splitted in several repos (warehouse/workflow/wms)

    Currently, we inherited an historical repository which is under-used due to its weird naming 'stock-logistics-tracking'. As Odoo in early versions named Packages as 'stock.tracking' : https://github.com/odoo/odoo/blob/6.1/addons/stock/stock.py#L474

    I see several approaches but I wanted the advice of wise people:

    - Rename 'stock-logistics-tracking' repository into 'stock-logistics-packaging' (which is not as easy as it seems to be, I suppose).
    - Create the new repository
    - Keeping the old one, adding all the stuff to be clearer : better README, better repo description, ... (easiest one).


    Thanks for your feedback

    --

    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


    by Daniel Reis - 10:30 - 10 Jan 2023