Contributors mailing list archives
Re: Service definition modulesby
Open for Small Business, Graeme Gellatly
I'm with David. contract is the right repo, if not a new repo called sale_contract. Terms and conditions form part of the contract with the customer, so it is most appropriate name. Indeed they are often called contractual terms.
On Thu, Sep 5, 2019 at 7:52 PM David Beal <firstname.lastname@example.org> wrote:
Hi Alexandre,If I understand the purpose, sale term condition, it's the exact scope ofalso existing in v10 with agreement_sale and agreement_accountThe objective here is just to have a minimal object, agnostic and versatile objectagreement means : "commercial term conditions" exactly (with your customers and suppliers)Maxime based its work about legal_agreement on top of itThen I propose than you build your modules on top of these, adding your needs on this simple objectEDI repo (and other dependencies) made by Alexis de Lattre use agreement.If you build another base object, then customer who want to use both will have redondant data !If you want move agrement_sale to another repo, it's not a problem for me.my 2 cts
David BEAL - akretion.comChef de projetOdoo Développement / IntégrationLe jeu. 5 sept. 2019 à 01:12, Pedro M. Baeza (Tecnativa) <email@example.com> a écrit :Please don't use plurals in the module name for following guidelines. Take also into account https://github.com/OCA/delivery-carrier/tree/11.0/partner_delivery_schedule that already allows to set delivery slots for partners, which is one of the concepts you are defining. If everything is related to delivery, I would put modules in OCA/delivery-carrier.Regards.