Review pending action items

@Esther Ogunjimi

10 minutes

TECH-654: Updates based on technical reviewDone

• ID BB (2)

• Messaging BB (2)

TECH-670: Candidate ProductsDone

• Consent BB

• Payment BB

• ID BB

Feedback from other participants. Please document any feedback/action items here: Egypt Deep Dive Takeaways

Post Release Priorities

@Wes Brown

What should GS priorities should be after the release?

Consent BB - to see more countries implementing GS and to continue updating the current spec.

@Ain Aaviksoo to send roadmap for post release to Wes.

Payment BB - Focus on user demo for govt to see how GS actually works. This will help us to build on other UCs as different govt may have different scenarios they might want to look at that are not in the current BB.

Use cases should be demonstrable for P2G in the sandbox environment from payment BB perspective.

Workflow BB - Making GS consumable for clients to experience and understanding where we are with test harness that has been built. This will help to address the gap in the workflow test protocol as there is no adaptors that are needed for the candidates application.

Sandbox team - Give people/govt the ability to experience BBs infrastructure.

More candidates around GovStack - this needs systematic approach to search OpenSource solutions which may fit under specifications. 

Some resources to assess and validate through certain use cases -  Practical knowledge which can be done by addressing country based community approach to test out these solutions.

Govstack procedures to become more agile ( decide>execute>evaluate > adopt).

Testing Team - Focusing on developing the compliance form and supporting the DPG's integration.

Summary

• Updates to specs based on feedback

• Facilitating usage and understanding of GovStack

• Testing/Compliance

  • Compliance tooling

• Additional software support/adaptors

  • Clear guidance and process

• Better (easier) support for local sandbox installations

• Ensure that high-value use cases (both reference and BB-specific) are well supported

• Streamline/Improve our internal processes

Status updates

Leads

30 minutes

• Issues to be addressed for release are tracked here: 23Q3 - W3 Tech Review Issues

Consent BB

• Almost done with API endpoints

Payment BB

• Spec will not ready for the next release until the Oct 18 as there few things that need to be added for the APIs.

Workflow BB

• Working on one API endpoint update

Sandbox team

Sandbox work will be ready to be part of the next publication.

Wes: Release notes should be high level with functional level features.

• Advance Roadmap

Sandbox Team

Team is working on QA account to test all BBs and their installation procedures. This will enable the team to be able to test BBs installation unattended from the building block vendor. This is to prove that all the documentation is sufficient and everyone can install it in their own environment.

Ongoing discussion on building blocks that can provide references and links to their internal user interfaces or something that is supposed to be published to manage interface. This is what we have to pose to the clients when they start to experience the building block infrastructure and this is not mandatory.

Currently, the team is finalising documentation to reflect the current state of the sandbox development including the new use cases.

Ongoing work with online building permit use case wireframe, the wireframe implementation will be connected to some mock services.

Testing team

Working on the compliance form, and the frontend work has started. Schedule with the milestones will be shared w/c Oct 16, 2023.

• API review issues are tracked here: TECH-942: 23Q3 API Review Proposed