2023-06-09 - Weekly update
Jun 9, 2023
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.
Meeting link: https://meet.google.com/rsf-cqaq-eyq at 07:30 UTC / 09:30 CET / 13:00 IST
Attendees
@Ain Aaviksoo (Deactivated) (meeting facilitator; meeting note keeper as Benjamin was in the train today)
@Benjamin Balder Bach (weekly note keeper and time keeper)
@PSRAMKUMAR
Meeting Note
Agenda | Presenter | Discussion |
---|---|---|
Action points from last week | @Ain Aaviksoo (Deactivated) | Updated the list |
Jira Kanban update | @Ain Aaviksoo (Deactivated) | Let’s make this fixed! |
How should we scope efforts for sandbox deliverables | @Ain Aaviksoo (Deactivated) @Benjamin Balder Bach @PSRAMKUMAR | We need to be sensible about how much to extend the mock application in order to ASAP accommodate.
|
Future collaboration with a tender | Skipped | Note-keeper: @Ain Aaviksoo (Deactivated) you fell out of the meeting, but I talked to Ramkumar about the task that we have ahead of us: Understanding how we want to govern specification work as a WG once that a tender starts to actively work on a candidate application. I’ll put it here for the next meeting, and it sounds like @PSRAMKUMAR already knows how WGs should function in this setting. |
Updates from TC meeting (fixed) | @Ain Aaviksoo (Deactivated) | Authentication and Cross-BB Authorization |
Gherkin scenario writing discussion (ongoing) | Skipped | |
Review necessary Gherkin scenarios to implement | @Benjamin Balder Bach Skipped | |
Spec 2.0: Unfolding new roadmap items | Skipped |
|
New issues | @sasi parked for future meeting |
Discussion: How shall we address such matters, which do not fit into specification format? |
|
|
|
|
|
|
|
|
|
|
|
|
New Action Items
Action Items from previous meetings
(the group can then address them and decide where and how their later proper “place” will be)
Decision
- We will reach out to SolDevelo for building more test integration and implementing more aspects of the Mock Application.