2023-11-10 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Nov 10, 2023
2 min read

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 ordinary starting time at 07:45 UTC / 09:45 CET / 13:15 IST

Attendees

  • @Ain Aaviksoo (meeting facilitator)

  • @Benjamin Balder Bach (note keeper)

  • @Lal Chandran (out)

  • @PSRAMKUMAR

  • @Philippe Page

  • @George J Padayatti

Meeting Notes

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Kanban board + Action points from last week

@Ain Aaviksoo

skipped

General update (5 min)

@Ain Aaviksoo

 

Candidate API spec improvements

@Ain Aaviksoo

What areas from DDX API spec are likely to be highly compatible with the BB Spec/Future roadmap:

  • Organizational entities

  • Onboarding

  • Administrative UI backend

Status updates

 

  • Sandbox

  • Test harness

Finalizing changeset

@Benjamin Balder Bach

There shouldn’t be anything left, but it’s unclear whether anyone had intentions of giving more inputs? https://github.com/GovStackWorkingGroup/bb-consent/pull/65

@George J Padayatti and @Benjamin Balder Bach confirms that there are no known gaps between the API specs.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Consent delegation

skipped

Review necessary Gherkin scenarios to implement

@Benjamin Balder Bach Skipped

CON-15: Create test configuration for Consent Configuration APIsIn Progress

Spec 2.0: Unfolding new roadmap items

Skipped

 

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

Understand roadmap of Testing team and if Test Harness-related items will be solved @Ain Aaviksoo - flag Satya

Action Items from previous meetings

@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
@Benjamin Balder Bach Prepare fixtures review for Lal
@Benjamin Balder Bach Finish translating SolDevelo’s review into issues (added after-the-fact)
@Ain Aaviksoo will coordinate with Sandbox team - note that Lal is requesting and end2end use case.
@Ain Aaviksoo coordinate with testing team re: DDX and API tests
@Ain Aaviksoo setup a meeting around 9 november
@Ain Aaviksoo confirm first DDX deliverable
@Ain Aaviksoo will reschedule next week’s Friday meeting to 2PM CET
@Benjamin Balder Bach solve a million Jira issues and do not let Ain have all action items alone

 

Decision

  1. Everything in the “main” branch is considered stable and can be depended on by DDX and testing team. Meaning that nothing to be considered premature or draft-like is added to APIs moving forward.