2023-01-13 - Weekly Update
Jan 13, 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 at 09:00am CET
Attendees
@Ain Aaviksoo (Deactivated) (meeting facilitator)
@Philippe Page
@Lal Chandran (out)
@Benjamin Balder Bach (weekly note keep and time keeper)
@sasi
@PSRAMKUMAR
Meeting Note
Agenda | Presenter | Discussion |
---|---|---|
Action points from last week | @Ain Aaviksoo (Deactivated) |
|
Updates from TC meeting | @Ain Aaviksoo (Deactivated) | Feedback on Compliance Concept and Integration. Scenarios (link to Confluence page) (by Digit). Any impact on our API development? Feedback on “Architecture and Non-Functional Requirement” document (link in GitBook). A dedicated team is looking for volunteers to work on it over next 2 months. Tech Committee action items to all wave 1&2 BBs. New UX for compliance of API testing has been presented. We will go over it in another meeting.
|
Gherkin scenario | @Benjamin Balder Bach @Ain Aaviksoo (Deactivated) | Status update based on scenario drafting document: https://govstack-global.atlassian.net/wiki/spaces/GH/pages/120946795 |
Consent BB Spec 2.0 planning | @Ain Aaviksoo (Deactivated) @sasi | Must move forward with next version of spec. First task: identify reference usecases
Tenders:
|
“Consent management” definition | @Ain Aaviksoo (Deactivated) | We renamed “Consent Management BB” to “Consent BB”. Is there a useful definition of “consent management” that we can apply? |
AOB | all hands | New potential member(s) to Consent BB Consent BB tender out around end of January |