Hello Pythoneers, I am excited to announce a Zope Directions Roadmap. http://dev.zope.org/Resources/ZopeDirections.html This document summarizes current thinking at Digital Creations about where the Zope platform is going from an architectural point of view. It summarizes informal conversations that we've been having internally for the past couple months. This paper talks about how we'd like to improve Zope to make it easier for Python developers. It puts some existing initiatives (e.g. Presentation Templates, and the Content Management Framework) in context, and discusses potential future projects like moving to a component architecture. I should point out that this document is not a concrete plan so much as a statement of what's on our minds. Zope development will continue to operate openly in the fishbowl (http://dev.zope.org/). We'd love to hear what you have to say. Are we heading in the right direction? Is there something else that we should be doing instead to help developers? Let us know. (Follow up should be on the zope-dev mailing list.) And when we begin new fishbowl projects (look for a component architecture project soon) jump in and help define Zope's future! -Amos <P><A HREF="http://dev.zope.org/Resources/ZopeDirections.html">Zope Directions Roadmap</A> - Paper describing Zope development plans. (20-Feb-2001) -- Amos Latteier mailto:amos@digicool.com Digital Creations http://www.digicool.com