iDEAL codesprint

iDeal is a Dutch, online payment system, widly adopted, but hard to implement.
 
In Drupal there are many iDeal implementations for übercart, but none are very solid and none are easy to implement; some are even plain insecure.
 
We, the Dutch Drupal community should focus development on one generic iDEAL layer. A general iDEAL payment API.
 
Then developers can build their small übercart-ideal-payment, ecommerce-ideal-payment or whatever-ideal modules on top of that.
 
We do not just need code, Documentation is just as important. One of the hardest part is finding out how to get it running, configured and how to get all the parameters right. Differences in implementation of banks, or their payment-plans make it extremely complex to get running fast.
 
If you have no experience with iDEAL, we will explain the basics here (only if you promise to help, it is not a free iDEAL-course :).
 
If you have code lying around for iDEAL implementations, please bring it.
 
iDeal is a Dutch, online payment system, widly adopted, but hard to implement.
 
In Drupal there are many iDeal implementations for übercart, but none are very solid and none are easy to implement; some are even plain insecure.
 
We, the Dutch Drupal community should focus development on one generic iDEAL layer. A general iDEAL payment API.
 
Then developers can build their small übercart-ideal-payment, ecommerce-ideal-payment or whatever-ideal modules on top of that.
 
We do not just need code, Documentation is just as important. One of the hardest part is finding out how to get it running, configured and how to get all the parameters right. Differences in implementation of banks, or their payment-plans make it extremely complex to get running fast.
 
Action-points for the sprint:

  • Explain the architecture to developers and documenters
  • Agree upon where to centralise our development
  • Investigate all available code and modules (bring your code too, please)
  • Document the generic API concept: mission statement and short introduction
  • Write (stubs of) howto's and help-texts
  • Distribute the code/development issues and todo's

Time of the sprint will follow.
Sprint will be in English, unless there are no none-dutch speakers at all attending.
 
For my initial work, refer to the ideal-payment-api on Github (note the crappy documenation :).
For some of the TODOs with this api, see the issue list
Note: It is not yet sure if we will take this one as our starting-point, or merely as one of the references and code-pieces.

I am wondering how the iDEAL sprint went?

What was discussed and done. How do we proceed from here?

Is there a place where things are organized?

We can provide a project tool, open atrium or basecamp if needed

Jons
(jons@joygroup.nl)

No Internets (tubes) at Stayokay

We do not have internets at stayokay, I was just told.
Please download any code you wish to bring, before the sprint.

In addition, you may want to fork http://github.com/berkes/Drupal-iDeal-payment-api

I will provide:

  • Printed documentation
  • a USB stick with libraries, a git repos of available code
  • a USB stick with the documentation in PDF
  • a small router when in need of a LAN

API, technical and user Documentatie wanted of ABN and rabobank.

I am still looking for (recent) Documentation on:
Mollie,
iDEAL easy (ABN),
iDEAL professional (Rabobank)
and iDEAL Zelfbouw (ABN)

General documentation will be the same between banks and plans, but technical documentation can differ greatly!

I will bundle all PDFs, and the attendants will be able to "look into them", because "technically" I am not allowed to distribute them .... ;)

Hoofdsponsors

De Drupaljam wordt mogelijk gemaakt door diverse sponsors. Hiernaast treft u de hoofdsponsors van het evenement. De organisatie van de Drupaljam bedankt alle bedrijven en personen die er voor zorgen dat ook deze Drupaljam weer een groot succes wordt!