/
2025-10-16 TSC Minutes

2025-10-16 TSC Minutes

Attendees & Representation

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

Representatives

Organization

Role

 

@Herbert Damker

Deutsche Telekom AG

Maintainer

x

@Shilpa Padgaonkar

T-Mobile US

Maintainer

 

@Jan Friman

Ericsson

Maintainer

x

@Toshi Wakayama

KDDI

Maintainer

x

@Ludovic Robert

Orange

Maintainer

x

@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

x

@massimiliano.troiani

Verizon

EUC Representative

 

@Doug Makishima

Summit Tech

EUC Representative

 

George Glass

alt: @Olta Vangjeli

TM Forum

TM Form Representative

 

@Mark Cornall

GSMA

GSMA Representative 

x

Community members may use @name tag to mark their attendance

Community: @Artur Krukowski @Alberto Ramos Monaga @Rafal Artych @Murat Karabulut

 

 

 

 

 

 

 

Action Item Review

LF Staff: @Casey Cain

Agenda

The project's Antitrust Policy is linked from the LF and project websites. The policy is important when multiple companies, including potential industry competitors, are participating in meetings. Please review it, and if you have any questions, please contact your company's 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

    • MCP White Paper progress (@Nick Venezia )

    • End User Council (@Nick Venezia )

    • Update on OWASP security guidelines evaluation (@Rafal Artych )

  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

Governance & Project Management issues

  • Centralized linting roll-out: now done for all 58 API repositories (not for DeviceStatus and KnowYourCustomer as they won’t change anymore)

    • Only for information, see wiki page under tooling for status.

  • https://github.com/camaraproject/ReleaseManagement/pull/275

    • Request for a final review until October 24th

    • The concept will be the base for the rework of the release process for all API repositories under the supervision of Release Management working group, to be introduced until Spring26, getting general process at latest for Fall26 cycle

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

    • We need new names for our meta-releases “Spring” and “Fall” to avoid hemispherical confusion. Would be good to have the names before the next AHC.

    • There are already some good proposals within the issue.

    • Potential way forward? Ranked vote? Include Outreach Committee in the vote?

    • Point the Marketing team to the issue, one round of comments → short list → ranked voting (TSC members & Outreach committee together)

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

    • @Alberto Ramos Monaga has prepared a wiki page with the details of the proposal

    • Proposed next steps (@Herbert Damker):

      • Create the formal pull request for API-Onboarding-and-Lifecycle.md, considering the offline comments → until next TSC creating a draft PR @Alberto Ramos Monaga

      • Start the first review round of Onboarding Trackers and API repositories without content/releases yet → initial list & information to the responsible proposal owners and codeowners

      • HomeDeviceQoD is a repository with an initial API version which hasn’t evolved since two meta-releases and without a plan to evolve (potential to be considered for archival in Phase 4)

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

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

    • reminder to provide feedback from the community

    • a number of LF project have already decided to migrate

    • we will need a vote sometime soon (transitioning until end of year?)

  • CAMARA TSC Election

    • The TSC Election (nominations) kickoff should begin on Oct 27, 2025

    • @Casey Cain and@Herbert Damker will collaborate with the community to ensure that all current maintainers and eligible candidates are accurately accounted for by Oct 24, 2025

API Backlog (@Alberto Ramos Monaga )

There are no new topics, only task reports.

  • Provider implementation - Energy Footprint Notification #262

    • Last updates: In relation to the Energy Footprint Notification API, the group is asking for a Provider implementation repository No objections - According to ProjectStructureAndRoles, a PI repository is considered a “sidecar” of the main API repository — it only needs minimal governance elements (CODEOWNERS, license, GOVERNANCE.MD, and /code/API_code). Therefore, as long as the PI repo has active code owners and is linked to an active API repository, no formal TSC approval is required.

    • Repository to be created as requested @Herbert Damker

  • Proposal “Dual-Phase Meta-Release Strategy: #194

    • Last updates: offline review of the wiki page with proposals for changes in CAMARA documents, creating issues for document changes out of it.

  • Clean-up process: #199

    • Last updates: wiki page created to discuss the proposal (Feedback collection phase). Eventually it will reflected in the lifecycle document (done in a PR).

Commonalities (@Rafal Artych )

Identity & Consent Management (@Jesús Peña García-Oliva on behalf of @Axel Nennker )

Release Management (@Tanja de Groot)

Specific Topics

Any Other Business

  • none

Next Meeting

Action items