2024-10-17 TSC Minutes

DRAFT AGENDA

Attendees & Representation

TSC Members attendance to be indicated in the table with an X in the far column.

Representative

Organization

Role

ย 

@Herbert Damkerย 

Deutsche Telekom AG

TSC Chair, Active Maintainer

ย 

@Shilpa Padgaonkar

Deutsche Telekom AG

Active Maintainer

ย 

@Jan Frimanย 

Ericsson

Active Maintainer

ย 

@Toshi Wakayama

KDDI

Active Maintainer

ย 

@Ludovic Robertย 

Orange

TSC Deputy Chair, Active Maintainer

ย 

@Adnan Saleemย 

Radisys

EUC Representative

ย 

@Doug Makishimaย 

Summit Tech

EUC Representative

ย 

@diego.gonzalezmartinez

Telefonica

Active Maintainer

ย 

@Jose Luis Urien Pinedo

Telefรณnica

Active Maintainer

ย 

@Mahesh Chapalamadugu

Verizon

EUC Representative

ย 

@Eric Murrayย 

Vodafone

TSC Deputy Chair

ย 

@Kevin Smithย 

Vodafone

Active Maintainer

ย 

@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

ย 

Community members may use @name tag to mark their attendance.

Community:

LF Staff:

Communities:

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

    • โ€ฆ

  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

Governance & Project Management issues

API Backlog (@Jorge Garcia Hospital @patricia.serranogonzalez@telefonica.com )

  • Repository for CustomerInsights created (was approved as โ€œTelcoIndexโ€ in TSC 2024-09-19)

  • โ€ฆ

Commonalities (@Rafal Artych @Pedro Dรญez Garcรญa )

  • Content from last meeting notes:

    • An issue for the scope version 0.5.0 : Commonalities/issues/273

      • All issues from the scope are marked with Spring25 label

      • Critical issues are additionally marked with priority label

      • Clean up and redesign of API Design Guidelines Commonalities/issues/306 - to be done after implementing changes in the guidelines

    • Maintenance release (0.4.1) needed to resolve # 301 Broken link to dpv document

      • Issue with commonalities version specified in all yaml (still 0.4.0). We are reluctant to update all the yaml as it not really needed.

      • We need to solve this problem for future. For example in the yaml we can indicate only the commonalities release major number (without the minor) like r1.

Identity & Consent Management (@Axel Nennker )

  • โ€ฆ

Release Management (@Tanja de Groot @Samuel Adeyemo )

  • Content from last meeting notes

    • Spring25 M0: the meta-release kick-off can be done in todayโ€™s TSC meeting. An email to all mailing list will be sent to inform the community. The meta-release plan is available here: Meta-release Spring25.

      • M0 is declared by the TSC Oct 3, 2024

    • Spring25 M1: Due to delays in the Fall24 meta-release, the M1 date is slightly impacted and shifted from Oct 15th to Oct 31st.

      • Exceptionally, the M1 will not yet have an alpha release available for Commonalities and ICM, but the relevant set of PRs covering the scope of the upcoming release shall be made available for Sub Project team review as follows:

        • PRs for critical issues must be created by Oct 15th (not necessarily merged)

        • PRs for other issues must be created by Oct 31st (not necessarily merged)

        • Alpha releases will be created as fast as possible after that and an M1 update announcement shall be sent at that point.

    • Info for Sub Projects: the API release tracker content for Spring25 is being updated, so please DO NOT create new API release trackers for Spring25 yet. Fall24 API release trackers SHALL NOT be copied. The new version will be available shortly.

    • Fall24 M6: The date is slightly delayed. Feedback is being integrated in the process and artefacts. This has no impact on the Spring25 content progress and should be finished latest by Oct 31st.

Specific Topic

  • None yet

Any Other Business

  • โ€ฆ

Next Meeting

  • Next TSC Meeting will be on November 17th, depending on above decision either

    • 08:00 UTC (09:00 CET / 00:00 PT) or

    • 09:00 UTC (10:00 CET / 01:00 PT)?

  • Specific agenda topics backlog:

    • GSMA OPAG โ€œNBI realisation guidelinesโ€ (Christina Santana Casillas, OPAG Chair)

Action items