cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: Status of XMLForm in Cocoon
Date Tue, 20 May 2003 13:15:16 GMT
On Tue, 20 May 2003, Bertrand Delacretaz wrote:

> Both are suboptimal options. A fork is a bad thing and unfortunately
> you seem to be caught in its consequences.

I disagree. A fork can be healthy sometimes and if you have a healthy community
around the forked stuff you'll move ahead faster.


> A third option would be for you or your company to jump in an
> contribute to the re-integration of into Cocoon, by
> refactoring what's here to use the components as external
> libraries (provided the license allows it, but I think it
> is the case).
> If this happens, would be in the same position as Chaperon
> and jfor for example, which (try to) live outside of Cocoon but are
> used here through clean interfaces.
> A fourth option, depending on where you're at in your project, would be
> to contribute to the new woody form stuff that is being developed and
> looks to me like it will get more support from the Cocoon team, due to
> the community wounds created by the xmlform fork (that's how I see it
> personally, not speaking for the team).
> This is Open Source - unless people "vote with their code" nothing
> happens.
> > I'm a bit worried about future.
> Understandable, this fork is a sad thing, but the door is open for
> people to help solve this.
> -Bertrand

View raw message