Re: was [OGo-Users] Ogo and ERP or CRM

On Thursday 27 November 2003 11:37, Kelley G wrote:


> yes this is proper design. :)
>
> arch design 101
> the ability to clearly integrate with other entities is critical to
> adoption of any software.
> integration relies on modularity.
> ogo is modular from the ground up.
> bloat comes from monolithic architecture. ( and marketing dept ) :)
>
> in open source one must be modular, because module development proceeds
> in parallel.
> as long as the interfaces remain consistent between modules,
> everything's ok.

All good points. There is a big diffference however between bloat, modularity, 
extensibility and the requests that were being asked. While I am not 
qualified to speak on OGo's design, OGo's adoption and penetration of the 
market will be dependant to a large degree on its provisioning of  accessible 
and standards compliants protocals, modules and API's which is a given based 
on its current license model. This is not however bloat. Bloat occurs when 
feature creep is not well planned or restricted to propriatory enhancements 
only.

Secondly it must be remembered that OGo is currently sponsored by its host 
company that derrives its revenue from customization and integration. Hence 
the two arguement fall in line and leave  the revenue channel open to the 
host firm. 

/ch

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss