DRAFT AGENDA
...
| 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 |
...
- 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/159Detailed , detailed proposal within Wiki: https://wiki.camaraproject.org/x/2IBFAg
- Comments from Thanks to Jorge Garcia Hospital :
- Concern about the mix/confusion (outside of the CAMARA community) we can have between the status of the project vs the status of the API crafted. Need clarification of the role of supporter and then maintainer/codeowner. Jorge Garcia Hospital point is that we can have supporter and then no commitment to have Maintainers - project have the risk to stay stuck. 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
...
- 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 )
...