1. Mailing Lists
  2. Contributors
  3. Re: The future of oca/bank-payment

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: The future of oca/bank-payment

Re: The future of oca/bank-payment

Avatar

Re: The future of oca/bank-payment

by
Acsone SA/NV, Stéphane Bidoul
- 02/04/2025 11:11:42
On Wed, Apr 2, 2025 at 6:52 AM Enric Tobella Alomar <notifications@odoo-community.org> wrote:
I reviewed the video. And it doesn't change my position. I think that it is an overengineer work to do something that is more natural with the current system. I don't see the real benefits of the change, as the current system does it properly with a more direct and simple approach. I think we should end this discussion soon in order to get a solution for 18 soon. 

I reviewed the account_payment_partner PR (https://github.com/OCA/bank-payment/pull/1439) and commented to explain again the drawback of keeping payment modes.

That PR hides the standard fields behind a group, but if for any reason someone needs to use the standard fields, they end up with a very confusing user interface with duplicate Payment Method/Mode fields with almost identical names and meanings on partners and invoices.
If we want to continue using payment modes, we need a better solution to that problem.
 
My proposal would be the following: Merge the modules migrated by Tecnativa. Create a separate system for your proposal (we could create a separate repo if you prefer).
 
I still hope we can converge. But if we can't, the way to fork is certainly debatable.

In "normal" open source projects, the main authors ensure the steering, and if some users are not happy with the direction taken they can fork.
In that view, asking the main author (arguably Alexis in this case) to fork himself is a bit awkward.

Best regards,

-Stéphane

Reference