Zope 2 is the original package that used the ZODB. Initially the ZODB was part of Zope2, later it was split out into a separate package.
Plone is a Content Management System built of top of Zope 2. It is very strong for multi-lingual applications and for quite a while was hot in the market. It could do a lot out-of-the-box, but when you try to do something significantly different, it is not very flexible.
Zope 2 was completely rewritten as Zope 3, and then evolved into ZTK, the Zope toolkit. The idea was that a number of applications could build on top of ZTK.
Django is very relational database centric, this product tries to include an object database. Another pairing that does not make sense to me.
Pyramid is probably the leading ZODB web framework. It is optimized for performace, and supports traversal or URL dispatch, Relational database or ZODB, and 3 different ways of configure it.
ZTFY is a both an application and a library built on top of ZTK. ZTFY restores the ZMI (User Interface), but not for development, only for content management. There are some excellent libraries in there. It was written and is in use by Thierry, but sadly no one else adopted it, so he is now moving to Pyramid.
Zope 3 and ZTK were difficult to use. So Grok was born. Grok simplifies the configuration required by ZTK/Zope 3. I love Grok. It makes the power of ZTK easy to use. This website was developed on top of Grok.
Flask is a light weight framework for connecting to relational databases. Accordingly it supports URL Dispatch rather than traversal. And now with Flask-ZODB, it supports an object database, but with URL dispatch. Makes no sense to me.
Zopache was used to buld this web site, and PrivaCV.com