...
| Representative | Organization | Role | |
|---|---|---|---|
Deutsche Telekom AG | TSC Chair, Active Maintainer | X | |
Deutsche Telekom AG | Active Maintainer | X | |
Ericsson | Active Maintainer | X | |
KDDI | Active Maintainer | X | |
Orange | TSC Deputy Chair, Active Maintainer | X | |
Radisys | EUC Representative | ||
Summit Tech | EUC Representative | ||
Telefonica | Active Maintainer | X | |
Telefónica | Active Maintainer | X | |
Verizon | EUC Representative | ||
Vodafone | TSC Deputy Chair | X | |
Vodafone | Active Maintainer | X | |
Vonage | Active Maintainer | ||
| George Glass | TM Forum | TM Forum Representative | X |
TM Forum | TM Forum Representative | X | |
GSMA | GSMA Representative | X | |
GSMA | GSMA Representative | X | |
Airtel | Active Maintainer |
...
- Initial content:
- To keep the number and variety of Sub Project within CAMARA manageable we have two proposals currently:
- Raise the barrier for new API Sub Projects to limit the number of Sub Projects and ensure their sustainability from the beginning, as proposed within issue #122 New working flow - API Approval
- Introduce different lifecycle phases for API Sub Project with a lightweight managed "Sandbox" phase before an API will get fully "Incubated" into CAMARA, as proposed in #129 Proposal for new API Project lifecycle approach (Sandbox + Incubated)
- Slides as presented within CAMARA Board Meeting at April 25th for proposal "129":
View file name API Sub Project Lifecycle - 04-25-2024.pdf height 150 - Feedback on the lifecycle phases within the Board was positive. There was a comment that the proposals are no either/or, that the criterium from #122 can be used at one of the gates of #129 (e.g. from Sandbox to Incubated)
- To keep the number and variety of Sub Project within CAMARA manageable we have two proposals currently:
- Discussion
- for proposal "129":
- Sandbox project would not require at least 2 contributors... 1 could be fine.
- Sandbox project could be managed in a separated Git Hub organization (e.g. "camarasandbox") to avoid confusion (to be checked with LF)
- Incubated project will require at least one production API implementation
- We will need a table to explain how sandbox & incubated version will be managed
- Impact on the API readiness checklist, maybe split into two different checklists
- Comments are welcome on both issues.
- for proposal "129":
Any Other Business
- Shilpa Padgaonkar Keeping in lines with commonalities WG, would be good to have one more Codeowner for ICM WG (we currently have 1 codeowner from TEF and 1 from DT).
...
- Next TSC Meeting will be on May 16th at 16:00 CEST / 14:00 UTC / 07:00 PST
- Specific agenda topics backlogfor May 16th - 20mn - Olta Vangjeli :
- Update from TMForum collaboration and how members are working in Catalysts and Operate APIs (Olta Vangjeli )
- Catalyst and Operate APIs update
- Can we have more usecases proposed how TMForum APIs and Camara communicate in e2e journeys
- ...
- Update from TMForum collaboration and how members are working in Catalysts and Operate APIs (Olta Vangjeli )
...