Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Meeting Note

Agenda

Presenter

Discussion

Action points from last week

Ain Aaviksoo (Deactivated)

Standup on Sprint 1 results 10min

Ain Aaviksoo (Deactivated)

https://govstack-global.atlassian.net/jira/software/c/projects/CON/boards/34?view=detail&selectedIssue=CON-26

Schema updates

Benjamin Balder Bach

https://github.com/GovStackWorkingGroup/bb-consent/pull/30

Do we keep endpoints for creating ConsentRecord and Signature the former way? Or do we only support the method decided at last meeting? Decided yes.

Dividing tasks for Gherkin scenario writing

all-hands
Moved to next meeting

See: https://cucumber.io/docs/gherkin/reference/

Planning next sprint - should contain also starting with “Spec v2” (@all)

all-hands
Moved to next meeting

Community outreach blog-post

Ain Aaviksoo (Deactivated)

Jira Legacy
serverSystem JIRA
serverIdf5c6bdaf-d23e-347d-a1e8-579e20a81dda
keyCON-71

...

  •  Book working group for an extended hour of Gherkin Scenario writing for next Friday’s meeting. Ain Aaviksoo (Deactivated)
  •  Executing the new decision of removing API endpoints and finish up related Jira issues, taking Sasi’s input from the end of the meeting into account Benjamin Balder Bach

Action Items from last meeting

Decision

...

  • The now unused endpoints from the previous sequence of Consent Record signing will be removed.
  • Input from Sasi after the end of the meeting is that we should make it easier for the external party that handles signature to know what to sign, making the payload construction internal for the Consent BB.