Skip to Content

Contributors

  • Re: V14, python version
    > Yes, Doodba is prepared for production, staging and development environments. Other Docker based solutions are also intended for production deployments.
    Great! Thanks for the great communication. 

    Regards

    by Syed Kamran Ali - 11:36 - 15 Oct 2020
  • Re: V14, python version
    > One silly question though, do you recommend docker solutions specifically Doodba for production?

    Yes, Doodba is prepared for production, staging and development environments. Other Docker based solutions are also intended for production deployments.

    Regards.

    by Pedro M. Baeza - 10:21 - 15 Oct 2020
  • Re: V14, python version
    Jairo, I'm afraid not: they are parallel meanwhile you have free slots, which for a free account, it's only 3 slots, so doubling/tripling the number of builds will even provoke than one CI status to not be completed in one shot.

    Regards.

    by Pedro M. Baeza - 10:16 - 15 Oct 2020
  • Re: V14, python version
    Thanks for sharing such a complex case. It is an eye opener...

    One silly question though, do you recommend docker solutions specifically Doodba for production? 


    Regards


    On Wed, 14 Oct 2020 at 9:27 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
    You can face the same problem we had in https://github.com/odoo/odoo/pull/50861, that led us to incorrect patches trying desperate to find a solution and to have deployments not correct meanwhile. The main problem is that this is not even detected by CIs. This doesn't happen very frequently, but as said, if you don't test it in a huge playground base, you will be on your own in the battle.

    I recommend you anyway to not install directly over the system, but use a middle layer like Docker. There are several solutions based on Docker, like ours called Doodba (advertise moment, hehe - although it's free and open source, so no real advertisement).

    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 Syed Kamran Ali - 10:16 - 15 Oct 2020
  • Re: V14, python version
    Just to clarify one little point:

    El mié., 14 oct. 2020 a las 20:56, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:
    The only possibility is to define several builds in the .travis.yml, each one with a Python version, which will double/triple the test time.

    Technically builds would be parallel, so they should last mostly the same amount of time.

    by Jairo Llopis - 10:10 - 15 Oct 2020
  • Re: Migration to v14 requirement - readony / invisible
    Uhm, you are right...  The source was from https://github.com/OCA/odoo-module-migrator/issues/32

    by Pedro M. Baeza - 09:01 - 15 Oct 2020
  • Re: Migration to v14 requirement - readony / invisible

    Is that a future deprecation?

    Odoo code still references attributes in this way:

    :                     <field invisible="context.get('no_mapping',False)"

    From account_consolidation, for example?

    Also, basic_model.js:

        _evalModifiers: function (element, modifiers) {
            let evalContext = null;
            const evaluated = {};
            for (const k of ['invisible', 'column_invisible', 'readonly', 'required']) {
                const mod = modifiers[k];
                if (mod === undefined || mod === false || mod === true) {
                    if (k in modifiers) {
                        evaluated[k] = !!mod;
                    }
                    continue;
                }
                try {
                    evalContext = evalContext || this._getEvalContext(element);
                    evaluated[k] = new Domain(mod, evalContext).compute(evalContext);
                } catch (e) {
                    throw new Error(_.str.sprintf('for modifier "%s": %s', k, e.message));
                }
            }
            return evaluated;
        },




    Richard deMeester

    Senior Development Analyst

    WilldooIT Pty Ltd

    E: richard.demeester@willdooit.com

    M: +61 403 76 76 76

    P: +61 3 9135 1900

    A: 10/435 Williamstown Road, Port Melbourne, Vic 3207

     

     

    Making growth through technology easy

     

     

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.



    From: Daniel Reis <dreis@opensourceintegrators.com>
    Sent: Thursday, 15 October 2020 5:12 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Migration to v14 requirement - readony / invisible
     
    Got it. I edited it for clarity.
    
    Thanks!
    
    On 14/10/2020 16:42, Pedro M. Baeza (Tecnativa) wrote:
    
    > Hi, sorry I meant to say invisible="<condition>". invisible="1" or 
    
    > invisible="0" is still supported. What it's not supported is to put an 
    
    > expression there, like `invisible=context.get("x")`
    
    >
    
    > Regards.
    
    >
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    > <https://odoo-community.org/groups/contributors-15>
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    > <https://odoo-community.org/groups?unsubscribe>
    
    >
    
    

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


    by Richard deMeester <richard.demeester@willdooit.com> - 01:46 - 15 Oct 2020
  • Re: V14, python version
    You can face the same problem we had in https://github.com/odoo/odoo/pull/50861, that led us to incorrect patches trying desperate to find a solution and to have deployments not correct meanwhile. The main problem is that this is not even detected by CIs. This doesn't happen very frequently, but as said, if you don't test it in a huge playground base, you will be on your own in the battle.

    I recommend you anyway to not install directly over the system, but use a middle layer like Docker. There are several solutions based on Docker, like ours called Doodba (advertise moment, hehe - although it's free and open source, so no real advertisement).

    Regards.

    by Pedro M. Baeza - 10:26 - 14 Oct 2020
  • Re: V14, python version
    Do you see any potential/known risks for deploying V14 on Ubuntu20 which has Python 3.8 as default version?

    On Wed, Oct 14, 2020 at 8:42 PM David Beal <david.beal@akretion.com> wrote:
    That's your preference that cover your workflow and odoo workflow
     
    Yes, Jean-Charles, that's why I prefer to stick in my deployments to the oldest supported Python version

    No problem with that.
    Another legitim workflow can be to use 3.8. In this case the only important thing is to have periodic feedback on potential regressions.

    For that, no need to have complete tests for each commit in every branch, we could only execute tests on this version every week.
    I don't know if it's easy to plan such tests based on cron, but if yes it could be a valid way to support several versions efficiently.

    What do you think?

    Thanks

    Regards


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


    Le mer. 14 oct. 2020 à 14:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    Yes, Jean-Charles, that's why I prefer to stick in my deployments to the oldest supported Python version, or being more specific, the version that Odoo has in its runbot and Odoo.sh infrastructure (that right now is Python 3.6), as that's the one battle-tested enough for all the rough edges that can happen. It's not only that Odoo launches without initial error...

    About the availability of any Python version in any system, that's not strictly true unless you go to a heavier virtualization layer as Docker, as some Python libraries won't compile.

    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


    by Syed Kamran Ali - 10:11 - 14 Oct 2020
  • Re: V14, python version
    I honestly don't see the feasibility of such a thing with current architecture. The only possibility is to define several builds in the .travis.yml, each one with a Python version, which will double/triple the test time.

    Regards.

    by Pedro M. Baeza - 09:56 - 14 Oct 2020
  • Re: V14, python version
    That's your preference that cover your workflow and odoo workflow
     
    Yes, Jean-Charles, that's why I prefer to stick in my deployments to the oldest supported Python version

    No problem with that.
    Another legitim workflow can be to use 3.8. In this case the only important thing is to have periodic feedback on potential regressions.

    For that, no need to have complete tests for each commit in every branch, we could only execute tests on this version every week.
    I don't know if it's easy to plan such tests based on cron, but if yes it could be a valid way to support several versions efficiently.

    What do you think?

    Thanks

    Regards


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


    Le mer. 14 oct. 2020 à 14:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    Yes, Jean-Charles, that's why I prefer to stick in my deployments to the oldest supported Python version, or being more specific, the version that Odoo has in its runbot and Odoo.sh infrastructure (that right now is Python 3.6), as that's the one battle-tested enough for all the rough edges that can happen. It's not only that Odoo launches without initial error...

    About the availability of any Python version in any system, that's not strictly true unless you go to a heavier virtualization layer as Docker, as some Python libraries won't compile.

    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 David BEAL - 09:40 - 14 Oct 2020
  • Re: Migration to v14 requirement - readony / invisible
    Got it. I edited it for clarity.
    
    Thanks!
    
    On 14/10/2020 16:42, Pedro M. Baeza (Tecnativa) wrote:
    
    > Hi, sorry I meant to say invisible="<condition>". invisible="1" or 
    
    > invisible="0" is still supported. What it's not supported is to put an 
    
    > expression there, like `invisible=context.get("x")`
    
    >
    
    > Regards.
    
    >
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    > <https://odoo-community.org/groups/contributors-15>
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    > <https://odoo-community.org/groups?unsubscribe>
    
    >
    
    

    by Daniel Reis - 08:11 - 14 Oct 2020
  • Re: Migration to v14 requirement - readony / invisible
    Hi, sorry I meant to say invisible="<condition>". invisible="1" or invisible="0" is still supported. What it's not supported is to put an expression there, like `invisible=context.get("x")`

    Regards.

    by Pedro M. Baeza - 05:40 - 14 Oct 2020
  • Re: New PMS Proposal
    Hi Jay, the current vertical-hotel repository is incompatible with the development of this pms, and although when we started working on this project, two years ago, we tried to do it with the current vertical hotel (of those not yet in OCA), we had to start from zero for not being able to make this development compatible with the structure and flows that we have been learning in the sector (for example, to connect it with sales channels such as booking.com, expedia, etc ...). 
    Mainly, our pms create new models for reservations and folios, while vertical-hotel create folio with delegated model from sale.order, create new model pms.property instead of use warehouses... etc. This is a important difference with consequences in all areas of management and integration (OTAs syncr, invoicing, sales management revenue, etc...), becouse, we need manage the unit price by night with date, not by unit.
    I think it would be convenient to keep both perspectives independent to see their evolution and, in any case, study the possible integration in the future (although I can anticipate that with the importants differences that exist, it would be difficult to automate the migration from a database with vertical-hotel to the pms, and vice versa. 
    Thanks!

    El mié., 14 oct. 2020 14:07, Jay Vora <vora.jay@serpentcs.com> escribió:
    Guys,
    Isn't it going to extend Vertical Hotel?
    Thanks,

    On Wed, Oct 14, 2020 at 4:31 PM Darío Lodeiros <dariodafoz@gmail.com> wrote:
    The PSC:
     - Darío lodeiros (dario@commistun.com), Helpdesk PSC member (https://github.com/dariolodeiros)
     - Eric Antones (eantones@nuobit.com) Community active member (https://github.com/eantones)

    El mié., 14 oct. 2020 a las 12:46, Stéphane Bidoul (<stephane.bidoul@acsone.eu>) escribió:
    We'll need to know PSC information.

    Will this be managed by an existing PSC ?
    Is it a new PSC ? If yes, who will be the PSC representative and first members ?

    -sbi


    On Wed, Oct 7, 2020 at 3:07 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    +1

    On Wed, 7 Oct 2020, 18:42 Roussel, Denis, <denis.roussel@acsone.eu> wrote:
    +1

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

    Hi!

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

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

    The work for December includes:

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


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

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

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

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

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



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

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



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | 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

    _______________________________________________
    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



    --

    Technology Services @ www.serpentcs.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


     
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com

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


    by dariodafoz - 03:11 - 14 Oct 2020
  • Re: V14, python version
    Yes, Jean-Charles, that's why I prefer to stick in my deployments to the oldest supported Python version, or being more specific, the version that Odoo has in its runbot and Odoo.sh infrastructure (that right now is Python 3.6), as that's the one battle-tested enough for all the rough edges that can happen. It's not only that Odoo launches without initial error...

    About the availability of any Python version in any system, that's not strictly true unless you go to a heavier virtualization layer as Docker, as some Python libraries won't compile.

    Regards.

    by Pedro M. Baeza - 02:36 - 14 Oct 2020
  • Re: V14, python version
    Odoo claims to keep compatibility with the latest version of python, yet it does not always have time to react in time as witnessed here: https://github.com/odoo/odoo/issues/59456#issuecomment-705433473.
    Therefore, it seems necessary to be able to freeze the python version (with 3 digits).
    I believe that all python versions (including the 2.7.*) can be available on any version of any distribution (even on oOSx) through python-virtualenv


    by Jean-Charles Drubay - 02:26 - 14 Oct 2020
  • Re: New PMS Proposal
    Guys,
    Isn't it going to extend Vertical Hotel?
    Thanks,

    On Wed, Oct 14, 2020 at 4:31 PM Darío Lodeiros <dariodafoz@gmail.com> wrote:
    The PSC:
     - Darío lodeiros (dario@commistun.com), Helpdesk PSC member (https://github.com/dariolodeiros)
     - Eric Antones (eantones@nuobit.com) Community active member (https://github.com/eantones)

    El mié., 14 oct. 2020 a las 12:46, Stéphane Bidoul (<stephane.bidoul@acsone.eu>) escribió:
    We'll need to know PSC information.

    Will this be managed by an existing PSC ?
    Is it a new PSC ? If yes, who will be the PSC representative and first members ?

    -sbi


    On Wed, Oct 7, 2020 at 3:07 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    +1

    On Wed, 7 Oct 2020, 18:42 Roussel, Denis, <denis.roussel@acsone.eu> wrote:
    +1

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

    Hi!

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

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

    The work for December includes:

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


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

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

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

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

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



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

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



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | 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

    _______________________________________________
    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



    --

    Technology Services @ www.serpentcs.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


     
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com


    by Jay Vora - 02:06 - 14 Oct 2020
  • Re: 14.0 branches
    Am 13.10.20 um 10:57 schrieb Daniel Reis:
    I believe the external_dependencies manifest key supports pinned versions.
    
    
    On 13/10/2020 08:36, Pedro M. Baeza (Tecnativa) wrote:
    
    > Stéphane, how to pin specific Python libraries versions in this 
    
    > workflow in the generated requirements.txt? We have several places 
    
    > with this requirement.
    
    
    The version pinnings it self, could be defined in a constraints.txt, so that it is separated from the packag names:
    https://pip.pypa.io/en/stable/user_guide/#constraints-files

    one could install this as follow:

    pip install -r requirements.txt -c constraints.txt

    -- 
    cheers
    Maik Derstappen
    
    
    derico - web development & consulting
    >> Python - Plone - Odoo - Pyramid - Django
    
    

    by md-lists - 01:45 - 14 Oct 2020
  • Re: V14, python version
    The same as Odoo keeps compatibility through all that versions, OCA should keep the same IMO. We can't go to the latest version, as we are forcing all the sysadmins to go to the latest distributions that have such Python version, and that is the same not feasible as the potential problems you expose, David.

    Regards.

    by Pedro M. Baeza - 01:01 - 14 Oct 2020
  • Re: New PMS Proposal
    The PSC:
     - Darío lodeiros (dario@commistun.com), Helpdesk PSC member (https://github.com/dariolodeiros)
     - Eric Antones (eantones@nuobit.com) Community active member (https://github.com/eantones)

    El mié., 14 oct. 2020 a las 12:46, Stéphane Bidoul (<stephane.bidoul@acsone.eu>) escribió:
    We'll need to know PSC information.

    Will this be managed by an existing PSC ?
    Is it a new PSC ? If yes, who will be the PSC representative and first members ?

    -sbi


    On Wed, Oct 7, 2020 at 3:07 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    +1

    On Wed, 7 Oct 2020, 18:42 Roussel, Denis, <denis.roussel@acsone.eu> wrote:
    +1

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

    Hi!

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

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

    The work for December includes:

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


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

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

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

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

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



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

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



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | 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

    _______________________________________________
    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 dariodafoz - 01:01 - 14 Oct 2020