2025-07-03 TSC Minutes

DRAFT MINUTES

Attendees & Representation

LF Staff:

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

  • ...

• 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/137265620

  • No comment - Approved

Action Item Review

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

  • Marketing activity for Fall25 still to be clarified

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

• https://github.com/camaraproject/ReleaseManagement/issues/238

  • Action: Need - at least for all stable API - to check if a patch release will be good enough (eg for OTP Validation)

  • Direction: API repositories can participate with a patch release within the meta-release

  • Details will be discussed within Release Management, processes are already in place

    • Especially timing regarding M3 vs M4

    • In current release cycle recommendation will be given based on existing release PRs (potentially changing to patch releases)

API Backlog ( @Alberto Ramos Monaga )

• No new APIs or proposals for this session.

For information:

• (urgent) API repository split was pushed for existing Location Insights repository due to:

  • Release Candidate for Most Frequent Location was been pushed

  • No new updates or information for Device Visit Location

• Frozen API proposal was merged (/Governance/pull/190) proposal for freezing API proposals and repositories when there is no activity. WoW will be implemented in backlog from now on.

Commonalities (@Rafal Artych )

• Commonalities r3.2 is created.

• Latest changes:

  • https://github.com/camaraproject/Commonalities/pull/488 - merged

  • https://github.com/camaraproject/Commonalities/pull/490

  • https://github.com/camaraproject/Commonalities/pull/492

• Release Management clarification

  • When implementing only changes related to Commonalities requirements should the patch version or minor version be incremented? (Are Commonalities changes bug fixes or improvements)

    • For subscription APIs there are breaking changes like subscription-ends --> subscription-ended and no stable API yet so minor version should be incremented v0.n.x → v0.n+1.x

    • Other APIs: no breaking changes from Commonalities

      • stable APIs: Patch version Z (x.y.Z | x > 0) or Minor version Y (x.Y.z | x > 0) - https://semver.org/#spec-item-6

      • initial APIs (0.y.z)

    • Particular attention is required for stable. @Herbert Damker will run the Versioning Assessment tool on these API (like done for OTP) to check if Patch release is just good enough.

Identity & Consent Management (@Jesús Peña García-Oliva )

• camaraproject/IdentityAndConsentManagement

  • ICM is nearly ready for the Fall25 public release. The only pending action is creating the public release PR. The deadline for the release is two weeks before the M4 milestone, which is currently set for August 31st, leaving ample time.

  • Clarify and Generalize login_hint Usage to Include Operator and Temporary Tokens (TS.43) in ICM documentation · Issue #296 - PR #297 to clarify the use of operator token as a TS.43 token is approved and will be merged into the public release r3.3.

  • Further info in ICM 0.4.0 - preparing the scope for meta-release Fall25 · Issue #275.

• camaraproject/ConsentInfo

  • The legalBasis field will be removed from the API response, and the API design will be amended to make it agnostic to the underlying legal justification for data processing.

  • The API endpoint path will be changed from /verify to /retrieve for better semantic accuracy and alignment with other CAMARA APIs.

  • The API will be enhanced to allow API Consumers to query the status for multiple scope-purpose combinations in a single API call.

  • All project documentation, including the README file and the API Backlog proposal, will be updated to reflect the new "legal basis agnostic" design of the API.

  • https://github.com/camaraproject/ConsentInfo/issues/24 - Created a draft pull request (#25) for the release candidate and a separate PR (#30) for the required API test definitions.

• Further info in https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/152338712

Release Management (@Tanja de Groot)

• Fall25 M3 cut off date for release PRs was Jun 28, but not all APIs are ready.

• Currently 62 APIs are proposed for the meta-release:

  • 27 new APIs

  • 35 updated APIs (of which 11 stable APIs (all 9 Spring25 stable APIs updates plus 2 first-time stable APIs)

  • These APIs account for 44 repositories to be reviewed.

• M3 readiness of (repository) release PRs:

  • 26 repositories have release PRs and release review issues - Release Management reviews have started

  • 7 addition repositories have a release PR in draft mode, as previous PRs still need to be merged

  • 7 repositories do not yet have a release PR but are more or less on the way

  • 4 repositories are proposed to not proceed for Fall25 (on

    • NetworkAccessManagement (many open issues without PRs, recommend to split yaml and to do a first release outside of meta-release; target the Spring26 meta-release)

    • WebRTC (no updates for Fall25, suggest to target the Spring26) - update: work resumed, potentially will participate in Fall25

    • HighThroughputElasticNetworks (no scope issue, no yaml, no PRs)

    • IoTSIMFraudPrevention (no scope issue, no yaml, no PRs)

• Additional people are now part of the Release Management review team: thanks to Kevin and Jose Luis to have joined their forces

  • 40 repositories to be reviewed over next week is 8 reviews per day = 1 new or 2 (new+update) reviews per person per day.

• PROPOSAL:

  • exceptionally, allow the 14 pending release PRs to be submitted until next tuesday COB July 8 (final cutt-off date)

  • Reviews already started and would be running in parallel until July 16th (one week is expected to be too short)

  • M3 final declaration by TSC on July 17th.

• NOTE, for APIs not doing any MAJOR or MINOR updates, but only PATCH updates in particular to align with Fall25 Commonalities and ICM, just a maintenance release may be done to be included in Fall25. See issue Allow maintenance releases to participate in the meta-releases · Issue #238 · camaraproject/ReleaseManagement.

Any Other Business

• ...

Next Meeting

• Next TSC Meeting will be on July 17th, 15:00 UTC

• Specific agenda topics backlog:

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

     

Action items