Review pending action items

@Esther Ogunjimi

10 minutes

https://govstack-global.atlassian.net/browse/TECH-654

• ID BB (2)

• Messaging BB (2)

https://govstack-global.atlassian.net/browse/TECH-670

• Consent BB

• Payment BB

• ID BB

Status Update

Leads

30 minutes

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

Testing team

The team is focusing on test reviews and have identified a huge need to do API schema reviews. Technofort work was also reviewed, there are some discrepancies and issues identified - some improvements are being implemented.

There is progress on the compliance form development; a schema is defined. Backend development is in progress and front end development will commence next week.

Sandbox Team

The team is still working on the integration of BBs

Work is ongoing on user interface for the online building permit use case

Working on polishing documentation as a grid with the product owner

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

Steve - API definitions as they exist today in the specs are not complete. This is part of the value of the sandbox, and the value of our country engagement work is to see where the gaps are and address them.

The API specs will continually be expanded and refined for building blocks. For instance, if ID BB needs to call payment BB or vice verse and we do not have the right API, then, payment BB and ID BB can work together to develop that new API and put it into the spec; that is the process that should happen. This type of conversation can happen first in the sandbox meetings and for cross cutting topics, it can be an agenda item to be discussed in TC to engage with different BB Leads.

Wes - Re. specification structure. We are going make changes to the template after the next release.

• API review issues are tracked here: https://govstack-global.atlassian.net/browse/TECH-942

API review recap - Soldevelo team went through all of the building blocks API definitions that are currently in the spec and identified gaps and things that were missing. Not everything that was flagged needs to be addressed right away for the next release. However, there are a lot of important things that the building block teams need to look at to make their API specs better, more consistent, and ensure that there are not major gaps.

Steve will standardize the specification format - converting everything to use camel case. Camel case can be used between both the URL endpoints as well as the data payloads of the data structures within those.

Inclusion of new software in GovStack Working Group

@Steve Conrad

15 minutes

How do we manage the BB software that has been contracted by GovStack?

The standard process for onboarding products into Gov Stack will be to go through the the testing harness and the compliance process where we work with an existing DPG to create adaptors and onboard them into the testing harness, then bring that DPG into the sandbox. For the products that have been implemented specifically for GovStack, they should live in repositories that are created under the GovStack umbrella.

For the contracted team, are they willing and able to host those GovStack compliant applications in their own repositories? Under the organisational umbrella that they represent and keep them for maintenance over the long term?

Rachel - if a contributing party, maybe a partner has commissioned a piece of software that helps with GovStack and it is not central to what GovStack is about, it should be owned and hosted on the resources of that contributing party.

David - Improvements have been made to an existing open source DPG to work with GovStack. It will make sense for providers to keep those in their repos

Meeliz - The source codes need to be open and stated clearly in the contract that they have to be reusable, and openly downloadable with obligation to validate yearly with the new version. GS might not be able to maintain and update all those features software which were onboarded during the project initiative.

Alek - Suggest repo naming to avoid clashes on names.

Egypt deep dive

@Steve Conrad

10 minutes

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