Version 1.0 final publishing

@Lal Chandran

@Benjamin Balder Bach

Publishing in GitHub and at https://docs.GovStack.global
How do we publish/send our working copies of GitBook? We cannot use the central GovStack integration. Need a solution to build documents.

Update from Tech Committee

@Ain Aaviksoo (Deactivated)

Tech Committee notes from July 28

• Stressed importance of demo use-case and that it is recognized / used by gov’t/donor?

• Test plan can verify the compliance with a BB specification

• Reach out to other DPGs to understand how they can use a consent BB and get inputs for test plan - from a real world scenario.

• We need to revisit APIs

• It’s crucial to understand external actors, we risk having a too narrow understanding of our own consent definition by only talking to other BBs

 Phase II Work plan

 @Ain Aaviksoo (Deactivated)

 Draft for discussion

Question to be forwarded: Can we postpone the detailed roadmap until we have worked out a test plan and revisited APIs (roadmap October)? Ain lays out the case for a possible 4-step plan.

Jira backlog

Lal has had a look at turning backlog into a board, @Ain Aaviksoo (Deactivated) will work it out.

Update on API development

 @Benjamin Balder Bach

 n/a - move to next meeting

Update on Demo development

@Benjamin Balder Bach

@Lal Chandran

Skipped - post-meeting note: @Benjamin Balder Bach has been suggesting that we keep the demo in bb-consent repo and publish updated demos in the release cycle of the building block. Demo and tests will be integrated for now. Demo lives in examples/demo as a deployment where specification compliance can be verified (we should keep it at 100%).

NB! Terminology: The demo is really a kind of mock of our API, it’s not a UI demo.

Planning test scenarios

Everybody

Skipped

AOB

Skipped