Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Message-ID: <3EBBA1ED.5040607@apache.org>
Date: Fri, 09 May 2003 08:41:17 -0400
From: Berin Loritsch <bloritsch@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
CC: Avalon Developers List <dev@avalon.apache.org>
Subject: Re: Regarding Excalibur XMLUtil and Store
References: <3EBABC21.5020308@apache.org> <b9ev47$eem$3@main.gmane.org>
In-Reply-To: <b9ev47$eem$3@main.gmane.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Stefano Mazzocchi wrote:
> on 5/8/03 3:20 PM Berin Loritsch wrote:
> 
> 
>>These two components are scheduled for the Excalibur Phase III
>>release.  The problem is that the documentation for them is non-
>>existant.  Since these components originated from Cocoon, can
>>we have some volunteers to write up some docs for them?
>>
>>We will be happy to commit anything we get.  I think it will be
>>better if the folks who use them the most wrote the docs than
>>those of us who do not use it as often.
> 
> 
> Better yet: put it back where they belong: here!
> 
> Anybody against this?

No.  The last time I suggested this, some developers thought that
it would be better there, and others (FOP to be specific) wanted
to use them.

So if you are going to have them here, please make them available
separate from Cocoon for their sakes.

Also, there was the option of opening up the Excalibur CVS to Cocoon
and JAMES so that all developers from those projects can maintain the
components that they use which were either developed in Avalon, or
for whatever reason were moved there.

The downside of that approach as you have pointed out in the past
is the number of emails that you would have to wade through.  The
CVS mail list has an alias for each repository, and when you subscribe
to the CVS mail list you get notifications for all changes in all
Avalon repositories.

Its a question of where the best place would be to have them.
The Avalon team has discussed using one of the commons projects
for hosting Avalon components, but most people (not all) are in
agreement that Avalon components should be hosted by Avalon in
general.  THese components in question can be argued as being
more Cocoon components than Avalon components.  We have some
Cocoon developers working on them that also have Avalon commit
access.  But that is not optimal.

At this present time the Avalon project does not have the infrastructure
to support a "component commons" of sorts.  There is alot of work to get
that to work seemlessly--which is not done yet.

Any input you could give us into solving this would be helpful.


-- 
"You know the world is going crazy when the best
rapper is a white guy, the best golfer is a black guy,
The Swiss hold the America's Cup, France is
accusing the US of arrogance, and Germany doesn't want
to go to war. And the 3 most powerful men in America
are named 'Bush', 'Dick', and 'Colon' (sic)".

-----Chris Rock


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org