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
Web-veistämö Oy/Avoin.Systems, Miku Laitinen.
- 14/08/2015 14:02:31
One argument for keeping modules in their own repos is that they can be used as git submodules. If all the modules are in the same repository, you have to 1. download all of them as a submodule, even if you need just one module, and 2. modify the odoo configuration file to include the directory as an addons path.

Also, you get only relevant issues and pull requests to your repository.

Miku Laitinen
AVOIN.SYSTEMS

On Fri, Aug 14, 2015 at 2:23 PM, <Mozetič@pad.odoo-community.org> wrote:
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).

On Fri, Aug 14, 2015 at 12:52 PM, Leonardo "LeartS" Donelli <learts92@gmail.com> wrote:
Hi all!
The OCA/website repository already contains 16 modules of which 4 are
actually ecommerce (website_sale) modules.
There are 22 PR for new modules, of which 6 are modules for the ecommerce.

Assuming all get merged, this would result in a repo with 38 modules.
By splitting the repo into OCA/website and OCA/website_sale, they
would have respectively 28 and 10 modules, which would make it simpler
to manage and to find the modules you're looking for.

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




--
Matjaž Mozetič, CEO
+386 41 745 131

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


Reference