2023-06-09 - Weekly update

Owned by Benjamin Balder Bach
Last updated: Jun 15, 2023
3 min read

Jun 9, 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

  •  

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

Updated the list

Jira Kanban update

@Ain Aaviksoo (Deactivated)

Let’s make this fixed!

How should we scope efforts for sandbox deliverables

@Ain Aaviksoo (Deactivated) @Benjamin Balder Bach

@PSRAMKUMAR

We need to be sensible about how much to extend the mock application in order to ASAP accommodate.

  • We need to stop developing the mock application at the point of overlapping too much with the future candidate application.

  • What is remaining in specification work that we need to be deciding in the WG in order to accommodate in the sandbox. We should definitely prioritize that as a team.

  • Niko is doing the sandbox roadmap, Satya is doing PM.

  • We need to continue developing inputs for the sandbox team to avoid (further) misunderstandings about how consent works.

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

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

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 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 @Ain Aaviksoo (Deactivated) @Philippe Page
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 Call: Experts for GovStack's Consent Working Group @Ain Aaviksoo (Deactivated)
Update testing overview with latest figures API Testing - status across BBs @Benjamin Balder Bach
Review this: https://github.com/GovStackWorkingGroup/bb-consent/pull/38 @Ain Aaviksoo (Deactivated)
Deceptive pattern review @Benjamin Balder Bach @Laurence Berry
Formulate questions to Payment BB about account mapper @Benjamin Balder Bach

Decision

  1. We will reach out to SolDevelo for building more test integration and implementing more aspects of the Mock Application.