2023-06-16 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Jun 23, 2023 by Ain Aaviksoo (Deactivated)
2 min read

Jun 16, 2023

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

  • @Philippe Page

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week (fixed)

@Ain Aaviksoo (Deactivated)

 

Jira Kanban update (fixed)

@Ain Aaviksoo (Deactivated)

 

Testing plan

@Benjamin Balder Bach

We have a testing plan in draft, it will be informative to SolDevelo. It’s not based on other BB’s test plans (we haven’t seen any, but @Benjamin Balder Bach will ask ind hindsight).

CON-16: Test plan by benjaoming · Pull Request #47 · GovStackWorkingGroup/bb-consent

Update on testing development

@Benjamin Balder Bach

Update:

  • New additions to testing and mock application

  • Improved structure

  • Discovered and fixed a systematic error in OpenYAML specs.

TODO:

  • Move focus 100% to WRITING Gherkin scenarios

  • SolDevelo ONLY implements scenarios that we write.

  • We start with configuration

  • Timeline is to handover Gherkin scenarios ready for implementation mid-week.

  • Gherkin scenarios will be written in this order:

    • configuration APIs

    • service APIs

    • auditing APIs

  • …this means there’s a natural progression of complexity.

  • @Philippe Page will start with auditing in parallel.

Future collaboration with a tender

Skipped

Note-keeper: @Ain Aaviksoo (Deactivated) you fell out of the meeting, but I talked to Ramkumar about the task that we have ahead of us: Understanding how we want to govern specification work as a WG once that a tender starts to actively work on a candidate application. I’ll put it here for the next meeting, and it sounds like @PSRAMKUMAR already knows how WGs should function in this setting.

Updates from TC meeting (fixed)

@Ain Aaviksoo (Deactivated)

Authentication and Cross-BB Authorization
We should give feedback to this document.

Gherkin scenario writing discussion (ongoing)

Skipped

Gherkin Scenario drafting document

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

Action Items from previous meetings

@Ain Aaviksoo (Deactivated) add and maintain definitions for subjects of Gherkin scenarios
@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 Consent BB FAQ these questions to be addressed
(the group can then address them and decide where and how their later proper “place” will be)
to write the outcome of discussions with @Philippe Page 2w ago @Ain Aaviksoo (Deactivated)
Review Consent BB FAQ and indicate if an answer is accepted CON-135: Review Consent BB FAQ and indicate if an answer is acceptedIn Progress @Ain Aaviksoo (Deactivated) @Philippe Page
Have someone send out Call: Experts for GovStack's Consent Working Group @Ain Aaviksoo (Deactivated)
Deceptive pattern review @Benjamin Balder Bach @Laurence Berry (we exchanged a few links and ideas during the final UX spec writing)
Formulate questions to Payment BB about account mapper @Benjamin Balder Bach
Give feedback to Authentication and Cross-BB Authorization @Ain Aaviksoo (Deactivated)
Present mock application to sandbox team Liaise with sandbox team @Benjamin Balder Bach
Put Consent BB on the agenda for today’s testing meeting @Benjamin Balder Bach

Decision

  1. We adopt the test plan in order to present it later: https://github.com/GovStackWorkingGroup/bb-consent/pull/47#pullrequestreview-1482962434