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
Tecnativa. S. L., Pedro M. Baeza
- 02/04/2025 11:45:31
> 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.

I hope all the problems we have in Odoo are of this difficulty ;)

2 easy solutions:

- With the existing group, hide the fields being added with this module with groups="!group" clause.
- Add another security group, so you can select both, one, another or none fields to be shown.

> 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.

I think he lost his rights not attending the project for years, being pinged continuously without any answer. Some non complete list of pings without answer:

https://github.com/OCA/bank-payment/pull/979#issuecomment-1304825620 (my large previous refactoring to use native account.payment object)

He has also refused several times to do forward-ports of his patches, or directly to not maintain the whole repository, because "he doesn't work on odd versions".

Regards.

Reference