Agenda

Antitrust Policy

• Review of previous meeting minutes
• Action Items Review
• Topics common to APIs
• KYC Match/ Fill-in API
• Age Verification API
• Tenure API
• Number Recycling API -not yet
• Subscription Status API -not yet
• AOB

→ The agenda was approved.

Review of previous meeting minutes

 MOM of 2024-08-20

• PR #145 (Created on 2024-08-25)
  • Can be approved and merged? 
  • → [2024-09-03] No comments and approved.  PR #145 is to be merged right after the meeting.   

Agenda document of 2024-08-20

• PR #144 (Created on 2024-08-25)
  • Approved and merged.

Action Items Review

Minutes

Topic common to APIs: Fall24 Meta-release

New (after the previous meeting)

• Remove countryMatchScore property (PR #137)
  • Fernando TEF created for the issue: "KYC Match : CountryMatchScore makes no sense" (Issue #134)
  • Approved and merged on 2024-08-20
  • → [2024-09-03] This PR was reviewed, because it was opened after the previous meeting and approved/merged before this meeting.  There was no additional comments.
• Update endpoint description to reflect all use cases (PR #138)
  • Fernando TEF created for the issue: "[KYC Match] Which fields are meant to be used for identification of the mobile phone user?" (Issue #135)
  • Approved and merged on 2024-08-20
  • → [2024-09-03] This PR was reviewed, because it was opened after the previous meeting and approved/merged before this meeting.  There was no additional comments.
  • → Clara TEF asked about Issue #135, and Fernando TEF explained.
• "Include test plan for kyc-match operation" (Issue #139) and "Include test plan for kyc-match operation" (PR #140) 
  • PR #140 is under discussion but needs to be merged ASAP (before the release PR #143 is merged).
  • → [2024-09-03] Toshi KDDI shared the Fall24 Meta-release schedule and his observation of the status: 
    • Each API subproject was expected to open its Release PR by 2024-08-26, so that the Release Management team could review all Release PRs by 2024-08-30.

    • However, it seems Release Management teams' review is going slow.  TSG meeting on Thursday 2024-09-05 will make a decision to go ahead for Meta-release (merging all Release PRs).  Not quite sure if Release Management team's review will complete by then.

    • In parallel, each API subproject needs to make all required pieces for its API public release by its Release PR being merged.

    • For KYC SP (Match/Fill-in), remaining pieces are Match test plan and Fill-in test plan, i.e. PR #140 and PR #142 respectively.  So, these two PRs need to be approved ASAP (by Release PR being merged).

  • → For PR #140, Toshi KDDI asked two questions by GitHub comment just before this meeting.  Fernando TEF answered the questions verbally.
  • → As there was no additional comment / question, it was understood that this PR #140 can be merged.
• "Include test plan for kyc-fill-in operation" (Issue #141) and "Include test plan for kyc-fill-in operation" (PR #142) 
  • PR #142 is under discussion but needs to be merged ASAP (before the release PR #143 is merged).
  • → [2024-09-03] For PR #142, as there was no additional comment / question, it was understood that this PR #142 can be merged.
• Release PR: Public Release for Fall24 meta-release (PR #143)
  • Fernando TEF created on 2024-08-24
  • Gilles Orange and Toshi KDDI, codeowners, have approved.
  • Waiting for Release-management maintainers' review
  • → [2024-09-03] Once PR #140 and PR #142 have been merged, only thing we can do would be to wait for Release Management team's review.

Ongoing

• Select API for CAMARA Meta-Release September (Issue #75)
  • Targed confirmed:
    • KYC Match v0.2 (v0.1 initial + v0.2 add scoring)
    • KYC Fill-in v0.1 (intial)
    • Age Verification v0.1 (intial) → de-prioritized and not included in Fall24
    • Release: Initial public release
  • LInks
    • Fall24 Meta-release: Meta-release Fall24
    • Releae process: Meta-release Process 
    • API Release Tracker: Match, Fill-in
  • Release-Management Issues:
    • KnowYourCustomer r1.1 release review (RM Issue #68)
    • KnowYourCustomer r1.2 release review (M4) (RM Issue #85)

Topic common to APIs

Ongoing

• Do Tenure API, NumberRecycling API and Shutdown Service Status API fit in KYC Family /KYC SP meeting? (Issue #109)
  • Discussion concluded as commented in Issue #109.
  • For Number Recycling, Initial codeowners and maintainers lists are being confirmed.
  • Shutdown Service Status API has been renamed to Subscription Status API.  Approved by TSC, and its repository has been created.
  • For Shutdown Service Status, Initial codeowners and maintainers lists are being confirmed.
• EasyCLA
  • Casey LF sent an email announcing EasyCLA has been enabled in all repositories, on 2024-08-31.  
  • Checks on all code mergers will verify if Contributors have a signed CLA agreement in place.  If you have any questions, please review our Getting Started guide <https://docs.linuxfoundation.org/v2/easycla/getting-started>  before submitting a ticket to https://support.linuxfoundation.org.

KYC Match/ Fill-in APIs

New

• Which phoneNumber information shell be used for KYC-match [southbound-call] (Disc #146)

  • Raised by Maximilian DT
  • → [2024-09-03] Huub KPN suggested to check Commonalities discussion on API MisUse (Issue #259).  It is related to this comment (Disc #146).
• Will restart Issues/PRs discussion after Fall-24 meta

Ongoing

• There are a lot of Issues, which need to be cleaned.

Age Verificaiton API

New

• Will restart Issues/PRs discussion

Ongoing

• Creation of a Pull Request for Age Verification API (Issue #46)
• Initial contribution of Age_Verification.yaml (PR #50)
• Add Age Verification to KnowYourCustomer SP’s Scope in README (Issue #81)

Tenure API Repo

New

• → [2024-09-03] Skipped discussion today.  Luis Lopez Vodafone explained that he is still waiting for feedbacks from Tenure maintainers.

Ongoing

• Comments

Done

• Comments

Number Recycling API  Repo

New

• None

Ongoing

• Initial codeowners and maintainers lists are being confirmed.

Done

• None

Subscription Statu API Repo

New

• None

Ongoing

• Initial codeowners and maintainers lists are being confirmed.

Done

• None

AOB

Next meetings:

• Next meeting #23: 2024-09-17 Tue, 0900-1000 CEST
• Future meetings:
  • #24 2024-10-01 Tue
  • #25 2024-10-15 Tue
  • #26 2024-10-29 Tue

Action items