1. Mailing Lists
  2. Contributors
  3. Re: Split OCA website repository into website and website_sale

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Split OCA website repository into website and website_sale

Re: Split OCA website repository into website and website_sale

Avatar

Re: Split OCA website repository into website and website_sale

by
Open Source Integrators, Maxime Chambreuil
- 14/08/2015 15:10:56
Matjaz,

Once upon a time, there was only one repository for all community modules: extra-addons.

The repository was more than 1Gb of space. It was a mess to download, to update, to manage and nobody really felt responsible to manage it.

By having ~100 repositories today, we give the opportunity for people to take in charge a smaller more-manageable part of the project. It is now easier to delegate to a group of people interested by the subject of a repo.

Technically, having one repo also means one level of quality/test coverage and today, we have projects with different level of maturity converging and improving at a different pace.

My few pros.
--
Maxime Chambreuil
+1 (514) 276-5468 #126

----- Le 14 Aoû 15, à 7:23, <"MozetiÄ�"@pad.odoo-community.org> a écrit :

What advantage does it give fragmenting the repositories so much? OCA repos are already way too fragmented for a server maintainer and while finding a module could seem easier in a less populated repo, we open another issue - finding the right repo. To do a simple update of the modules we have to navigate between exaggerated number of folders to perform repeatedly a simple git pull just to have all the repos updated. How is it simpler to manage that way?

Example: for a simple service company I would need at least: account-invoicing, hr, hr-timesheet, knowledge, management-system, partner-contact, project-service, sale-workflow, server-tools, web and website.

What's the point of this fragmentation? Finding a module? Crtl+F does the job by name in a single repo, grep -r does it by content... So why? X repos means X git pulls just to keep in sync (or git fetch+git rebase+git pull+git push for the forks)... to not even mention the translation teams nightmare that fragmented repositories represent - Transifex translation memory is not shared between projects and OCA will have (between 6.1, 7.0, 8.0 and in the close future 9) hundred of them by this pace.

I don't want to criticize, I just want to understand why (i started with the cons, give me the pros please).


Matjaž Mozetič, CEO
+386 41 745 131

Reference