On 24/10/2014 6:52 AM, Jacopo Cappellato wrote:
On Oct 24, 2014, at 9:58 AM, Jacques Le Roux <[email protected]>
wrote:
I guess at some point the disabled specialpurpose components in trunk will end
in Attic.
Not necessarily: a disabled component could be a specialized version (e.g. for
a specific industry or for a specific payment processor) of some of the
application components and could be actively maintained; in this case it would
make sense to disable it by default (because by default OFBiz should be as
generic as possible) but still keep it in the trunk (and possibly in some
releases, e.g. ofbiz-specialpurpose-13.07.03.zip).
Jacopo
This is another area where sub-projects would help.
The software would be maintained in its own repo and would be supported
by an identifiable team that actually cared about it and would be
responsible for building the community to support that function.
There would be someone (or some people) able to say if it was going to
be ported to the latest release and bugs backported to previous releases.
If that sub-project died, it would be clear and everyone would know that
it was not going to be available as part of future OFBiz releases unless
some group took charge of the sub-project and did the work.
This structure would help everyone and increase the transparency around
the management of components.
Ron
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
