El lun, 14-08-2006 a las 20:59 +0100, Ross Gardler escribió: > This is a Random Thought. The ideas contained within are not fully > developed and are bound to have lots of holes. The idea is to promote > healthy discussion, so please, everyone, dive in and discuss. >
Just some quick remarks. Is our focus on framework or on implementation for the new trunk? NOTE: I am not saying we should or we shouldn't. I can deeply understand the motivation of the RT and will state my opinion about it later. > The Drawbacks > ============= > > What are the drawbacks of getting rid of Cocoon? > > Probably the biggest drawback would be that we have to code it. There's > not a huge amount of work to be done, but there are some neat things in > Cocoon that we would have to reimplement or find elsewhere. We may be > able to extract some of the code from Cocoon, but I'm not convinced this > is a good approach. > > Because of this need to write the code it will mean that Forrest would > initially take a step backwards in terms of its functionality. The other thing is that the existing community is right now pretty much cocoon orientate. Dropping cocoon in 2.x can have the side effect that the current community *may* loose interest in forrest (cocoon have been a big selling point in the past). The critical question is, how many people (as devs) can we attract to join the rewrite dropping cocoon, taking a step back in functionality, focusing on java for new components? How many committer and devs will work on branch, how many on trunk, how many on both? I hope to see a healthy discussion, which will give some leads regarding above questions. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
