Kanban board + Action points from last week (fixed)

Ain Aaviksoo (Deactivated)

Most teams are prioritizing Egypt meeting, Ain Aaviksoo (Deactivated)

Feedback from meetings in Egypt

Ain Aaviksoo (Deactivated)

8 use-cases developed! Many great examples. 3 were very easy to

Introduction to the DDX Consent BB.

Lal Chandran

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

• Project management

• Development workflows

• Test plan

• etc… (see page for all details)

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:

• Critical to avoid conflating the solution with the Building Block, solution should be 100% independent in nature but 100% compatible with Consent BB. This is mostly an input about naming things…

• Solution and adapter, are they separated?

• Are you aware of the bb-consent/examples/ structure?

• Are you aware of GovStack UX Guidelines that are published?

• What to do with APIs that aren't part of GovStack specs - expose them in the same structure?

• What will be the workflow between Consent BB and DDX team?

Ain questions:

• What do we need to accommodate in the Consent BB planning? What "best-practice" guidance is found for building solutions for GovStack?

• What sort of workflows are great, for instance for building consent. How will engagement with other BBs work? Will you be able to work on this aspect?

Consent delegation

skipped

• Jira Legacy
  server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key CON-52

• Where is the relationship between individuals stored?

  • The application is aware of it?

  • Another BB is aware of it?

  • Auditing should be able to verify it

Review necessary Gherkin scenarios to implement

Benjamin Balder Bach Skipped

Spec 2.0: Unfolding new roadmap items

Skipped

New issues

sasi

parked for future meeting

• What do we expect other BBs that call Consent-BB to store?

• When do we like to use Consent-BB and when do we not expect this? (This should also be know to the auditor.)

Discussion: How shall we address such matters, which do not fit into specification format?