2022-10-14 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Oct 14, 2022
2 min read

Oct 14, 2022

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

Attendees

  • @Ain Aaviksoo (Deactivated) (meeting facilitator)

  • @Philippe Page (not attending)

  • @Lal Chandran (not attending)

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

  • @sasi

  • @PSRAMKUMAR

  • Maksim

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Intro of Maksim (new Consent BB group member)

Maksim

 

Follow-up on previous Action Items (Fixed)

Meeting facilitator

 

Test plan update (5 min)

@Ain Aaviksoo (Deactivated)

Update from new weekly test meeting

Stepping through
Step 3 necessitates a decision about where

Consent BB is “generic”, it does not just exist for MCC servince. Registration should happen with reference to an existing foundational ID, bu

ID BB has its own UI for all user inputs, this is never delegated (a decision was made)

Open discussion: How should Consent BB as-is integrate with the 3rd step. Do we need to change APIs already now or can we find a fit with the existing APIs?

Questions raised

Maksim

When will procurement happen exactly and how will we be able to have changes introduced if it’s already in November?

Next meeting

 

Rachel will hopefully visit in or after the meeting to introduce GitBook

 

 

 

 

 

 

 

 

 

 

 

 

 

Action Items

Book Rachel @Ain Aaviksoo (Deactivated)
Prepare Gherkin intro @Benjamin Balder Bach
Request read/write permissions to Maksim for Jira/Confluence etc: maksim.ovtsinnikov@gmail.com
Organize additional team meeting for resolving step 3 of @Ain Aaviksoo (Deactivated)

Action Items from last meeting

Add comment in API somewhere to clarify its maturity @Benjamin Balder Bach
Link up with new test lead, Satyajit Suri @Ain Aaviksoo (Deactivated)
Background in testing, pending alignment with Satyajit Suri, we will present an intro to the test strategy and how we can deliver @Ain Aaviksoo (Deactivated) @Benjamin Balder Bach
Writing workshop: Pending input from Satyajit Suri, @Ain Aaviksoo (Deactivated) and @Benjamin Balder Bach prepares a test scenario workshop
Release API 1.0.0 @Benjamin Balder Bach

 

Decision