Rather than try to find one specific direction at this stage, or creating new wish lists, we need to find a definite way forward. Let solutions evolve.
Here is one proposal. *) Current trunk continues as-is, based on Cocoon-2.1 *) Create an SVN area for each group who want to try to develop something new. A completely empty space for each group of people to start from scratch. *) Assign each a simple code name (so as not to descend into naming wars or set false impressions about what will be next), e.g. ForA, ForB, ForC. *) Conduct all discussion on this dev list. Use labels for each experiment, e.g. [ForB] my subject So subjects having no label would relate to the general current project. *) Let each specific experiment evolve at its own pace. *) When solutions approach being useful, vote to replace the trunk codebase. This also allows the people who currently use, and are generally happy with Forrest, to continue. It also lets us all put effort into the much needed release and enables subsequent faster release cycles. We have a good community and project infrastructure here. Let us build upon it. -David
