[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#312858: O: zope-emarket -- Simple e-commerce system for Zope



Package: wnpp
Severity: normal

The current maintainer of zope-emarket, Luca - De Whiskey's - De Vitis <luca@debian.org>,
is apparently not active anymore.  Therefore, I orphan this package
now.  If you want to be the new maintainer, please take it -- see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: zope-emarket
Binary: zope-emarket
Version: 0.2.0a4-12
Priority: optional
Section: web
Maintainer: Luca - De Whiskey's - De Vitis <luca@debian.org>
Build-Depends-Indep: debhelper (>= 4.1.16)
Architecture: all
Standards-Version: 3.5.9
Format: 1.0
Directory: pool/main/z/zope-emarket
Files: af49d7836af147a27d2c2c3b2ee308e2 610 zope-emarket_0.2.0a4-12.dsc
 a7662a78d090fa8ed1d8c0559a3140ba 53055 zope-emarket_0.2.0a4.orig.tar.gz
 90828190f6a8f47440b4c608010403a6 6648 zope-emarket_0.2.0a4-12.diff.gz

Package: zope-emarket
Priority: optional
Section: web
Installed-Size: 516
Maintainer: Luca - De Whiskey's - De Vitis <luca@debian.org>
Architecture: all
Version: 0.2.0a4-12
Depends: zope, zope-zpatterns, debconf (>= 0.5)
Filename: pool/main/z/zope-emarket/zope-emarket_0.2.0a4-12_all.deb
Size: 62468
MD5sum: e22bbce3ccf17942a39d9cfba730c945
Description: Simple e-commerce system for Zope
 Basically an EMarket is a folderish object that (currently) consists
 of a set of methods and five folderish 'Specialists'. Each specialist
 is responsible for managing one particular type of object. They have
 methods, and racks: methods to interface to the rest of the application,
 and racks to handle the storage and retrieval of the objects
 they manage:
 .
 marketItems: manage the market items in the EMarket
 .
 shoppers: manage the shopper objects
 .
 basketManager: manage the 'shopping baskets'
 .
 basketItemManager: manage the items in the shopping baskets.
 .
 transactions: manage the completed transactions
 .
 The idea here is to provide a framework for a 'shopping area' that is
 at once flexible, simple, and reasonably robust. The display of the
 market area is determined by editable templates that are contained in
 the marketItems folder. The display of the shopping 'Baskets' is
 managed by templates in the shoppers folder. This way each EMarket can
 be customized easily. Also, the developer picks the classes they
 want to use for shoppers, marketItems, etc... so they can also be used
 to customize the look and feel of the market.

Justification: No activity in 16 months, no response to pings



Reply to: