Contributors mailing list archives

contributors@odoo-community.org

Avatar

Re: Service definition modules

by
Camptocamp SA, Joël Grand Guillaume
- 05/09/2019 07:48:50

But the sets of modules we're talking about is more about defining parameters on terms, that can be customized at customer level. So it is more a generic way to deal with terms and parameters linked to customer orders.

Then each of those parameter will probably call some features (distributed across several area: deliveries, invoicing, etc..)

So we're looking to where we should push those set of modules (for the parameters as described here https://github.com/OCA/stock-logistics-warehouse/issues/694).

Can we vote ?

1) include in delivery
2) Include in sale-workflow
3) include in contract
4) or agreed for a new repo sale-term-condition

I vote for 4) as it is not only linked to deliveries or sales nor contract (in the meaning of the current set of modules that mostly deal with contract with customers, not really on the definition of services.

Regards,

Joël


On Thu, Sep 5, 2019 at 1:12 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> 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



--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28


Reference