Nov 25, 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 (out)
@Lal Chandran (out)
@Benjamin Balder Bach (weekly note keep and time keeper)
@sasi
@PSRAMKUMAR (out)
@Maksim Ovtsinnikov (out)

Meeting Note

Agenda	Presenter	Discussion

Agenda	Presenter	Discussion
Action points from last week	@Ain Aaviksoo (Deactivated)
Sprint status review	@Ain Aaviksoo (Deactivated)	https://govstack-global.atlassian.net/jira/software/c/projects/CON/boards/34/backlog?view=detail&selectedIssue=CON-62&issueLimit=100
Reminders	Watch the GitBook trainings Onboarding docs - do you have access to all platforms and the respective Consent project spaces? GitBook, GitHub, Slack, Jira, Confluence?
Schema updates	@Benjamin Balder Bach	https://github.com/GovStackWorkingGroup/bb-consent/pull/30
GitBook “in review”	@Benjamin Balder Bach	Lets review together as an example?
Gherkin scenario writing	all-hands	Can we hash out some .feature files with a set of (generic!) scenarios that are relevant to the MCC registration use-case? (details can be added later) We went through a Gherkin Feature that Ain is drafting. PUSHED TO NEXT MEETING

Action Items

Prepare suggestion for adjustments to avoid Consent Records pending signatures needing to be stored in the system @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

Decision

Everyone are highly encouraged to reach out to experts that could be interested in reviewing our specification.
We agree to @sasi’s suggestion that Consent Records pending signature should not be stored in the system.
We will need to adjust API endpoints, schemas and call sequences.