...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
DRAFT
...
MINUTES
Attendees & Representation
...
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 | x | |
Summit Tech | EUC Representative | x | |
Telefonica | Active Maintainer | x | |
Telefónica | Active Maintainer | x | |
Verizon | EUC Representative | ||
Vodafone | TSC Deputy Chair | x | |
Vodafone | Active Maintainer | ||
Vonage | Active Maintainer | x | |
George Glass | TM Forum | TM Forum Representative | |
TM Forum | TM Forum Representative | ||
GSMA | GSMA Representative | x | |
GSMA | GSMA Representative | x |
...
- Approval request for new repositories (see https://lists.camaraproject.org/g/tsc/message/160)
- "Most Frequent Location" (see https://lists.camaraproject.org/g/tsc/message/164)
- Proposed Initial maintainer/codeowner:
- Fernando Prado (Telefonica)
- Fabrizio Moggio (TIM)
- Will be potentially managed within "Location Insights" family together with "Device Visit Location"
- Decision: Approved
- Proposed Initial maintainer/codeowner:
- "Best Interconnection" and "Device Visit Location" waiting for Maintainer/Codeowner lists
- Also ready for creation: "
Home Devices -Network Access Management":Name
Company
Role
GitHub User
Christopher Aubut
Charter Communications
CODEOWNER
@caubut-charter
Randy Levensalor
CableLabs
CODEOWNER
@RandyLevensalor
Mayur Channegowda
Vodafone
CODEOWNER
@mayur007
Justin Pace
Charter Communications
MAINTAINER
@justin-pace-charter
- Decision: Approved
- "Most Frequent Location" (see https://lists.camaraproject.org/g/tsc/message/164)
...
- Draft scope for v0.4 release (relevant for Fall-24 meta-release) for discussion:
- Proposal to tackle open subscription issues Common proposal to tackle subscription-based open issues. · Issue #185 · camaraproject/Commonalities (github.com) - mains points:
- Align our subscription model with CloudsEvents subscriptions one
- Introduce a
status
attribute in the template as we have fair UCs that can leverage this (Retrieve expired subscriptions for monitoring, deactivate a subscription if an user revoked her/his consent, etc...). API subproject could decide to use it or not. - Improve the model to allow consumers to subscribe to more than one event types with a single subscription but at least for the first meta-release we enforce to have only event type per subscription. After this first meta release decision to handle several event types in one subscription request should be discussed at API sub projet level
- Add
filters
and it's up to API Project to use it. We recommend to be very cautious as it add complexity so it should be keep for very relevant UC. - Add
initialEvent
inconfig
as well to manage request to get event when current situation of a device corresponds to the subscriptions type. .
Identity & Consent Management (Axel Nennker )
...
- Current time plan (from https://wiki.camaraproject.org/x/3qN3):
- Meta Release Fall24
- M0 approved and will be communicated
- M1 initiated.- main deliverable will be the release scope of Commonalities and ICM
- Approach for API families - latest proposals - two options
- Multiple APIs within one sub project:
- Have to release always do their releases together
- Can The APIs can have different versions, but every API has to have a defined version within the release package
- Repository releases release tag names are decoupled from the API versions contained within the repository
- If APIs won't be able to release together has t be able to release together (e.g. having different teams/codeowner working on it) they have to be in different repositories
- In this case API should be carved out into own sub project repositories
- Multiple A set of sub project repositories can be managed as a "family", with one wiki page, meeting etc.
- Today this is the case already with NumberVerify, OTP Validation and SimSwap. They are managed together in one meeting and but in three repositories.
- EdgeCloud is an example recommended to carve out in multiple repositories for API development
- Multiple APIs within one sub project:
- Sandbox "release" within Meta-release: will have x.y.z with x=0, "incubated" APIs will have x >= 1
- Sandbox and Incubated APIs can be together within one repository
- Tanja de Groot presented the current draft of the Release Checklist (note: link to work in progress document, content will change)
- Request to working group: elaborate Release Checklist and present against next meeting with more details.
...
- From past TSC Minutes:
- We have currently two project without (visible) work within the repositories
- Device Swap (repository created but no activity over the last 6 months)
- IMEI Fraud (Attached to device identifier repository but no activity there on this API)
- Are these APIs still relevant?
- If, yes, how to find volunteers who will work on them?
- If no volunteers: Postpone these APIs to a later time?
- We have currently two project without (visible) work within the repositories
- Device Swap seems to be solved: according to messages on the mailing lists there is a contribution in preparation, based on off-line work between MTN and Airtel. Ludovic will Robert will contact Wassem Amra.
- IMEI Fraud: Eric was in contact with MTN (proposal owner of IMEI Fraud). Will API will not be part of target release for Fall-24. If interest to develop will come up, setting up a separate Sub Project recommended.
- Action: Eric Murray to inform API Backlog and Helene from GSMA Product Team.
...
- Casey Cain presented the options to get current meeting invites <add details>.
- Action point: update entries within https://lists.camaraproject.org/g/all/calendar and delete entries within other mailing list calendars.
- Herbert Damker proposed to open a discussion to anchor (all) meetings in CAMARA on UTC time (not urgent, but should be concluded before end of EU daylight saving time in October)
...