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

Version 1 Current »

Community Attendees:

LF Staff:

Agenda

Antitrust Policy

  • Action Items Review

  • PRs to review:

    • #53 - Notification compliance - Merged! (tick)

    • #56 - VvoipSessionInformation schema review - Merged! (tick)

    • #59 - Fix/api file names - NEW

      • Covers issue #57

  • Issues to discuss:

    • Subproject management

      • #58 - Scope for webrtc-events API for Spring 25 CAMARA meta release (wip) subproject management

      • #51 - Spring25 API requirements

      • #50 - Spring25 Documentation requirements documentation

    • #57 - File names and api-name subproject management

    • #55 - Allow implicit subscription for RACM and CallHandling enhancement

    • #52 - Branded Calls impact in WebRTC API

    • #25 - Emergency call support for BYON enhancement

  • Others

    • Next release scope

    • Next meeting date

Minutes

PRs to review

  • #53 - Notification compliance - Merged! (tick)

  • #54 - VvoipSessionInformation schema reviewed - Merged! (tick)

  • #59 - Fix/api file names - NEW

    • It covers issue #57 to rename APIs and their files following the common rules. Alto it simplifies terms, remove custom naming and clarifies API scope: register, call, or track events.

      • BYON-CallHandling → webrtc-call-handling

      • BYON-RACM-Service → webrtc-registration

      • BYON-WebRTC-Events → webrtc-events

    • Also patches API URLs to be aligned with CAMARA

    • And includes a little bit more of documentation

    • Looks good for all the team. Looking for approval to merge ASAP

Issues to discuss

  • #58 - Scope for webrtc-events API for Spring 25 CAMARA meta release (wip)

    • subproject management

    • Required to cover all points based on templates for API readiness and changelog to be included on doc folder

    • This issue will do the work for webrtc-events. We will extra issues like this for webrtc-call-handling and webrtc-registration

    • This issue (and other scopes) will overseed #51 and #50

  • NEW ISSUE: All APIs must comply with Commonalities 0.5 before releasing (warning)

  • #57 - File names and api-name subproject management

    • Discussed during PR#59. Will be closed when merging

  • #55 - Allow implicit subscription for RACM and CallHandling enhancement

    • Agreed to be included for next release

  • #52 - Branded Calls impact in WebRTC API

    • No news

  • #51 - Spring25 API requirements (tick)

    • Overseed by #58 and following ones. Agreed to close

  • #50 - Spring25 Documentation requirements documentation (tick)

    • Overseed by #58 and following ones. Agreed to close

  • #25 - Emergency call support for BYON enhancement

    • Agreed to be included for next release

Others

  • Summary for next release: During discussion of #58 we have an agreement about the scope for next release. It will include

    • Emergency call support #25

    • Implicit events support #55

  • All active participants are invited to consider potential candidates to expand the CODEOWNERS list.

  • Next meeting: January 28th

Action items

  • Review, fix and merge #59 (Fix/api file names)
  • Create scope tasks for all APIs
  • Create issue for commonalities 0.5

  • No labels