Agenda

Presenter

Duration

Discussion

Review pending action items

 @Esther Ogunjimi

 10 minutes

TECH-654: Updates based on technical reviewDone

Status update

BB Leads

30 minutes

Scrum standup-style (what we did this week; plans for next week; blockers/pain points and open/unresolved questions?

• Specification 1.0 publication

TECH-615: Building Block Alignment to Template for 1.0 PublicationDone

• Workflow BB

  • Waiting for adaptor update

• Consent BB

  • API test harness work ongoing

  • Working on the next version of the specification - delegation of consent

• Payment BB

  • Working on defining how to use voucher for payment

• UI/UX BB

  • Working on Somalia UI/UX standards with Yolanda

• USCT use case definition TECH-225: Implement INST-1 - Unconditional Social Cash Transfer Use CaseIn Progress

  • Waiting for feedback to the comments before proceeding.

• Testing

  • Payment G2P API is completed

  • Completed the ID BB API 6 endpoints

  • Blocked by the endpoints that are UI dependent for ID BB and Payment BB voucher payment APIs

  • Finalised Digital Registries BB

How to define BBs consent service build in for discussion

@Ain Aaviksoo (Deactivated)

15 Minutes

The whole idea of GovStack is that discrete functions are maintained in separate BB-s and not lumped into super-BB’s

Open

Open

Identity BB APIs For decision

@Dominika Bieńkowska (Deactivated)

15 minutes

Some are dependent on UI and cannot be tested. How should we move forward?

Having issues with wallet and regarding tokens which should be set in the cookies; there is no assurance it will work with other software.

Taylor - recommending to hard code random value and wait on the candidate to come along, then the test can be modified.

Rachel - change the test, does that mean we also need a small amendment to the spec?

Dominika - it can be both ways; once spec is updated, and also update test.

AOB

@Rachel Lawson (Unlicensed)

https://govstack-global.atlassian.net/l/cp/1KwtHyMc

All BB Leads to read and add comments