2024-09-05 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:

Community: @Ben Hepworth @Samuel Adeyemo @Rafal Artych @Tanja de Groot @Pierre Close Patricia Serrano @Salehi, Farnaz | Faren | RMI  @Jorge Garcia Hospital @Ming Hui 

Agenda

• Review and approval of previous meeting minutes

• Action Items Review

• General Topics

  • API Backlog

  • Release Management

  • Identity & Consent Management

  • Commonalities

  • Governance & project management issues

• Specific Topics

  • ...

• Any Other Topics

Minutes

Review and approval of previous meeting minutes

• Minutes of previous TSC meeting: 2024-08-22 TSC Minutes
  
  

  • No comment - agreed

Action Item Review

• See home page Technical Steering Committee

  • email poll for Open source Summit still to be done.

API Backlog (@Ricardo Serrano Gutierrez @Jorge Garcia Hospital )

• Patricia Serrano introduction - Patricia steps in for Ricardo. Welcome !

• Info: New repositories for DeviceQualityIndicator, DeviceDataVolume, SubscriptionStatus are created

• New API proposal brought to TSC: QualityByDesign

  • See message https://lists.camaraproject.org/g/tsc/message/223

  • Proposal supported by Charter, Liberty Global, Vodafone

    • This API would be part of the Connectivity Insights API Family

    • ... but separate repository

  • API Proposal: Link

  • Discussion on the name of the API - @Chris Howell raised that Quality by Design is probably too marketing

    • Consider to rename it.

    • @Herbert Damker Discussion of an user story under this title make sense, but "QualityByDesign" will be a larger story, involving several APIs, including the QualityOnDemand family.

  • Discussion about how the QoS score could be computed

    • @Kevin Smith Research into the scoring (this is IETF, but also active in Broadband Forum via the Quality Attenuation standard): https://datatracker.ietf.org/doc/draft-olden-ippm-qoo/

    • As of now QoSscore computing is not part of the API. This is an issue for @Ludovic Robert @Chris Howell - We need some uniformity to compute this. @Kevin Smithagreed - data send back must be consistently across implementations.

  • Next steps:

    •   Do we create a repo with current name? or another name? QualityInsights? QualityAction?

    • TSC Proposal:

      1.  @Herbert Damker creates the repo QualityByDesign 

      2.  @Ben Hepworthprovides user story/ies, 

      3. (Project team) Discuss the concept & propose rename

      4. (TSC) Adjust the name

    • (Regarding execution of 2- 4.: @Herbert Damker will create an issue within the new Repository which will point this out)

Release Management (@Tanja de Groot Initial content by @Herbert Damker on behalf)

• Meta-release Fall24 - CAMARA Project - Confluence

  • M4 Release Pull Requests available for 25 APIs which will be in the Meta-Release

    • Team of reviewers: @Tanja de Groot @Samuel Adeyemo @Herbert Damker @Rafal Artych @Ludovic Robert @Jose Luis Urien Pinedo 

    • Some issues found during the reviews - addressed by Codeowners of the API Repositories

    • Some final reviews outstanding

  • Release PR with Stable APIs - all reviews are almost done

    • location-verification - DeviceLocation 

    • number-verification - NumberVerification  

    • one-time-password-sms - OTPValidation 

    • simple-edge-discovery - SimpleEdgeDiscovers

    • sim-swap - SimSwap 

  • All five Stable APIs are blocked by the same issue: the mandatory Test Statement has not been done

    • See issue #89 in ReleaseManagement: Clarify how to proceed with requirement "Test result statement" for stable APIs 

    • What is the requirement: "Statement in a discussion issue of the API Sub Project by at least one of the API Sub Project members that the Gherkin feature files have been successfully executed against their (lab) API implementation." 

    • We need a decision here in the TSC if and how we exempt the Stable API candidates in the Fall24 Meta-Release from this requirement

      • @Tanja de Groot raised the point about our confidence to release these APIs in stable without performing complete testing

      • @Herbert Damker not an example but we should let go. These APIs have been implemented already in several countries. 

        • If we have issue in the test definition we can have a patch version

        • We have to add a sentence to warn about this point.

        • in the checklist table we fill a link in the column & and redirect to the footnote

          @Tanja de Groot will propose a footnote and provide information on issue #89

  • TSC Approval of M4 (all release PRs of Sub Project reviewed by Release Management)

    • We can merge release PRs and create the releases when review completed

    • M4 Release tracker date:  date when the merged is done by the project

  • Next Steps for M5 (all release PRs merged and public releases created)

• Next release cycle ("Spring25") starts at September 30th (M0 - Kickoff)

• @Herbert Damker shared a slide deck introducing the CAMARA release management

  • Attached to the minutes below.

Identity & Consent Management  (@Axel Nennker )

• Public Release r0.2.0 available since August 22nd

• An issue is open to discuss the scope of the next version: IdentityAndConsentManagement/issues/193 - scope should be closed for Sep 30, 2024 

• @Chris Howell asked for more feedback on 'Replace Frontend Flow to unify consent collection and reduce latency' GitHub Issue

Commonalities (@Rafal Artych )

• Public Release r0.4.0 available since August 23rd

• An issue is open to discuss the scope of the next version: Commonalities/issues/273 - scope should be closed for Sep 30, 2024

Governance & Project Management issues

• EasyCLA Introduction (@Casey Cain )

  • Activated on August 30th for all repositories (https://lists.camaraproject.org/g/all/message/82)

  • Issues experienced?

    • Only one issue so far- resolution in progress

• Communication Material for Meta-Release

  • Press Release prepared by Marketing Working Group (@Jill Lovato  @Markus Kümmerle ), reviewed and completed by @Herbert Damker 

    • Send to CAMARA Board Members for quotes

  • Slides about CAMARA Meta-Releases and the content of Fall24 Meta-Release prepared by @Herbert Damker 

    • Slides are meant to complement the CAMARA (marketing) presentation

• Sandbox/Incubated/Graduated/Archived proposal - new proposal for the lifecycle of API Repositories

  • Issue in Governance to comment: https://github.com/camaraproject/Governance/issues/159

  • Detailed proposal within Wiki: https://lf-camaraproject.atlassian.net/wiki/x/sive

    • Comments from @Jorge Garcia Hospital :

      • Concern about the mix/confusion (outside of the CAMARA community) we can have between the status of the project vs the status of the API crafted.

      • Need clarification of the role of supporter and then maintainer/codeowner. @Jorge Garcia Hospital  point is that we can have supporter and then no commitment to have Maintainers - project have the risk to stay stuck. 

• Migration of wiki.telekom.de into Atlassian Cloud

  • Was tentatively scheduled for August 29th ... any update? (@Casey Cain )

Any Other Business

• none

Next Meeting

• Next TSC Meeting would be on September 19th at 16:00 CEST / 04:00 UTC / 07:00 PST

• Specific agenda topics backlog:

  • @Kevin Smith Arazzo Specification discussion https://lists.camaraproject.org/g/tsc/topic/camara_tsc_arazzo_1_0/107766330, to be scheduled in next TSC.

Action items