Attendees

  • Ricardo Serrano (TEF)
  • Javier Villa (TEF)
  • Deepak Jaiswal (TMUS)
  • Santiago Troncoso (Quobis)
  • Rafal Artych (DT)
  • Pradeep Achar Pushpa (Mavenir)

Agenda

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

  1.  Review PR#40 Linting corrections. Corrections based on PR#37 and verified with linting tools. Verify that we are using the correct file version and are  aligned.
    1. Review the solved conflicts with PR #28
  2. Linting rules & workflows PR#41.
    1. Linting workflows configured as defined in Commonalities.
  3. Review AP from last meeting
    Open a document for list emergency scenarios and additional related information [

Issue#25]

    Correct SessionId names (RACM and VooipSessionId) update the PR and tag Ricardo and Deepack.
    Include documentation in code API Yaml according to the commonalities.

NOTES:

    • Remember that from now on we will use the tool ZOOM for meetings.
    • Meetings will be 30 minutes long.

Discussion.

Item

Who

Description

Review PR#40 Linting corrections. Corrections based on PR#37 and verified with linting tools. Verify that we are using the correct file version and are  aligned.

Review the solved conflicts with PR #28 

Ricardo

There are no conflicts and mistakes within the different paths

The NotificationChannel schema is utilized for both Requests and Responses and therefore includes a ChannelId. Please note that the ChannelId should not be set or provided by the client; it will be returned by the platform in the Response.

POST Method for Notification Channel:

  "resourceURL": "string", REMOVE
  "callbackURL": "string", REMOVE
  "channelId": "string", REMOVE

Merged PR#27 Flow documentation AllIf the flow documentation is finish and reviewed. Merge offline
Merged PR#40 AllReview linting errors, correct if is necessary and merged. Update in regard of first item
Meta release version discussionAllLooking forward for next steps for a demo release.


Action points

Actions

Who

Open a document page for emergency call informationRicardo
PR#27 flow to be merged after participants reviewAll
PR#40 to be merged after correcting POST Method of the Notification Channel and after review.Ricardo


AOB

  • Next meeting will be the 18th  of June
  • Next meeting will be at 16h CEST 30minutes long 
  • The next meetings will be held by the LFX Zoom platform.
  • From then to now the minutes will be uploaded to Confluence
  • No labels