2024-05-02 TSC Minutes

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. 

LF Staff:

Community:

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
  • Sub Project Lifecycle proposals
• Any Other Topics

Minutes

Review and approval of previous meeting minutes

• Minutes of previous TSC meeting: 2024-04-18 TSC Minutes
  
  • ...

Action Item Review

• (For the list of open action items go to home page of Technical Steering Committee) - Action Items are currently not working?
  • Alternatively we can look on  2024-04-18 TSC Minutes or copy them over to here

Governance & Project Management issues

• CAMARA Board Meeting on April 25th - short debrief (Herbert Damker )
  • No questions or feedback about API backlog, Commonalities, Identity & Consent Management
  • Release Management - Herbert mentioned need for additional Community Release Manager(s)
  • API Sub Project Lifecycle - shortly introduced issues #122 and #129 - the Board general expressed support for the lifecycle stages 
  • EasyCLA vs Developer Certificate of Origin (DCO) - options presented and discussed, Board asked for time until next meeting
    
    • In consequence EasyCLA deactivated also on QualityOnDemand repository (was activated for test purposes)
  • ...
• New way to manage Maintainers of Sub project in teams and as members of github.com/camaraproject
  • Aim is to improve the management of access rights regarding effort and reliability
  • Proposed way, tested for QualityOnDemand  
    
    • Maintainers of all Sub Projects will be invited as members to the CAMARA GitHub organization
    • For each Sub Project there will be a GitHub team
      • can be mentioned in GitHub as @camaraproject/<respository-name>_maintainers
      • can be added as reviewers to PRs within the Sub Project
      • will have "triage" access within the Sub Project (only code owners have "write" access)
    • The parent of all these teams is @camaraproject/maintainers
    • Further changes to support the above:
      • The CAMARA admin team will get owner of all MAINTAINERS.md and CODEOWNERS files
      • A change of these will be approved and merged if the majority of the existing Maintainers in a Sub Project have approved the change request (exceptions for new Sub Projects)
      • The MAINTAINERS.md files will get a new column "GitHub Name"
  • Discussion 
    • ...

API Backlog (Ricardo Serrano Gutierrez )

• Initial content:
  • Status of migration:
    
    • Active Issues have been migrated
    • Old PRs will remain in the old repo and Ricardo will move them to the new one once approved and merged
    • New PRs and Issues must be opened in the new repo (GSMA is aware of this)
  • APIs in Pipeline
    
    • No APIs for approval this time 
  • Update API-onboarding.md Governance PR#130 Will review the file and provide a new version with the upcoming updates
  • API Backlog new table format  APIBacklog issue#4 Ricardo is working on this
  • Status of the setup of approved APIs (Most Frequent Location, DeviceVisitLocation, NetworkAccessManagement)??
• Discussion:
  • ...

Commonalities (Rafal Artych )

• Initial content:
  • In the commonalities call on 29.04 2024-04-29 Commonalities WG Minutes, the scope of 0.4.0 has been finalized and includes the below topics
    • Error responses
    • Enhancement of Test Definitions
    • Subscriptions
    • Linting ruleset update
    • Wildcard scopes
    • Few other smaller issues
  • Some issues have been labelled as backlog to keep them out of scope of 0.4.0
  • Request to Camara members to actively participate in the call being arranged by TEF to discuss test definition enhancement. Slots have been added to Slack comms-wg channel.
  • Request to Camara members to review the subscriptions PR
• Discussion:

Identity & Consent Management (Axel Nennker )

• Initial content:
  • PR121 https://github.com/camaraproject/IdentityAndConsentManagement/pull/121 merge is currently pending due to the purpose issue discussion. WG-Members are currently planning to setup an adhoc call to discuss this in detail on the possible solutions/options available. Axel Nennker  is on vacation until 01.05. He will reach out to setup a slot after he is back.
• Discussion:

Release Management (Tanja de Groot Samuel Adeyemo )

• Initial content:
  • M0: was approved on 2024-04-18, but announcement still needs to be sent. Check draft M0 announcement here: Release Management announcements - sending of the M0 announcement is dependent on the finalization of the API release tracker page.
  • M1: Proposal to shift by 2 weeks to 2024-05-15, but this is maybe not sufficient as holidays in many countries. Means one month delay wrt standard schedule.
  • M2 will likely also shift by 2 weeks
  • M3: shifts with the M1 date
  • Other milestones: no change
  • API Sub-projects should start to prepare the release assets for their APIs for release and align with Commonalities and ICM AS OF TODAY. When can an alpha release for Commonalities & ICM be created ?
  • In the general meta-release schedules: moved M2 one week earlier and M3 one week later.
  • Process definition status:
    • Updates the milestone table with new format and clarified actions - near final
    • Update of process descriptions near final;
    • API readiness checklist to be finalized.
• Discussion:

Sub Project Lifecycle proposals (Herbert Damker )

• Initial content:
  • To keep the number and variety of Sub Project within CAMARA manageable we have two proposals currently:
    • Raise the barrier for new API Sub Projects to limit the number of Sub Projects and ensure their sustainability from the beginning, as proposed within issue #122 New working flow - API Approval
    • Introduce different lifecycle phases for API Sub Project with a lightweight managed "Sandbox" phase before an API will get fully "Incubated" into CAMARA, as proposed in #129 Proposal for new API Project lifecycle approach (Sandbox + Incubated)
  • Slides as presented within CAMARA Board Meeting at April 25th:
    
  • Feedback on the lifecycle phases within the Board was positive. There was a comment that the proposals are no either/or, that the criterium from #122 can be used at one of the gates of #129 (e.g. from Sandbox to Incubated) 
• Discussion
  • ...

Any Other Business

• Shilpa Padgaonkar  Keeping in lines with commonalities WG, would be good to have one more Codeowner for ICM WG (we currently have 1 codeowner from TEF and 1 from DT). 

Next Meeting

• Next TSC Meeting will be on May 16th at 16:00 CEST / 14:00 UTC / 07:00 PST
• Specific agenda topics backlog:
  • Update from TMForum collaboration and how members are working in Catalysts and Operate APIs (Olta Vangjeli )
    • Catalyst and Operate APIs update
    • Can we have more usecases proposed how TMForum APIs and Camara communicate in e2e journeys
  • ...

Action items