Le 21/03/2012 16:16, Anil Patel a écrit :
Jacques,
I don't use pos, but I think it's good idea to keep it where it's. I
think it's more likely, it will be used more than what goes in Extra.
It fits "specialpurpose".
Why do you think a component will be used more if its in specialpurpose
section, instead of Extras.
Personally think it opposite, If a business is interested in using POS, they will find be
able to find it from Extras as well. Like any other Ofbiz application, The Users of POS
application will will respond by saying "UX sucks" :). At that point Company
who deployed the POS will be motivated to improve it. If POS is in Extras its will be
much easy for new developer to become active committer.
In some cases, contributor may want to change License on a components. Doing
such thing will be possible for Ofbiz Extras.
As I said in a previous email, imo
1) it's very important for the end-user to be very clear especially for
the license,
2) for visibility, we should not have too many "project" or
'repository", so in OFBiz-extras, we should have only a few project, not
one per plug-in, but one per repository.
example of repository
- all plug-in with a Apache 2.0 license and hight quality level
- all plug-in with a Apache 2.0 license, in development process
- all plug-in with a Apache 2.0 license, with no more activity
- all plug-in with a GPL license and hight quality level
- all plug-in with a GPL license, in development process
- all plug-in coming from a company or community with a associated license
- ...
One of the reasons (I am sure there were many) why OpenTaps was started is
License.
I will personally like to have more freedom around UI toolset. Ofbiz Extras
will make it possible. And if application is well accepted by users then it
will get popular and community will grow.
of course, I agree, but only if maturity, support type (large community,
commercial, ...) license constrain is readable.
Regards
Anil Patel
On Wed, Mar 21, 2012 at 10:48 AM, Anil Patel<[email protected]> wrote:
People are really worried on the idea of moving certain components from Ofbiz
trunk to Ofbiz Extras. Why is it so?
Moving a component from Ofbiz trunk to Ofbiz Extras does not mean that the
component is not good and so we are throwing it out. Instead idea is to allow
components to grow by giving them little more freedom.
Like Jacopo mentioned in one of his responses, Projects from Ofbiz Extras can
still post updates on Ofbiz lists.
Finally if a Project in Extras is useful for business, people will keep
improving it and community will grow.
Thanks and Regards
Anil Patel
HotWax Media Inc
On Mar 21, 2012, at 8:34 AM, Jacques Le Roux wrote:
They are more generic sure, I wonder for the pos...
Jacques
From: "Mansour Al Akeel"<[email protected]>
Jacques,
Yes. You are right. I meant projectmgr. :)
I believe assetmaint and projectmgr are used more than others and good
to keep them where they are.
Thank you.
On Wed, Mar 21, 2012 at 10:02 AM, Jacques Le Roux
<[email protected]> wrote:
partymgr is in application will not move, you meant ProjectMgr right?
Jacques
From: "Mansour Al Akeel"<[email protected]>
I would recommend keeping partymgr and assetmaint.
I am not sure if accounting depends on assetmain.
On Wed, Mar 21, 2012 at 6:59 AM, Pierre Smits<[email protected]>
wrote:
+ 1 on move of majority of apps in specialpurpose to 'Extras', excluding
projectmgr as it displays how to use OFBiz in a different industry than
ecommerce/webshop. Is it not so that OFBiz is versatile. ProjectMgr does
deliver some of that versatility.
Regards,
Pierre
Op 20 maart 2012 12:47 schreef Jacopo Cappellato<
[email protected]> het volgende:
H) specialpurpose/*: move several (if not all, apart ecommerce) of the
components to "Extras" (if there are persons interested to become
committers/maintainers) or to "Attic"
There seems to be a general agreement to slim down the number of
applications in this group and move them to Extras (see exceptions
below).
I am summarizing here some notes but we should actually use this thread
to
continue the discussion about what should go to specialpurpose in
general
rather than focusing on the decision about removal of specific
applications; we can then start a separate thread for each component.
Adrian would like to keep one or two components to demonstrate the
concept
of reusing artifacts to create custom applications (Jacopo: can we use
the
"exampleext" component for this?)
Hans would like to keep the ones that he considers feature complete like
asset maintenance, LDAP, POS, e-commerce, cmssite, projectmgr and scrum.
Jacopo: in my opinion even in the above list provided by Hans there are
applications that are barely examples (cmssite) or are very specific
implementation of very specific requirements (difficult to be used if
your
company doesn't have exactly these requirements): projectmgr and scrum;
some of these components also extends (adding special purpose fields)
the
generic data model and this happens even if the user is not interested
in
evaluating the specialpurpose component. I also don't think that some of
the components meet minimum quality requirements to be distributed with
OFBiz: for example the scrum component uses a mechanism that is unique
to
demo its features (i.e. published a demo webapp with online instructions
for demo data) that is not used by other applications (and this makes
the
suite of applications inconsistent); also, the component refers to
resources that are owned by Hans' company. All in all, they seem very
specific piece of codes that should better live as optional plugins
downloaded separately. So in my opinion the "concept" of specialpurpose
application is in general better suited for Apache Extras rather than
for
the OFBiz svn and releases.
