As most of you probably saw, there's a thread on cocoon-dev suggesting that Forrest ought to be a Cocoon subproject, with the consensus being it "makes sense".
AFAICT the only practical difference would be that Cocoon committers would automatically become Forrest committers. Sounds fine to me. Can we vote on these issues then? Vote 1: Cocoon committers automatically become Forrest committers Vote 2: Forrest should become a subproject of Cocoon (http://cocoon.apache.org/forrest) I vote +1 and +/-0. Both make sense, but 2) seems slightly more pain than gain, unless there's some advantage I've overlooked. --Jeff
