2024-04-04 TSC Minutes

Owned by Herbert Damker
Last updated: Apr 19, 2024Version comment
6 min read

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. 

Representative

Organization

Role

 

Representative

Organization

Role

 

@Herbert Damker 

Deutsche Telekom AG

TSC Chair, Active Maintainer

x

@Shilpa Padgaonkar

Deutsche Telekom AG

Active Maintainer

 

@Jan Friman 

Ericsson

Active Maintainer

x

@Toshi Wakayama

KDDI

Active Maintainer

x

@Ludovic Robert 

Orange

TSC Deputy Chair, Active Maintainer

x

@Adnan Saleem 

Radisys

EUC Representative

 

@Doug Makishima 

Summit Tech

EUC Representative

x

@diego.gonzalezmartinez

Telefonica

Active Maintainer

x

@Jose Luis Urien Pinedo

Telefónica

Active Maintainer

x

@Mahesh Chapalamadugu

Verizon

EUC Representative

 

@Eric Murray 

Vodafone

TSC Deputy Chair

x

@Kevin Smith 

Vodafone

Active Maintainer

x

@Chris Howell 

Vonage

Active Maintainer

 

George Glass

TM Forum

TM Forum Representative

 

@Olta Vangjeli 

TM Forum

TM Forum Representative

 

@Henry Calvert 

GSMA

GSMA Representative 

 

@Mark Cornall 

GSMA

GSMA Representative

 

LF Staff: 

Community: @Tanja de Groot @Rafal Artych Cevdet Emre Yilmaz, @Uwe Rauschenbach @Ming Hui Foo Musa Gacemer @Ramit Chawla@Ricardo Serrano Gutierrez @Yacine Kheddache @Pierre Close 

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

  • Specific Topics

    • No life sign projects - how to handle these?

    • (if time left) Add structure to sub project and working group information

  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

CAMARA Project Updates ( @Casey Cain  & all)

  • Project meetings

    • Due to Daylight Savings Time, meetings will likely need to be updated.  Ping @Casey Cain & @Evan Harrison on Slack with your move requests and they will be processed this Friday.

    • If you have not yet moved to Zoom, please let @Casey Cain & @Evan Harrison when you are ready so we can move.

      • All project meetings that were listed in project repositories have been created.  We are just waiting on projects to reach out to @Evan Harrison & @Casey Cain  to migrate to the new zoom meetings.

    • Make sure that you are encouraging everyone to have a LF ID.  We are noticing that a lot of people are joining the project calls that do not have an LF ID.  This will ensure that they can find meeting invites and recordings on LFID Profile at https://openprofile.dev 

  • Status of EasyCLA introduction (@Casey Cain )

    • From previous minutes: Activation for CLA is delayed for right now until GSMA is resolved, Casey took action to send mail to Mark Cornall

      • GSMA Follow-up taking place on Apr 12, 2024 

  • Open Office Hours  (@Casey Cain to provide next slots)

    • Open Office Hours was delayed due to Casey & Evan both being ill.  New invites for the Open Office Hours has been sent

Change Working Groups into Sub Projects (https://github.com/camaraproject/Governance/issues/84)(@Herbert Damker )

  • Proposal (as in https://github.com/camaraproject/Governance/issues/84):

    • Create separate repositories for all Working Groups (Commonalities and Release Management already available, API Backlog and Marketing todo)

    • The new repositories follow the same procedures as the repositories for Sub Projects. That means it will have maintainers and code owners, but no WG_participant.md files

    • To distinguish repos for Working Groups from repos for API Sub Projects we use a new badge "Working Group"

    • Existing content will be added into the new repositories, issues will be transferred 

    • The existing "Working Groups" repository is set to read only after the content is transferred and then archived after 1 month

  • How to define the initial set of Maintainers and Codeowners for the API Backlog repository?

    • API Backlog:

      • Proposal: candidates for Maintainer in API Backlog group are all current participants who have attended >=4 of the last 6 meetings (9 candidates, representing ATT, CableLabs, Charter Communication, Ericsson, GSMA, Nokia, Telefonica (2), Vodafone). Further 6 candidates if >=3 of last 6 meetings or >=5 of of last 9 meetings (Deutsche Telekom, Huawei, Orange, Schabodi, Telefonica, Vodafone). The candidates would need to commit to the Maintainer role to get Maintainer.

      • Codeowner will be defined by the Maintainer group

    • Maintainers and code owners of Marketing Working Group will be defined by the existing working group respective the Outreach Committee members nominated by Board members

  • Approved by the TSC

Release Management (@Samuel Adeyemo @Tanja de Groot )

Identity & Consent Management ( @Axel Nennker )

  • Not much feedback from TSC members on our request to comment on "purpose" and whether multiple purposes are a business requirement

    • Request for action to all: Please add your company's position

  • Working on the last remaining open topics before merging our Interoperability and security document. Thanks to TEF for summing up the open points.

    • Most difficult remaining point is how to represent "purpose" (see previous point). If there is no consensus within the next meeting, the only option might be to have no statement about it in the first version of the profile (= deleting the current proposal of adding an explicit parameter from the PR). 

  • Steady participation, we are making progress

Commonalities (@Rafal Artych )

API Backlog (@Ricardo Serrano Gutierrez )

  • There was not enough time left for the API Backlog items, especially the proposals from https://lists.camaraproject.org/g/tsc/message/149, they are postponed to next TSC meeting

  • CPE Management:

  • @Ricardo Serrano Gutierrez mentioned that there potentially will come a lot of new proposals with GSMA Product team "Drop 4" and we need to discuss how to handle that.

  • @Herbert Damker reminded of the name of the working group "API Backlog", which means that proposals can also stay there until the project has enough bandwidth to manage the work on the proposals. Criteria need to be defined about which proposals will be put into "work in progress" (= will be developed and afterwards managed in a sub project).

No life sign projects - how to handle these? (@Herbert Damker @Ludovic Robert )

  • Following points were only shortly mentioned my @Ludovic Robert , but not discussed (=> backlog item) 

    • We have currently two project without (visible) work within the repositories

      • Device Swap (repository created but no activity over the last 6 months)

      • IMEI Fraud (Attached to device identifier repository but no activity there on this API)

    • Are these APIs still relevant?

      • If, yes, how to find volunteers who will work on them?

      • If no volunteers: Postpone these APIs to a later time?

Add structure to project and working group information (@Casey Cain )

  • Postponed to a later TSC due to lack of time.

Any Other Topic

  • none

Next Meeting

  • Next TSC Meeting will be on April 18th, 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?

    • No life sign projects - how to handle these? (@Ludovic Robert )

    • Add structure to project and working group information (@Casey Cain )

Action items