/
2025-02-06 TSC Minutes

2025-02-06 TSC Minutes

Owned by Herbert Damker, created
Last updated: yesterday at 9:53 pm
6 min read

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

x

@diego.gonzalezmartinez

Telefonica

Maintainer

x

@Jose Luis Urien Pinedo

Telefónica

Maintainer

 

@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

x

George Glass

TM Forum

TM Form Representative

x

@Henry Calvert / @Mark Cornall

GSMA

GSMA Representative 

x

Community members may use @name tag to mark their attendance

Community: @Kevin Smith

 

 

 

LF Staff:

Community: Laszlo Suto, @Rafal Artych @Kevin Smith @ALI IQBAL @Axel Nennker @Pierre Close @Jorge Garcia Hospital Nuno Rodrigues, Ravi Shekhar

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

    • Evaluation of “Incubation Candidates” & way forward

    • Proposal for update of CAMARA wiki structure

    • Optional, if time: Linting with reusable workflows across the API repositories

  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

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

    • Open action item “Review open issues within Governance and propose way forward for them @Herbert Damker” will be addressed in next agenda topic.

Governance & Project Management issues

API Backlog (@Jorge Garcia Hospital )

  • No new APIs proposed by backlog in this session.

  • Ongoing actions (news to come!):

    • Closing WoW for API onboarding and tracking process:

    • Including templates for participants in each wiki-page for APIs

      • Draft to be shared in next backlog meeting.

      • Template to be included in each current API (and new)

    • Proposing a re-shaping of current API backlog list

      • Maintain current API backlog tracker for under-discussion APIs

      • Create a new dynamic table (confluence can be the host) for live APIs under specification, avoiding duplicities with release management information

    • Including marketing material for APIs

      • requested by @Markus Kümmerle to each API owner, ETA 14th February EoB

        • There is a link with an example in Markus email

        • Herbert proposed this deliverable to be added in the wiki (and not in the API repo)

      • to be included in meta-release requirements for API readiness checklist

Commonalities (@Rafal Artych )

Identity & Consent Management (@Axel Nennker @diego.gonzalezmartinez )

  • No important ICM topics relevant for TSC

  • ICM 0.3.0 - preparing the scope for meta-release Spring25 #193 is on track

  • Consent URL API vs OIDC consent collection

  • https://github.com/camaraproject/IdentityAndConsentManagement/issues/258 - please have a view, will be discussed in next ICM meeting

  • Issue about certification - @Axel Nennker indicated that ICM is not the right place to handle this request.

    • For Herbert this is a policy at GSMA level not CAMARA

      • @Herbert Damker Action: Move the issue to gouvernance - please comment on this issue

      • @Ludovic Robert This is fine as long as the problem is solved because it cause issue on our API adoption

      • @Shilpa Padgaonkar We have to provide documentation & link to the GSMA process.

  • @Mark Cornall raised the fact that company come for certification with no clue about CAMARA flow requirement (private_key_jwt, pkce, etc…)

    • Mark will open an issue & good practice are more than welcome

Release Management (@Tanja de Groot )

M2

  • Commonalities 0.5.0-rc.1 & ICM 0.3.0-rc.1 both released as r2.2. Some documentation updates planned for the public release.

  • Public releases: latest 2 weeks before M4 (target: Feb 14 for the release PR, final approval by TSC on February 20th, see above in Commonalities)

M3

  • Proposed: 37 APIs in 20 repositories: 13 new APIs and 24 updates from Fall24

    • Fall24 APIs that will not be updated for Spring25: 1 (HomeDeviceQoD)

    • No M3 review request, so will skip Spring25: 1 (DedicatedNetworks)

  • M3 review status: 30 APIs (in 17 repositories) done; 7 APIs (in 3 repositories) review ongoing

  • Issues found:

    • Several APIs are missing the required test files

    • several APIs are not aligned with Commonalities r2.2 & ICM r2.2

  • Below table counts API repositories with (H)igh, (M)edium and (L)ow risk to meet release alignment.

    • High is mainly because of the missing test files or not being aligned to the Commonalities and ICM releases

Repositories Feb 6 2025

Missing test files

Missing r2.2 alignments

H

M

L

OK

SKIP

Repositories Feb 6 2025

Missing test files

Missing r2.2 alignments

H

M

L

OK

SKIP

Count

5

2

6

4

6

4

1

Percentage

 

 

30%

20%

30%

20%

 

Note: the details of this table can be found here: https://lf-camaraproject.atlassian.net/wiki/x/gwBVB

  • Mitigation

    • For new stable APIs - need to be OK or else stay on initial API version

    • For new initial APIs - relaxed regarding test files … to be available until M4 (public release)

    • Discussion on progress in the next RM meeting (email to be sent to maintainers)

M4

  • No change: Feb 28th

M5:

  • No change: March 15th

Evaluation of “Incubation Candidates” & way forward (@Herbert Damker)

  • Initial evaluation available on Incubating Candidates Fall24

  • Next steps?

    • Let one week to review @Herbert Damker proposal

    • Decision will be taken in a TSC vote which ends on Feb 14, 2025. The proposed decision is

      • to incubate the “green” API repositories based on the available information directly

        • which are: CallForwardingSignal, DeviceLocation, DeviceStatus, SimpleEdgeDiscovery, NumberVerification, OTPValidation, SimSwap, KnowYourCustomer, QualityOnDemand

      • to ask the API Backlog Working Group to check the remaining four candidates and give a recommendation about their incubation, if possible within for the TSC meeting on February 20th

        • which are: CarrierBilingCheckOut, ConnectivityInsights, HomeDeviceQoD, PopulationDensityData

Proposal for update of CAMARA wiki structure (@Herbert Damker , @Casey Cain )

  • Proposed structure is on https://lf-camaraproject.atlassian.net/wiki/x/kQBMB

  • Will allow filtered views as needed, e.g. all Incubated API Repositories on one page

  • No comments from the team - this is nice ! → Request to change to LF team

    • In addition the name “Number Verification” was accepted for the Sub Project which includes NumberVerification, OTPValidation and SimSwap (they are already running their meetings together under this name)

  • Note: There is no change regarding links to the API definition (YAML) files within GitHub by this reorganization in the wiki

Optional: Linting with reusable workflows across the API repositories (@Rafal Artych )

  • https://github.com/camaraproject/Commonalities/issues/263

    • Repository for hosting reusable workflows with linters configuration and documentation: xCAMARA-tooling?

      • @Herbert Damker probably X prefix is not required - let’s call it Tooling

    • Flexibility to use rulesets for Guidelines version and customization for specific API requirements

  • demo (postponed to a later TSC session)

Any Other Business

  • ...

Next Meeting

  • Next TSC Meeting will be on February, 20th, 15:00 UTC (16:00 CET)

  • Specific agenda topics backlog:

    • Linting with reusable workflows across the API repositories (with demo) @Rafal Artych

Action items

Related content

2025-01-16 TSC Minutes
2025-01-16 TSC Minutes
CAMARA Project
More like this
Proposed Wiki Structure with Sandbox and Incubated API Repositories
Proposed Wiki Structure with Sandbox and Incubated API Repositories
CAMARA Project
Read with this
2024-12-05 TSC Minutes
2024-12-05 TSC Minutes
CAMARA Project
More like this
Incubating Candidates Fall24
Incubating Candidates Fall24
CAMARA Project
Read with this
2024-11-07 TSC Minutes
2024-11-07 TSC Minutes
CAMARA Project
More like this
2025-01-23 API backlog minutes
2025-01-23 API backlog minutes
CAMARA Project
Read with this