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)
Benjamin Balder Bach (weekly note keep and time keeper)
Meeting Note
Agenda | Presenter | Discussion |
|---|---|---|
Action points from last week | ||
Standup on Sprint 1 results 10min | ||
Schema updates | https://github.com/GovStackWorkingGroup/bb-consent/pull/30 | |
Dividing tasks for Gherkin scenario writing | all-hands | |
Planning next sprint - should contain also starting with “Spec v2” (@all) | all-hands | |
Community outreach blog-post | CON-71 - Getting issue details... STATUS |
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 inviteAin 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.