DRAFT AGENDA
Attendees & Representation
TSC Members may indicate their attendance by marking an X in the column to the right.
Community members may use @name tag to mark their attendance below the table.
| 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 |
LF Staff:
Community:
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
- Release Management
- API Backlog
- Commonalities
- Identity & Consent Management
- Specific Topics
- Arazzo Specification discussion (Kevin Smith)
- Any Other Topics
Minutes
Review and approval of previous meeting minutes
- Minutes of previous TSC meeting: 2024-09-05 TSC Minutes
- ...
Action Item Review
- See home page Technical Steering Committee
- ...
Governance & Project Management issues
- Migration of wiki.telekom.de into Atlassian Cloud
- Was tentatively scheduled for August 29th ... any update? (Casey Cain )
- Sandbox/Incubated/Graduated/Archived proposal - new proposal for the lifecycle of API Repositories
- Reminder: Issue in Governance to comment: https://github.com/camaraproject/Governance/issues/159, detailed proposal within Wiki: https://wiki.camaraproject.org/x/2IBFAg
- Thanks to Jorge Garcia Hospital for intensive review and valuable comments.
- Agreed changes to the proposal based on the comments (not yet. applied to the proposal text):
- Clarification that there are for cases of outcome for scope enhancements / new API proposals in API Backlog (if accepted within the working group):
- Scope enhancements which are only impacting existing APIs are handled in existing API Repository
- Scope enhancements proposed by a Sub Project and resulting in a new API: The Sandbox API Repository will immediately part of a Sub Project.
- If an independent API proposal aims to be part of an existing Sub Project and gets accepted by the Sub Project, the Sandbox API Repository will be part of the Sub Project from the beginning as well.
- An independent API proposal which has no target Sub Project gets only a Sandbox API Repository, but yet a Sub Project.
- Within the Incubation pre-requisites it is sufficient that a previous (initial) version has been implemented – deleting the requirement that it has been (commercially) "launched"
- Clarification that there are for cases of outcome for scope enhancements / new API proposals in API Backlog (if accepted within the working group):
- Further points:
- Clarification that the nomination of a Maintainer for an API Repository after the initial development phase isn't time consuming, to encourage the active support from operators for an API they want to get incubated
- With the current proposed requirements
Release Management (Tanja de Groot) - updated
- Meta-release Fall24 - CAMARA Project - Confluence
- M5 declared, as announced on the all mailing list (https://lists.camaraproject.org/g/all/topic/camara_fall24_meta_release/108462715)
- Next release cycle ("Spring25") starts on September 30th (M0 - Kickoff)
- Initial indication that the M1 may need to be delayed. Date to be determined next week in RM meeting.
- M6: feedback on release process welcom from all participants. Please provide feedback either as a GitHub issue in the ReleaseManagement repo or on the Meta-release feedback page.
- Updates to the process will be incorporated for use in the upcoming meta-release.
API Backlog (patricia.serranogonzalez@telefonica.com Jorge Garcia Hospital )
- Repository for QualityByDesign created (as decided last meeting)
- TelcoIndex API
- Dedicates Networks API
Commonalities (Rafal Artych )
- An issue is open to discuss the scope of the next version: Commonalities/issues/273 - scope should be closed for
- Since 5 APIs are now stable - how to deal with guidelines enforcing breaking changes
Identity & Consent Management (Axel Nennker )
- ICM patch release r0.2.1
- Discussion on signed authentication requests
- Sorting issues into what is planned to be included in Spring25
Specific Topic: Arazzo Specification discussion (Kevin Smith )
Any Other Business
- ...
Next Meeting
- Next TSC Meeting would be on October 3rd at 10:00 CEST / 8:00 UTC / 01:00 PST
- Specific agenda topics (backlog):
- ...
Action items
- ...