Page Comparison

DRAFT AGENDA

Attendees & Representation

...

LF Staff: Casey Cain Evan Harrison 

...

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

      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)

  ...

  • Approval request for new repositories (see https://lists.camaraproject.org/g/tsc/message/160)
    Initial Maintainer for the to be created API Backlog Sub Project :
    • "Most Frequent Location" (see https://lists.camaraproject.org/g/tsc/message/164)
      
      • "FrequentLocation" under discussion as alternative name
      • 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
  • API Proposal "Device Quality Indicator" to be added to DeviceStatus sub project (see https://lists.camaraproject.org/g/tsc/message/160)
  • • 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

  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 )

  ...

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

  ...