Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Attendees

Meeting Note

Agenda

Presenter

Discussion

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

Jira backlog

Update on API development

 Benjamin Balder Bach

 n/a - move to next meeting

Update on Demo development

Benjamin Balder Bach

Lal Chandran

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

Planning test scenarios

Everybody

AOB

Action Items

  • Raise to Technical Committee: Jira or GitHub issues?
  • Build tasks in Jira:
    • List out other external actors that can make use of

Decision

  • Where do we put new changes? Ain Aaviksoo (Deactivated) ensures the consistency of the Google Docs 1.0.0RC2. Changes go to the Google Doc, Lal Chandran takes responsibility to ensure the porting of changes on GDoc to GitBook.
  • No labels