Le 21/01/2015 02:13, Adrian Crum a écrit :
I disagree. This is an open source software project where decisions
should be made based on good design principles. The work is being done
by volunteers, so I don't see how "cost/benefit" applies.
It is also a community driven project where decisions get debated,
volunteers working for the project should take into consideration users
point of view.
If a such modification has advantages for the community, it may also
have some drawbacks.
"cost/benefit" should be interpreted as " pros and cons" and should be
always apply.
So it is good to have such proposal , debate theme but it will better to
have a kind of road map and plan the changes for future.
Sometime, some volunteers decide to make some important changes and
commit theme without a pre-discussions, without jira and that is a not
the good way to manage the project.
Thank you all for the work you provide, the commitment etc..
Youssef Khaye
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 1/20/2015 5:04 PM, Hans Bakker wrote:
Jacopo,
'nice' is not enough reason to change the directory structure.....
Please this is a business application where decisions should be taken
based on cost/benefit.
Regards, Hans
On 20/01/15 18:41, Jacopo Cappellato wrote:
In my opinion it would be nice to review how we organize the code in
our components and switch to a directory layout that is more inline
with what other projects are doing, for example:
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
More specifically I would like to switch from, for example:
script/org/ofbiz/product/
src/org/ofbiz/product/
src/org/ofbiz/product/test/
to:
src/main/java/org/ofbiz/product/
src/main/minilang/org/ofbiz/product/
src/main/groovy/...
src/test/java/org/ofbiz/product/
What do you think?
Jacopo
