Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

DRAFT AGENDA

Attendees & Representation

TSC Members may indicate their attendance by marking an X in the column to the right.

Community members may use @name tag to mark their attendance below the table. 

RepresentativeOrganizationRole

Herbert Damker 

Deutsche Telekom AG

TSC Chair, Active Maintainer

Shilpa Padgaonkar

Deutsche Telekom AG

Active Maintainer

Jan Friman 

Ericsson

Active Maintainer

Toshi Wakayama

KDDI

Active Maintainer

Ludovic Robert 

Orange

TSC Deputy Chair, Active Maintainer

Adnan Saleem 

Radisys

EUC Representative

Doug Makishima 

Summit Tech

EUC Representative

diego.gonzalezmartinez

Telefonica

Active Maintainer

Jose Luis Urien Pinedo

Telefónica

Active Maintainer

Mahesh Chapalamadugu

Verizon

EUC Representative

Eric Murray 

Vodafone

TSC Deputy Chair

Kevin Smith 

Vodafone

Active Maintainer
Chris Howell

Vonage

Active Maintainer
George Glass

TM Forum

TM Forum Representative

Olta Vangjeli 

TM Forum

TM Forum Representative

Henry Calvert 

GSMA

GSMA Representative

Mark Cornall 

GSMA

GSMA Representative

LF Staff:

Community:

Agenda

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

  • Review and approval of previous meeting minutes
  • Action Items Review
  • General Topics
    • Governance & project management issues
    • API Backlog
    • Commonalities
    • Identity & Consent Management
    • Release Management
  • Specific Topics
    • ...
  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

DescriptionDue dateAssigneeTask appears on
  • Check if  linting can help to preserve backward compatibility (e.g. with warnings in case of breaking changes) Rafal Artych  
03 Oct 2024Rafal Artych2024-09-19 TSC Minutes

Governance & Project Management issues

  • 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:
        • ...
    • 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

API Backlog (Ricardo Serrano Gutierrez )

  • Approval request for new repositories (see https://lists.camaraproject.org/g/tsc/message/160)
    • BestInterconnection
      • Proposed Maintainer & Codeowners: ...
    • LocationInsights (with "Most Frequent Location" and "Device Visit Location" as API proposals)
      • Proposed Maintainer & Codeowners: ...
  • API Proposal "Device Quality Indicator" to be added to DeviceStatus sub project
  • ...

Commonalities (Rafal Artych )

  • 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 in config as well to manage request to get event when current situation of a device corresponds to the subscriptions type. .

Identity & Consent Management (Axel Nennker )

  • ...

Release Management (Tanja de Groot Samuel Adeyemo )

No life sign projects - how to handle these? (Ludovic Robert Eric Murray )

  • 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?
  • Device Swap: according to messages on the mailing lists there is a contribution in preparation, based on off-line work between MTN and Airtel.
    • ...

Any Other Business

  • ...

Next Meeting

  • Next TSC Meeting will be on ... <derive from https://wiki.camaraproject.org/x/KAAG>
  • 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?
    • ... 

Action items

  •  
  • No labels