2023-05-23 - Weekly update

Owned by Benjamin Balder Bach
Last updated: May 26, 2023 by Ain Aaviksoo (Deactivated)
3 min read

May 23, 2023 (postponed)

About this document: Agenda and notes are kept in the same document, a separate copy of the document is maintained for each meeting. Please add agenda points before the meeting. Action items created in previous meeting and all other unresolved action items are kept in the document. Please tick off any completed items.

Meeting link: https://meet.google.com/rsf-cqaq-eyq at 07:30 UTC / 09:30 CET / 13:00 IST

Attendees

  • @Ain Aaviksoo (Deactivated) (meeting facilitator; meeting note keeper as Benjamin was in the train today)

  • @Benjamin Balder Bach (weekly note keeper and time keeper)

  • @PSRAMKUMAR

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

 

Updates from TC meeting (fixed)

@Ain Aaviksoo (Deactivated)

We are in dialogue about how we find solutions that can match our specification. Consent BB doesn’t have any candidate real-life products, so we need to figure out if there is much we can do. Suggestion to reach out to MOSIP.

Gherkin scenario writing discussion

 

Review necessary Gherkin scenarios to implement

@Benjamin Balder Bach

https://govstack-global.atlassian.net/browse/CON-15

Payment BB’s account mapper

@Benjamin Balder Bach

Ramkumar: 2 guiding factors for all BBs might emerge

1) Any sensitive data that is key to the BB, responsibility will be allocated to the BB.
2) UI is not outsourced to other BBs - IDBB will not outsource UI to other BBs.

Our remark to 2) will come after reading the draft principles of Consent UI presented by the UI/UX team.

A lot of BBs are looking for a way to include their UI requirements/principles. UI/UX team is looking for examples.

IDBB sync-up

@Ain Aaviksoo (Deactivated)

 

 

 

 

Spec 2.0: Unfolding new roadmap items

 

 

New issues

@sasi

parked for future meeting

  • What do we expect other BBs that call Consent-BB to store?

  • When do we like to use Consent-BB and when do we not expect this? (This should also be know to the auditor.)

Discussion: How shall we address such matters, which do not fit into specification format?

 

 

 

 

 

 

 

 

 

 

 

 

New Action Items

UI/UX draft for consent ideas @Ain Aaviksoo (Deactivated)
Clean up Kanban board to have only active issues in progress @Ain Aaviksoo (Deactivated) @Benjamin Balder Bach
Make Jira board look nice for anyone that wants to contribute @Ain Aaviksoo (Deactivated)
Have someone send out @Ain Aaviksoo (Deactivated)
Update testing overview with latest figures @Benjamin Balder Bach
Review this: @Ain Aaviksoo (Deactivated)

Action Items from previous meetings

@Ain Aaviksoo (Deactivated) add and maintain definitions for subjects of Gherkin scenarios
@Philippe Page sign up to GitBook via GitHub or tell @Ain Aaviksoo (Deactivated) what your existing signup email is.
@Ain Aaviksoo (Deactivated) consider if the decision to have “external ID” and “external ID type” referencing Individuals is relevant for the Key Desicion Log (if it’s not already there)
@Philippe Page will finish the initial descriptions and commit himself to the ones he feels appropriate
@sasi will articulate in these questions to be addressed
(the group can then address them and decide where and how their later proper “place” will be)
Add to ticket with the links to relevant discussion by other groups @Ain Aaviksoo (Deactivated)
@Ain Aaviksoo (Deactivated) will add to
@PSRAMKUMAR to review the GitBook PR Ain created
to write the outcome of discussions with @Philippe Page 2w ago @Ain Aaviksoo (Deactivated)
Open Jira issue: Epic for Internal Workflows, tasks for each internal workflow @Benjamin Balder Bach
Open Jira issue: Epic for Universal Social Cash Transfer @Benjamin Balder Bach See CON-2 + Cross-reference TECH Jira tickets about the same.
@Ain Aaviksoo (Deactivated) identify a process to give feedback and guidance to the use cases analysis lead by the sandbox team
Review and indicate if an answer is accepted @Ain Aaviksoo (Deactivated) @Philippe Page
Review @Ain Aaviksoo (Deactivated)

Decision

  1. Onboard new members in 1:1 interviews - if it scales. If there is too much interest, we pick a different model.