/
2025-04-03 TSC Minutes

2025-04-03 TSC Minutes

Owned by Eric Murray
Last updated: Apr 03, 2025

Attendees & Representation

TSC Members may indicate their attendance with an X in the far column

TSC Members may indicate their attendance with an X in the far column

Representatives

Organization

Role

 

@Herbert Damker

Deutsche Telekom AG

Maintainer

 

@Shilpa Padgaonkar

Deutsche Telekom AG

Maintainer

 

@Jan Friman

Ericsson

Maintainer

X

@Toshi Wakayama

KDDI

Maintainer

X

@Ludovic Robert

Orange

Maintainer

 

@Tanja de Groot

Nokia

Maintainer, Release Manager

X

@diego.gonzalezmartinez

Telefonica

Maintainer

X

@Jose Luis Urien Pinedo

Telefónica

Maintainer

X

@Eric Murray

Vodafone

Maintainer

X

@Mahesh Chapalamadugu

Verizon

Maintainer

 

@Nick Venezia

Centillion.ai

EUC Representative

 

Massimiliano Troiani

Verizon

EUC Representative

 

@Doug Makishima

Summit Tech

EUC Representative

 

George Glass

TM Forum

TM Form Representative

 

@Mark Cornall X

GSMA

GSMA Representative 

 

Community members may use @name tag to mark their attendance

Community: @Kevin Smith @Pierre Close @Rafal Artych @Axel Nennker @Artur Krukowski

 

 

 

LF Staff:

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

    • ...

  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

Governance & Project Management issues

API Backlog (@Jorge Garcia Hospital)

  • No new APIs proposed in this session.

Note: Network Health Assessment & Network Traffic Analysis proposals, reviewed during previous TSC and with pending comments to be solved are still under fix.

Commonalities (@Rafal Artych )

  • Preparation of Meta-relase Fall25 scope #423

    • Cleanup and slim down design guidelines document - Priority for M1

    • Changes related to errors, event subscriptions and other raised issues

    • Artifacts (testing, linting) for M2

  • Commonalities next version 0.6 or 0.9?

    • Internal decision for Commonalities for initial versions

    • Preference to increment sequentially

  • Tooling - linting reusable workflows to be implemented in CAMARA repositories by M3 or M4?

    • Must be enabled on a per-repository basis, only for main branch

    • Some repositories will be tested by M3

    • Proposed to be enabled for all repositories that are part of meta-release by M4

    • Open point if all repositories should have this enabled by M4, even if not part of meta-release

    • Documentation will be available before M3, preferably by Commonalities M2

Identity & Consent Management (@Axel Nennker )

Release Management (@Tanja de Groot )

  • Spring25 meta-release reached the M6 milestone. The Spring25 meta-release is now closed.

    • For the stable APIs of the Spring25 meta-release, Sub Projects are asked to ensure to update their test statement issue once implementation tests have been achieved. Target is to close by April 29th.

    • For APIs that need to do a patch, they should follow the process as described here API Release Process | PATCH update and request review of the maintenance release PR by camaraproject/release-management_maintainers.

  • Fall25 meta-release

    • M0: Request to TSC to declare Fall25 meta-release kickoff (M0)

      • M0 declared: yes, supported by TSC

        • No objections raised in meeting by voting members, but meeting not quorate

        • @Tanja de Groot Check with @Herbert Damker before sending e-mail declaring M0

      • The meta-release plan can be found here: Meta-release Fall25

    • M1: proposal to shift date from April 15 to April 29th

      • Commonalities and Identity & Consent Management

        • teams are preparing their alpha release, but need a bit more time given the heavy load of Spring25

        • the scope issues with the Fall25 content are available on the meta-release page

      • AIl Sub Projects can start creating their API release trackers and reading the scope issues in preparation.

      • Release Management prepares a few updates to the process based on feedback which mainly concerns the following:

        • guidelines for versioning in notification URLs (update to Commonalities API design guidelines)

        • continuous numbering of release-candidates across pre-releases in the same meta-release to avoid number clashes

      • Meeting update:

        • No objections raised to shifting M1 date to 29th April

    • Release Management pages are now identified by a icon.

Any Other Business

  • None

Next Meeting

  • Next TSC Meeting will be on Thursday, April 17th, 15:00 UTC (Note: 17:00 CEST / 08:00 PST)

  • Specific agenda topics backlog:

    • None

Action items

Related content