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.
Representative | Organization | Role | |
---|---|---|---|
Deutsche Telekom AG | TSC Chair, Active Maintainer | x | |
Deutsche Telekom AG | Active Maintainer | x | |
Ericsson | Active Maintainer | x | |
KDDI | Active Maintainer | x | |
Orange | TSC Deputy Chair, Active Maintainer | x | |
Radisys | EUC Representative | ||
Summit Tech | EUC Representative | ||
Telefonica | Active Maintainer | x | |
Telefónica | Active Maintainer | ||
Verizon | EUC Representative | ||
Vodafone | TSC Deputy Chair | x | |
Vodafone | Active Maintainer | ||
Vonage | Active Maintainer | ||
George Glass | TM Forum | TM Forum Representative | |
TM Forum | TM Forum Representative | x | |
GSMA | GSMA Representative | x | |
GSMA | GSMA Representative | x |
LF Staff:
Community: Ricardo Serrano Gutierrez Tanja de Groot Pierre Close Rafal Artych Lazlo Suto Ramesh Shanmugasundaram Guang-Han Ma Samuel Adeyemo
Agenda
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. |
- 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-06-20 TSC Minutes
- Herbert Damker will check that there are no unintended changes to the minutes (two corrections in participants list done)
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 https://github.com/camaraproject/EasyCLA
- 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
- Herbert prepared a simple Git Repo (EasyCLA) to allow testing https://github.com/camaraproject/EasyCLA
- 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 "ReceiveSMS"
- DeviceStatus have been discussed the adoption of the two new APIs (...). Issue still open for positions.
Commonalities (Rafal Artych )
- Release 0.4.0-rc.1
- Release PR: #240
- The PR will be merged EOB July 10th if no objection (bug fix could be done after).
- Release PR: #240
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 fix could be done after)
- Release PR: #177
Release Management (Tanja de Groot Samuel Adeyemo )
- 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 is June 10th.
- 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
- email to tsc list ready to be sent
- One week for Commonalities ans ICM release PR review comments from today's TSC meeting
- 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).
- We have to be aware of a Marketing event September 16th
- This is the top priority for the projects right now.
- We can inform code owners (via mail list) about the milestones check list
- Do we need to move the M3 as it is very soon?
Any Other Business
- No other comment.
Next Meeting
- Next TSC Meeting will be on July 20th at 16:00 CEST / 14:00 UTC / 07:00 PST
- Specific agenda topics backlog:
- No proposal .... Release preparation make the teams very busy
- Herbert proposed to have a sync with the Marketing team
Action items
- ...