> -----Original Message-----
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 21, 2004 3:29 PM
> To: Depot Development
> Subject: Re: Future of Avalon & Depot collaboration
>
> On Tuesday 22 June 2004 02:34, Adam R. B. Jack wrote:
> > > I hope the atmosphere here will be equally positive to this initiative.
> >
> > My expectations are yes, yet with some tensions due to
> > philosophy/approach/goal differences. Personally, I see that as healthy
> &
> > welcome it.
>
> Ok, good!
>
> Now let the due process have its strides. I don't expect any opposition,
> but
> the issue will need to go to the PMC (which I am not part of anymore), and
> there are ASF "eyes" in there, who may have some opinion about it, which
> may
> take a few extra days to vent, but I hardly see that there will be any
> political obstacles.
>
> The rest is technology, and that is easy... :o)

I'm really sorry I haven't been active in these threads.  I've seen the
messages pop up in my email clients, but just haven't had the time to get
to them.

I agree with Niclas that it appears there is support for transfer and
collaboration within the Avalon community.  My only real concern is making
sure we all have a better understanding of each others goals and what
Depot is all about.

For example, what I personally would like to see is a TLP that is charged
with maintaining the ASF repository and also provides a collection of
tools for managing such repositories.  This would include things like
Depot as well as Avalon Repository (classloader creation) and perhaps some
future swing or webapp Repository Browser.

Reading the short description of Depot on the main website leads me to
believe my vision of a repository-centric TLP is in line with Depot's
mission.  However, after reading a few emails I'm left with the impression
that perhaps this is outside the scope of the project.

In the end, I would like to see the collaboration but I also want and need
a better idea of what Depot is shooting at.

---
  jaaron     <http://www.jadetower.org>

Reply via email to