Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff:
Community:
Name | Organization | Present |
|---|---|---|
| Fabrizio Moggio (Chair) | TIM | X |
| Robert Ludovic | INNOV/NET | X |
| Fan Yang | China Unicom | X |
| Rafal Artych | T-Mobile | X |
| Productive.ai | 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. |
- Call Forwarding Signal API introduction
- Meetings scheduling and setting up the work
- Requirements gathering
Minutes
- LF Policies
- Agenda approval
- Brief CAMARA introduction, intent based approach and explanation of the Camara Readiness Checklist: Commonalities/documentation/API-Readiness-Checklist.md at main · camaraproject/Commonalities (github.com)
- ( In addition, I would like to give you a reference to the Commonalities WG, where you can find the CAMARA design Guidelines and other useful information. Have a look here: https://github.com/camaraproject/Commonalities/tree/main?tab=readme-ov-file#frequently-accessed-output-documents )
- I would create a document to map the API development status according to the Camara Readiness Checklist
- Discussion on Use Cases: Provide concrete Use Cases · camaraproject/CallForwardingSignal · Discussion #3 (github.com)
- The idea is to add use cases here and discuss about them on specific Discussions. We can open here a new use case as "UseCase-x: use case name" with a description on the use case. Anyone that want to discuss about it can open a new Discussion with "UseCase-x: use case name" in the title. So we have here a clean list of the uses cases.
- Fabrizio will create the first use case, the one already described in the API home page.
- Fang Yang will propose a new Use Case
- The proposed time slot and day for the API Call was agreed, anyway it is not the best for everyone. Maybe a discussion can be open to define a better time slot
- Is the phone number, target of the call FWD, returned as an API output? There was a first discussion on this topic. A Discussion will be open on GithHub
- First discussion on Conditional and Unconditional call FWD support. A Discussion on this will be open on GithHub
- Discussion on User Consent: Consent Management · camaraproject/CallForwardingSignal · Discussion #7 (github.com)
- Robert will check with his legal office
Action Item
- 1-1: create a document to map the API development status according to the Camara Readiness Checklist (fabrizio moggio)
- 1-2: create the first use case based on the one already identified and described in the Api home page (fabrizio moggio )
- 1-3: create a new use case (Fan Yang)
- 1-4: create a Discussion on phone number, target of the call FWD, as output of the API. (fabrizio moggio )
- 1-5: create a Discussion on Conditional and Unconditional call FWD support (Enlai Chu )
- 1-6: check with Legal Office the user consent topic (Ludovic Robert)
Task report
Looking good, no incomplete tasks.
Action items
- 1-1: create a document to map the API development status according to the Camara Readiness Checklist (fabrizio moggio)
- 1-2: create the User Story for the Bank Frauds use case (https://github.com/camaraproject/CallForwardingSignal/discussions/3#discussioncomment-8694420) (fabrizio moggio )
- 1-3: create a new use case (Fan Yang)
- 1-4: create a Discussion on phone number, target of the call FWD, as output of the API. (fabrizio moggio )
- 1-5: create a Discussion on Conditional and Unconditional call FWD support (Enlai Chu)
- 1-6: check with Legal Office the user consent topic (Ludovic Robert