Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DRAFT MINUTES

...

RepresentativeOrganizationRole

Deutsche Telekom AG

TSC Chair, Active MaintainerX

Deutsche Telekom AG

Active MaintainerX

Ericsson

Active Maintainer

KDDI

Active MaintainerX

Orange

TSC Deputy Chair, Active Maintainer

Radisys

EUC Representative

Summit Tech

EUC RepresentativeX

Telefonica

Active Maintainer

Telefónica

Active MaintainerX

Verizon

EUC Representative

Vodafone

TSC Deputy ChairX

Vodafone

Active Maintainer

Vonage

Active Maintainer
George Glass

TM Forum

TM Forum Representative

TM Forum

TM Forum Representative

GSMA

GSMA Representative

GSMA

GSMA Representativex

...

Community: Tanja de Groot Bart van Kaathoven Axel Nennker Jorge Garcia Hospital Ramesh Shanmugasundaram Ramit Chawla Samuel Adeyemo Rafal Artych Nuno Rodrigues 

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.

  • Review and approval of previous meeting minutes
  • Action Items Review
  • General Topics
    • Governance & project management issues
    • API Backlog
    • Commonalities
    • Identity & Consent Management
    • Release Management
  • Specific Topics
    • na
  • Any Other Topics

...

Release Management (Tanja de Groot Samuel Adeyemo )

  • Meta-release Fall24 - CAMARA Project - Confluence
  • M3 status:
  • APIs:
    • See meta-release page for API milestone status.
    • WebRTC missing release tracker 
    • Those APIs that want to be in the meta-release need to create their release tracker (else they are not visible for Release Management)
    • Once their release PR for M3 is ready, they need to add the release-management_maintainers as a reviewer of the PR to kick off the review process.
  • M4 status
    • APIs that passed M3 (or submitted for approval) can start to prepare their public release PR for the M4.
    • Stable APIs (5 so far) will be submitted for M4 approval by TSC - for discussion:
      • review the release candidates of stable APIs by Commonalities and ICM ASAP - create an issue in Comm. and ICM projects. Check in particular wrt the above API misuse issue (too detailed error msg, return parameters that should not be there)
    • Aug 26th: latest date that APIs should provide their final release PRs. Changes since M3 should be documented in CHANGELOG.md.
    • TSC on Sep 5th shall make final decisions on meta-release participation and stable status.

...