Contributors mailing list archives


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

- 28/08/2015 15:16:35
Hello all,

just a word to say this illustrate again the dead end of trying to manage several modules in the same branch. IMHO the only soultion is indeed one module = 1 repo and have eventually a list of official OCA semantic tags to classify the modules. There will always be border line modules, cross dependencies and whil we can probably overcome this specific issue, such issues will only arrise more and more often.

Also today, the OCA isn't yet really visible commercially speaking. That means people who take care of managing it such as PSC, have a growing burden, as number of modules and PR's grow with little incentive for it. I think it's important to keep a good balance and keep the OCA scope inside something doable. That is the OCA won't manage all Odoo modules of the world and this is very fine. I think this also means we should quickly establish a list of stable central modules for which a high level of security/burocracy is required and by opposition have a lot more flexible rules for maturing satellite modules for which there is not enough experienced active contributors anyway.

That being said kudos for the hard work again.

On Fri, Aug 28, 2015 at 10:23 AM, Maxime Chambreuil <> wrote:

Could you be more specific about what you would put in OCA/vertical-service ? Do you have modules today that would fit in there ?

I think PMI, as well as other PM methodologies (GTD, Agile, Scrum, etc) should be in OCA/project.

Maxime Chambreuil
+1 (514) 276-5468 #126

----- Le 27 Aoû 15, à 18:53, Daniel Reis <> a écrit :

<blockquote cite="" type="cite">
There are some people interested to contribute contract related modules. Where should they contribute those modules ?

We had (and still exists) an OCA/contract repo.
But it's content was not distinctive enough and it was merged into `OCA/project-service` (see
I still agree with that decision and think that Contract related features should go in an OCA/project repo.

<blockquote cite="" type="cite">
I think vertical-service is not specific enough. That's why we have vertical-isp, vertical-travel or vertical-hotel. A lot of companies in our economies provides services, but the type of services is very different and requires a different verticalizations to support their activities: legal (document management), accounting, payroll, IT, transportation (map view with GPS localization), accomodation (hotel), home services (fleet, route management and optimization).

Good point.
The service features are really about "service management", and the proposed name is probably too generic.
Service Management is not an industry, so I'm not sure if "vertical" is appropriate.

Some possibilities for a _new_ repo name and semantics could be:

- OCA/project-service (project modules specific to service management)
- OCA/vertical-service-management (solutions for service management companies, probably including other areas other than project, such as sales, invoicing, reporting, etc.)

With the isolation of Service Management features, does it make sense to include PMI Project Management modules in it's own repo, maybe vertical-projet-management? (PMI is not the only methodology for PM, so I advise against vertical-pmi)

Would these three separate repos be more helpful than a single one?


Post to:

Post to:

Raphaël Valyi
Founder and consultant
+55 21 3942-2434