DRAFT AGENDA
Attendees & Representation
...
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 | ||
Chris Howell | Vonage | Active Maintainer | |
George Glass | TM Forum | TM Forum Representative | |
TM Forum | TM Forum Representative | ||
GSMA | GSMA Representative | ||
GSMA | GSMA Representative |
...
- Review and approval of previous meeting minutes
- Action Items Review
- General Topics
- Governance & project management issues
- API Backlog
- Commonalities
- Identity & Consent Management
- Release Management
- Meta Release Fall24
- M0 approved and M1 initiated.
- Meta Release Fall24
- Specific Topics
- ...
- Any Other Topics
...
- Easy CLA Introduction
- Discussion with GSMA ongoing (Casey Cain)
- Proposal for decision: Activate EasyCLA without further delay, as already previously decided for several past dates
- Rational:
- Contributor License Agreements (CLA) or DCO (Developer Certificate of Origin) has to be introduced and enforced - mandatory for LF projects
- Linux Foundation recommended the use of EasyCLA for CAMARA, accordingly the activation of EasyCLA have been prepared
- Linux Foundation recommended the use of EasyCLA for CAMARA, accordingly the activation of EasyCLA have been prepared
- CLAs (or DCO) are necessary to protect contributors and project maintainers, it ensure that all contributions are done in accordance with the license of the project (ingoing = outgoing)
- GSMA has their OPAG "Sandbox" as agreed, to be able to contribute work which was created within OPAG to CAMARA
- Discussion & Decision:
- ...
- Rational:
- Note: The ProjectCharter is requiring currently both, CLA and DCO, that is according to Open Source experts unnecessary. Has to be resolved and updated together with LF.
- Update of README.md structure in all sub projects
- New working flow - API Approval (Ricardo Serrano Gutierrez )
- Move Working Groups into own Sub Project repositories
- See https://github.com/camaraproject/Governance/issues/84
- API Backlog - list of maintainers (Ricardo Serrano Gutierrez )
- ...
...
- 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 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 )
...
- 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: according to messages on the mailing lists there is a contribution in preparation, based on off-line work between MTN and Airtel.
- ...
...