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)
Benjamin Balder Bach (weekly note keeper and time keeper)
George Padayatti
PSRAMKUMAR (out)
sasi (out)
Meeting Note
Agenda | Presenter | Discussion |
---|---|---|
Kanban board + Action points from last week (fixed) | Most teams are prioritizing Egypt meeting, Ain Aaviksoo (Deactivated) | |
Feedback from meetings in Egypt | 8 use-cases developed! Many great examples. 3 were very easy to | |
Introduction to the DDX Consent BB. | Development in public, wiki is here: https://github.com/decentralised-dataexchange/bb-consent-docs/wiki Many structures are in place, including “work packages” (WPs): https://github.com/decentralised-dataexchange/bb-consent-docs/wiki/wps-and-deliverables
There is a lot of water-fall structures: WP3a is development, WP3b is testing phase, WP04 is verification etc. This accommodates ITU, but there are agile workflows, including sprints and Slack-based communication. Everything should be possible to run locally on a developer machine. Kanban on Trello for high-level project management. GitHub has milestones regarding WP3. All repositories have been created and live in https://github.com/decentralised-dataexchange “bb-consent-docs” is the MAIN repository. A Consent Design Specification / UX document is in a Google Doc (link TBD). Note-keeper reaction: A lot of really wonderful work has happened around defining wireframes for Admin workflows!! Work regarding bb-consent/examples/ will happen in WP4, work starts on November 1st. Benjamin questions:
Ain questions:
| |
Consent delegation | skipped | |
Review necessary Gherkin scenarios to implement | Benjamin Balder Bach Skipped | |
Spec 2.0: Unfolding new roadmap items | Skipped | |
New issues | parked for future meeting |
Discussion: How shall we address such matters, which do not fit into specification format? |
New Action Items
- Schedule tech meeting Lal Chandran
- Schedule / update agenda for next meeting with remaining questions from this meeting’s discussions Benjamin Balder Bach
Action Items from previous meetings
- Ain Aaviksoo (Deactivated) consider if the decision to have “external ID” and “external ID type” referencing Individuals is relevant for the Key Desicion Log (if it’s not already there)
- Philippe Page will finish the initial descriptions and commit himself to the ones he feels appropriate
- Create Jira epic to track individual Gherkin scenarios being drafted and implemented Benjamin Balder Bach
- Add cases that we want to cover for Internal Workflows section in - CON-109Getting issue details... STATUS Benjamin Balder Bach
- Review Ain’s presentation outline Benjamin Balder Bach
- Schedule a meeting Monday/Tuesday window 10-15 CET Ain Aaviksoo (Deactivated)