Payment Manager Adoption

[lewisdaly]

Request Summary:

Mojaloop Community adoption of Payment Manager

Request Details:

• Deadline: <When do we need a decision by?>
• Impact (Teams): <If your proposal is accepted, what team(s) will be affected by it?>
• Impact (Components): Mojaloop SDK,

DA TODOs:

• [ ] review the documentation (all)
• [ ] review docs related to constructing new Connectors (from hackathon participant's perspective @MichaelJBRichards)
• [x] conduct a OSS Scan on dependency vulnerabilities, libraries (@lewisdaly, @godfreykutumela )
• [ ] detailed code review (@lewisdaly, @pedrosousabarreto )
• [ ] Run the docker-compose version: https://github.com/pm4ml/on-premise-deploy

Issues raised by the DA to be addressed by Payment Manager Team

• [ ] Repository naming conventions - concern about adding 25 new repos to the Mojaloop org
• [ ] Fork of the Mojaloop SDK must be merged in before Payment Manager can be adopted
• [ ] E2E tests - how are they run? What is their scope? Are they automated?

Post-Adoption Followup

• [ ] Unit test coverage for individual repos

Artifacts:

• [ ] Payment Manager github org: https://github.com/pm4ml/
• [ ] Docs: https://pm4ml.github.io/documents/payment_manager_oss/latest/index.html

Dependencies:

• [ ] If Applicable

Accountability:

• Owner: @lewisdaly
• Raised By: @lewisdaly

Decision(s):

- **Approved By:** ### Details - [ ] Actual decision made as a result of discussion ## **Follow-up**: - [ ] Actions to implement the decisions

[godfreykutumela]

What is the status of this issue! @lewisdaly @MichaelJBRichards

[elnyry-sam-k]

Update on 8th June:

DA feedback provided on two items below, but this is also blocked by #86

1. Needs documentation of repositories as there are a good number of repos
2. Needs tests added to follow normal Mojaloop OSS guidelines on test coverage (90% at unit testing level)

[MichaelJBRichards]

@MichaelJBRichards will report to Product Council that issue 85 has been closed on the grounds that the issue is well understood, and the work consequent on our decision has no firm timetable. We will suggest a meeting of Product Council to consider how matters should proceed. @PaulGregoryBaker will present to Product Council, if required, on the state of play and the options available, and they will decide on the best course of action.