2024-01-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:

Community: Herbert Damker 

Agenda

• Roll Call
• Action Items Review
• Agenda Bashing
• General Topics
  
  • API Backlog
  • Commonalities
  • Identity & Consent Management
  • Release Management
• Any Other Topics
  • Topics for Governing Board of CAMARA Fund?

Minutes

Action Item Review

API Backlog

• API proposal "Device Location Retrival" - see message https://lists.camaraproject.org/g/tsc/message/105
  • Initial version of the YAML already available within the sub project "Device Location"
  • Hence just a formal approval required
• API proposal "Network Slicing" - see message https://lists.camaraproject.org/g/tsc/message/104
  • Application proposal: APIproposal_NetworkSlicing_ChinaUnicom.md
    • Discussion within related issue: https://github.com/camaraproject/WorkingGroups/issues/317
    • Supporting presentation in PPT
    • Endorsed by API Backlog WG Jan 11th, see meeting minutes

Commonalities

• Initial input info by Shilpa
• Target date for release 0.3.0 is to be ready for approval on 05.02.2024
• Linting ruleset and guidelines PRs are currently under review. We need to close this review soon.
• API Testing guideline doc has 1 open point left. After this discussion is resolved, PR can be merged.
• Security-scheme and scope update in design guidelines document and reference to document in ICM are also currently in review. 
• Other release 0.3.0 specific PRs are minor documentation changes.

Identity & Consent Management

• Initial input info by Diego
• Agreements regarding releases:
  • V0.1 to be generated. All issues marked as required for the release are solved
  • V0.2 to be progressed as fast as possible. Scope: clarifications on existing scope requested by existing issues
  • V0.3 will include enhancements
• OIDC profile:
  • To be created in CAMARA. Not to rely on starting it in OIDF working group to avoid risk of delay. TEF has offered to provide initial draft covering CAMARA scope and needs; MobileConnect existing profile to be used as valid reference. DT also offered to be active here and provide a contribution.
• Duplicity of information GSMA-CAMARA
  • AuthN/AuthZ flows will be in CAMARA. Existing ones to be evolved as needed. 
  • Issue to be opened in GSMA so duplicated info there is replaced with a reference to CAMARA. GSMA to still have needed information regarding interconnection and routing, referencing to CAMARA when needed

Release Management

• Initial input info by Herbert
• There are two important streams regarding release management:
  • Setup of a release process and schedule for a CAMARA wide "meta release"
  • Addressing the issues within Consolidation Issue for open points release management · Issue #9 · camaraproject/ReleaseManagement (github.com) which are giving guidance to sub project regarding release and versioning topics
  • The latter work will change documents which are under responsibility of Commonalities => how to address it best?
• CAMARA wide "meta release"
  • The coordination of a snapshot across all CAMARA sub projects, including the coordination of dependencies (e.g. to Commonalities)
  • Requires at least two Release Managers for CAMARA
    • Tanja Groot that Nokia is willing to nominate Samuel Adeyemo to act as Release Manager
    • Request for further nominations will be addressed to the Governing Board
  • Release managers report to TSC about release progress
• The training material from LF about Release Management is available here: https://wiki.camaraproject.org/x/QAEG

Any other topic

• Topics for Governing Board of CAMARA Fund on Jan 25th?

Action items