2023-05-23 - Weekly update
May 23, 2023 (postponed)
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 07:30 UTC / 09:30 CET / 13:00 IST
Attendees
@Ain Aaviksoo (Deactivated) (meeting facilitator; meeting note keeper as Benjamin was in the train today)
@Benjamin Balder Bach (weekly note keeper and time keeper)
@PSRAMKUMAR
Meeting Note
Agenda | Presenter | Discussion |
---|---|---|
Action points from last week | @Ain Aaviksoo (Deactivated) |
|
Updates from TC meeting (fixed) | @Ain Aaviksoo (Deactivated) | We are in dialogue about how we find solutions that can match our specification. Consent BB doesn’t have any candidate real-life products, so we need to figure out if there is much we can do. Suggestion to reach out to MOSIP. |
Gherkin scenario writing discussion |
| |
Review necessary Gherkin scenarios to implement | @Benjamin Balder Bach | |
Payment BB’s account mapper | @Benjamin Balder Bach | Ramkumar: 2 guiding factors for all BBs might emerge |
IDBB sync-up | @Ain Aaviksoo (Deactivated) |
|
|
|
|
Spec 2.0: Unfolding new roadmap items |
|
|
New issues | @sasi parked for future meeting |
Discussion: How shall we address such matters, which do not fit into specification format? |
|
|
|
|
|
|
|
|
|
|
|
|
New Action Items
Action Items from previous meetings
(the group can then address them and decide where and how their later proper “place” will be)
Decision
- Onboard new members in 1:1 interviews - if it scales. If there is too much interest, we pick a different model.