Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (herse.apache.org: domain of ross.gardler@googlemail.com
 designates 209.85.146.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=KTG0rpKT9VgteHMSi94txfrAKkIKAKU+BiNiFPMnlbHL5aYLGH8UnJd7tJkbJNKOOqy1ZKrCa4u34pkIVcK3gO0JG5X/otyrYr0aZDfKJhMKfYDcMkf1AlM9Agt9McbcFK6+c2mJdFUZfxuyDwoHahRcDw/4DmyVJFLO2hYzs0w=
Message-ID: <61c9bc470707170403ne5b0f97h299d549efc8660d3@mail.gmail.com>
Date: Tue, 17 Jul 2007 12:03:19 +0100
From: "Ross Gardler" <rgardler@apache.org>
Sender: ross.gardler@googlemail.com
To: dev@forrest.apache.org
Subject: Re: direction of forrest
In-Reply-To: <499888440707160516s6f527957p27ebdce52de3ace7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <499888440707160516s6f527957p27ebdce52de3ace7@mail.gmail.com>

On 16/07/07, Tim Williams <williamstw@gmail.com> wrote:
> So, I ask what's the future of forrest?  Is Forrest2 or some
> derivative the answer?  Status Quo?

Thanks for raising this Tim. I don't have time for a full answer right
now, and given I am travelling at present I doubt I will have time for
one until later in the week, or maybe even next week. So, my very
quick answer for now is...

Forrest is dead, long live Forrest2.

When I say Forrest2 I do not necessarily mean the code in whiteboard
(although I think it is pretty cool), I mean the concept of Forrest 2.
For those who have not read my original Forrest2 direction see the
archives that Tim linked to in his post, the summary is...

Forrest is an XML publishing framework, it is not a web framework.

Our dependence on Cocoon is unnecessary and is restricting our
continued development since Cocoon is moving in different directions
these days, i.e. no CLI in Cocoon 2.2 so no way to move to true
blocks, so no way to become more usable.

The value in Forrest is our transformations.

Forrest 2 aims to leverage that value whilst adding flexibility to our
users to be able to use it in whatever environment they need (which
may be Cocoon, but may not be).

BUT...

Who will do this? I'd love to say I will, but I am only one person and
right now I don't have the time or, to be honest, the inclination.
However, if we gather community support around whatever the concept of
Forrest2 becomes I could well be swayed.

I look forward to catching up on this discussion and hopefully helping
to build on whatever develops.

Ross