Bug#123532: O: zope-zpatterns -- Database Independence and Framework Integration for Zope
The current maintainer of zope-zpatterns, Mike Goldman <email@example.com>,
is apparently not active anymore. Therefore, I orphan this package
now. If you want to be the new maintainer, please take it -- retitle
this bug from 'O:' to 'ITA:', fix the outstanding bugs and upload a
new version with your name in the Maintainer: field and a
* New maintainer (Closes: #thisbug)
in the changelog so this bug is closed.
Some information about this package:
Maintainer: Mike Goldman <firstname.lastname@example.org>
Depends: libc6 (>= 2.1.94), zope (>= 2.2.0-1)
Description: Database Independence and Framework Integration for Zope
Provides a variety of base classes and frameworks for Zope product and
application development. Some currently available patterns include:
Plugins: A framework for Folder-like object ("plugin containers") to
have management tabs ("plugin groups") that hold collections of objects
("plugins") supporting a particular collaboration interface ("plugin
SheetProviders: A framework for providing database-independent property
sheets to objects. SheetProviders are PlugIns which Racks and
Specialists use to give their contents PropertySheets, without any
objects (besides the SheetProviders) needing to know how the property
sheets are implemented or where they are stored. One can create
SheetProviders that store data in literally any kind of database
accessible by Zope.
AttributeProviders: Similar to SheetProviders, but for individual object
Racks: A framework for database-independent collections of objects.
Racks retrieve or store objects. They are SheetProviderContainers and
AttributeProviderContainers, and thus allow for property sheets and
attributes to be added to their contents from another database. The
default Rack implementation stores all data in the ZODB (as do the
default "provider" implementations), but the framework code is
documented for easy subclassing to create alternative storage methods.
Specialists: A way of organizing your applications around object
interfaces and class-level services. (Known as Implementors in the
original RIPP Model).