2023-11-02 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:

• Pierre Close (AT&T)

• Ming Hui Foo (Singtel)

• Tanja de Groot (Nokia)

• Uwe Rauschenbach (Nokia)

• Parichaya Shrivastava (Spry Fox Networks)

• Rafal Artych (Deutsche Telekom AG)

• Ramesh Shanmugasundaram (Spry Fox Networks)

Agenda Proposal

• Antitrust Policy

• Introduction

  • Roll Call

  • (Action Items Review)

  • Agenda Bashing

  • Meeting Minutes in Wiki - tbd

• Release Management (#82)
  
  

  • API Families & APIs (discussion paper)

  • Release management trainings

• Commonalities & ICM
  
  

  • Updates?

• API Backlog

  • Update and decision on SiteToCloud proposal

• (Further) open issues in https://github.com/camaraproject/Governance/issues

• AOB

Antitrust Policy

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.

Open

Minutes

Recording of this meeting can be found here.

Note: Meeting recordings can always be found by everyone at https://openprofile.dev/my-calendar and then clicking on the "Past Meetings" tab.

Action Item Review

Meeting Minutes within Wiki instead of Github

• Meeting agreed that meeting minutes would only be recorded in the wiki

Release Management

• Linux Foundation release management support service
  
  

  • Those interested in this training should subscribe via release+subscribe@lists.camaraproject.org to the release management mailing list.

  • David McBride will use the mailing list to agree dates for training session (3x 50 minutes)

• A new working group repository will be created to define the Release Management process for CAMARA

  • Once the process is defined, it can be considered to transfer responsibility to the Commonalities sub-project

  • ACTION: Create a repository for "Release Management" @Herbert Damker 

• Discussion paper "API Families & APIs" (Herbert Damker)
  

  • Proposal is that sub-projects be grouped into API families, which manage meetings, minutes, mailing lists and co-ordinate dependencies between related APIs 

  • In response to questions, Herbert clarified that:

    • The concept of "API families" is already included within the CAMARA project charter

    • The proposals for API families would not affect current release management as no API yet has a release. 

  • Kevin Smith suggested to consider using github lists as a way of grouping sub-projects into families

  • ACTION: Herbert to create an issue to discuss the concept of API families further

Commonalities & ICM

• Jan Friman commented that the relationship between the TSC and the Commonalities and Identity & Consent sub-projects was not clear, particularly on how these different groups should inter-work

  • ACTION: Jan to raise an issue in Governance requesting clarification (now complete, see here)

API Backlog

• Update and decision on SiteToCloud proposal

  • Eric Murray provided an update, noting that:

    • Some discussions on the API scope had taken place, but the proposal to the Backlog WG remained unchanged

    • No specific objections to the API scope had been raised

    • Although the scope was similar (if not identical) to that of TMF 759, this is no obstacle to creating a CAMARA sub-project to develop the proposal as the intended API users are different with different levels of expertise and domain knowledge

  • DECISION: It was agreed that the Site To Cloud API proposal could proceed, with further discussion on the scope taking place within the new sub-project

• Improvements of onboarding process

  • New API proposals will be available in the Backlog WG repository for at least 1 week before the TSC meeting where they will be discussed. TSC members are expected to familiarise themselves with each proposal before the TSC meeting.

  • Companies participating in the OGW Product Workstream are expected to submit their API proposals via that process. If submitted directly to the CAMARA Backlog WG, it can be expected that they will remain in backlog for a longer period for clarification.

(Further) open issues

• https://github.com/camaraproject/Governance/issues

AOB

Action items