Re: Compromise: Code Transfer

2004-09-28 Thread Paul Hammant
Leo, Cornerstone is still here, and I think Paul Hammant is still doing some work there - mainly just bugfixes. (Sorry Paul if you're doing major work, you're just not very noisy about it.) Am making it CDI capable (death to type1 !) so is just a minor change. - Paul -- ThoughtWorks - recrui

Re: Compromise: Code Transfer

2004-09-28 Thread Niclas Hedhman
On Wednesday 29 September 2004 01:23, Leo Sutic wrote: > So, are we good go to for a PMC vote on this, to get the formalities done? Nice try. :o) I wish I could help... Cheers Niclas -- +--//---+ / http://www.bali.ac/ / http://niclas.hedhman.org / +--//-

Re: Compromise: Code Transfer

2004-09-28 Thread Leo Sutic
On Tue, 28 Sep 2004 10:48:12 -0700, Farr, Aaron <[EMAIL PROTECTED]> wrote: > The underlying issue is that if we transfer the Framework code to Excalibur > then we've effectively made Merlin a TLP here in Avalon. That is already a fact. How much discussion and development is non-Merlin here? Phoen

RE: Compromise: Code Transfer

2004-09-28 Thread Farr, Aaron
> -Original Message- > From: Leo Sutic [mailto:[EMAIL PROTECTED] > > So, are we good go to for a PMC vote on this, to get the formalities done? Leo, There appears to be agreement to transfer Framework and LogKit to Excalibur, but there are a couple issues: 1. What about the rest of no

Re: Compromise: Code Transfer

2004-09-28 Thread Leo Sutic
On Tue, 28 Sep 2004 19:45:09 +0800, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Tuesday 28 September 2004 19:06, Leo Sutic wrote: > > > Excalibur (and I) will take care of 4.x. We'll support it. It has a > > huge installed base, and we're extremely wary of rocking the boat the > > slightest (re

Re: Compromise: Code Transfer

2004-09-28 Thread Leif Mortenson
Niclas Hedhman wrote: The same goes for LogKit. Personally, I won't use it in production installations, and would like to transfer the technology to where I think it belongs, the Logging project. I would also suggest that those who do understand, use and evolves it further to follow as committer

Re: Compromise: Code Transfer

2004-09-28 Thread Niclas Hedhman
On Tuesday 28 September 2004 19:06, Leo Sutic wrote: > Excalibur (and I) will take care of 4.x. We'll support it. It has a > huge installed base, and we're extremely wary of rocking the boat the > slightest (read: in case of having to save the world we might call a > vote). I am not at all forei

Re: Compromise: Code Transfer

2004-09-28 Thread Leo Sutic
On Mon, 27 Sep 2004 18:04:49 -0400, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > Leo Sutic wrote: > > Merlin is a path that diverges from the path chosen by > > those of us in the "old guard" - the bunch of people > > dependent on Cocoon and other pre-Merlin architectures. > > > You want to evolve

RE: Compromise: Code Transfer

2004-09-27 Thread Noel J. Bergman
Leo Sutic wrote: > Merlin is a path that diverges from the path chosen by > those of us in the "old guard" - the bunch of people > dependent on Cocoon and other pre-Merlin architectures. > You want to evolve Merlin into Avalon Planet. I want a stable > Framework 4.x. > + Framework 4.x moves to e

Compromise: Code Transfer

2004-09-27 Thread Leo Sutic
> I know I don't contribute much to the project. I am merely a user > that began using Avalon recently. I hope to become a contributor > to the project, but for now, I'm not. So, it's probably not really > my place to make any comments here. Wrong. Unless you speak, how can anyone listen to you?