This is my personal opinion. ---oOo---
Status: Forrest appears to be at a standstill. It has been a long time since a release. Also the previous release had a long gap. ---oOo--- Possible future directions: A) Stay with current situation of Cocoon-2.1 version. There is plenty of development that can be done with our current Forrest/Cocoon technology. Fine-tuning and clean-up. Fully implement the new xml properties system. I gather that it is ready. Just needs to be configured for our sample sites, plugins, and docs, and also documentation updated. New plugins. Improve the plugin infrastructure and address the needs of ASF releases for our plugins. Improvement and clean-up of documentation. Development can still be done at Cocoon-2.1 and our packaged Cocoon be updated. The process is well documented. B) Try to upgrade to Cocoon-2.2 version. See past discussion in our dev mail archives. C) Try to upgrade to Cocoon-3 version. I don't know whether Cocoon-3 is ready or possible for Forrest. Would someone else comment. D) Develop some other core. See past discussion in our dev mail archives. E) Cease Forrest and move to the Apache Attic. http://attic.apache.org/ ---oOo--- Whatever happens, we still need to make a release. Whatever happens, more people need to assist with the project management tasks. ---oOo--- My opinion is that Forrest needs to make a decision about which direction, and stick with it, developers get involved to start Forrest moving again, and build the community. Options A to D have previous discussion in the dev mail archives. -David
