Date index for Dec 2002
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [achievo] Achievo 1.0 revised roadmap
Hi Ivo,
I agree that splitting Achievo into downloadable modules is a good idea.
I believe the development of the individual modules will go faster and more
modules will become available. I do think that the 3rd part of your manual
will be essential. Otherwise individual updates will be lost when a new
version of a module is released.
Grtx,
Marcel
----- Original Message -----
From: "Ivo Jansch" <ivo dot
To: <achievo dot
Sent: Tuesday, December 03, 2002 11:47 PM
Subject: [achievo] Achievo 1.0 revised roadmap
> Hi,
>
> those of you reading this list for a while now, might remember my
> original goals for Achievo 1.0 (which can also be found on
> http://www.achievo.org/development):
>
> * Finishing the scheduler feature
> * Finishing the finance features (billing)
> * Finishing the cost registration feature
> * Finishing the resource planning feature
> * PostgreSQL/Oracle database compatibility
> * User interface improvements
>
> Several things made me rethink these goals.
>
> First of all: billing, cost registration and resource planning need a
> lot of work before they can be considered stable enough for daily use.
> So much work in fact, that they would cause quite a delay for the next
> stable release, given the current resources I'm able to dedicate to them.
>
> Second: these features are, for a lot of current users and potential new
> users, not an essential part of Achievo.
>
> Third: Achievo now has quite a powerful module api, making it possible
> to implement these features as add-on modules instead of making them an
> integral part of Achievo.
>
> Based on these 3 arguments, I would like to propose a revised roadmap,
> and would like your input on this proposal:
>
> The proposal comes down to the following activities that I've planned
> for the release of Achievo 1.0:
>
> * Strip cost registration, resource planning and billing from the base
> Achievo product, and move them into separately downloadable modules,
> each with their own development status, so they can be developed
> independently of the Achievo 'core' application.
> * Improve module support, mainly by providing a way to easily
> maintain, install and upgrade add-on modules, and insuring that
> version conflicts and compatibility issues will be kept to a
> minimum.
> * Provide more ways for modules to influence eachothers behaviour, and
> create seemless integration (especially for the userinterface).
> * Provide webspace for add-on modules, so they can be downloaded from
> the achievo.org site.
> * Improve postgresql and oracle compatibility, and provide a means for
> easily maintainable, per-module, databaseindependent, install and
> upgrade scripts.
> * Provide bugzilla and CVS repository for the modules, to aid in their
> development.
>
> The main advantages of maintaining separate modules are:
> * Achievo base application development is not negatively influenced by
> the development status of the modules.
> * Modules can each have their own maintainer, to promote active
> development
> * Reduces 'feature bloat' (don't install what you don't need)
>
> I would welcome any feedback (positive or negative) on the above roadmap
> changes.
>
> Greetings,
> Ivo
>
>
>
> [ Achievo mailing list - http://www.achievo.org/ ]
> [ to unsubscribe send an e-mail to achievo-unsubscribe dot
>