2024-05-16 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: @Evan Harrison @Casey Cain 

Community: @Axel Nennker @Pierre Close @Yacine Kheddache @Rafal Artych @Tanja de Groot @G. Murat Karabulut @Lyle Bertz @Yacine Kheddache 
 @Ali Gilani @Ricardo Serrano Gutierrez @Jorge Garcia Hospital 

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

  • Update on Sub Project Lifecycle proposal

  • Update from TM Forum collaboration and how members are working in Catalysts and Operate APIs

• Any Other Topics

Minutes

Review and approval of previous meeting minutes

• Minutes of previous TSC meeting: 2024-05-02 TSC Minutes
  
  

  • No comments -  draft mention removed.

Action Item Review

• For the list of open action items go to home page of Technical Steering Committee) 

  • No comment

Governance & Project Management issues

• EasyCLA vs DCO Update (@Casey Cain)

  • Ready to be sent out independently and ready for board approval. 

• New way to manage Maintainers of Sub project in teams and as members of github.com/camaraproject (@Herbert Damker )

  • Update: Teams created, updates and review of MAINTAINERS.md files will be done one by one (see Governance/issues/134)

• Update of README.md structure in all sub projects

  • Template aligned and updated, update within Sub Projects be done within part of them

  • Update of Wiki pages (which will show the README.md files inline) in work

• Change Working Groups into Sub Projects

  • Almost done, about 9 pull request of APIBacklog need to be get closed within the old WorkingGroups repo

• Provide a user-friendly snapshot for CAMARA users and developers

  • Will be partly covered of Release Management, see API release trackers

API Backlog (@Ricardo Serrano Gutierrez )

• Initial content:

  • New API Proposals (see https://lists.camaraproject.org/g/tsc/message/183)

    • VerifiedCaller

      • This new subproject has been approved and is ready to be created

    • Tenure

      • Separate repo to be created within the KnowYourCustomer use case. 

      • @Toshi Wakayama  wants to verify with the KnowYourCustomer members to see if it is OK to have Tenure API as part of KnowYourCustomer family. If any changes need to be made the team will follow up accordingly.

      • Discussion on the API objectives: "long term" info (this line is 14 years old) vs "short term" check (this line is older than 60 days)

Commonalities (@Rafal Artych )

• Initial content:

  • Release 0.4.0 scope: Comment in Issue #175

  • Dedicated call on 16/05 presented enhancements for Test Definitions Guidelines

    • Request to Camara members to review: https://github.com/camaraproject/Commonalities/pull/203

  • Request to Camara members to review the subscriptions PRs:

    • Create subscription-notification-template.yaml

    • Update API-design-guidelines for subscription

  • Reactivated discussion in Revise the device object definition to simplify it issue

• Discussion:

  • There is an issue of compatibility when using multiple identifiers that needs to be addressed

    • Needs a dedicated meeting involving ICM & Commonalities team. Telefonica team will set up this (@diego.gonzalezmartinez )

Identity & Consent Management (@Axel Nennker )

• Initial content:

  • PR #121 with initial version of "CAMARA Security and Interoperability Profile" is merged.

  • Scope definition for v0.2 available in IdentityAndConsentManagement/issues/146

  • PR #155 CAMARA-API-access-and-user-consent.md alignment with last decisions made in profile

  • Propose Sebastien Dewet as additional codeowner and maintainer

• Discussion:

  • @Sébastien Dewet  from Orange is candidate to be the 'third' codeowner of this project

    • OK from @Herbert Damker from DT & Telefonica approved the PR

Release Management (@Tanja de Groot @Samuel Adeyemo )

• Initial content:

  • Updated API-Readiness-Checklist PR available for review: Add API-Readiness-Checklist.md to RM project (#29)

  • Progress of meta-release plan: Meta-release Fall24 

    • M1 shifted to latest end of May; M2 kept on 15/06

    • Scope issue links have been added to the meta-release plan. Commonalities and ICM may have to prioritize the closing of main functional/technical issues or decide to move to next meta-release in order to reach an alpha release by 05-31. 

  • Release Management issues list nearing completion: see 2024-05-07 Release WG Minutes

• Discussion:

  • No comments

Update on Sub Project Lifecycle proposal (@Herbert Damker )

• Initial content: Herbert reminded the maturity 4-steps cycle then proposed CAMARA API sub project lifecycle: API Proposal → Sandbox API → Incubated API → graduated (to be defined later)

  • See slide deck presented:
    

  • Recommend opening an issue to discuss the following question further:
    
    

    • Question on Sandbox version shift & meta release: should not be correlated?for Incubated API a new version should be in a meta-release? 6 months time could be too long for some sandbox API?

• Discussion

  • To be continued offline (for Sandbox/Incubated and criteria within https://github.com/camaraproject/Governance/issues/129

Update from TMForum collaboration and how members are working in Catalysts and Operate APIs (@Olta Vangjeli ) - 20 mins

• Slides presented by @Olta Vangjeli:
  

• Bilateral direction to build common UC & collaborate

  • CAMARA → TMF: We have the user stories in API that can provide "food for thought" for larger UC

  • TMF → Outputs from TMF autonomous network work could be a source to new CAMARA apis (or improvement of existing API)

• Let's continue the discussion...

Any Other Business

• No other topic.

Next Meeting

• Next TSC Meeting will be on June 6th at 10:00 CEST / 08:00 UTC / 01:00 PST

Action items