Re: Discussion: Replace framework by Moqui.

[Michael Brohl]

I totally agree with your opinion about the license. The licensing is a strong and often very important point for using (or not using) a framework like OFBiz for building a company's software landscape.

Regards,

Michael Brohl
ecomify GmbH
www.ecomify.de


Am 21.05.15 um 15:28 schrieb Ron Wheeler:

From my experience with a lot of different customers using or evaluating OFBiz the liberal Apache License is a non-technical key argument for choosing it. Most customers build an important part of their business on OFBiz, for example nearly all of the eCommerce/portal users. Licensing risks, long term support by the community, overall costs etc. are thoroughly evaluated. As a consultant, I won't advise my customers to use a framework with unclear licensing or uncertain community. I think Moqui is well worth a thoroughly evaluation and even if I had not the time to take a deeper look at it, I assume that it would be an improvement. But the licensing issue has to be solved to make it a considerable option.

I am not a lawyer and Apache's legal team should be approached before we embark on a plan that involves the use of a third party tool that does not have an Apache license or a license that is known to be compatible with inclusion in an Apache product.

Ron


On 21/05/2015 4:49 AM, Scott Gray wrote:

At the moment, from my reading of the source that Jacques found, it would not be possible to release a Moqui-based framework under an Apache license. Moqui is in a no-man's land where your right to use it depends on what country you are in and unless you are the owner, it is not clear how your can redistribute it internationally. If we write a layer to go between Moqui and the OFBiz components to replace the framework, users would have to decide if they could legally run Moqui and would have to go get it on their own and install it separately. For the moment my preference would be to focus on getting the current framework into a separate sub-project, clean up the current dependency issues, document it and release it as a separate deliverable with an Apache license and its own roadmap and "marketing" plan. That is based on assertions from knowledgeable people in this project that it is valuable on its own for others who want to develop other sorts of business applications. Even if Moqui is a better framework technically, the Apache license would make the Apache OFBiz Framework a more desirable product for an organization wanting to invest in creating an application.

Advance cast of -1 in case I miss the vote if it ever comes.


Moqui" is to rewrite the apps to be moqui apps.  If that was done, what

for Moqui and become application curators and essentially be a different
project.  But what's the point of doing that here rather than over at
moqui? (wherever "at moqui" is)


hybrid into OFBiz until we can phase out the OFBiz framework completely.

apps.

Regards
Scott

On 27 April 2015 at 02:11, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

Moqui is it's own eco-system. The only way to "replace the framework with does it have to do with OFBiz@Apache? We could rename the project to Apps The work I think Adrian is suggesting is introducing Moqui as some sort of To me that seems like a convoluted way to go instead of just rewriting the

On Apr 26, 2015, at 3:09 PM, Adrian Crum <
adrian.c...@sandglass-software.com> wrote:

How about "Replace framework core functionality - like entity engine,

service engine, and security with Moqui."

Is that specific enough?

Not really: we have talked about bringing the whole Moqui codebase into

Moqui, or reimplementing them and the sentence above doesn't specify a
direction.
And why entity engine, service and security and not for example


Jacopo

the OFBiz trunk (bad idea in my opinion), or migrating the applications to transaction management, connection pooling, ui technology, logging etc...?

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 4/26/2015 1:47 PM, Jacopo Cappellato wrote:

The discussion is interesting and fascinating but in this thread

completely different ideas have been expressed: from forking Moqui into

OFBiz to rewriting OFBiz applications from scratch on top of Moqui etc...

My vote will be negative if the vote will be as generic as "replace

OFBiz framework with Moqui" is because it would not be an actionable item

and there could be 1000 totally different ways to implement it.

Jacopo


On Apr 26, 2015, at 1:58 PM, Adrian Crum <

adrian.c...@sandglass-software.com> wrote:

This has been discussed for nearly a week now. Shall we start a vote?

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 4/20/2015 6:31 AM, Hans Bakker wrote:

Again, as discussed at the ApacheCon in Austin we should start setting up a plan how to best move the ERP application to the Moqui framework.

Moqui should not be part of the Apache foundation however the ERP
application should remain there.


establish a clean separation between application and frameworks and
hopefully getting David Jones back into the project.

Yes, I realize i open the pandora box :-) but we need to make some

Not only will it improve development of the ERP system but also will

major

decisions....

Regards,
Hans Bakker
antwebsystems.com

smime.p7s
Description: S/MIME Cryptographic Signature