...
- 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:
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
- ...
Any Other Business
- ...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 Meeting
- Next TSC Meeting will be on May 16th at 16:00 CEST / 14:00 UTC / 07:00 PST
- Specific agenda topics backlog:
- 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 )
...