2023-01-06 - Weekly Update

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

Jan 6, 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

Attendees

  • @Ain Aaviksoo (Deactivated) (meeting facilitator)

  • @Philippe Page

  • @Lal Chandran

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

  • @sasi

  • @PSRAMKUMAR

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

 

Timesheet

@Ain Aaviksoo (Deactivated)

Notice that GovStack has new individual reporting for timesheet & TOR. Yolanda has contacted people individually by email.

Updates from TC meeting

@Ain Aaviksoo (Deactivated)

New general compliance specification is out for review

A new tracking document is created (API Testing - status across BBs ), we aren’t asked to report back but Dominika and team monitors all Building Blocks. We’ll figure out some feedback or if we should add updates there since Consent BB appears incorrect.

New UX for compliance of API testing has been presented. We will go over it in another meeting.

  • Feedback and remarks to send back.

  • What metrics for compliance comparison to Consent BB?

 

 

 

 

 

 

Gherkin scenario writing

all-hands

See: https://cucumber.io/docs/gherkin/reference/

Scenario drafting document: Gherkin Scenario drafting document

Proposal for work mode:

  • Ain goes through scenarios

  • Benjamin goes over alignment with API spec

  • Philippe does final critical review

“Consent management” definition

@Ain Aaviksoo (Deactivated)
pushed to next meeting

We renamed “Consent Management BB” to “Consent BB”. Is there a useful definition of “consent management” that we can apply?

Planning next sprint - should contain also starting with “Spec v2” (@all)

all-hands
pushed to next meeting

 

Action Items

Next meeting: Feedback on API test reporting UX
Compliance concept - @Ain Aaviksoo (Deactivated)
Finish the first full draft of Gherkin scenario service APIs - @Ain Aaviksoo (Deactivated)

Action Items from last meeting

@Benjamin Balder Bach update Tracking Pipeline document
@Ain Aaviksoo (Deactivated) Introduce the Gherkin working document
@Ain Aaviksoo (Deactivated) catch up with Yolanda re: new use cases
@Benjamin Balder Bach and @Lal Chandran add latest IMAGE renditions of sequence diagrams.
@Ain Aaviksoo (Deactivated) and @Benjamin Balder Bach come up with major themes / features for Gherkin work
Presentation of API endpoints, mocks and tests for technical committee meeting Thursday @Ain Aaviksoo (Deactivated) Everyone: Read email forwarded from Jaume about new IMBB
Book Consent working group for an extended hour of Gherkin Scenario writing for next Friday’s meeting. @Ain Aaviksoo (Deactivated)

Decision