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.
If Moqui is a separate deliverable of the OFBiz project and included in
the OFBiz ERP as a clean dependency, then managing Moqui development
with git, Maven and any other tool should not make the OFBiz universe
unstable even if the main development stays on SVN and Ant.
It should probably have its own release roadmap if it is used by other
projects but once again, I don't see any negative impact on the rest of
OFBiz.
I am not sure that it is a good idea in general but these issues are not
the source of any concern.
Ron
On 29/04/2015 3:41 AM, Jacques Le Roux wrote:
I was rather reluctant about this but after the PoC concept has been
introduced by several persons and reading the last exchange between
Adam and David (where David said <<with the clarification that to me
"begin replacing" implies a PoC effort in a branch>>) I sort of
changed my mind, unlike Nicolas I will not vote -1 but 0.
Like him I don't like the idea of plugging Moqui jars in OFBiz. On the
other hand I understand Moqui is open source and everybody has access
once a Github account is created hence 0 and not -1. It's still not a
+1 because this adds extra complexitiy (2 repos, 2 set of tools, how
to communicate, etc.) I don't like much :/
David mentioned <<There is a chance Moqui Framework could become a
separate ASF project, though the name "Apache Moqui" is oddly
contradictory>> I guess still using Git as preferred commit medium
(but as said Jacopo with anyway Svn as ultimate repo at the ASF).
David also said he would prefer <<the distributed and moderated
approaches used in the Linux kernel more than the community approach
mandated by the ASF.>> which I believe was David's main concern when
he created Moqui.
That's could seem contradictory with ASF policy but remember that each
project can define its own policy. Personnaly I don't see a problem
with that, I trust David not wanting to become a benevolent dictator,
he many times always proved to simply want the best for the OFBiz
project. Mixed with << I would rather let people come along, express
interest, and thoroughly prove merit before they take on such a role.
>> I understand that a Moqui podling would be created without direct
connection with OFBiz committers.
It's certainly too early to get conclusions about having 2 separate
projects working together (in ASF or not), but I can already see some
concerns
If we introduce Moqui in OFBiz we can't avoid to speak about the 2
diverging ways of doing things at the UI level. Though I have not used
Moqui I believe it is more flexible for this aspect, but again this
add complexity. I know we are speaking about that yet, just saying,
because if the PoC works it's the next step.
Sorry for the long and confusing post, it's hard to explain what I
feel better.
Jacques
Le 26/04/2015 16:44, Adrian Crum a écrit :
As was discussed last week, there is some interest in replacing some
(or all) of OFBiz with Moqui
(http://www.moqui.org/framework/index.html).
To the scope reasonable, I propose that we begin by converting the
following parts of the OFBiz framework with Moqui:
Entity Engine
Service Engine
Security
Other parts of the OFBiz framework could be converted as well, but I
think this would be a good starting point, and if is successful, then
more of OFBiz can be converted later.
I believe we can create a thunk component to help solve compatibility
problems, but that is a separate discussion. I only mention it here
in case compatibility concerns might influence a vote.
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
