Archives
Contributors
Re: Request for new repository sale-terms-conditions
Request Cancelled: oca/contract exists and is a suitable place. On 05/09/2019 10:21, Alexandre Fayolle wrote: > Hello Pedro, > > Not everything is related to delivery. We have other aspects related to > order preparation, order invoicing for instance. > > Regarding the naming proposition, I was first thinking of the repository > name (and should have used hyphens instead of underscores). However, > "Term & Condition" does not exist in english. This expression is always > using the plural form. In my opinion you should think of the final 's' > as part of the spelling, as in "logistics". In any case, I would really > like to avoid sale_term_multi_and_condition_multi ;-) > > Can we create a new repository sale-terms-conditions? > > Alexandre > > On 05/09/2019 01:12, Pedro M. Baeza (Tecnativa) wrote: >> 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. >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> Post to: mailto:contributors@odoo-community.org >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> > > -- Alexandre Fayolle Chef de Projet Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 11:36 - 5 Sep 2019
Reference
-
Service definition modules
Hello all, In relation with the WMS modules Camptocamp is currently working on, I'm working on a set of modules to manage service definition. The idea is to be able to store a set of service levels agreed on with the customer, with a number of parameters which are specified, and have default values, but can be customized for a given customer, or a given sale order. Typically the parameters could be: * management of backorders * days of delivery * hour of delivery * invoicing per order (with order reference) or invoicing per delivey * packaging details in the invoice * product grouping preference (e.g. a customer could ask for an order of 10 product1, 10 product2, 10 product3 to be packages in 10 parcels containing each 1 product1, 1 product2, 1 product3 instead of 3 packages containing a singe product reference) * constraints on the delivery truck (max dimension, max weight)... The basic set of user stories is available in https://github.com/OCA/stock-logistics-warehouse/issues/694 (this issue will be moved to a better place once we've answerd the question below) I'm planning to build this as a base module providing the models required to define the service definitions, and set this on a customer and on a sale order (+ propagation to invoices and deliveries), + different smaller modules related to the different aspects (deliveries, packaging, invoicing...) I would like to propose these as alpha modules in the OCA but I'm unsure what repository to target: * option 1: new repository oca/sale-service-definition, all the addons go there * option 2: in repository oca/sale-workflow, at least for the base module, but then I'm not comfortable in adding cross repository dependencies, because some of the other modules would probably live in the WMS repository, others in sale-workflow, others in some maybe in stock-logistics-* * option 3: in repository oca/contract because this is related to sale contract, but I'd like to avoid polluting a self contained module with lots of cross dependencies * elsewhere ? Dear contributors, what would be the best course of action in your opinion? -- Alexandre Fayolle Chef de Projet Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 10:46 - 4 Sep 2019