1. Mailing Lists
  2. Contributors
  3. Re: One module one repo

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Repo Metadata

Re: New Repository Payroll

Avatar

Re: One module one repo

by
dar
- 28/06/2019 13:30:35
Hi, an update on this one.

I just relesaed odooup version 0.0.9 which solves the deployment issues in the BEST possible way.
We're left with the more fundamental organisational problem of mixing oranges and apples in one's interpretation while think "all the same" in another's interpretation.

v0.0.9  was realized thanks to Sirum GMBH: a great place to work in Hamburg Speicherstadt for Odooers.

New features:
- sparse-checkout + dockerignore module white listing
- dependency analyzer + validator

Best Regards,
Euer David

On Fri, Jun 21, 2019 at 7:41 PM David Arnold <dar@xoe.solutions> wrote:
Hi All,

Thanks for the great feedback.
It looks like we are getting somewhere near substance. ;-)

Finding the right scope seems to be an eternal topic...
For thought: "All modules in a repo should cycle their version in sync. This verison should be exposed as git tags."

I still ow you consolidating the feedback, which I'll try to deliver on this weekend.
Thanks for helping pushing this topic forward.

I'm very interested in produce insights through good discussions which can bring us (me, you, everyone) further.

Best Regards,
David A.

On Thu, Jun 20, 2019 at 7:42 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Regarding translations, Martin Trigaux is working on hosting translations outside of the main Odoo repo (for a future Odoo version).

When that work we'll proably use it for OCA too.

-sbi

On Thu, Jun 20, 2019 at 2:17 PM Graeme Gellatly <gdgellatly@gmail.com> wrote:
A long time ago I used to agitate for 1 module per repo, I even did it for my own stuff and quit pretty fast. Disaggregation/aggregation at build time is far easier than at dev time. 

A little off topic, a split I'd like to see / always wondered about (and in core as well) is a separation of translations from code. It clouds commit history and last time I checked made up ~80% of the size of Odoo codebase  (which admittedly was v7, 267mb with just en_us vs 1.2gb). Also, and I'm guessing here, I imagine translators aren't so much topic repo focused. I don't know how practical it is or how it might work, but it would have a far greater effect on build sizes than 1 module per repo.

Also off topic, but I wouldn't mind starting to see more of an Apps approach. Not for everything, but I feel certain repos lend themselves to this. I kind of did it a little bit recently in account-financial-reporting repo although the reasoning there was more to do with deduplication of effort. For example - mis_builder. Have mis_app with a config screen with the option to include budget. Or web repo, so much good stuff there but all little modules doing one thing each, a Web Interface app with a bunch of options. Or server-tools.



On Thu, Jun 20, 2019 at 10:37 AM Nhomar Hernández <nhomar@vauxoo.com> wrote:


On Wed, Jun 19, 2019 at 5:27 PM Rafael Blasco <rafael.blasco@tecnativa.com> wrote:

Hello,

 

In my functional side

 

“functional consistency”

 

Totally agree with you Stéphane.

 

We didn’t have any issues working with one repo multiples modules in 6 years.


I have 10 years doing it on this way, and even now I try to use as less branches/repos as possible.

BTW, imagine for ones second 1 repo 1 module will become Odoo maintainance as complex as maintain an **apt** repository..

IMHO innecesary overload.

REgards.

 

Regards,

Rafael

 

 

De: Stéphane Bidoul [mailto:stephane.bidoul@acsone.eu]
Enviado el: miércoles, 19 de junio de 2019 18:43
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: One module one repo

 

My current point of view is that one module one repo is totally impractical indeed.

 

The reasons are:

- infrastructure maintenance and scalability as Pedro mentioned

- also very important is that the repos must be designed around a mix of functional consistency and willingness of a team and PSC representative to maintain their content

 

Deployment considerations are irrelevant to the design the repo structure IMO.

 

Best regards,

 

-sbi

 

On Wed, Jun 19, 2019 at 5:32 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:

This simply can't be done due to OCA infrastructure, with runbot, Travis, Weblate, etc and all the maintenance burden they bring.

 

Regards.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--

--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269 (Telegram)
Móvil México:
+52 1 4773933942 (Whatsapp)

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Reference