2024-04-18 TSC Minutes

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: @Casey Cain @Evan Harrison 

Community: @Rafal Artych @Tanja de Groot @Ming Hui Foo @Yacine Kheddache @Pierre Close @Samuel Adeyemo @Ricardo Serrano Gutierrez @Axel Nennker 

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

  • Approved. 

Action Item Review

• For the list of open action items go to home page of Technical Steering Committee 

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

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

      • GSMA will come to a proposal to @Casey Cain and asks for one additional session with LF team.

        • @Herbert Damker did see other option to move forward.

          • Decision is at CAMARA board level with TSC recommendation.

        • @Casey Cain provided the options - We need to have one enforced anyway to act accordingly to our project charter.

          1. Have a decision at governing board

          2. Move to easyCLA right now (which is not really an option as we need governing board validation)

          3. Forgo the EasyCLA agreement and turn on DCO (Developer Certificate of Origin) enforcement.

        • @Mark Cornall will meet GSMA lawyers and get back to LF team with proposal.

        • @Casey Cain  will reach out to LF legal team in regard to CLA agreements, afterwards we can schedule a meeting with GSMA.

  • 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

  • @Casey Cain & @Evan Harrison will help project to adapt to new README.md file & meeting minutes details. Do not hesitate to email Casey & Evan  

• New working flow - API Approval (@Ricardo Serrano Gutierrez )

  • See https://github.com/camaraproject/Governance/issues/122

    • Prerequisite to have at least 3 companies supporting new API proposal to launch it.

    • We keep it open till next TSC to get community view.

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

    (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)
    
    

    • 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

  • "Best Interconnection" and "Device Visit Location" waiting for Maintainer/Codeowner lists

  • Also ready for creation: "Home Devices - Network Access Management":

    • Decision: Approved

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 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

• Request to working group: define scope of release which will follow the milestones below for the Fall-24 release.

Release Management (@Tanja de Groot @Samuel Adeyemo )

• Current time plan (from https://lf-camaraproject.atlassian.net/wiki/x/uR3e):
  
  

  Open

  

• 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 always do their releases together

    • The APIs can have different versions, but every API has to have a defined version within the release

    • Repository release tag names are decoupled from the API versions contained within the repository

  • If APIs won'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

    • 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 but in three repositories.

      • EdgeCloud is an example recommended to carve out in multiple repositories for API development

• 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 within next TSC meeting with more details.

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 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 Robert  will contact Wassem Amra. 

• IMEI Fraud: Eric was in contact with MTN (proposal owner of IMEI Fraud). 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.

Any Other Business

• @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)

Next Meeting

• Next TSC Meeting will be on May, 2nd, 2024 at 10:00 CEST / 08:00 UTC / 01:00 PST (see https://lf-camaraproject.atlassian.net/wiki/x/0RDe for meeting links)

• 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