Attendees & Representation
| ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Representatives | Organization | Role | ||||||||||
Deutsche Telekom AG | Maintainer | x | ||||||||||
Deutsche Telekom AG | Maintainer | x | ||||||||||
Ericsson | Maintainer | x | ||||||||||
KDDI | Maintainer | x | ||||||||||
Orange | Maintainer | x | ||||||||||
Nokia | Maintainer, Release Manager | x | ||||||||||
Telefonica | Maintainer | x | ||||||||||
Telefónica | Maintainer | x | ||||||||||
Vodafone | Maintainer | x | ||||||||||
Verizon | Maintainer | x | ||||||||||
EUC Representative | x | |||||||||||
Verizon | EUC Representative | |||||||||||
Summit Tech | EUC Representative | x | ||||||||||
George Glass | TM Forum | TM Form Representative | ||||||||||
GSMA | GSMA Representative | x |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Community members may use @name tag to mark their attendance |
Community: Rafal Artych Kevin Smith Axel Nennker Mark Cornall Pierre Close Gary Clift G. Murat Karabulut Olta Vangjeli Artur Krukowski
LF Staff: Casey Cain
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
General Topics
Governance & project management issues
Release Management
API Backlog
Commonalities
Identity & Consent Management
Specific Topics
...
Any Other Topics
Minutes
Review and approval of previous meeting minutes
Minutes of previous TSC meeting: 2025-03-06 TSC Minutes
no comments
Action Item Review
See home page Technical Steering Committee for current list of open action items
all done
Governance & Project Management issues
Wiki update (Casey Cain)
Visual Flair (Work in progress)
⚛️ Repositories
✍️ Minutes Pages (top level)
🏁 API Release Tracking
Landing pages updated
https://github.com/camaraproject/Governance/issues/184 :
2FA requirement will be enabled on March 24th, still 22 people with disabled 2FA
Material for Spring25 communication
Clean-up of Spring25 meta-release page by Tanja de Groot
Press Release in preparation by Jill Lovato (technical input Herbert Damker )
CAMARA Presentation update in work by Markus Kümmerle
Update of CAMARA GitHub README in https://github.com/camaraproject/.github/pull/14 by Herbert Damker
Hint: Updated table in preview mode[Update: the PR is merged in meantime, see https://github.com/camaraproject for the overview README]
Release Management (Tanja de Groot )
Release Management team has declared Spring25 M4 on March 18.
All Sub Projects have provided their public API release. See: Meta-release Spring25
13 new APIs (in 10 repositories (2 from Fall24)): BlockchainPublicAddress, DeviceStatus, CustomerInsights, DeviceIdentifier, DeviceSwap, KnowYourCustomer, Tenure, NumberRecycling, RegionDeviceCount, WebRTC
23 updated Fall24 APIs (of 25, in 11 repositories): ConnectivityInsights, CallForwardingSignal, CarrierBillingCheckout, DeviceStatus, DeviceLocation, KnowYourCustomer, NumberVerification, OTPValidation, PopulationDensityData, QualityOnDemand, SimSwap
The Spring25 meta-release has a total of 36 APIs in 19 API repositories
For stable APIs, test statement of at least one API implementer is part of the API readiness checklist. For the 6 8 stable APIs:
4 6 have provided partial API test statements: code generation was successful, but the test feature files have not yet been used (DeviceLocation, DeviceStatus, QualityOnDemand, SimSwap)
2 APIs have not provided any test statement yet (NumberVerification, OTPValidation).
Release management proposes to TSC that an exception is applied for this meta-release, as, due to delays in schedule, limited time was available to do actual testing. The risk on problems with these APIs is expected to be low because:
4 of the stable APIs were already stable in Fall24 (DeviceLocation, NumberVerification, OTPValidation, SimSwap), so low risk.
2 4 new stable APIs (DeviceStatus, QualityOnDemand) have partial test statements and are expected to be tested as soon as the test support for feature files has been put in place.
Release management has asked the Sub Projects to keep the test statement issues open for some time to gather more information and give credibility to the stability of the APIs.
Request to TSC to declare Spring25 M5 - meta-release milestone
Proposal accepted and M5 declared: Supported by TSC
We have had discussion about GSMA certification for Number Verification 2.0 - This point requires additional discussion between CAMARA and GSMA about minimal scope required for certification (Does only one flow authCode or CIBA is just good enough or do we mandate both flows?).
API Backlog (Jorge Garcia Hospital)
Update on voting results (mail to TSC to be added heresee also https://lists.camaraproject.org/g/tsc/message/276 ): The TSC approved with their votes the creation of ConsentInfo, IoT Network Optimization, and Dynamic Predictive Connectivity Data
Consent Info API (API Onboarding tracker) - repository already created: ConsentInfo
IoT Network Optimization (API Onboarding tracker)
Dynamic Predictive Connectivity Data (API Onboarding tracker)
One new API proposed: eSIM Remote Management
(See message from Jorge Garcia Hospital with proposal for eSIM Remote Management)
Supported by China Unicom, original issue, eSIM Remote Management template
Decision: OK to move forward.
Note: Network Health Assessment & Network Traffic Analysis proposals, reviewed during previous TSC and with pending comments to be solved are still under fix.
API descriptions to be updated according to Spring25 release (version and content, if applies).
Especially needed is an update for NumberVerification 2.0.0 in r2.4
Commonalities (Rafal Artych )
Started draft PR https://github.com/camaraproject/Commonalities/pull/430
removed redundant, descriptive texts and reordered content → CAMARA API Design Guide.md
dedicated subscription guidelines → CAMARA API Event Subscription and Notification.md
Discussions in https://github.com/camaraproject/tooling/discussions
Identity & Consent Management (Axel Nennker )
https://github.com/camaraproject/IdentityAndConsentManagement/issues/275
issued were labeled fall25 Thanks Jesús Peña García-Oliva
https://github.com/camaraproject/ConsentInfo/
Repository was created and work started.
Consent Info API PR https://github.com/camaraproject/ConsentInfo/pull/4
https://github.com/camaraproject/IdentityAndConsentManagement/pull/268
Any Other Business
Request for TSC to poll API authors (Kevin Smith)
what environment(s) they use to edit APIs
what challenges they experience in the API production lifecycle
The purpose is to help the Tooling repository produce the most useful and useable tools.
Marketing consideration for September release as Open Source Summit Europe occurs end of August - do we want to target this date?
Not sure…Herbert Damker we might need to identify another appropriate event for the announcement of Fall25 meta-release, as otherwise too many activities of the release cycle would happen in the vacation time and there would be again not enough time for testing of the release candidates. M5 target date is currently September 15th.
Action item: Herbert Damker to discuss announcement event of Fall25 meta-release with Marketing working group
Next Meeting
Next TSC Meeting will be on Thursday, April 3rd, 09:00 UTC (Note: 11:00 CEST / 02:00 PST)
Herbert Damker will be on KubeCon EU in London, not able to join.
Eric Murray / Ludovic Robert will step in
Specific agenda topics backlog:
...
...
Action items
- Herbert Damker to discuss announcement event of Fall25 meta-release with Marketing working group