2024-07-04 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: @Ricardo Serrano Gutierrez @Tanja de Groot @Pierre Close @Rafal Artych Lazlo Suto @Ramesh Shanmugasundaram @Guang-Han Ma @Samuel Adeyemo 

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

  • (none)

• Any Other Topics

Minutes

Review and approval of previous meeting minutes

• Minutes of previous TSC meeting: 2024-06-20 TSC Minutes
  
  

  • @Herbert Damker will check that there are no unintended changes to the minutes (two corrections in participants list done)(Update: Check done and draft status removed)

Action Item Review

• See home page Technical Steering Committee

Governance & Project Management issues

• EasyCLA Introduction (@Casey Cain )

  • Herbert prepared a simple Git Repo (EasyCLA) to allow testing:

    • camaraproject/EasyCLA: Repository for Contributors to test/initiate the EasyCLA signing process (github.com)

    • Up to the team to test by doing a short trivial PR

• New proposal how to manage "API Families" as Sub Projects with a set of API "family member" repositories
  
  

  • Proposal got approved and merged

API Backlog (@Ricardo Serrano Gutierrez )

• RegionUserCount got renamed into RegionDeviceCount

• ShortMessageService scope extended with "Receive SMS"

• DeviceStatus have been discussed the adoption of the two new APIs (Device Connection Quality Indicator, Device Data Volume). Issue still open for positions.

  • See Proposed Sub-Project Scope Enhancement: Device Quality Indicator API · Issue #176 · camaraproject/DeviceStatus (github.com)

Commonalities (@Rafal Artych )

• Release 0.4.0-rc.1

  • Release PR: #240

    • The PR will be merged EOB July 10th if no objection (bug fixes could be done after).

    • All TSC participants are asked to review the PR if not yet done.

Identity & Consent Management  (@Axel Nennker )

• Release 0.2.0-rc.1

  • Release PR: #177

    • The PR will be merged EOB July 10th if no objection (bug fixes could be done after)

    • All TSC participants are asked to review the PR if not yet done.

Release Management (@Tanja de Groot @Samuel Adeyemo )

Open

• Commonalities and ICM scope issues and alpha release PRs/releases under review for one week. 

  • M0 / pre-M1 / pre-M2 announcement - email sent (2024-07-04)

  • Approval to be provided in this TSC meeting

  • Declare M1 in this meeting ?

    • Only alpha version for commonalities -> M1 was done on June 10th (v0.4.0-alpha.1 released by Commonalities)

• Release PRs for M2 for Commonalities and ICM release-candidates ready for review by TSC (one week review time)

  • requested to add @camaraproject/tsc-participants as reviewers to the 2 release PRs
    (update: done by @Herbert Damker, added the team also with read access to the repository to allow to get them mentioned)

  • email to tsc list ready to be sent (update: done by @Tanja de Groot )

  • One week for Commonalities and ICM release PR review comments from today's TSC meeting (see also above)

  • RC proposals for Commonalities & ICM are in progress and be merged by July 10th. 

  • As such, M2 will be pronounced July 10th

• 18 APIs listed on the Fall24 meta-release plan.

  • Do we need to move the M3 as it is very soon? 

    • Keep it for now and check it during next TSC and decide then.

    • Question about requirement of the basic test cases & documentation for the release candidate step (M3)

      • Some answers can be found in API-Testing-Guidelines.md

  • We have to be aware of a Marketing event September 16th (on Open Source Summit 2024) where the meta-release is planned to be announced

  • This is the top priority for the projects right now.

    • We can inform code owners (via mail list) about the milestones check list 

Any Other Business

• No other comment.

Next Meeting

• Next TSC Meeting will be on July 18th at 16:00 CEST / 14:00 UTC / 07:00 PST

• Specific agenda topics backlog:

  • No proposal .... Release preparation makes the teams very busy  

  • Herbert proposed to have a sync with the Marketing team

Action items