2024-04-18 TSC Minutes

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. 

LF Staff:

Community:

Agenda

• 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

• Minutes of previous TSC meeting: 2024-04-04 TSC Minutes
  • ...

Action Item Review

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
  • See https://github.com/camaraproject/Governance/issues/124
• New working flow - API Approval (Ricardo Serrano Gutierrez )
  • See https://github.com/camaraproject/Governance/issues/122
  • ...
• Move Working Groups into own Sub Project repositories
  • See https://github.com/camaraproject/Governance/issues/84
  • API Backlog - initial list of maintainers (see previous TSC Minutes) (as of https://lists.camaraproject.org/g/tsc/message/165):
    

    Ricardo Serrano	Telefonica	MAINTAINER/CODEOWNER	@TEF-RicardoSerr
    Ludovic Robert	Orange	MAINTAINER	@bigludo7
    Jorge Garcia	Telefonica	MAINTAINER	@jgarciahospital
    Mark Cornall	GSMA	MAINTAINER	@MarkCornall
    Eric Murray	Vodafone	MAINTAINER	@eric-murray
    Noel Wirzius	DT	MAINTAINER	@NoelWirzius
    Christopher Aubut	Charter Comunications	MAINTAINER	@caubut-charter

    (additional Codeowners to be agreed within the Maintainer Group, 3 recommended)

API Backlog (Ricardo Serrano Gutierrez )

• 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)
    • "FrequentLocation" under discussion as alternative name
    • Proposed Initial maintainer/codeowner: 
      • Fernando Prado
      • Fabrizio Moggio
    • Will be potentially managed within "Location Insights" family together with "Device Visit Location"
    • ...
  • "Best Interconnection" and "Device Visit Location" waiting for Maintainer/Codeowner lists
• API Proposal "Device Quality Indicator" to be added to DeviceStatus sub project (see https://lists.camaraproject.org/g/tsc/message/160)
• Initial Maintainer for the to be created API Backlog Sub Project :

Commonalities (Rafal Artych )

• Draft scope for v0.4 release (relevant for Fall-24 meta-release) for discussion:
  • https://github.com/camaraproject/Commonalities/issues/175
• 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 )

• Working on getting https://github.com/camaraproject/IdentityAndConsentManagement/pull/121 merged.
  
  • Still some discussion on how to specify purpose
• Hoping to convince participants that the current version is a working compromise on what we can  agree on
• Some new issues for after the merge e.g.: ICM examples
• Some old issues for after the merge e.g.: DPoP
• First discussions/issues on operator token and how to support them in ICM and Camara APIs

Release Management (Tanja de Groot Samuel Adeyemo )

• Current time plan (from https://wiki.camaraproject.org/x/3qN3):
  
• Meta Release Fall24
  • M0 approved and M1 initiated.

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