Community mailing list archives
Re: [Business] New OCA repository to suggestby
We have created xml tool in
Am 19. September 2014 16:29:57 schrieb Joël Grand-Guillaume <firstname.lastname@example.org>:
1) AgreedMy vote goes for:3) We should decide the name if the repo/project in case we only have one. I suggested connector-interface.2) We should decide if we want one repo / project per interface (so here one for connector-odbc and connector-file)Hi,
Thanks for your feed-back.@Raphaël: I agree on one connector = one project/repo. But this context is especially true for connector on a specific tools (like Magento, Sage, etc...). I wanted a place where to share modules around connecting with standard interfaces (like XML, .csv, ODBC,...). So my suggestion is about having only one project that:* Provide tools, hooks, libs, methods and base module to deal with external data inside odoo* Module in this repo/project must NOT be linked to a specific tools, but oriented on format / interface
* On a mid-term basis : merge modules to have a proper library based on the connector to handle such a problematic (like a layer to manage file, then another for .csv, another for .xml,...). That's my main reason to vote in favor of having all those module in one repo => easier to merge in the future.* Reduce the administrative workload (honestly, running the OCA for several months now show me/the board that this become important.)1) We should decide if we accept the creation of a project based on the connector framework only (no module will land here that doesn't use it, if you need it, please write a new thread to suggest your own new project).
So, if I summarize:2) Prefer to have only one project (easier to maintain, easier to merge / make synergy), but I can live with 23) AgreedThanks for your vote.
Joël_______________________________________________On Fri, Sep 19, 2014 at 3:59 PM, Raphaël Valyi <email@example.com> wrote:Sorry, typing to fast, I meant;"I personally think we should NOT gather these connectors under a single repo"On Fri, Sep 19, 2014 at 10:49 AM, Raphaël Valyi <firstname.lastname@example.org> wrote:Hello,I personally don't think we should not gather these connectors under a single repo. That will remain an exception when you want several of these connectors together in a single project.On the contrary, putting them in a single repo will create artificial additional repo dependencies tor the repo: some connectors will depend on sale modules, other on e-commerce modules, other on purchase modules, other on MRP modules...At the end of this logic we will end up with a single bloated repo depending on many repos. The contrary of what we want with a modular solution.So I think we would better go with 1 connector = 1 repo. I think the current lack of proper packaging of OpenERP modules led us to wisely group modules by functional area to avoid painful test-ability, installation and book keeping for the other existing modules. But with connectors, I don't see this logic working: they tend to be really different one from another, they also typically go with an operational cost related to data duplication and consequently you won't often use several connectors in the same project.Well at least this is my opinion.--On Fri, Sep 19, 2014 at 10:27 AM, Mignon, Laurent <email@example.com> wrote:Hi again,'connector-interfaces' sounds to me more generic (IMO, connector-import-export is a bit too long). But I don't remember if it was proposed during the discussion on the mailing list.lmiOn Fri, Sep 19, 2014 at 2:42 PM, Markus Schneider <firstname.lastname@example.org> wrote:Hi, we have a discussion on the connector mailing list about the "names" of this repositories. But we find no final conclusion because everyone has a different point of view. What i can summarize is: 1) The new repositories should be related to "connector" so modules without "connector" are need some other home. 2) From our point "connector-file" fells not right, because we have some modules where we export data, and send it at the end by email. My suggest is "connector-import-export" was the best option to have a repository for modules to import and export data with the connector framework without related to a special backend. Kind Regards Markus On 19.09.2014 10:53, Joël Grand-Guillaume wrote: > Dear community, > > > I want to suggest a new repository/project to include within the OCA > under the connector-maintainers team responsibilities. I would call it > "connector-interfaces". > > The purpose to this new project would be to host generic connector among > various interfaces to collect and updates data in Odoo. As example, I > already have 2 candidates modules: > > * connector_file : Which provide necessary tools and methods to deal > with the importation of huge files using the connector (see : > https://github.com/camptocamp/connector-file) > > * connector-odbc : Which provide necessary tools and method to access, > load and update data from an ODBC source (not publicly release yet, but > this is the purpose of this mail) > > I can see also in the future other connector among other interfaces : > EDI,... > > Do you agree on such a new project ? > > > Regards, > > > Joël > > > -- > > > *camptocamp* > INNOVATIVE SOLUTIONS > BY OPEN SOURCE EXPERTS > > *Joël Grand-Guillaume* > Division Manager > Business Solutions > > +41 21 619 10 28 > www.camptocamp.com > > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59> -- Dipl.-Comp.-Math. Markus Schneider Softwareentwickler initOS GmbH & Co. KG An der Eisenbahn 1 21224 Rosengarten Mobil: +49 (0)172 2303699 Phone: +49 (0)4105 5615613 Fax: +49 (0)4105 5615610 Email: email@example.com Web: http://www.initos.com Geschäftsführung: Dipl. Wirt.-Inf. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Haftende Gesellschafterin: initOS Verwaltungs GmbH Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRA 201840 USt-IdNr: DE 275698169 Steuer-Nr: 15/205/21402--
Business mailing list