bloritsch 2002/12/16 09:16:12
Added: src/proposal/avalon5 discussion-points.txt
Log:
Adding the discussion-points.txt until we have a Wiki
Revision Changes Path
1.1 jakarta-avalon/src/proposal/avalon5/discussion-points.txt
Index: discussion-points.txt
===================================================================
This document is to keep track of discusstion points
related to Avalon 5 development. When things get to
a point where they can be focused on in the Avalon-Dev
site without being considered noise.
The general format will be something like this:
Topic: Should we do XYZ?
Explanation:
The following text should be a more descriptive
form of the XYZ topic. Either provide
justification, or clarification of what the
proposal entails.
PRO:
bloritsch - It looks good to me.
CON:
Each topic will be separated by a row of dashes.
----------------------------------------------------
Topic: Should we incorporate Commons Logging?
Explanation:
This move would increase synergy with other
projects and reduce the amount of code that we
need to maintain. The issue was raised by Mauro
Telivi, and we need further communication to
figure out what is the best solution.
PRO:
CON:
---------------------------------------------------
Topic: Should we use Maven for the build?
Explanation:
Our current build architecture is chaotic to say
the least. We have no less than three methods
of generating documentation, and serveral fairly
complex build scripts. Maven helps smooth out
the inconsistencies in the approach, and still
allows for plugging in a documentation building
tool like Fortress. Most importantly, it will
get rid of many JAR files in our CVS directory,
and simplify the build process for our users.
PRO:
bloritsch - We are in desparate need of a unified
and simple build architecture. IMO, Maven is
the best choice we have available.
CON:
--------------------------------------------------
Topic: Should we unify the CVS structures?
Explanation:
We currently have ~9 CVS structures. The purpose
was to separate the different projects and make
it very clear what code belongs to which project.
That project also helps us identify areas of tight
coupling and what projects depend on which other
projects. That can still be done in one CVS
structure, using directories to distinguish the
projects.
PRO:
bloritsch - We have some projects that are no
longer supported or needed (like Testlet).
It would be a good way to clean out the cruft,
and help manage the focus and scope of Avalon.
CON:
--------------------------------------------------
Topic: Should we make the Avalon maling lists from
avalon.apache.org?
Explanation:
We are currently our own entity. We are not
a Jakarta project any more. I would suggest
the mailing lists (in addition to
[EMAIL PROTECTED]): developers@, users@,
cvs@, and possibly general@ and announce@.
PRO:
bloritsch - It would help establish the
Avalon brand instead of Jakarta.
CON:
------------------------------------------------
Topic: Should we use our avalon.apache.org site?
Explanation:
Whether we asked for it or not, the site does
exist, but it is currently empty. We should
put our current stuff in the new location, and
use redirects to point us all to the new
location. It would also enable us to make
sure we have mirror friendly distributions.
PRO:
bloritsch - Again we are solidifying Avalon.
CON:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
