| |
|---|
Meeting Frequency, Communication and Collaboration | Transition from weekly to bi-weekly meetings. The primary focus of the meetings is technical coordination and resolving integration issues. Proposal for dedicated contact persons for each building block for more efficient problem-solving. Use of Slack channels and other platforms for ongoing communication.
|
Compliance and Specification | Concerns about building blocks not being fully compliant with Gov Stack specifications. Issues with API versions and their impact on the use case. The need for building blocks to be use-case agnostic, and a challenge to this assumption.
|
Clarity of Roles and Timelines | The sandbox team is responsible for designing and implementing the USCT use case. The building blocks should be compliant with GovStack specifications, which should be use-case agnostic. Questions about the readiness and compliance of building blocks. The need for a clear timeline for when building blocks will be ready and compliant. Concerns raised about the lack of clear deadlines for delivering working installations in the playground and sandbox environments. This is crucial for resource planning. Roles of the "playground" and "sandbox" environments were clarified. The playground is for initial deployment and learning, while the sandbox is for more formalized, automated procedures.
|
Technical Issues | API instability and non-responsiveness. Concerns were raised about the integration of different building blocks, including identity, payments, and consent. Issues like versioning and callbacks were mentioned. Last-minute changes in API specifications causing disruptions. Need more agile ways of working to expedite the integration process. The need for bilateral meetings to resolve specific issues. Need for dedicated personnel from the BB partners to assist with API integration. Mifos acknowledges the need but expresses reservations due to resource constraints. BB’s to provide demonstration to Sandbox teams on how to use the APIs as an immediate next step before diving into hands-on coding workshops. With regards to the Mifos deployment on the Sandbox, the team has a lack of clarity regarding which version of the specification the team should be developing against. David clarified that the team is developing to the spec agreed upon by the payments Working Group, which is not the one that will become V2 in September. The version in use is 1.4, as per PI2 documents. Concerns about the version that was signed off not working as expected in the sandbox environment. Concerns expressed on inconsistencies in API documentation (David to check back with the relevant team for clarification and correction.) Discussion around the ability to do fresh deployments based on learnings from the playground and the need for testing before implementation.
|