2025-02-20 TSC Minutes

DRAFT MINUTES

Attendees & Representation

LF Staff: @Casey Cain

Agenda

• 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

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

• Any Other Topics

Minutes

Review and approval of previous meeting minutes

• Minutes of previous TSC meeting: 2025-02-06 TSC Minutes

  • No comments, draft label removed

Action Item Review

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

  • none

Governance & Project Management issues

• Result from vote to approve Incubating candidates (@Casey Cain)

  • TSC participants where asked to vote on the transition of CallForwardingSignal, DeviceLocation, DeviceStatus, SimpleEdgeDiscovery, NumberVerification, OTPValidation, SimSwap, KnowYourCustomer, QualityOnDemand

  • Vote result - only 7 participants voted until today 15:30 → vote extended to Friday, February 21st.

    • Please vote now, we are close to a clear result (TSC Participants find the vote in their dashboard on openprofile.dev)

    • Vote result will be updated tomorrow, but already quorum for all API Repositories in the vote.

  • Update on vote result Feb 21, 2025(as of 12:00 UTC): 11 out of 13 possible votes, all API repositories in the vote approved for transition to Incubating stage (number of “+1” in brackets, remaining are abstains): CallForwardingSignal (10), DeviceLocation (11), DeviceStatus (11), SimpleEdgeDiscovery (10), NumberVerification (11), OTPValidation (10), SimSwap (11), KnowYourCustomer (10), QualityOnDemand (11)

• New issues within Governance

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

    • The currently documented terminology "Sandboxed"/"Incubated"/"Graduated" for API repositories in ProjectStructureAndRoles deviates from the terms used within CNCF for these maturity levels:

      • Sandbox

      • Incubating

      • Graduated

    • Aligned with Marketing WG (updates of Website)

    • PR #183 under review, 3 approvals already (Update: merged on February, 21st)

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

    • TSC is asked to decide that 2FA will get required for members of CAMARA organization (98 as of today)

      • Use of 2FA is a general recommendation for all work in GitHub.com, but we can enforce it in our organization

    • Proposed date to enable it in CAMARA organization is mid of March

    • Conclusion: We will adopt the 2FA and add it as required in March.

• Updates from Markus Kümmerle (Marketing WG)

  • New API descriptions:

    • API Overview web page is already live: API Overview.

    • Small changes expected until weekend after review of API progress towards meta release

    • API descriptions are in progress: 59 total → 22 open, 37 created & in review (by API Backlog WG and GSMA OGW product work stream), 0 live.

    • Example: https://camaraproject.org/location-verification/

    • Working Group descriptions are in progress: 5 total → 1 open, 0 created & in review, 4 live

  • CAMARA presentation will be updated with latest changes until 21.02.2025 (MWC version)

  • MWC planning:

    • DevCon presentation

    • CAMARA evening event

    • 3x PoD (“Point of Demo” = a screen to present) session at GSMA booth

API Backlog (@Jorge Garcia Hospital )

• 2 new API proposal(s) from APIBacklog working group

• Device Management, supported by Verizon and China Telecom.

  • New Sandbox proposed to solve IoT device management use cases including:

    • Communication Function Management

    • Device Subscription State Management

    • Real-Time Monitoring

  • Original Issue #50 & #95; Device Management template

    • @Jose Luis Urien Pinedo raised the point about the proposed name to generic

      • IoT Device Management is probably better as repository name

    • @Tanja de Groot raised the point about additional check to be done by the backlog team when a new API submission is done: Correct wording is used in API description & Use-cases (example: no gateway word in UC !!)

  • Conclusion: OK from TSC for sandbox repository creation

• IoT SIM Fraud Prevention API, supported by China Telecom.

  • New Sandbox proposed to solve IoT SIm Fraud use cases including 3 API proposals (to be aligned in API proposal):

    • Device to SIM Binding (IMEI) management

    • Device area restriction binding management

    • IoT fraud prevention

  • Original Issue #96; Templates: Device Area Restriction Device Card Binding. IoT SIM Fraud Prevention  

    • @Herbert Damker : Question about RBAC (role based access control) could be needed with IoT - This should be part of the WG discussion

  • Conclusion: OK from TSC for sandbox repository creation

• One API enhancement:

  • Application Profile (for Connectivity Insight), proposed by Verizon

    • Align Application profiles in Connectivity Insight including the requirements agreed in Edge Cloud APIs. Validated by both subgroups.

  • Original Issue #109; Templates: Template

  • Conclusion: OK to add this functionality to existing Application Profiles API, currently in ConnectivityInsights repository

• Participants and Description templates are now included in each API (repository) confluence page

  • Include descriptions as reported in CAMARA webpage (work in progress)

    • E.g.CallForwardingSignal API Description

    • → Any update shall be communicated to backlog groups for updating the webpage accordingly

    • → Will be included as required deliverable in next meta-release (Fall25)

  • Include participants of the repository

    • E.g. CallForwardingSignal Participants

    • Each group and participant to get included.

• APIs for incubation

  • CarrierBillingCheckOut ConnectivityInsights HomeDeviceQoD PopulationDensityData → not ready for incubation as no public statement of production deployment yet

  • Will be included post-spring25 as soon as they are ready, by:

    • Open a issue in backlog requesting for incubation 

    • Backlog reviews the fulfillment of the requirements

    • Backlog requests TSC validation

    • Repo validated and status evolved.

Commonalities (@Rafal Artych )

• https://github.com/camaraproject/Commonalities/pull/419 ready to be merged

  • updated https://lf-camaraproject.atlassian.net/wiki/x/AYDEB - latest changes are impacting APIs using event subscriptions

    • Need to be considered by all API projects (in particular if subscriptions are managed)

• Update: release PR is merged and public release 2.3 created

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

• https://github.com/camaraproject/IdentityAndConsentManagement/pull/269

• New ICM description for CAMARA web site(thanks @Jesús Peña García-Oliva )

• Hot topic regarding CAMARA usability and commercial successhttps://github.com/camaraproject/IdentityAndConsentManagement/pull/268

• Still working on https://github.com/camaraproject/IdentityAndConsentManagement/pull/266

Release Management (@Tanja de Groot )

• M2: ICM has delivered their public release, and Commonalities will also release today

• M3 has been reached today as all proposed APIs have delivered their release-candidate. See https://lf-camaraproject.atlassian.net/l/cp/auGH7MGq

  • release-candidates available for 36 APIs in 19 repositories.

• M4 date is to be maintained on Feb 28th, so the request to all API Sub Projects is the following ASAP:

  • Update the APIs that have “subscription APIs” in-line with the latest Commonalities public version. See guidelines here: https://lf-camaraproject.atlassian.net/l/cp/rU3hXEwU

  • Test the API release-candidate.

  • Prepare the public release PR

  • Add the “release-management_maintainers” as a reviewer when your public release PR is ready.

    • Having more reviewer to help @Herbert Damker & @Tanja de Groot will be appreciated.

    • Adding test result statements will be also helpful - like this one: https://github.com/camaraproject/DeviceLocation/issues/296#issuecomment-2669801467 – as a reminder: they are mandatory for Stable API public releases, and we want to minimize the needed exceptions. Please add in the issues also if you are working on tests, but will deliver them only shortly after the Spring25 milestones.

• M5 date: March 15th

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

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

• Working repository:https://github.com/camaraproject/tooling

• Will be introduced for Fall25 release cycle

• Please use the time up to M6 of Spring25 for feedback towards Release Management which points were most tedious, need to be improved, and especially how do you think they can be improved.

• @Kevin Smith will support the work in the Tooling repository and is interested to automate also tasks beyond linting

Any Other Business

• none

Next Meeting

• Next TSC Meeting will be on March 6th, 9:00 - 10:30 UTC (10:00 - 11:30 CET)

  • Question: who will not be able to join due to MWC? Will we have quorum?

    • Meeting will take place but short one, several key persons will not be in

• Specific agenda topics backlog:

  • none

Action items