CivicActions

Simon is giving a presentation about the ecommerce module.
- an overview of who's been involved and history of the module

Current Practices & Directions:
comprehensive online business solution
documenting all code
docs at drupalecommerce.org
new maintainers - w/ new maintainers, there's been a lot of rapid development. yet it's a challenge to manage.
contrib modules in own projects
reduce tickets - Bruno has been knocking 'em out - down from 250 active tickets. Now barely in the top 10 open tickets

API's
Checkout API: to be improved with D6.
Receipts API "everything to do with money" incorporates the old Payment API
Trasaction API: everytime something happens, modules can listen in.
Ecommerce API - plans to integrate with actions module. captures events workflow, payment and new: Payment Allocations... as part of fixing a paypal bug that allowed for people to change the amount of a transaction, the Part part of the API will maintain the original (actual) price amount and deduct the (now) partial payment.

eCommerce doesn't have a specific definition for where it's best. Simon's personal opinion is that we're covering what suits everyone's needs. The big challenge will be to consolidate and going through the code to reduce it.

Audience: eCommerce is, like Drupal, two things: an out of the box solution, and also a framework for customizing the solution.

New:
Product Features is now being developed along parallel lines as CCK. Allows adding features (like "recurring" which adds expiration, for instance).

reivew of eC modules (role discount, coupon, Charge, recurring)

in V4, partial payments to affiliates and contributors

currency support is on its way.

Challenges:
code is added, but not reduced
some code neglected w/o maintainer is using
rapidly changing APi's
synchronizing releases with contrib modules.
Allowing addt'l maintainers
Bloat: eC tries to be everything