Contributors mailing list archives

Browse archives


RE: Renaming OCA/project-service to OCA/vertical-service

Moduon Team, S. L., Rafael Blasco (Moduon)
- 01/09/2015 14:18:38
Hi all,

Even though this thread in solved and closed (+1 the solution) I had this 
e-mail in my draft and I would like to send you my point of view. As 
contributor I have doubts.

We (Antiun) work with our clients 99% core+OCA, and verticals we don't push 
to OCA, verticals remain private. Thanks of this methodology when we want to 
push in OCA we extract which common functionality will be useful for all 

This threat is about project-service but here I think we are really 
discussing (must be) about which is "the rules" for repos in OCA. This is 
not clear and that’s why all the time there are discussions about this.

- Remember "Split OCA website repository into website and website_sale ", 
the person who open this discussions was for sure because he doesn’t realize 
that e-commerce repo exits..
- Remember OCA opened Event, Survey for obviously purpose. If this happends 
I don't understand why something as important as projects, contract and 
services OCA is going to have a single repo.
- There are also discussions with OCA/Social as OCA/Marketing doesn't 
[solved] - If anyone wants to search for project modules, will search 
projects and no services. Vertical-services is ambiguous and confusing

- Where to put modules related with **membership** and contracts?