The Promice of Zope3 in the Practise of Plone - Goldegg funding initiative
Document Actions
The Goldegg funding initiative has a few basic goals. First, Goldegg should strengthen the existing stack by funding the medium-term activities that don't usually get funded: planning, coordination, etc. As an example, Zope Corporation very generously pays for Jim Fulton to act in this role for Zope 3, with the result being technical coherency and clarity in decision-making.
Second, Goldegg should improve the stack relations by getting the stack leaders to work together during the same release cycle. This includes funding for sprints which provide face-to-face time. With this, development that would be best done at a lower stack layer might be done there more frequently.
Third, Plone should get a convincing response to the "What about Zope 3?" question.
Fourth, Plone should improve the issue raised by Alan regarding "Plone-the-Product" (PtP) and "Plone-the-framework" (PtF). The Plone project should grow new framework only when it can't reasonably be done at the CMF, Five/Z3, or Python layers. Goldegg tries to get the key players together on a near-term, fast-payback progress towards coordinated releases.
The purpose of the first Goldegg funding initiative is to speed the adoption of Zope 3 technology into the CMF and Plone. Goldegg One is focused on the next release cycle of CMF (CMF 2.0) and Plone (Plone 2.2), thus keeping its scope in check. However, the deliverables will come about by working more closely the CMF, using the license of the CMF, and helping the key players of the CMF with the roadmap.
Zope 3 holds much promise as an improved application server framework. Thanks to the "Five" project, this promise is available in Zope 2 applications and is now standard with Zope 2.8. Thus, existing applications can use Zope 3 technologies without a full rewrite. Both Plone and CMF can benefit from Five. Both have Five-related roadmap items with high payback and low disruption. Also, the Z3 architecture gives Plone and CMF a chance to avoid spawning new mini-frameworks, such as event models.
_____
tags:
