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. 

RepresentativeOrganizationRole

Herbert Damker 

Deutsche Telekom AG

TSC Chair, Active MaintainerX

Shilpa Padgaonkar

Deutsche Telekom AG

Active MaintainerX

Jan Friman 

Ericsson

Active MaintainerX

Toshiyasu Wakayama

KDDI

Active MaintainerX

Ludovic Robert 

Orange

TSC Deputy Chair, Active MaintainerX

Adnan Saleem 

Radisys

EUC Representative

Doug Makishima 

Summit Tech

EUC Representative

Diego González Martínez

Telefonica

Active MaintainerX

Jose Luis Urien

Telefónica

Active MaintainerX

Mahesh Chapalamadugu

Verizon

EUC Representative

Eric Murray 

Vodafone

TSC Deputy ChairX

Kevin Smith 

Vodafone

Active MaintainerX

Chris Howell 

Vonage

Active Maintainer
George Glass

TM Forum

TM Forum RepresentativeX

Olta Vangjeli 

TM Forum

TM Forum RepresentativeX

Henry Calvert 

GSMA

GSMA RepresentativeX

Mark Cornall 

GSMA

GSMA RepresentativeX

Ramit Chawla 

Airtel

Active Maintainer

LF Staff:

Community: Ming Hui Foo Pierre Close Tanja de Groot Laszlo Suto Uwe Rauschenbach Ramesh Shanmugasundaram 

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

Minutes

Review and approval of previous meeting 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
      • No comments/questions
    • Open Action Items from last TSC Minutes copied over and updated within Action Item section below.

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)
  • Discussion in TSC about EasyCLA:
    • Herbert Damker Tendency is to go to DCO but no formal decision from CAMARA Board yet.
    • Mark Cornall  from GSMA recommends DCO has we know how it works already in several projects. 
    • DCO is not unusual as several open source projects moved to this.
  • 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 
      • Ludovic Robert Probably good opportunity to update the Maintainers list for each projet.
      • Herbert Damker This update can be done with PRs on all MAINTAINERS.md file (see Action Items)

API Backlog (Ricardo Serrano Gutierrez )

  • Initial content:
    • Status of migration to https://github.com/camaraproject/APIBacklog
      • 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 (MostFrequentLocation, DeviceVisitLocation, NetworkAccessManagement)?
      • Herbert Damker regarding MostFrequentLocation & DeviceVisitLocation, there was in last TSC the decision to have two repositories, but on call/wiki page. https://lists.camaraproject.org/g/tsc/message/175 is stating that this was a misunderstanding. Proposal: create one Sub Project "LocationInsights" for both APIs as proposed in the message (the Sub Project can later decide if they need to carve out the APIs).
      • Herbert Damker NetworkAccessManagement was waiting for confirmation of the Sub Project name. It this is given, the repository can be created tomorrow.
  • Discussion:
    • No opposition to "LocationInsights"& "NetworkAccessManagement" names from TSC
    • Eric Murray On "IMEI Fraud", Helene from OGW Product team informed. If it will come back with support, it should go into an own repository. Henry Calvert will get into touch with the original API proposal owner.
    • Device Swap work should begin shortly as we have a list of contributors. First task is to update the MAINTAINERS.md file. 

Commonalities (Shilpa Padgaonkar on behalf of 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 https://camara-project.slack.com/archives/C063F56KT38/p1714469868024789.
    • Request to Camara members to review the subscriptions PR
  • Discussion:

Identity & Consent Management (Axel Nennker )

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.
      • This is challenging as we do not have yet PR for some main commonalities point as Test Definition topic.
      • Request to Kevin Smith to create a specific repository for SimpleEdgeDiscovery API from Edge Cloud project.
    • 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 ?
      • Commonalities & ICM are asked to create an alpha-release at least two weeks before the release candidate at M2 milestone.
    • 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 (will be done in Release Management repository)
  • 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:
    • Slides as presented within CAMARA Board Meeting at April 25th for proposal "129":
    • 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
    • for proposal "129":
      • Sandbox project would not require at least 2 contributors... 1 could be fine.
      • Sandbox project could be managed in a separated Git Hub organization (e.g. "camarasandbox") to avoid confusion (to be checked with LF)
      • Incubated project will require at least one production API implementation
      • We will need a table to explain how sandbox & incubated version will be managed
      • Impact on the API readiness checklist, maybe split into two different checklists
    • Comments are welcome on both issues.

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 for May 16th - 20mn - Olta Vangjeli  :
    • 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

Remaining ones from past meeting (updated):

New action items derived from minutes:

  • Create an issue within Governance to update all MAINTAINER.md files and open the respective PRs in repositories Herbert Damker (16 May 2024)
  • Open an issue to create a separate repository for Simple Edge Discovery API Kevin Smith (done, https://github.com/camaraproject/APIBacklog/issues/37)
  • Check with LF how Sandbox project can be separated from Incubated project Herbert Damker (16 May 2024)
  • Create a presentation and tables which show the relation of project lifecycle phases vs API versions, including checklist proposals Herbert Damker (16 May 2024)