Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Attendees

Allan Bernard Artun Gürkan PSRAMKUMAR Vasil Kolev Satyajit Suri Nico Lueck Meelis Zujev (Deactivated) Aleksander Reitsakas Steve Conrad Valeria Tafoya Nico Lueck Damian Borowiecki (Deactivated) Paweł Gesek David Higgins karim.jindani Kibuuka, Arnold Laurence Berry

Agenda

Presenter

Duration

Discussion

Review pending action items

 

 10 minutes

 

https://www.youtube.com/watch?v=4ASKMcdCc3g

 

TECH-654 - Getting issue details... STATUS

TECH-670 - Getting issue details... STATUS WIP

Messaging BB candidate: Rapid pro. Discussion on adaptation requirements underway

TECH-742 - Getting issue details... STATUS

Status Updates

Leads

30 minutes

https://www.youtube.com/watch?v=Xk24DMOInnQ

https://govstack-global.atlassian.net/jira/plans/reports/6EFAz

Wave 3 specifications update - PSRAMKUMAR

Sandbox team

Working to integrate BB into the UC and collaborating with BBs

Working Djibouti UC

Publish simulation on public channel next week

Architecture team

Addressing infrastructure using kubertes - how to deploy the infrastructure

Authorisation - how to associate users with roles.

Vasil - not knowing what is connected to BBs is over simplified and this will be discuss at the architecture meeting tomorrow.

Steve -

Capability definition

Artun Gürkan

15 minutes

https://www.youtube.com/watch?v=u_BcMXgws6Y

23-07-12 Introducing Idea of Service Blocks (Capabilities)

Testing and Integration

PSRAMKUMAR

20 minutes

https://www.youtube.com/watch?v=kxGWsHYITAw

Questions from testing team:

Should we establish two separate types of test suites for BBs in corresponding folder - /mocks and /emulator of corresponding github folders. Question who will develop mocks and who will develop emulators - prioritized roadmap

  • Are emulators use-case specific? 

  • DPG compliance :  is 100% API coverage essential for a DPG to qualify? What if based on a specific usecase, a partial set of APIs are needed and a DPG is fully complaint to those but not all of the APIs of the BB spec? Should compliance need to be qualified in relevance to a Use-case or not ? Should we have  use-case based test suites in addition to  maintaining a full test suite?

  • Building a generic adapter that can transform any payload based on a JSON schema mapping input output name fields and format. Developing a simple tool to map field names and generate the JSON schema for different adaptations.

  • Testing UI level switching between BBs

How we converge on a common format for RegisteringInstitutionID

karim.jindani

15 minutes

https://www.youtube.com/watch?v=u_BcMXgws6Y&t=65s

This is essential to be defined for consistency in the spec. So that all BBs are aligned especially in the case of multiple Institutions or Gov Entities on an instance.

Action Item

  • Esther Ogunjimi to message wave 1&2 to populate the Future consideration epics with tasks
  • Put review tasks in Jira

  • No labels