2025-09-04 TSC Minutes

Attendees & Representation

LF Staff:

Agenda

• Review and approval of previous meeting minutes

• Action Items Review

• General Topics

  • Governance & project management issues

  • Release Management

  • Commonalities

  • Identity & Consent Management

  • API Backlog

• Specific Topics

  • Update on MCP Whitepaper progress (@Nick Venezia)

  • Proposal “Dual-Phase Meta-Release Strategy” (@Alberto Ramos Monaga @Jorge Garcia Hospital)

• Any Other Topics

Minutes

Review and approval of previous meeting minutes

• Minutes of previous TSC meeting: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/207847425

  • No comments

Action Item Review

• See home page Technical Steering Committee for current list of open action items

  • Update about MCP Whitepaper postponed to next TSC (@Nick Venezia couldn’t join)

Governance & Project Management issues (@Herbert Damker , @Casey Cain )

• Post Fall25 planning:

  • Rethink the overall meta-release strategy → proposal from @Alberto Ramos Monaga & @Jorge Garcia Hospital, see below in special topic: https://github.com/camaraproject/Governance/issues/194

  • Rework of release workflow and metadata (less manual, more automation) → proposal in https://github.com/camaraproject/ReleaseManagement/pull/275 - thanks for constructive feedback to reviewers, next step is planning of implementation and migration

  • “Clean-up” -> process and criteria needed for stale API Repositories and their archiving needed

    • API Backlog will create a proposal for process and criteria (extend the process for “frozen” API proposals towards Sandbox) - until first TSC in October @Alberto Ramos Monaga @Jorge Garcia Hospital

  • Kick-off of next release cycle after Fall25 retrospective (M6), but please start already with planning in the Working Groups and Sub Project during September (updates in TSC on September 18th?)

• Roll-out of centralized linting (including Gherkin linting for test definition files)

  • Done for all API repositories involved in Fall25 (status page) - no major issues, two teams opened questions about the rules in Commonalities

  • Roll-out will be continued to the remaining repositories

Release Management (@Tanja de Groot)

• M4

  • 40 Fall25 participating repositories have their M4 review issues

    • All release PRs are available.

    • Release Management reviews are ongoing but release PR approvals are suspended until next week’s Release Management meeting to check if there are any issues found that have to still be applied to many APIs before M4.

    • 12 Fall25 M4 review issues are marked as “reversed”: this is related to the discrepancy between Commonalities error data types in CAMARA_common.yaml and in API Design Guide. The expected order is as in the API Design Guide (status, code, message).

      • this is not a client breaking change.

      • API projects may decide to anticipate the upcoming Commonalities maintenance release (r3.4 / v0.6.1) - see issue #526 - while still referencing Commonalities r3.3

      • another update could be a change to feature files for the reference to NetworkAccessIdentifier

  • M4 declaration: target was Aug 31.

    • reviews will be done till Sep 15

      M4 date shifts to the Release Management meeting on Sep 16.

• M5

  • M5 date: target September 15; slight shift to expected in TSC on September 18.

  • Marketing target event - proposed: week after TSC e.g. thursday Sep 25.

• Release review process automation (Spring26)

  • Great progress is being made (thanks to @Herbert Damker and @Rafal Artych ) on the automation of release PR reviews

  • This will lead to some changes in the Release Management process, and result in simplifying the API projects work by automating version updates and release tracker work.

  • Testing of the new process is planned for the upcoming Spring26 timeframe.

• M6

  • As part of the feedback period about the meta-release several proposals are ingoing and can be reviewed. You can also provide additional feedback. please see the following links for review:

    • Release review automation concepts: see https://github.com/camaraproject/ReleaseManagement/pull/275

    • Meta-release strategy update proposal from @Alberto Ramos Monaga & @Jorge Garcia Hospital, see: https://github.com/camaraproject/Governance/issues/194

    • Clean-up” process and criteria for stale API Repositories and their archiving: proposal to be provided (see above Post Fall25 section)

    • Wishlist for linting/automations: see Release PR checks - CAMARA Project - CAMARA Project - feel free to add (Note: this needs to be turned into a checklist so that implemented items can be ticked off).

    • Any other feedback you want to share on the Feedback page: Meta-release feedback - CAMARA Project - CAMARA Project

Commonalities (@Rafal Artych )

• Public release for Fall25 https://github.com/camaraproject/Commonalities/releases/tag/r3.3

  • Properties order of ErrorInfo schema in template files not consistent with API Design Guide

  • Updatedhttps://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/198443045

  • Patch release r3.4 prepared with Commonalities version 0.6.1 restoring correct properties order in template files - PR #527

• Issue #528 Fix "x-camara-commonalities" value format to be understood as a string - suggested by TSC to be included in Spring26

• gherkin-lint ruleset is based on default ruleset of the tool:

  • Issue #520 to be used to discus modifications based on experiences from automatic linting roll-out

• Defining the scope for Spring26 to be started, some backlog topics:

  • Security section in Design Guidelines

  • subscription APIs (including notification authentification)

  • linting rulesets improvements

Identity & Consent Management (@Axel Nennker )

• Planning and work for the Spring26 meta-release have now commenced:

  • New tracking issue https://github.com/camaraproject/IdentityAndConsentManagement/issues/311

  • First features ICM is working on for Spring26

    • https://github.com/camaraproject/IdentityAndConsentManagement/issues/288

    • https://github.com/camaraproject/IdentityAndConsentManagement/issues/312

    • https://github.com/camaraproject/IdentityAndConsentManagement/issues/316

• Consent Info API public release pending final approval:

  • The WG has completed its work for the public release (r1.2) as part of the M4 milestone.

  • https://github.com/camaraproject/ConsentInfo/pull/33 is ready and awaiting final approval from the release management team before it can be merged and officially published.

API Backlog (@Jorge Garcia Hospital)

• API proposed for review for Sandbox:

  • Sponsored Data: allows third parties to sponsor mobile data usage for end users in a destination-agnostic way. It enables the initiation, monitoring, and termination of sponsored data sessions via secure operator interfaces.

    • Proposed by Telecom Argentina, original issue #223 and API proposal #224 (with additional information).

    • Sandbox repository to be independent.

    • Question on end-user notification for sponsored data caps (e.g., 100MB): raised who should inform the user when the allowance is consumed. Clarified it’s the sponsor’s responsibility, based on callback events sent by the API — the network/operator doesn’t notify end users directly.

      • Decision: [delayed] - Due to short time to review an offline approval will be done by vote (by next Thursday)

Special Topic: Update on MCP Whitepaper progress (@Nick Venezia)

• No update, postponed to Sept 18th

Special topic: Proposal “Dual-Phase Meta-Release Strategy” (@Alberto Ramos Monaga @Jorge Garcia Hospital):

• A dual-phase meta-release cadence is being proposed for CAMARA, explicitly distinguishing between:

  • Sandbox phase (0.x) → APIs released iteratively throughout the year for early testing and validation.

  • Stable phase (1.x and above) → APIs aligned with meta-releases (typically Fall), optimized for large-scale deployment and long-term support.

• Goal: Improve alignment with real operator adoption patterns, reduce redundant validation efforts, and formalize versioning rules and lifecycle transitions.

• Grounded in practice: Reflects GSMA deployment data (Q2 2025), pilot experiences, and feedback from multiple working groups.

• Next steps

  • Formal issue has been published in the Governance group, including extended documentation (#194)

  • Feedback is open, and the proposal will be further explored in coordination with the others working groups.

• https://github.com/camaraproject/Governance/issues/194

• AP: Request to all Working Group to provide feedback before the next TSC meeting within the issue or in other form

Any Other Business

• ...

Next Meeting

• Next TSC Meeting will be on September 18th, 15:00 UTC

• Specific agenda topics backlog:

  • ...

  • ... 

Action items