Contributors mailing list archives
Re: One module one repoby
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 <firstname.lastname@example.org> wrote:On Wed, Jun 19, 2019 at 5:27 PM Rafael Blasco <email@example.com> wrote:
In my functional side
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.
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.
On Wed, Jun 19, 2019 at 5:32 PM Pedro M. Baeza (Tecnativa) <firstname.lastname@example.org> wrote:
This simply can't be done due to OCA infrastructure, with runbot, Travis, Weblate, etc and all the maintenance burden they bring.
Post to: mailto:email@example.com
----Nhomar HernandezCEO Vauxoo.Site: http://vauxoo.comTwitter: @nhomarBlog: http://nhomar.comGithub User: https://github.com/nhomarOdoo Gold PartnerSkype: nhomar00 (Envia mail previo no lo superviso siempre).HangOut: firstname.lastname@example.orgMóvil Venezuela:
+58 4144110269 (Telegram)Móvil México:
+52 1 4773933942 (Whatsapp)