2022-12-20 - Weekly Update (rescheduled)

Owned by Benjamin Balder Bach
Last updated: Dec 20, 2022
2 min read

Dec 20, 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

  • @Lal Chandran (out)

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

  • @sasi (out)

  • @PSRAMKUMAR

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

 

Next meeting? (how long seasonal break?)

@Ain Aaviksoo (Deactivated)

Benjamin put this item here to know when we are starting again and what people’s general bandwidth is during the seasonal break.

First meeting 2023: Friday January 6th

Roadmap update for wave 2

@PSRAMKUMAR and @Ain Aaviksoo (Deactivated)

New use cases are coming in. A small informal meeting can resolve what is interesting to Consent BB in the new use cases. Yolanda is setting up the first reviews.

 

Standup on Sprint 1 results 10min

@Ain Aaviksoo (Deactivated)

https://govstack-global.atlassian.net/jira/software/c/projects/CON/boards/34?view=detail&selectedIssue=CON-26

Dividing tasks for Gherkin scenario writing

all-hands

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

Scenario drafting document:

We should identify all major features+scenarios from our sequence diagrams.

Try to use Slack for communication during this process, rather than Confluence comments - the workflow with Confluence is invisible to others and rather slow.

“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

@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

Action Items from last meeting

Move weekly meeting series to 9 AM CET
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

  1. Gherkin scenarios focus on the “correct” behavior of actors and users. The “incorrect” or malicious behavior of systems and actors are tracked later.
  2. We maintain actors terminology for our Gherkin work and add anything outstanding to the specification afterwards
  3. Find good excuses to do Gherkin rather than holidays