Hi Jacopo, Like I said in my earlier posting: I am a proponent of any kind of integration solution that will drive adoption by both user and contributor. I regard this as as such. Yet I can't bypass the heated comments made by some about what goes in and what not in the feature set supported by this project, even though I at times do not agree with those statements. And yes, this is a concern that touches us all, and impacts the future of the project. Some more effort to build consensus (by more than just a few contributors) for a mid term strategy should be in order. And I agree, though this is a proving ground, it is as bigger/more encompassing and separate issue.
Apart from that, might I suggest another approach: in stead of committing the solution straight away into the special purpose stack, why don't you create the umbrella issue and attach the patch to it so that people can test drive it, create the necessary tasks for completion of the OFbiz solution (think descriptive documents as per OFBIZ-5838 <https://issues.apache.org/jira/browse/OFBIZ-5838>, including implementation guidelines, etc) and when it passes the RTC process (within a limited time frame - e.g. 3 or 6 months) and gathers sufficient JIRA votes commit it to the stack as an optional (meaning include in trunk/future branches/releases without referencing it in the build.xml of the stack). That way we enable due diligence/due process regarding inclusion into the OFBiz product and provide users with a choice. What do you think? Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Tue, Mar 10, 2015 at 7:04 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > Hi Pierre, > > please see inline: > > On Feb 27, 2015, at 12:30 PM, Pierre Smits <pierre.sm...@gmail.com> wrote: > > > Jacopo, All, > > > > I am a proponent of any kind of OFBiz integration solution that will > > enhance the feature set and drives the adoption. It is good to see that > > people are willing to put the effort in, as we see (and have seen) with > > components (like BIRT, PoS) and other attempts (Asterisk integration, > > Jackrabbit, etc) and solutions (Magnolia/CATO, BigFish). > > > > However, I remember a discussion thread not long ago where strong > opinions > > were voiced about not having more under the umbrella of the Apache OFBiz > > project. > > In my opinion this is a separate (but interesting/important) topic that > should not interfere with this proposal; that discussion could go on for > months but the current situation is that in the OFBiz trunk we have > additional (specialpurpose) components and until we have them then we can > also consider the adoption of new ones (if valuable); if and when we will > decide to move all the components to another place (another trunk or an > external repository etc...) then we will move all (or most) of them > including new ones. > > > > > It seems to me that we should discuss strategy, process and risks first, > > before we discuss integration of anything into the project. Otherwise we > > will be having the same discussion over and over with each integration > idea > > that pops up. > > We will never come up with a general rule for inclusion/exclusion and we > will have to take a decision on a case by case basis considering different > factors including: code quality, interest by the community, committers > available to help, etc... > The important topic, in my opinion, for this thread is figuring out if > such a component may be interesting to end user companies (but for them we > will have to look into Magento forums) or to service providers with > customers in the OFBiz and Magento space. > > Regards, > > Jacopo > > > > > Best regards, > > > > Pierre Smits > > > > *ORRTIZ.COM <http://www.orrtiz.com>* > > Services & Solutions for Cloud- > > Based Manufacturing, Professional > > Services and Retail & Trade > > http://www.orrtiz.com > > > > On Fri, Feb 27, 2015 at 9:17 AM, Jacopo Cappellato < > > jacopo.cappell...@hotwaxsystems.com> wrote: > > > >> Hi all, > >> > >> in the last year, the research and development lab of HotWax Systems has > >> implemented a series of components and tools for OFBiz. > >> Some of them are ready-to-be-used applications and, in my opinion, would > >> be a good fit for OFBiz. > >> > >> After discussing the topic internally, we believe that the community > could > >> benefit from them and at the same time help to further improve them. > >> > >> Accordingly, I would like to start by exploring with you the opportunity > >> to include in OFBiz our integration with Magento eCommerce platform. > >> > >> Magento eCommerce (http://magento.com/products/overview) is a popular > >> solution for merchants; it is an open source product (but the company is > >> owned by eBay). > >> In terms of features it competes with the OFBiz ecommerce component, but > >> it is easier to setup and with a shorter go to market. > >> For these reasons it is a good fit for small-medium merchants that need > an > >> ecommerce store with no backend capabilities and it has a very large > users > >> base. > >> > >> We realized that there could be a rather large group of merchants, > already > >> using Magento for online sales, that may be interested in integrating it > >> with a powerful ERP system for the backend tasks (order fulfillment, > >> accounting etc...). > >> > >> The integration component we have implemented has a nice user interface > to > >> import categories, products, orders from Magento eCommerce and then > synch > >> held/cancelled orders; there are screens to manage shipment options and > >> product store settings. > >> > >> You can find some screenshot here: > >> http://people.apache.org/~jacopoc/magento-integration-2.png > >> http://people.apache.org/~jacopoc/magento-integration-3.png > >> http://people.apache.org/~jacopoc/magento-integration-4.png > >> http://people.apache.org/~jacopoc/magento-integration-5.png > >> > >> Arun Patidar led the effort and is happy to provide additional details > so > >> please feel free to ask any questions. > >> > >> In my opinion this product could be integrated as a specialpurpose > >> component, but I am open to suggestions. > >> > >> What do you think? > >> > >> Jacopo > >
