banking-addons-drivers team mailing list archive

[Ignacio Ibeas <ignacio@xxxxxxxxxx>]

Hello,

@Alexis.

First of all sorry for my english.

The option that propose Pedro comes because there are companies that use 
account_payment_extension, and they can't change to banking addons.
So we have developed a new project based in banking addons but without its 
dependence. This project try to get some tools specific tools for SEPA. This 
tools not depends of account_payment_extension, account_banking_payment or any 
other, only have the tools to export and can be used for any module.

Also we make the module to be easy to make inheritance.

I understand your point of view about join account_payment_extension and 
banking addons. But the limit date is near, and the companies that user 
account_payment_extension need a solution now.

If you check the module of this project you can see that banking-addons can 
use it, only replace the wizard. And with this project we reduce the 
maintenance of sepa file format to only one module.
You can see here: https://launchpad.net/sepa-tools
Now in OpenERP 6.0 and 6.1. 7.0, available in few days.

And the account_payment_sepa merge for account_payment_extension here:
https://code.launchpad.net/~openerp-sepa-team/account-payment/account-payment-
sepa-6.1/+merge/200480


PS: I have seen your direct debit module and I will compare your direct debit 
wizard with the generic sepa_pain module of sepa-tools project.
Also in few days we publish other module that update IBAN accounts from BBAN. 

Greetings,
Ignacio Ibeas




On Viernes, 3 de enero de 2014 22:19:24 Alexis de Lattre escribió:
> Happy new year to all the banking addons team !
> 
> @Pedro :
> 
> Sorry for this late answer (I was on holidays until recently). Please
> find my comments below.
> 
> Le 24/12/2013 16:47, Pedro Manuel Baeza Romero a écrit :
> > Here in Spain we have a problem that I want to discuss with all of you
> > for a long time, but as everyone, I have been very busy with end of
> > year tasks and the usual stuff, so I take now to talk about it: as
> > other countries, we are using /account_payment_extension/ as our main
> > module for grouping payments and export them to bank files (up to
> > SEPA, in SPAIN were CSB files). But now that SEPA arrives, we are
> > facing that if we want to reuse community work, we have to switch to
> > /account_banking_payment/ module, that is incompatible with
> > /account_payment_extension/. So we need to choose one of this bad
> > possibilities: a) uninstall /account_payment_extension/ and loose all
> > the payment history; b) don't install account_banking_payment and stay
> > as is; c) re-develop SEPA modules using /account_payment_extension/ as
> > base.
> > 
> > There are people in Spain that want the choice C and have started to
> > work on it, but I would like to get to a common ground to avoid
> > duplicating community efforts, so I want to propose something: why
> > don't we work together on common modules that can be used for both.
> > For example, call it /sepa_pain/, /sepa_direct_debit/ and
> > /sepa_credit_transfer/ with the general stuff, and then make little
> > bridge modules for each of the choices calling methods on the other
> > modules (/account_banking_sepa/ and /account_payment_sepa/, for
> > instance). What do you think about this solution? Do you think it's
> > possible? If you want, we can work together in a code sprint to
> > achieve this.
> 
> I think there are better options that the options a, b or c that you
> propose :
> 
> d) make account_payment_extension compatible with the banking addons
> 
> e) merge account_payment_extension and the banking addons i.e. implement
> in the banking addons the features of account_payment_extension that are
> currently not present in the banking addons
> 
> I don't have experience personnally with account_payment_extension, but
> I am often confronted to people who install the SEPA modules from the
> banking-addons and have to uninstall account_payment_extension to make
> it work.
> 
> After a very rapid look at account_payment_extension, I think that
> option e) is probably the best. I think that it shouldn't be a lot of
> work to add the main features of account_payment_extension in the
> banking-addons. For that, the first thing to do is to list the main
> features of account_payment_extension that are not present in the
> banking-addons. Pedro, I see in the log history that you are currently
> the main contributor on account_payment_extension. Maybe we could
> organise a phone meeting to talk about this ?
> 
> Regards,
> 
> > Regards and Merry Christmas!
> > 
> > 
> > 2013/12/24 Alexis de Lattre <alexis.delattre@xxxxxxxxxxxx
> > <mailto:alexis.delattre@xxxxxxxxxxxx>>
> > 
> >     Dear banking-addons friends,
> >     
> >     Le 12/12/2013 14:51, Alexis de Lattre a écrit :
> >         Le 12/12/2013 11:13, Alexis de Lattre a écrit :
> >             B) once the merge proposal is merged, continue the work on
> >             the module "account_banking_pain_base" to mutualize more
> >             code between the credit transfer and direct debit, and add
> >             the new features added in the module for credit transfer
> >             during the Akretion-Noviat code sprint in the module for
> >             direct debit.
> >         
> >         In fact, I started to work on point B. It is in this branch :
> >         
> >         https://code.launchpad.net/~akretion-team/banking-addons/70-sepa-t
> >         rf-dd-updates
> >         <https://code.launchpad.net/%7Eakretion-team/banking-addons/70-se
> >         pa-trf-dd-updates>
> >         
> >         
> >         I plan to continue the work in the coming days.
> >     
> >     My work on the module "account_banking_pain_base" is now mature
> >     and I now mutualize as much code as possible between the module
> >     account_banking_sepa_credit_transfer and
> >     account_banking_sepa_direct_debit. As my merge proposal
> >     https://code.launchpad.net/~akretion-team/banking-addons/70-sepa-direc
> >     t-debit/+merge/195139
> >     <https://code.launchpad.net/%7Eakretion-team/banking-addons/70-sepa-d
> >     irect-debit/+merge/195139> was still not merged, I have cancelled it
> >     and I made a new merge
> >     proposal :
> >     
> >     https://code.launchpad.net/~akretion-team/banking-addons/70-sepa-trf-d
> >     d-updates/+merge/200019
> >     <https://code.launchpad.net/%7Eakretion-team/banking-addons/70-sepa-t
> >     rf-dd-updates/+merge/200019>
> >     
> >     This is a big merge proposal because it contains A LOT of work on
> >     SEPA credit transfer and SEPA direct debit. So let's review this
> >     and get it merged before the SEPA migration deadline (February 1st
> >     2014) !
> >     
> >     Regards,

Ignacio Ibeas
Acysos S.L. (www.acysos.com)
LinkedIn: http://lnkd.in/Mi37Fk
Launchpad: http://launchpad.net/acysos
Github: http://github.com/acysos
C/ Miguel Astrain 18, 1º Oficina A
31006 Pamplona, Navarra.
ignacio@xxxxxxxxxx
Tel. 948238905
Móvil 639452423
---------------------- // -------------------
La información contenida en este mensaje de correo electrónico es 
confidencial, para ser leída por la(s) persona(s) a quién se dirige. El 
acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la 
persona a la que va dirigido, cualquier divulgación, copia o distribución de 
la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción 
tomada o dejada de tomar basada en la información contenida en este mensaje 
queda prohibida y puede ser ilegal.
The information in this e-mail is confidential and may be legally privileged. 
It is intended solely for the addressee. Access to this e-mail by anyone is 
unauthorised. If you are not the intended recipient, any disclousure, 
copying, distribuition or any action taken or omited to be taken in reliance 
on it, is prohibited and may be unlawful.