Agenda

Presenter

Duration

Discussion

Review pending action items

 @Esther Ogunjimi

 10 minutes

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

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

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

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

UX Switching

@karim.jindani

15 minutes

https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/39QVhd0jD6S29Isr7KGF/architecture-and-nonfunctional-requirements/8-ux-switching - UX switching

Feedback from @Steve Conrad engagement with Registration and ID building block providers to confirm basic assumptions to move towards specifications.

Status updates

• Leads contract update

• Specification release progress - September

Lead

30 minutes

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

Testing team

• Finalising registration steps for Online Construction Permit

• Waiting for the final sign-off for the outreach communication steps

• The team did not get the final sign-off for the USCT and the data verification step from @Ingmar Vali

• Completed openIMIS integration

• Focusing on the improvement of the testing platform and the UX.

• Working on design for the compliance form.

Ramkumar - There should be visibility of how the UC is being broken down into BBs to ensure we are mapping the UCs with the right BBs.

Dominika - The stakeholders should be defined for the review process of the UC handover from PC to TC

Ramkumar - who is responsible for signing off the example implementation?

Wave 3

Steve - Based on the architecture review, tickets will be created in Jira for the updates required, and content in the specs that need to be changed.

Wes - there is no ample time to have a TAC review for the wave 3 specs as the release is due by the end of September. This next release will focus on receiving feedback from the external reviewers.

Messaging BB

The team will be working on the messaging bridges to the existing applications like WhatsApp, but this will be after the September release. There no changes that need to be added to the current spec for the September release.

Scheduler BB

Multiple event scheduler will be added to the spec but because of time constraints; this will not be part of the September release. However, Ramkumar will still send the changes to be included int he spec to Wes to review for post September release.

IM BB

There are errors identified in v1.0 of the specification. Alek will work to resolve these errors. The spec will have the same functionalities but without errors. Alek will get the changes into the spec on or before Aug 25, 2023.

Workflow BB

On future scope, it was decided by the team to incorporate the ability to surf a running instance. This is because the team does not want to add new updates to v2 as the spec already has a high quality and defensible surface area for the WF engine.

The change request to define the internal workflows of a workflow engine(WF 58). This change will give people the wrong idea to create new software. The team is hoping the spec will achieve a certain level of transparency and compliance at the API and flexibility. The team will not be working on this Jira ticket.

Release process

@Steve Conrad

15 minutes

Identify the requirements prior to September release

• Wave 3 specs are being reviewed by the architecture team.

• Steve and Wes will consolidate the review comments into Jira tickets

• All wave 1&2 changes should be in the next one week, so the review process can start.

• Valeria will work on the specs to ensure the language is consistency

• September release will include all the wave 1&2 spec, GIS, UX / UX, eMarketplace and eSignature spec.

Next UC

@Wes Brown

@Steve Conrad

10 minutes

Identify the next Use Cases to work on Use Case Discussions

• We have worked on the Unconditional Social Cash Transfer UC

• Online Construction Permit is almost done.

• Steve will work with the SolDevelo team on priorities.

AOB

Should we cancel next TC’s meeting because of the meeting in Egypt?

GIZ Partner project proposed to write Chatbot BB Specs alongside their second implementation in Kenya. Any doubts? Anything or anyone to consider when creating a WG of volunteers on this? @Nico Lueck

FYI, good news : Consent BB Specs are being used by Rwanda Gov and World bank in a RFP for a new new Single Digital ID system @Nico Lueck