2024-05-14 CFS Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community:

Name



Organization





Present

Name



Organization





Present

Fabrizio Moggio (Chair)

TIM

x

Robert Ludovic

INNOV/NET

x

Fan Yang

China Unicom



Rafal Artych

T-Mobile

x

Enlai Chu

Productive.ai

x

Stefano Falsetto

CK Hutchison

x

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.

  • Last Meeting Report Approval

  • Open Discussions

    • Conditional/Unconditional

  • YAML and Documentation update

  • Release Management

  • Next Steps

  • Action Items



Slides: https://wiki.camaraproject.org/download/attachments/14778665/CAMARA%20Call%20Forwarding%20Signal%202024-05-14.pptx?api=v2

Minutes

  • Last meeting minutes approved

  • Conditional/Unconditional discussion is agreed as closed. Adopting Option 5 the CFS API is not just related to Anti Fraud, it is open also to other UCs.

  • The YAML needs an update on the CallForwardingSignal Resource because Conditional and Unconditional can be both active. Maybe we can use an object with Boolean parameters.

  • Use Case 3 needs some more discussion to verify if some more detail on Conditional FWD types is needed. 

  • Use Case 3 is not yet included in the YAML Documentation because it is still under discussion

  • Next call in two weeks (28th of May)



Task report

The work is progressing as planned.



Action items

2-1: create User Story for UseCase-2 (Fan Yang)
2-3: integration of the Linting tool (@Rafal Artych )

Fix the yaml according to the issue #28 (@fabrizio moggio )
@Rafal Artych  integrates the MegaLinter tool
4-1: Update YAML according to option 5
Update the documentation as well
5-1: Update the CallForwardingSignal Resource (@fabrizio moggio )