Attendees & Representation
TSC Members attendance to be indicated in the table with an X in the far column.
Representative | Organization | Role | |
Deutsche Telekom AG | TSC Chair, Active Maintainer | ||
Deutsche Telekom AG | Active Maintainer | ||
Ericsson | Active Maintainer | ||
KDDI | Active Maintainer | ||
Orange | TSC Deputy Chair, Active Maintainer | ||
Radisys | EUC Representative | ||
Summit Tech | EUC Representative | ||
Telefonica | Active Maintainer | ||
Telefónica | Active Maintainer | ||
Verizon | EUC Representative | ||
Vodafone | TSC Deputy Chair | ||
Vodafone | Active Maintainer | ||
Vonage | Active Maintainer | ||
George Glass | TM Forum | TM Forum Representative | |
TM Forum | TM Forum Representative | ||
GSMA | GSMA Representative | ||
GSMA | GSMA Representative |
Community members may use @name tag to mark their attendance.
Community:
LF Staff:
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
API Backlog
Commonalities
Identity & Consent Management
Release Management
Specific Topics
Arazzo Specification discussion
Any Other Topics
Minutes
Review and approval of previous meeting minutes
Minutes of previous TSC meeting: <add link>
...
Action Item Review
See home page Technical Steering Committee for current list of open action items
…
Governance & Project Management issues
TSC Election (Casey Cain)
…
Wiki migration done
Sandbox/Incubated/Graduated approach
Draft PR for changes of ProjectCharter and ProjectStructureAndRoles available in https://github.com/camaraproject/Governance/pull/161
Reviews and feedback already welcome
TBD: creation of API-Onboarding-and-Lifecycle document (update of current API-Onboarding.md with the new approach)
API Backlog (Jorge Garcia Hospital patricia.serranogonzalez@telefonica.com )
Repository for DedicatedNetwork created (as decided last meeting), TelcoIndex naming still under discussion along supporters.
New API proposals brought to TSC (2):
See informative message https://lists.camaraproject.org/g/tsc/message/230
Scope Enhancement for Network info:
Supported by Vodafone and DT. Filled template: link. Original issue: 66.
Meant for including more information on current Device Status API, including Network Type (e.g.2/34G, 5GNSA/SA, non-3GPP..)
Decision: Not for decision, only informative as already agreed in both backlog and subproject. Already included into Device Status group scope, as agreed in issue 143 and PR 158.
Consent URL API:
Supported by Telefonica and KPN. Filled template: link. Original issue: 68. Additional material: link
Meant for providing an out-of-band consent gathering mechanism that can be triggered in a separated moment (apart from API authentication phase) and in an arbitrary device (not only the API-targeted device), enhancing current mechanisms tied to Authcode or CIBA token flows.
Decision:
Commonalities (Rafal Artych )
An issue for the scope version 0.5.0 : Commonalities/issues/273
All issues from the scope are marked with Spring25 label
Critical issues are additionally marked with priority label
Clean up and redesign of API Design Guidelines Commonalities/issues/306 - to be done after implementing changes in the guidelines
Maintenance release (0.4.1) needed to resolve # 301 Broken link to dpv document
Identity & Consent Management (Axel Nennker )
Release r0.2.1 which fixes some links
Release Management (Tanja de Groot Samuel Adeyemo )
Spring25 M0: the meta-release kick-off can be done in today’s TSC meeting. An email to all mailing list will be sent to inform the community. The meta-release plan is available here: Meta-release Spring25.
Spring25 M1: Due to delays in the Fall24 meta-release, the M1 date is slightly impacted and shifted from Oct 15th to Oct 31st.
Exceptionally, the M1 will not yet have an alpha release available for Commonalities and ICM, but the relevant set of PRs covering the scope of the upcoming release shall be made available for Sub Project team review as follows:
PRs for critical issues by Oct 15th
PRs for other issues by Oct 31st
Alpha releases will be created as fast as possible after that and an M1 update announcement shall be sent at that point.
Info for Sub Projects: the API release tracker content for Spring25 is being updated, so please DO NOT create new API release trackers for Spring25 yet. Fall24 API release trackers SHALL NOT be copied. The new version will be available shortly.
Fall24 M6: The date is slightly delayed. Feedback is being integrated in the process and artefacts. This has no impact on the Spring25 content progress and should be finished latest by Oct 31st.
Arazzo Specification discussion (Kevin Smith)
An introduction to the recently-released Open API Initiative ‘Arazzo’ specification, for TSC consideration:
Any Other Business
...
Next Meeting
Next TSC Meeting will be on October 17th, 16:00 CEST / 07:00 PST / 14:00 UTC
Specific agenda topics backlog:
...