/
2025-06-19 TSC Minutes

2025-06-19 TSC Minutes

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

x

@Shilpa Padgaonkar

Deutsche Telekom AG

Maintainer

x

@Jan Friman

Ericsson

Maintainer

x

@Toshi Wakayama

KDDI

Maintainer

x

@Ludovic Robert

Orange

Maintainer

x

@Tanja de Groot

Nokia

Maintainer, Release Manager

absent (Herbert will stand-in for RM)

@diego.gonzalezmartinez

Telefonica

Maintainer

x

@Jose Luis Urien Pinedo

Telefónica

Maintainer

x

@Eric Murray

Vodafone

Maintainer

x

@Mahesh Chapalamadugu

Verizon

Maintainer

x

@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

 

@Henry Calvert

alt: @Mark Cornall

GSMA

GSMA Representative 

 

Community members may use @name tag to mark their attendance

Community:

@Artur Krukowski @Murat Karabulut @Axel Nennker @Pierre Close @Kevin Smith

 

 

 

 

 

 

Action Item Review

LF Staff:

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

    • End User Council (EUC)

    • OWASP security guidelines

  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

Governance & Project Management issues

  • Results from votings started after previous TSC meeting:

    • Vote to approve the promotion of the Device Swap API Repository to the Incubation Lifecycle state: 9 votes, all “Approve”

    • Vote to approve the promotion of the Population Density Data API Repository to the Incubation Lifecycle state: 9 votes, all “Approve”

    • Congratulations to the the teams of Device Swap and Population Density Data!

    • Changes in Wiki and GitHub already done.

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

    • All README files within API repositories aligned with the current template (at least the first 15 lines)

    • Consistency of the README badge, descriptive text and wiki page link as well the validity of the wiki page link will be regularly checked via “Repository Overview” workflow (see next item). So: please don’t touch the first 15 lines

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

    • Repository created, currently used for:

      • workflow to create new (Sandbox) API Repositories

      • set of workflows which allows bulk changes across the repositories of CAMARA

      • reporting workflows to support the administration of repositories and releases

    • Open for new proposals - please raise an issue in the repository

API Backlog (@Jorge Garcia Hospital)

  • No new APIs or proposals for this session.

  • To update:

    • Incubation process voting results: see above. DeviceSwap is now an Incubating API Repository in Sub Project “Number Insights”, PopulationDensityData the first Incubating API Repository in new Sub Project “Population Density Data” (might be renamed if combined with further APIs in future).

    • Frozen API governance proposal review and approval: https://github.com/camaraproject/Governance/pull/190

Commonalities (@Rafal Artych @Pedro Díez García )

Identity & Consent Management (@Axel Nennker )

Release Management (@Tanja de Groot@Herbert Damker )

  • M2

  • M3: https://lf-camaraproject.atlassian.net/wiki/x/FQApAg

    • First release-candidates (release PRs) of APIs - Jun 21 => moved by TSC decision to June 28th (Saturday next week).

      • TSC will review on July 3rd the status of available release PRs

    • API Sub Projects to merge all content PRs created separately from the release PR which should ONLY update the changelog, the version, the release assets, etc. as per Wiki guidelines.

    • 61 APIs proposed for the meta-release (numbers are not final as API repository teams can decided until M3 milestone to participate), thereof

      • 30 new APIs

      • 31 updated APIs, thereof 9 stable APIs (of which 2 first stable APIs)

      • 40 repositories

    • M3 review issue contains the detailed checklist for reviewers

    • “Admin PRs”: Automated changes have been gracefully enabled by Herbert in GitHub. API Sub Projects may need to merge such “admin PRs” generated to do updates impacting all APIs when possible. example: the update of the API-Readiness-Checklist with an additional row on the API description page (with update due at M4).

    • Call for additional reviewers - please join the Release Management meetings to offer your services!

Specific Topic

  • End User Council (EUC) (@Nick Venezia )

    • Lot of confusion about how to get access to actual APIs and the way of onboarding

    • Creating a library of user journeys how to use the APIs

      • e.g. describing the different roles and responsibilities

      • e.g. which companies can help with onboarding

    • Re-engage people who where involved early and left later, getting feedback about where we can better

  • OWASP security guidelines (@Kevin Smith )

    • The OWASP API Security project publishes an API Security Top 10 , describing key threats and mitigation solutions. These include vulnerabilities in the OAS YAML files that provide the API definition. Spectral have produced an OWASP API Security Ruleset which detects and logs these vulnerabilities, allowing the API codeowner to apply the appropriate fix. This follows a ‘Secure by design’ principle of ‘shift left’, meaning standard API definitions undergo a vulnerability check before they are passed to implementing publishers. The intention is to add this to the global linters in the Tooling repository, and to test against some sample API definitions, with the goals being (1) enhance API Design Guidelines to recommend appropriate OWASP principles, and (2) assess when such linting could be introduced to the meta-release lifecycle (post Fall 25)

Any Other Business

  • none

Next Meeting

  • Next TSC Meeting will be on July 3rd, at 9:00 UTC

  • End User Council will be added to the regular TSC agenda on each 3rd Thursday of a month

  • Specific agenda topics backlog:

    • OWASP security guidelines (@Rafal Artych@Kevin Smith ) - if there are more learning within CAMARA

Action items (from above)

@Jesús Peña García-Oliva Create an issue and PR to update the scope change of ConsentInfo (update of API proposal template) in API Backlog working group