Contributors mailing list archives


RE: New Repo Proposal - Vertical Health

Moduon Team, S. L., Rafael Blasco (Moduon)
- 06/12/2016 04:17:10

Hi Dave,

Sorry if I missed something and I repeat a question. What about (Open Source Health care system )?. It sounds quite similar



De: David Lasley []
Enviado el: lunes, 5 de diciembre de 2016 19:08
Para: Contributors <>
Asunto: Re: New Repo Proposal - Vertical Health


From this thread, I think the issue sounds like we are just having growing pains as more and more modules come under the OCA umbrella. I will start a separate thread in the next few days on this & we can keep this one scoped at where the nutritional modules should go.


I am firmly against including these modules in Vertical Medical for the reasons outlined previously regarding the current depth of the repo in the incubators.


It sounds like we have two options here:


1. We expand the definition of scope of partner-contact to include a more broad definition of attributes that can be added to partners.

2. We create a new repo for these modules, scoped at Health.


I am for #2.


— Dave Lasley


On Dec 4, 2016, at 1:52 AM, Daniel Reis <> wrote:


Repository organization should be guided by application area.
The most important thing about this grouping is to ensure focus from the maintainer team.

Nutrition-related modules form a group that should be kept together in the same repository.
They were being hosted at Partner-contact, but I don't thing they fit the purpose of that repo.
vertical-medical is the next best candidate, but medical features are a separate thing from nutrition.

Keeping the principle that we should keep repos as much focused as possible, I think it  would be best to have a separate repo for these features.



Citando Andi Becker <>:

The whole vertical organisation is more contraproductive than it really helps. Some modules i.e. need to be used in several verticals. On the otherhand you can't really find modules you need because they have no own repository. 


With gitup -c you could easily monitor which module really got updated and which is already compatible with v10. Instead you need now multiple manual steps because of verticals which are a repository with tons of submodules.


Each module in an own repository and those linked in vertical group lists would make things more transparent. 


Those linked repo lists could also be easier to be adjust to current versions. It really does make much sense that all oca repos look like they are version 10 and when you look inside some modules are not even working in 9. It is a great illusion causing frustration also with customers who check those and think they all have already been ported. 


Much better would be to have those linked list to each single module repo! 


On Dec 4, 2016, at 2:53 PM, robert rottermann <> wrote:



On 03/12/2016 23:37, Nhomar Hernandez [Vauxoo] wrote:

<blockquote cite="" type="cite">


On Sat, Dec 3, 2016 at 4:22 PM, David Lasley <> wrote:

Additionally, I have expanded Vertical Medical to more than 50 modules in my incubator. I’m having a serious organization problem right now as it is to be honest, and am trying to offload as much logic as possible.

I am not against more repositories, but even in the last months it has been better for me have less modules than more modules, the same for repositories (even if it is technically feasible administer a lot of repositories) in terms of design it is too difficult to respect in the meanwhile the separated design and we are being frequently lost in what already exists or not exist.

this is mostly an documentation and indexing problem.
<blockquote cite="" type="cite">


That's my 2 cents.

Nhomar Hernandez

CEO Vauxoo.

Twitter: @nhomar

Odoo Gold Partner

Skype: nhomar00 (Envia mail previo no lo superviso siempre).

Móvil Venezuela:
+58 4144110269

Móvil México:
+52 1 4773933942