2022-12-02 - Weekly Update

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

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

  • @PSRAMKUMAR

  • @Maksim Ovtsinnikov (out)

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

 

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

Schema updates

@Benjamin Balder Bach

Consolidates endpoints and schema with latest meetings on UC-Post-Partum-001-Registration_PostPartum_and_InfantCare by benjaoming · Pull Request #30 · GovStackWorkingGroup/bb-consent

Do we keep endpoints for creating ConsentRecord and Signature the former way? Or do we only support the method decided at last meeting? Decided yes.

Dividing tasks for Gherkin scenario writing

all-hands
Moved to next meeting

See: Gherkin Reference - Cucumber Documentation

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

all-hands
Moved to next meeting

 

Community outreach blog-post

@Ain Aaviksoo (Deactivated)

CON-71: Blogpost for community outreachDone

Action Items

Book working group for an extended hour of Gherkin Scenario writing for next Friday’s meeting. @Ain Aaviksoo (Deactivated)
Executing the new decision of removing API endpoints and finish up related Jira issues, taking Sasi’s input from the end of the meeting into account @Benjamin Balder Bach

Action Items from last meeting

Lay out question Consent Record state “paradox” and forward through @Lal Chandran - @Benjamin Balder Bach
Set up Monday meeting and invite@Ain Aaviksoo (Deactivated)
Presentation of API endpoints, mocks and tests for technical committee meeting Thursday @Ain Aaviksoo (Deactivated)
Move last 6 sprint issues migrated from GitHub to the backlog @Ain Aaviksoo (Deactivated)
Everyone: Read email forwarded from Jaume about new IMBB
Prepare suggestion for adjustments to avoid Consent Records pending signatures needing to be stored in the system @Benjamin Balder Bach

 

Decision

  1. The now unused endpoints from the previous sequence of Consent Record signing will be removed.
  2. Input from Sasi after the end of the meeting is that we should make it easier for the external party that handles signature to know what to sign, making the payload construction internal for the Consent BB.