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

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: HR Attendance - Performance Issue in "Theoretical vs Attended Time Analysis"

Re: HR Attendance - Performance Issue in "Theoretical vs Attended Time Analysis"

Avatar

Re: The future of oca/bank-payment

by
Datenbetrieb Technologie UGh, Peter Niederlag
- 03/04/2025 11:29:57 
Hi,

thx for all the passion and patience everythin puts into finding a 
responsible way to pave the road to the future.

As a newbie I can't participate in the discussion due to a lack of 
knowledge.

If no general agreement can be found I'd vote for a good 
communication-strategy that avoids the "f"-word in favor of opinionated 
branching/repos under the umbrella of OCA with the message and strategy 
of "-legacy" vs '-enterprise-compliant" or "-next" and the freedom of 
choice for the users. No agreement should result in free 
choice/competition for the users while clearly explaining the users of 
the two different approaches.

Everyone heading in the very same direction probably would still be the 
best option of all.

best regards,
thx to all you people strengthening the open source way of getting 
things done,
Peter



On 02.04.25 21:36, Virginie Dewulf wrote:

> Hello contributors,

> Thanks for sharing your opinions on this important topic.

> *Proposed next steps:* A

> continuous chain of emails won't help to find a common solution. With

> the "Community Health" WG, I propose to organize an online meeting with

> the concerned parties to find a way towards an agreement. Luc's

> suggestion of having a few days together is a good one, if there is no

> agreement online. The Spanish Odoo Days will be held in June soon: this

> could be a good opportunity.

> The result of the meeting will be shared in this thread to keep a public track of the conversation.

> *A reminder of our intention as a community* We

> are all on the same team, trying to find an open source way in the Odoo

> ecosystem that changes every year. I sometimes picture Odoo S.A. as a

> big and super fast boat on the sea of ERPs. The OCA is a gathering of

> hundreds of small little sailboat (=our PSC teams responsible for

> managing several repos), trying to follow the wind and stay together as

> much as possible. But it is sometimes really hard and chaotic (like with

> the account apocalypse in v13).

> *The underlying problematic of this discussion* Here

> we have an important question: who is the captain of this specific

> sailboat? As each part of the sailboat has been built by a different

> contributor and sometimes taken care for several years by another, who

> has the legitimacy to decide of the future? Or isn't something we can decide by principle and we might need to have a process to decide for each situation?

> This is the

> question that we will need to answer as a community, because those

> discussions happened in the past and will continue to arise. And to not

> loose our time and energy on fighting between each others, we will need

> proper governance guidelines on this.

> This will be a task for the

> Governance Working Group in the next months, with a proposition to be presented to the Delegates for the 2025 Annual General Assembly in autumn

> in a newer version of the PSC-guide [1] (which at the moment mention nothing about process to find an agreement).

> Enjoy your week!   Virginie Dewulf Executive Director  Odoo Community Association [2] (OCA) +32 477 64 17 20

> Le mer. 2 avr. 2025 à 11:52, Enric Tobella Alomar < notifications@odoo-community.org [3] > a écrit :

> I know that Alexis did a massive job in the past, but if we check the contributors information provided by github we get the following that the main contributor is Pedro.

> https://github.com/OCA/bank-payment/graphs/contributors [4]

> Also, it is similar if we check the collaboration data extracted from the PRs. In the last 5 years the Top 15 is the following:

> User

> Created PRs

> Merged PRs

> Comments

> Reviews

> OCI

> pedrobaeza

> 49

> 49

> 776

> 539

> 623

> victoralmau

> 72

> 68

> 38

> 64

> 147

> HaraldPanten

> -

> -

> 93

> 80

> 90

> alexis-via

> 41

> 22

> 84

> 48

> 86

> carlosdauden

> 9

> 8

> 12

> 60

> 74

> ValentinVinagre

> 5

> 5

> 40

> 49

> 63

> sergio-teruel

> 5

> 4

> 11

> 35

> 45

> luc-demeyer

> 26

> 14

> 38

> 15

> 40

> joao-p-marques

> 12

> 12

> 19

> 18

> 38

> etobella

> 16

> 15

> 14

> 12

> 35

> ramiadavid

> 11

> 10

> 9

> 19

> 35

> Tisho99

> 15

> 15

> 24

> 10

> 34

> MiquelRForgeFlow

> 12

> 11

> 16

> 15

> 33

> rousseldenis

> 7

> 4

> 28

> 19

> 31

> StefanRijnhart

> 5

> 4

> 20

> 20

> 31

> It is obvious that he is involved a lot in this repo, but there is a group of main authors. If we check data, Alexis is not "the main author", he is one of the main authors.

> Kind regards,

> El mié, 2 abr 2025 a las 11:17, Stéphane Bidoul (< notifications@odoo-community.org [5] >) escribió:

> On Wed, Apr 2, 2025 at 6:52 AM Enric Tobella Alomar < notifications@odoo-community.org [6] > 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 [7] ) 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

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [8]

> Post to: mailto: contributors@odoo-community.org [9]

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [10]

> 

> --

> *Enric Tobella Alomar* CEO & Founder

> www.dixmit.com [11]

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [12]

> Post to: mailto: contributors@odoo-community.org [13]

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [14]

> 

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [15]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [16]

> 

> 

> 

> [1] https://odoo-community.org/about/psc-guide

> [2] https://odoo-community.org/

> [3] mailto:notifications@odoo-community.org

> [4] https://github.com/OCA/bank-payment/graphs/contributors

> [5] mailto:notifications@odoo-community.org

> [6] mailto:notifications@odoo-community.org

> [7] https://github.com/OCA/bank-payment/pull/1439

> [8] https://odoo-community.org/groups/contributors-15

> [9] mailto:contributors@odoo-community.org

> [10] https://odoo-community.org/groups?unsubscribe

> [11] http://www.dixmit.com

> [12] https://odoo-community.org/groups/contributors-15

> [13] mailto:contributors@odoo-community.org

> [14] https://odoo-community.org/groups?unsubscribe

> [15] https://odoo-community.org/groups/contributors-15

> [16] https://odoo-community.org/groups?unsubscribe

> 

mit freundlichen Grüßen,
Peter Niederlag

-- 
Dipl. Ökonom Peter Niederlag
Geschäftsführender Gesellschafter

Lösungen für digitale Zeiten
Agile DevOps, Cloud, TYPO3, Odoo und Linux

Datenbetrieb Technologie UG(haftungsbeschränkt)
Lipper Hellweg 146,  33605 Bielefeld
Geschäftsführer: Peter Niederlag
HRB 41826 Amtsgericht Bielefeld
Fon 0521 / 446 958 60
Fax 0521 / 446 958 69

Reference