Jeff Turner wrote: > 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
+1 ... love the twist - parents join the children. > Vote 2: Forrest should become a subproject of Cocoon > (http://cocoon.apache.org/forrest) 0 ... While it might make sense, i cannot yet see the pros and cons. Perhaps we need some discussion before voting on this. One thing that might make a difference is that the Cocoon PMC is more active (though i am not on the XML PMC so i cannot really tell) and is more relevant to the issues that Forrest encounters. One disadvantage with moving Cocoon and Forrest away from xml.apache.org is that all Cocoon and Forrest committers are already automatically committers on xml-commons and could be helping that important project to find its feet. --David
