My point was about the suggestion that you might want to add it as a TLP
in ASF but there were concerns about the amount of effort to start an
ASF project.
It was not about the current fact that Moqui is already a project.
I feel more comfortable about using ASF artifacts in our own products
than I do about other libraries but we do use a lot of non-ASF software
as key technologies (Spring, MySQL are key non-ASF technologies for
Artifact Software).
There was also some concern about the license under which Moqui is released.
Ron
On 30/04/2015 1:48 AM, David E. Jones wrote:
On 29 Apr 2015, at 08:01, Ron Wheeler <[email protected]> wrote:
What is the reason not to absorb Moqui or a fork of Moqui into OFBiz if we
decide to replace the existing framework with Moqui.
Is there a reason to have Moqui as a separate Apache project? Seems like extra
overhead for no advantage.
Moqui is already a separate project. The OFBiz community could certainly create
a fork of Moqui and change whatever is desired (though that shouldn’t be
necessary), but Moqui Framework is already a separate project with its own
ecosystem of business artifacts and applications. That won’t ever change, Moqui
will always be a separate project.
-David
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
