2022-10-07 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Oct 11, 2022
2 min read

Oct 7, 2022

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

  • @Ain Aaviksoo (Deactivated) (meeting facilitator)

  • @Philippe Page

  • @Lal Chandran

  • @Benjamin Balder Bach (weekly meeting secretary)

  • @sasi

  • @PSRAMKUMAR

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Follow-up on previous Action Items (Fixed)

Meeting facilitator

Skipped: After the meeting we talked about how we can open the meetings with a routine to set the agenda and revisit action items

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: Test plan structure suggestions by benjaoming · Pull Request #13 · GovStackWorkingGroup/bb-consent

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

Add comment in API somewhere to clarify its maturity @Benjamin Balder Bach
Link up with new test lead, Satyajit Suri @Ain Aaviksoo (Deactivated)
Background in testing, pending alignment with Satyajit Suri, we will present an intro to the test strategy and how we can deliver @Ain Aaviksoo (Deactivated) @Benjamin Balder Bach
Writing workshop: Pending input from Satyajit Suri, @Ain Aaviksoo (Deactivated) and @Benjamin Balder Bach prepares a test scenario workshop

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 Chandran@Ain Aaviksoo (Deactivated)

 

Decision

  1. Release API as 1.0.0