Aegir Billling Meeting Notes 22 October 2008

Unofficial Notes from Aegir Billing Requirements Meeting Oct. 22, 2008

(Note Taker: Roland Tanglao)

Please edit this and add anything missing or fix errors!

Attendees:

1. Adrian Rossouw (vertice, Raincity Studios aka 'RCS')
2. Francis Pilon (piloni, RCS)
3. Xiong (xiongxiong, RCS)
4. EclipseGC (From the Worx company)
5. Antoine Beaupré - (Anarcat, Koumbit)
6. Roland Tanglao (rolandtanglao, RCS))

Notes

1. nobody updated the wiki page with requirements http://groups.drupal.org/node/15973
2. no ubercart folks in the meeting (held at irc.freenode.net #hm2 on IRC)
3. Adrian: we will need to port the hosting front end to D6 before we can do billing integration
4. Roland: but in parallel we can:
   1. get the billing requirements to be approved
   2. write high level billing design right, saying what are the billing pieces and
   3. tentatively assign who's doing what pieces
5. 'Interim billing' == HM1 billing ported to Aegir
6. Adrian: november bryght light billing will use existing (hm1 billing) & december bryght light billing will use aegir port of hm1 billing
7. Adrian has been playing around with ubercart billing and researching it
8. Roland to install ubercart and play around and get familiar and see what's possible out of the box, would be nice to have ubercart folks go over the requirements wiki page first so he doesn't waste time exploring things that don't work
9. Adrian: ubercart seems to have the requirement to enter credit card when creating a Bryght Light site or node in general, no provision for 30 day trial, Roland to confirm with ubercart folks
10. Adrian - some technical issues: what happens when Credit card fails, what happens when an order is free, i.e. $0.00, how does a node transition from queue->order which becomes recurring billing?
11. Francis: perhaps ubercart does handle 30 day trial as follows using "conditional actions": product X is free and doesn't require CC and then after 30 days, the node/product association changes
12. Adrian: the recurring payment module is very close to what we need: the first 90% is there it's the last 90% that worries me