Some Zope 2 development proposals. Nowadays these might be tracked also in Launchpad, like Zope 3 proposals. There is a whole wikiful of older proposals here.
- Non Retried Actions
- Actions that are external to ZODB (i.e. sending mail, adding data to external databases, moving robot arms) don't want to be retried if there is a ZODB Conflict. We should queue them up and run them once the commit succeeds
- Eggifying Zope's extension mechanism ("Products")
- For their upcoming versions, Zope 2 consuming platforms such as Plone are creating standard Zope3-style Python packages while still having Zope 2 products around. This proposal aims at unifying the deployment of products and Python packages into a Zope 2 instance alike by using Python eggs and their entry point system.
- Acquisition and __parent__ pointers
- This proposal aims at bringing Zope 2 a bit closer to Zope 3 by making the widely used Acquisition API aware of Zope 3's __parent__ pointers. This will alleviate the need of using Acquisition base classes in Zope 2 for every security-sensitive object, be it persistent or just a dynamically looked up component such as a view. The goal is to enable the use of Zope 3 components in Zope 2 straight away without creating subclasses that mix in Acquisition for security's sake.