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 Current »

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.

Attendees

Meeting Note

Agenda

Presenter

Discussion

Follow-up on previous Action Items (Fixed)

Meeting facilitator

API release decision

Benjamin Balder Bach Lal Chandran

Release 1.0.0? API and spec are version aligned. We aim to have the API as 1.0.0, too.

Comment from Sasi: What kind of long-term support do we have for releases of specifications?

Comment from Ramkumar and Lal: The APIs align with specs and use cases, this is the most critical part now.

Test plan, strategy (10 min)

Benjamin Balder Bach
See also: https://github.com/GovStackWorkingGroup/bb-consent/pull/13

What should be the next steps?

Workshop?

Ramkumar: New lead for test (Satyajit Suri). Needs alignment across all BBs.

Gherkin intro (5 min)

Benjamin Balder Bach

How do we align Gherkin scenarios and specification document?

Additional resources for building tests and demo

Ain Aaviksoo (Deactivated)

Maxim is a new member of the team, formalities being sorted out

Action Items

Action Items from last meeting

  • Forward 2 proposals for TAC - possible to mention general perspective, that we have to start everything from scratch and that “best-practice” sharing is desirable when a general standard/convention isn’t adopted. Lal ChandranAin Aaviksoo (Deactivated)
  •  

Decision

  • Release API as 1.0.0
  • No labels