Don Brown wrote:
The purpose of this merger is not to create yet another framework or kill off competition, but to start collaborating as framework developers for the greater good of the general community. By focusing on who can do what or why can't a project release something, you are missing the point. The point is to collaborate to build a single Action-based framework that combines the talents of the Struts and WebWork teams, and hopefully more.

But that's precisely my point... isn't the best way to combine the talents to "take the cuffs off", so to speak, and not worry about backwards-compatibility? Why should those talents be shackled to that compatibility *IF* the existing frameworks are going to continue to be actively developed? Your proposal explicitly states that SAF1 will do so... if the Webwork folks were to say the same thing, that to me removes the need to keep compatibility (and even if they didn't want to do that, which I agree is completely their choice, is the community big enough to warrant sticking with compatibility?). That's my point. I see it as a way to maximize the outcome of the merger.

> Yes, there will be compromises, and yes, we can't
"force" anyone to do anything, but we are here aren't we, so let's make the most of it.

Again, precisely my point. There are a lot of good ideas being talked about... but many of them either can't be done, or can't be done to their full potential, if backwards-compatibility is still clung to. If the existing branches can continue to develop, then the community is not hurt by breaking compatibility, they are actually HELPED because the merger yields a much greater value in the end, and people will probably want to migrate despite the problems.

The purpose of this proposal is come to some sort of agreement of where we want to take Struts Action 2, so we can get back to work.

Of course, it'd be foolish for it to have any other purpose :) I'm just raising one way that agreement might be reached sooner than later. I might be wrong, but I'm putting it out there for discussion just the same.

Don

Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to